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 files not getting logged further by nginx worker process. As per the comments tried to edit the nby krishna - Nginx Mailing List - English
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 nginx log will be generated). /var/nginx/logs/*log { daily rotate 20 missingok notifeby krishna - Nginx Mailing List - English
Workaround: restarting nginx helps and logs getting generated.by krishna - Nginx Mailing List - English
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 and why its occurring . Config: #Log file format log_format main '$remote_addr - $remoby krishna - Nginx Mailing List - English