<div class="gmail_quote">On Mon, Mar 1, 2010 at 2:25 PM, MarkMT <span dir="ltr"><<a href="mailto:nginx-forum@nginx.us">nginx-forum@nginx.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I tried renaming the file and restarting - no access.log file was created on subsequent accesses.<br>
<br>
Other thoughts?<br></blockquote><div><br></div><div>On linux, lsof -c nginx (as root) should tell you if nginx has the logfiles opened.</div><div>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).</div>
<div>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.</div><div><br></div><div>Hope this helps!</div><div><br></div></div>