Intermittent: Anacron 'cron.daily' email

Put support questions regarding OPI here. Examples are hardware related issues and other questions that are specific to OPI.
Post Reply
murtagh
Posts: 19
Joined: Fri Sep 05, 2014 9:50 pm

Intermittent: Anacron 'cron.daily' email

Post by murtagh » Mon Oct 06, 2014 4:37 pm

This is a minor bug, but it might be able to be debugged. Occasionally I get an email from the anacron daemon saying it errored out. My OPI is not particularly stressed (minimal email, minimal Owncloud, etc) becuase I am still setting it up. Here are the emails:

Title: Anacron job 'cron.daily' on opi
Date: 2014-09-23 07:36
Body:
/etc/cron.daily/logrotate:
initctl: invalid command: reopen-logs
Try `initctl --help' for more information.
invoke-rc.d: initscript php5-fpm, action "reopen-logs" failed.
error: error running non-shared postrotate script for /var/log/php5-fpm.log of '/var/log/php5-fpm.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

###
Title: Anacron job 'cron.daily' on opi
Date: 2014-09-28 07:35
Body:
/etc/cron.daily/logrotate:
initctl: invalid command: reopen-logs
Try `initctl --help' for more information.
invoke-rc.d: initscript php5-fpm, action "reopen-logs" failed.
error: error running non-shared postrotate script for /var/log/php5-fpm.log of '/var/log/php5-fpm.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

###
Title: Anacron job 'cron.daily' on opi
Date: 2014-10-06 07:35
Body:
/etc/cron.daily/logrotate:
initctl: invalid command: reopen-logs
Try `initctl --help' for more information.
invoke-rc.d: initscript php5-fpm, action "reopen-logs" failed.
error: error running non-shared postrotate script for /var/log/php5-fpm.log of '/var/log/php5-fpm.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

User avatar
tor
Posts: 120
Joined: Thu Aug 14, 2014 3:42 am
Contact:

Post by tor » Mon Oct 06, 2014 8:40 pm

Hi murtagh,

Thank you for the detailed error report, appreciated!

This is unfortunately a known upstream, Ubuntu, bug. If you are interested in reading more about it information is available here: https://bugs.launchpad.net/ubuntu/+sour ... ug/1230917

Since this is annoying but non fatal we have not yet decided on how to proceed on the matter. Fix it locally or wait for a fix upstream. We are not the only people with this problem by the looks of the bug report.

A good guess is that if it's not fixed upstreams when we get the current workload down is that we do something locally. This is however not an ideal situation since that would mean that we diverge from Ubuntu which we would like to avoid if possible.

I hope that this clarifies the situation.

Best!

/Tor

Post Reply