Access logging has stopped

Server NGINX
1

Entries in the access.log for my nginx server mysteriously stopped on
Feb 16. I haven’t made any change to the configuration files. Any
suggestions of where I should be looking to figure out why it has
stopped logging incoming requests?

Posted at Nginx Forum:

2

Maybe it grows and fill up your partition? I faced this problem with
other application.

Danny Trinh
Linux Admin

3

Thanks for the suggestion. However I don’t think that’s it, as the
error.log in the same directory is still being written and the
filesystem is only 53% full.

Posted at Nginx Forum:

4

On Mon, Mar 1, 2010 at 3:31 AM, MarkMT [email protected] wrote:

Thanks for the suggestion. However I don’t think that’s it, as the
error.log in the same directory is still being written and the filesystem is
only 53% full.

Maybe it just grew too big for your filesystem? what if you restart
nginx?
what if you rename it and then restart nginx?

5

I tried renaming the file and restarting - no access.log file was
created on subsequent accesses.

Other thoughts?

Posted at Nginx Forum:

6

On Mon, Mar 1, 2010 at 2:25 PM, MarkMT [email protected] wrote:

I tried renaming the file and restarting - no access.log file was created
on subsequent accesses.

Other thoughts?

On linux, lsof -c nginx (as root) should tell you if nginx has the
logfiles
opened.
Also, “strace” may help in understanding whether it’s a file permission
problem (actually I believe it isn’t, nginx should not start if it can’t
write to its logfiles).
Also, you may have some stale processes, so stop nginx, and then check
via
ps aux if you have any left… if you do kill them via killall nginx.

Hope this helps!

7

Thanks! It turned out to be stale processes. I removed them and logging
has now resumed. Much appreciate your help.

Mark.

Posted at Nginx Forum: