e-mail notification, cron error messages

Xaneu · 5. Dezember 2016

Hi,

I installed OMV about a few weeks ago and activated the e-mail notification.
Since that I get:

Hourly the following email:

E-mail Subject: [NAS-Server.local] Cron <root @ NAS server> root cd / && run-parts --report /etc/cron.hourly
E-mail content: / bin / sh: 1: root: not found

and daily the following email:

E-mail Subject: [NAS-Server.local] Cron <root @ NAS server> root test -x / usr / sbin / anacron (Cd / && run-parts --report /etc/cron.daily)
E-mail content: / bin / sh: 1: root: not found

and weekly the following email:

[NAS-Server.local] Cron <root @ NAS-server> root test -x / usr / sbin / anacron (Cd / && run-parts --report /etc/cron.weekly)
/ Bin / sh: 1: root: not found

I think that something with the execution of the OMV system cronjobs does not work.

Does somebody has any idea?

Xaneu

Xaneu · 7. Dezember 2016

Hi,

I have solved the problem now after a long internet search.
The reason was that in the file "/var/spool/cron/crontab/root" user were listed (here: root).
Since the crontab files in the directory "/var/spool/cron/crontab" belongs exclusively to individual users (here: root), no users may be listed in this crontab files.

Wrong:

Code

# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.ZM955N/crontab installed on Wed Dec  7 20:09:39 2016)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.


SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin


# m h dom mon dow user	command
17 *	* * *	root	cd / && run-parts --report /etc/cron.hourly
25 6	* * *	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6	* * 7	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6	1 * *	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#

Alles anzeigen

Correct:

Code

# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.ZM955N/crontab installed on Wed Dec  7 20:09:39 2016)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.


SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin


# m h dom mon dow command
17 *	* * *	cd / && run-parts --report /etc/cron.hourly
25 6	* * *	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6	* * 7	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6	1 * *	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#

Alles anzeigen

After I changed the file it worked.
Why the system had generated the wrong file format is unclear to me !?

Xaneu

ryecoaaron · 7. Dezember 2016

That file doesn't exist on any of my systems and I can't find anything in the OMV source code that would create it.

Xaneu · 8. Dezember 2016

Ups,

Thanks for the hint.
I had already wondered that no more OMV users have the same problem.

In recent weeks, I've had a lot of work to move everything from my previous server to the new OMV-based server (File server, Web server, SQL Server, SMS server, various cronjobs...).
Not everything has worked smoothly. Therefore, I can not rule out that this is a cause of several additional installations and uninstallations (outside the OMV system).

In any case, I am glad that OMV is obviously not the cause.

Xaneu

e-mail notification, cron error messages

Jetzt mitmachen!

Tags