I can confirm the bug. I can observe it on many servers - but not only
on Debian ones, but on Ubuntu servers too. There is nginx 1.10.3 everywhere.
On Thu, Mar 30, 2017 at 09:05:56PM +0300, Paul Tötterman wrote:
# lsof -p $(systemctl show -pMainPID nginx| cut -d= -f2)|grep /var/log
This actually showed no *.log.1 -files being open, but lsof -c nginx
|grep ... does
Hmm, so the log.1 file is referenced by a worker, and not the master
proc
> # lsof -p $(systemctl show -pMainPID nginx| cut -d= -f2)|grep /var/log
This actually showed no *.log.1 -files being open, but lsof -c nginx
|grep ... does
> # invoke-rc.d nginx rotate
> # lsof -p $(systemctl show -pMainPID nginx| cut -d= -f2)|grep /var/log
Didn't start showing *.log.1 -files o
Hello Paul,
On Fri, Mar 24, 2017 at 10:14:21AM +0200, Paul Tötterman wrote:
Package: nginx
Version: 1.10.3-1
Severity: normal
Dear Maintainer,
I noticed that access.log.1 kept growing and access.log had size 0. Clearly
logrotate had run, but something doesn't quite work. lsof showed nginx stil
Package: nginx
Version: 1.10.3-1
Severity: normal
Dear Maintainer,
I noticed that access.log.1 kept growing and access.log had size 0. Clearly
logrotate had run, but something doesn't quite work. lsof showed nginx still
having access.log.1 open. It seems that logrotate calls
invoke-rc.d ngin
5 matches
Mail list logo