mails from Anacron

jigg3 · 19. Oktober 2014

Hi guys,

I'm getting nearly every week one mail from anacron with following content:

Code

/etc/cron.daily/logrotate:
Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}
invoke-rc.d: initscript rsyslog, action "reload" failed.
error: error running shared postrotate script for '/var/log/autoshutdown.log
'
Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}
invoke-rc.d: initscript rsyslog, action "reload" failed.
error: error running shared postrotate script for '/var/log/transmissionbt.log
'
run-parts: /etc/cron.daily/logrotate exited with return code 1

What shall I do?

Ozymandias · 19. Oktober 2014

Same Problem here...

votdev · 19. Oktober 2014

Open a bug report for the transmissionbt plugin. The script uses the wrong script command args. The 'reload' argument has been removed in Debian Wheezy.

T-A-Z · 19. Oktober 2014

I also get daily emails about an anacron job, but mine is cron.daily.

Code

/etc/cron.daily/apt:
Creating index of upgradeable packages ...
Creating index of OpenMediaVault plugins ...

Today it additionally contained:

Code

/etc/cron.daily/openmediavault-mdadm:
MAILADDR server@domain.de

Any idea which program is responsible?

rowie · 20. Oktober 2014

same here!

Zitat

Anacron job 'cron.daily' on nas [nas]
/etc/cron.daily/openmediavault-mdadm:
MAILADDR ...

Zitat

Anacron job 'cron.daily' on nas [nas]
/etc/cron.daily/logrotate:Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}invoke-rc.d: initscript rsyslog, action "reload" failed.error: error running shared postrotate script for '/var/log/autoshutdown.log 'run-parts: /etc/cron.daily/logrotate exited with return code 1/etc/cron.daily/openmediavault-mdadm:MAILADDR

Zitat

Anacron job 'cron.daily' on nas [nas]
/etc/cron.daily/logrotate:
Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}
invoke-rc.d: initscript rsyslog, action "reload" failed.
error: error running shared postrotate script for '/var/log/autoshutdown.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

virgafox · 20. Oktober 2014

same here: mdadm sends me a message containing only my email address..

votdev · 20. Oktober 2014

mdadm mail address issue will be solved in 1.0.30.

Solo0815 · 20. Oktober 2014

rowie:

please enable the autoshutdown-plugin at least once to get rid of the error with the (missing) autoshutdown.log

T-A-Z · 20. Oktober 2014

Thanks for your fix regarding mdam volker.
However I am also getting emails regarding apt, any idea's how this can be fixed?

Code

Subject: Anacron job 'cron.daily' on $host
/etc/cron.daily/apt:
Creating index of upgradeable packages ...
Creating index of OpenMediaVault plugins ...

rowie · 21. Oktober 2014

@Solo0815

enabled and one minute later disabled!

Solo0815 · 21. Oktober 2014

Then the error should be gone. Please repot, if it is still there

begeisterter · 20. Mai 2016

Hallo,

trotz des Tipps, den autoshutdown einmal zu aktivieren und sofort wieder zu deaktivieren bekomme ich die tägliche Mail mit folgendem Inhalt:

Betreff: Anacron job 'cron.daily' on Server [Server]

Inhalt:
/etc/cron.daily/apt:
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...

Wie stelle ich das ab?

KarlKarlsen · 15. Oktober 2016

Hey,

cron is by default sending the output of its scripts via mail (in case something goes wrong).
The scripts can be found in /etc/cron.daily/* and /etc/cron.weekly/*.

If you get this:

Zitat

/etc/cron.daily/apt:
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...

Apparently /etc/cron.daily/apt calls the mkaptidx script from omv which always creates output:

Just comment out this lines in /usr/sbin/omv-mkaptidx and there should be no output.

If you get this:

Zitat

/etc/cron.daily/apt:
verbose level 2
power status (255) undetermined, continuing
system is on main power.
sleeping for 1641 seconds
power status (255) undetermined, continuing
system is on main power.
check_stamp: interval=86400, now=1476396000, stamp=1476309600, delta=86400 (sec)
download updated metadata (success).send dbus signal (success)
check_stamp: interval=86400, now=1476396000, stamp=1476309600, delta=86400 (sec)
download upgradable (success)
check_stamp: interval=86400, now=1476396000, stamp=1476309600, delta=86400 (sec)
unattended-upgrade (success)
check_stamp: interval=1814400, now=1476396000, stamp=1475791200, delta=604800 (sec)
autoclean (not run)
skip aging since MaxAge is 0

Alles anzeigen

You can disable it via editing the /etc/apt/apt.conf.d/02periodic configuration file:

set APT::Periodic::Verbose to 0:

APT::Periodic::Verbose "0";

If you get this:

Zitat

CRON-APT RUN [/etc/cron-apt/config]: Thu Oct 6 08:05:56 CEST 2016
CRON-APT SLEEP: 73, Thu Oct 6 08:07:09 CEST 2016
CRON-APT ACTION: 3-download
CRON-APT LINE: /usr/bin/apt-get -o Acquire::http::Dl-Limit=25 dist-upgrade -d -y -o APT::Get::Show-Upgraded=true
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
<some packages>
6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/40.8 MB of archives.
After this operation, 473 kB of additional disk space will be used.
Download complete and in download only mode

Alles anzeigen

You can disable this via the Webinterface: Notification -> Notifications: Disable "Software Updates"

If you get this:

Zitat

/etc/cron.weekly/openmediavault-update-smart-drivedb:
Updating smartmontools 5.41 drive database ...
/usr/share/smartmontools/drivedb.h updated from branches/RELEASE_5_41_DRIVEDB

Edit the /etc/cron.weekly/openmediavault-update-smart-drivedb file (line 50+51), that it looks like this:

#echo "Updating smartmontools ${version} drive database ..."
eval ${tmpscript} 2> /dev/null

Linkinsoldier · 15. Oktober 2016

What shall I do if I get this?

/etc/cron.weekly/openmediavault-update-smart-drivedb:
Updating smartmontools 5.41 drive database ...
sed: Kann 32 Elemente nicht auf stdout schreiben: Datenübergabe unterbrochen (broken pipe)
cat: Schreibfehler: Datenübergabe unterbrochen (broken pipe)
/usr/share/smartmontools/drivedb.h updated from branches/RELEASE_5_41_DRIVEDB

Does anyone know why the pipe is broken? I am still on omv 2 and I would guess some update of openmediavault last week might have caused this? System is unchanged for weeks and I never got this error before...!

Chris71 · 17. Oktober 2016

And an additional question: What's the purpose of the following mail, I get daily on my OMV 3 installation:

Code

Cron <root@nas> test -x /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null [nas.*************]


invoke-rc.d: policy-rc.d denied execution of start.

Of course, I could modify policy-rc.d, and from what I've seen, it seems to be related to sysvinit (which is a bit odd, since Debian 8 uses systemd instead), but without knowing the reason for it, I don't want to

Thanks
Christoph

mails from Anacron

Jetzt mitmachen!

Tags