Re: Empty error and access log

2019-09-27 Thread Francis Daly
On Fri, Sep 27, 2019 at 01:36:55AM -0400, krishna wrote: Hi there, I do not have the answer for you. But... > Figured out that, nginx.pid file doesn't have the correct PID value(it > contains 1) - which could be valid since nginx is running inside docker > container and we are setting up the lo

Re: Empty error and access log

2019-09-26 Thread Francis Daly
On Thu, Sep 26, 2019 at 06:13:55PM +0300, Maxim Dounin wrote: > On Thu, Sep 26, 2019 at 06:22:41AM -0400, krishna wrote: Hi there, > > -rwxr-xr-x. 1 root root 0 Sep 25 03:13 access.log > > -rwxr-xr-x. 1 root root 0 Sep 26 03:34 error.log > > These files are only writable by root, hence nginx wor

Re: Empty error and access log

2019-09-26 Thread krishna
Hello All, Thanks for the updates. Figured out that, nginx.pid file doesn't have the correct PID value(it contains 1) - which could be valid since nginx is running inside docker container and we are setting up the log rotation from the host machine where the log files getting rotated but new fil

Re: Empty error and access log

2019-09-26 Thread Maxim Dounin
Hello! On Thu, Sep 26, 2019 at 06:22:41AM -0400, krishna wrote: > Dear Team, > > I have configured access_log and error_log at https block level and > sometimes(like after log rotation), could see the logs are with 0 bytes > (which means, nothing logged though it serves the requests and applicat

Re: Empty error and access log

2019-09-26 Thread Maxim Dounin
Hello! 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://

Re: Empty error and access log

2019-09-26 Thread Francis Daly
On Thu, Sep 26, 2019 at 07:25:45AM -0400, krishna wrote: Hi there, > logrotate has been used to archive the nginx log files on daily basis from > the machine and below is the configuration. > postrotate > /usr/bin/kill -USR1 `cat /var/pid/nginx.pid 2>/dev/null` 2>/dev/null || > true #PID file

Re: Empty error and access log

2019-09-26 Thread rick_pri
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

Re: Empty error and access log

2019-09-26 Thread krishna
Hi Francis, Thanks for the reply. logrotate has been used to archive the nginx log files on daily basis from the machine and below is the configuration. Once it has been executed, the files would get zipped in gzip format and new files would get created (as killing the nginx PID, further the ngi

Re: Empty error and access log

2019-09-26 Thread Francis Daly
On Thu, Sep 26, 2019 at 06:22:41AM -0400, krishna wrote: Hi there, > I have configured access_log and error_log at https block level and > sometimes(like after log rotation), could see the logs are with 0 bytes > (which means, nothing logged though it serves the requests and application > is acce

Re: Empty error and access log

2019-09-26 Thread krishna
Workaround: restarting nginx helps and logs getting generated. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,285708,285709#msg-285709 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Empty error and access log

2019-09-26 Thread krishna
Dear Team, I have configured access_log and error_log at https block level and sometimes(like after log rotation), could see the logs are with 0 bytes (which means, nothing logged though it serves the requests and application is accessible). Any help would be appreciated to figure out the issue