I checked my syslog this morning and noticed a lot of errors. I commented out the hourly cron to hopefully fix the parsing error, but apparently it didn't work. Any ideas on the rest?

 

 

Feb 28 00:08:01 Media crond[1093]: failed parsing crontab for user root: cron="" 
Feb 28 00:47:01 Media crond[5244]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 01:22:34 Media kernel: mdcmd (23): spindown 1
Feb 28 01:47:01 Media crond[24079]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 02:47:01 Media crond[6121]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 03:47:01 Media crond[23565]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 04:40:01 Media crond[5226]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null to /dev/null 
Feb 28 04:40:48 Media kernel: md: sync done. time=24508sec
Feb 28 04:40:48 Media kernel: md: recovery thread sync completion status: 0
Feb 28 04:47:01 Media crond[7568]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 04:59:35 Media kernel: mdcmd (24): spindown 3
Feb 28 05:47:01 Media crond[21594]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 06:47:01 Media crond[2950]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 07:47:01 Media crond[16515]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 08:47:01 Media crond[30622]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 09:47:01 Media crond[12893]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 10:47:01 Media crond[27106]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 
Feb 28 11:47:01 Media crond[8747]: unable to create mail file /var/spool/cron/cron.TQdpLn/cron.root.1093: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null 

 

I'm also attaching a complete syslog.

 

Also, can you see what is causing the drives to not spindown? Is it becasue of the error sending the e-mail that the drives wouldn't spin down? Nothing has accessed my unRAID box all since around 3 AM this morning and at 12 Noon all drives were spun up.

syslog022812.txt

I just noticed the failed parsing crontab for cron error in my log tonight. Did you ever figure out what it was? I'm not using any emailing addon or plugin.

It's caused by an add-on. Disable them until you determine which one is causing the problem.

In my case it was an add-on with simple features causing it, Sf added a cron as a workaround for another problem early on in its release, since been fixed and causes the erroneous cron error. Later versions of SF have fixed this, so if you've updated then this is not your problem.