[SRU] php5-fpm logrotate errors after package switched to upstart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
php5 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
* After the switch to Upstart in Saucy, php5-fpm log rotation began to break. It was reported that individuals were getting weekly cron warning emails during logrotation.
[Test Case]
* This test case happens with automatic rotation of logs, in which weekly cron warnings get triggered. With the fix, these weekly cron warnings for log rotation should not be triggered.
[Regression Potential]
* This change is an upstream change that appears to have been present in the repositories in Debian and even further upstream for some time without regressions.
* Regression potential is minimal, if only in cases where the pid gets lost, and other issues crop up.
[Other Info]
* This bug is referred to by the MIR bug for php5-fpm (#1267255)
[Original Description]
Getting weekly cron warning emails during logrotation after php5-fpm package switched to upstart in Saucy.
root@ops:~# lsb_release -rd
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10
root@ops:~# apt-cache policy php5-fpm
php5-fpm:
Installed: 5.5.3+dfsg-1ubuntu1
Candidate: 5.5.3+dfsg-1ubuntu1
Version table:
*** 5.5.3+dfsg-1ubuntu1 0
500 http://
100 /var/lib/
root@ops:~# cat /etc/logrotate.
/var/log/
rotate 12
weekly
missingok
notifempty
compress
delaycompress
postrotate
invoke-rc.d php5-fpm reopen-logs > /dev/null
endscript
}
root@ops:~# dpkg -S /etc/logrotate.
php5-fpm: /etc/logrotate.
root@ops:~# invoke-rc.d php5-fpm reopen-logs
initctl: invalid command: reopen-logs
Try `initctl --help' for more information.
invoke-rc.d: initscript php5-fpm, action "reopen-logs" failed.
Changed in php5 (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in php5 (Ubuntu): | |
importance: | Medium → High |
description: | updated |
Changed in php5 (Ubuntu Trusty): | |
status: | Triaged → In Progress |
Is there any way to quickly address this problem by myself?