Empty error and access log

Maxim Dounin mdounin at mdounin.ru
Thu Sep 26 15:09:45 UTC 2019


On Thu, Sep 26, 2019 at 09:13:20AM -0400, rick_pri wrote:

> We recently noticed this on our servers and we were using USR1 for
> postrotation which wasn't working as expected.  We changed the post rotation
> command to be HUP and this fixed the issues of rotation being borked.
> http://nginx.org/en/docs/control.html
> It says that USR1 should reopen logfiles after they have been renamed but we
> found that this didn't work

The USR1 is the right way to ask nginx to reopen log files, and it 
is enough for log rotation.  While using HUP is also possible, it 
does full configuration reload, and using it for log rotation is 
wrong - for example, this may result in accidental use of a 
configuration being edited.

If USR1 does not work for you, most likely it is because log files 
after log rotation cannot be opened for writing by worker 
processes.  Fix is to assing correct access rights to the new 
files created during log rotation, and also make sure nginx worker 
process are able to access the directory with the log files.

Maxim Dounin

More information about the nginx mailing list