July 29, 201312 yr Did something happen with the cache mover on this version? I've had the same settings for years to invoke the mover at the top of the hour, either every 1 hour or two hours. But something has changed. One it doesn't seem to be trying to do it at the top of the hour any more. And two it seems to always fail. I always get a message in the log that shows this. These are from my unRAID1 and unRAID3 setups. Jul 29 07:51:01 Tower crond[1409]: failed parsing crontab for user root: */2* * * /usr/local/sbin/mover |& logger Jul 29 08:19:01 Tower3 crond[1249]: failed parsing crontab for user root: */2* * * /usr/local/sbin/mover |& logger The mover isn't running like it used to and it isn't at the top of the hour. My mover settings currently are 0 */2* * * which is supposed to be every 2 hours at the top of the hour. or I'll have it set to 0 */1* * * which is supposed to be every hour at the top of the hour. The only way I have been able to initiate the mover is by doing it manually. Did something change? Do I need to have different settings for the mover?
July 29, 201312 yr If your paste is literally what you have then you need to have a space between fields. You're missing one by the looks of it, which would also match with the parse error cron is giving you. e.g */2* * * */2 * * *
July 29, 201312 yr Author If your paste is literally what you have then you need to have a space between fields. You're missing one by the looks of it, which would also match with the parse error cron is giving you. e.g */2* * * */2 * * * I would have never figured that out. I guess at some point I removed the space by accident. Thanks.
Archived
This topic is now archived and is closed to further replies.