Recently I've been getting the following errors e-mailed to me.

 

Subject: Cron <root@d274878dc813> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
/etc/cron.daily/logrotate:
invoke-rc.d: policy-rc.d denied execution of reload.

 

Subject: Cron <root@d274878dc813> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
/etc/cron.daily/logrotate:
invoke-rc.d: policy-rc.d denied execution of reload.
invoke-rc.d: policy-rc.d denied execution of reload.

 

I am pretty certain the errors are from one of the two following changes recently.

I had recently setup a cron job to my Go file for a weekly backup of my Docker/VM's from this thread https://lime-technology.com/forum/index.php?topic=38905.0

I've also recently left the UnBalance Docker as running.

I assume one of the two is generating the error (I'm assuming it's the backup/weekly cron job), however what do I need to fix the error?

 

Thanks!

Received this again this morning, certainly doesn't seem to be daily.

Someone has to have an idea of what this means? 

Input much appreciated.

 

E-mail from today:

Cron <root@4a098718778e> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
/etc/cron.daily/logrotate:
invoke-rc.d: policy-rc.d denied execution of reload.

It now seems to be daily...

No ideas?.. Help a brother out!

 

Cron <root@4a098718778e> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
/etc/cron.daily/logrotate:
invoke-rc.d: policy-rc.d denied execution of reload.

 

Looks like a docker container from this:

 <root@4a098718778e>

 

Does  4a098718778e match one of your container IDs? (use the advanced view in the webgui docker tab, or enter '

docker ps

' at the command line)

Looks like a docker container from this:

 <root@4a098718778e>

 

Does  4a098718778e match one of your container IDs? (use the advanced view in the webgui docker tab, or enter '

docker ps

' at the command line)

 

I knew adding the "help a brother out" line would be beneficial!.. LOL

I'm away from home at the moment, but that should help a bunch to narrow it down. Thanks for your help, and I'll post what I find.

This container ID lines up with the UnBalance docker, I've posted the issue in it's respective thread, will mark solved once we can fix the issue.