[Unraid OS version 6.10.0-rc1 available]

2 hours ago, trurl said:

Are you using a plugin for mover? If so, you should post on the support thread for the plugin. You can go directly to the correct support thread for any of your plugins by clicking on its Support Link on the Plugins page of your Unraid webUI.

Actually i installed a few plugins, to try them out. i will check if this is caused by one of them... 

thanks for pointing this out.

[Unraid OS version 6.10.0-rc1 available]

Hi there...

I am currently testing 6.10RC1 as a new user and i must say, i am impressed and really like what i see there.

However, i do encounter an issue with the crontab for the mover.

The log itself states the following line:

 

Aug 30 10:55:01 Horus crond[1786]: failed parsing crontab for user root: /usr/local/sbin/mover.old start 2>/dev/null

 

when i check the crontab the entry looks cropped from all cron information except from the cmdline:

 

# Generated system monitoring schedule:
*/1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

# Generated mover schedule:
0 */1 * * * /usr/local/sbin/mover |& logger

# Generated schedule for forced move
 /usr/local/sbin/mover.old start 2>/dev/null


# CRON for CA background scanning of applications
18 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2
>&1

# Generated ssd trim schedule:
0 */1 * * * /sbin/fstrim -a -v | logger &> /dev/null

# Generated system data collection schedule:
*/1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

 

Any ideas what i could have done wrong, or is this maybe a bug in the rc1?

 

PS: The mover itself however does start, but of course not the .old one....

 

cheers,

Alex