joeman2116 Posted December 12, 2011 Posted December 12, 2011 Dec 10 22:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 10 23:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 00:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 01:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 02:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 03:33:33 Tower39 kernel: mdcmd (40): spindown 2 Dec 11 03:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 04:26:56 Tower39 kernel: mdcmd (41): spindown 5 Dec 11 04:27:07 Tower39 kernel: mdcmd (42): spindown 4 Dec 11 04:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 05:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 06:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 07:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 08:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 09:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 10:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 11:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 12:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 13:14:34 Tower39 kernel: mdcmd (43): spindown 3 Dec 11 13:14:35 Tower39 kernel: mdcmd (44): spindown 4 Dec 11 13:16:15 Tower39 kernel: mdcmd (45): spindown 2 Dec 11 13:19:27 Tower39 kernel: mdcmd (46): spindown 5 Dec 11 13:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 13:53:15 Tower39 kernel: mdcmd (47): spindown 2 Dec 11 14:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 15:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 16:12:31 Tower39 kernel: mdcmd (48): spindown 3 Dec 11 16:21:24 Tower39 kernel: mdcmd (49): spindown 2 Dec 11 16:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 17:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" Dec 11 18:43:01 Tower39 crond[1064]: failed parsing crontab for user root: cron="" This is what I am seeing and was wondering if someone might be able to steer me in the right direction to determine what might be causing the cdrond errors? My system is working well - its just these errors that keep popping up I am using unraid5 bld12A - Thanks in advance Joe
MisterWolfe Posted January 30, 2012 Posted January 30, 2012 I am having this as well. Jan 30 06:57:01 Tower crond[999]: failed parsing crontab for user root: cron="" Jan 30 06:57:01 Tower crond[999]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jan 30 07:57:01 Tower crond[999]: failed parsing crontab for user root: cron="" Jan 30 07:57:01 Tower crond[999]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Has anyone else experienced this or have a solution?
MisterWolfe Posted January 30, 2012 Posted January 30, 2012 I have the following packages running. bwm-ng htop iftop ssmtp unraid status email monthy parity check overtemp shutdown Clean powerdown unrar I also installed the unraid SF: .9g menu mod. These errors popped up after a power outage. I could just remove the cronjobs for root, but I'd rather figure out why it happened.
MisterWolfe Posted January 30, 2012 Posted January 30, 2012 I looked in /var/spool/cron/crontabs and there was an file there for the user root- in addition to a file called root. I do not have a user created called root-, just the standard root user. The files were identical, so I removed the file called root- from the cron location since there was no user account to associate it with. I don't know why the cron job was added for a non existent user, though.
MisterWolfe Posted January 30, 2012 Posted January 30, 2012 Ok, after some digging, it appears there is an erroneous entry in the crontab. crontab -e shows this: #Scheduled Parity Check cron="" Which is directly above the proper entry for the Monthly parity check. I've commented the cron="" out and will see if this fixes the issue. Still a mystery as to how it got there.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.