Welcome! Log In Create A New Profile

Advanced

RE: logrotate (?) screws it badly

Reinis Rozitis
October 06, 2023 04:30AM
> postrotate
> /bin/kill -USR1 `cat /run/nginx.pid 2>/dev/null` 2>/dev/null || true
> endscript
>}
```
> and I wonder...
> if it is logrotate's _fault_ or perhaps I screwed Nginx's configs somewhere? For after logs got rotated Nginx logs into: access.log.1 & error.log.1 and now as it should, you
> know access.log & error.log


You need to check if the postrotate command completes successfully (for example - is the pid file in correct path? / I would remove all the || true parts and just leave kill -USR1 `cat /run/nginx.pid`).

Now it seems that logrotate just renames the files but nginx is not getting the signal and still has open handle to them so keeps logging in the renamed file.

rr
_______________________________________________
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

logrotate (?) screws it badly

lejeczek via nginx October 06, 2023 02:14AM

RE: logrotate (?) screws it badly

Reinis Rozitis October 06, 2023 04:30AM

Re: logrotate (?) screws it badly

Ralph Seichter via nginx October 06, 2023 04:42AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 108
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready