I noticed something odd on my Syslog this morning:

 

This error had started showing up almost hourly:

Aug 22 01:24:01 Tower crond[1163]: failed parsing crontab for user root: /usr/local/sbin/mover |& logger 
Aug 22 02:24:01 Tower crond[1163]: failed parsing crontab for user root: /usr/local/sbin/mover |& logger 
Aug 22 03:24:01 Tower crond[1163]: failed parsing crontab for user root: /usr/local/sbin/mover |& logger 
Aug 22 04:24:01 Tower crond[1163]: failed parsing crontab for user root: /usr/local/sbin/mover |& logger 

 

Looking through the Syslog I came across this event:

Aug 21 21:30:35 Tower emhttp: shcmd (105): crontab -c /etc/cron.d - <<< "# Generated mover schedule: 2 /usr/local/sbin/mover |& logger"

But normally my mover schedule had been:

Aug  7 20:11:02 Tower emhttp: shcmd (33): crontab -c /etc/cron.d - <<< "# Generated mover schedule: 30 3 * * * /usr/local/sbin/mover |& logger"

(this line is from when the server was last rebooted)

 

I've attached an edited copy of my syslog so it picks up just prior to the change of the generated mover schedule. Incidently, around this time I had been copying some files from the server to my workstation and had the transfer hang or stall. I ham-handily cancelled the transfer but didn't see any errors logged. I later transferred the files successfully.

 

I did a little unRAID Forums searching regarding the error and decided it might be linked to a problem with the mover schedule format. Sure enough, the mover schedule had changed in the webGUI. I rebooted the server and set the schedule properly. I also ran the mover manually and all seems to be OK.

 

So, the question is why did the mover schedule change seemingly on it own? Thanks for your input!

Syslog-2013-0822-part.txt

Check Settings->Share Settings

Check Settings->Share Settings

Yes, that's where I first noticed the change to my normal mover schedule. I forget what it had changed to but it was not nightly at 3:30a (my usual). I should look up crontab setting to see what just a "2" would give you. BTW, it seems to be holding the correct value over, at least, one reboot.

 

Thanks!

A 2 will fail with the error given

Thanks dgaschk for verifying that. I'm marking it solved. It was just one of those things.......

I've been adding and moving disks around and on my last restart I started getting the same problem.

 

Found in the logs:

Nov 30 08:50:21 kingsnake emhttp: shcmd (45): crontab -c /etc/cron.d - <<< "# Generated mover schedule: 2 /usr/local/sbin/mover |& logger"

 

which generated the errors:

crond[1211]: failed parsing crontab for user root: /usr/local/sbin/mover |& logger

 

reset my scheduled to daily and hopefully it's cured.  I have no idea why it lost the previous setting.

 

 

From what I've seen over the last couple of months, the change in the mover schedule is a result of issues with the "new" webGUI (available from Github). The stock GUI that ships with v5.0+ is OK. Now, it's a known problem and Tom (limetech) is working on it.