Michael Kaaber Posted August 15, 2018 Share Posted August 15, 2018 I use the plexinc/pms-docker Repository The Plex Media Server works but I have a lot of these errors in the System Log. Aug 15 04:51:01 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 05:11:01 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 05:31:02 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 05:51:11 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 06:12:01 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 06:32:11 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 06:53:01 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 07:13:11 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 07:34:01 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 07:54:02 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 08:15:01 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 08:35:11 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Aug 15 08:55:11 plex crond[1881]: failed parsing crontab for user root: /usr/local/sbin/mover force 2>/dev/null Is the 'Generated schedule for forced move' ok? Should there be something before the '/usr/local/sbin/mover force 2>/dev/null' root@plex:~# cat /etc/cron.d/root # Generated docker monitoring schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 30 5 * * * /usr/local/sbin/mover &> /dev/null # Generated parity check schedule: 0 6 1 * * /usr/local/sbin/mdcmd check &> /dev/null || : # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated unRAID OS update check schedule: 11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated schedule for forced move /usr/local/sbin/mover force 2>/dev/null # Generated cron settings for plugin autoupdates 15 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 # Generated ssd trim schedule: 15 12 * * * /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 root@plex:~# Quote Link to comment
Squid Posted August 15, 2018 Share Posted August 15, 2018 In the settings for mover tuning, you didn't enter in a Cron expression when you enabled force moverSent via Tapatalk because my laptop doesn't fit in my pocket Quote Link to comment
Michael Kaaber Posted August 15, 2018 Author Share Posted August 15, 2018 Thank you for you reply. Is it the 'Cron Schedule to force move of all files' I shall enter the Cron expression? What shall I enter there? Quote Link to comment
Michael Kaaber Posted August 16, 2018 Author Share Posted August 16, 2018 I found the answer here :-) https://lime-technology.com/forums/topic/70783-plugin-mover-tuning/?page=2 Quote Link to comment
Casadream_1 Posted June 19, 2023 Share Posted June 19, 2023 I have exactly the same problem following the update of the plugin recently, in 2023. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.