not fine

#49
by intlex - opened
The user specifies that the config is fully functional and correct. The "surprise" is related to a specific option that resulted in 5 GB of something (most likely logs).

Let's re-examine the config from this perspective. What could possibly generate 5 GB?

   access_log off — access logs are disabled on server 443. So, it's not the access logs.
   error_log off — also disabled at the server level.
   limit_req_log_level error — now this is interesting! By default, limit_req_log_level is set to error. This means that every time a limit_req (429) is triggered, an entry is written to the error_log.

But wait, error_log off is set at the server level. Does that mean the error_log isn't being written? Not exactly — error_log off within the server context doesn't disable error logging globally, only at that specific level. In fact, in Nginx, error_log off in a server block means that for this particular server, the error_log is not written. But limit_req_log_level error will still write to the error_log... Hmm, no, error_log off in the server block indeed disables error_log writing for this server.

Sign up or log in to comment