If this was fixed in version 25, then it appears to have regressed
somewhere between then and version 87. I observed precisely this
behavior on a system that once ran postgres but later ran squid: the
squid logs never rotated and the cron mail came in with the glob failure
error listed above.
Our version of /etc/logrotate.d/postgresql-common did in fact have the
missingok, but it appears that this did not help. The glob error above
appears to be an uncatchable exception of some sort. It would appear
that the fix released did not have the desired effect.
Here's dpkg -l postgresql-common:
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version
Description
+++-=====================================-==============================-============================================
rc postgresql-common 87
PostgreSQL database-cluster manager
Here's the logrotate mail dated Sat, 9 Aug 2008 06:48:26 +0100 (BST)
/etc/cron.daily/logrotate:
error: error accessing /var/log/postgresql: No such file or directory
error: postgresql-common:1 glob failed for /var/log/postgresql/*.log
run-parts: /etc/cron.daily/logrotate exited with return code 1
--
postgresql-common 24: Causes complete logrotate failure
https://bugs.launchpad.net/bugs/26653
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
