All of a sudden I am getting this error. All was working good and I didn't change anything. Any idea where this is coming from?

 

Sep 10 18:56:02 Server crond[1555]: failed parsing crontab for user root: #015
Sep 10 19:15:02 Server crond[1555]: failed parsing crontab for user root: #015
Sep 10 19:33:11 Server crond[1555]: failed parsing crontab for user root: #015
Sep 10 19:51:11 Server crond[1555]: failed parsing crontab for user root: #015
Sep 10 20:09:02 Server crond[1555]: failed parsing crontab for user root: #015
Sep 10 20:28:01 Server crond[1555]: failed parsing crontab for user root: #015

Edited September 12, 20178 yr by KriZ82

There's an invalid entry in the cron file

 

What's the output of 

cat /etc/cron.d/root

and

crontab -l

 

Output of cat /etc/cron.d/root

# Generated ssd trim schedule:
45 4 * * * /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

# Perform a daily backup of my main share at 6:30am
30 6 * * * rsync -a --delete /mnt/user/Pictures\ and\ Video/ /mnt/disks/Backup_Pictures |& logger

# 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 3 * * * /usr/local/sbin/mover |& logger

# Generated parity check schedule:
0 2 28 * * /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 array status check schedule:
20 0 * * 1 /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null

output crontab -l

 

# If you don't want the output of a cron job mailed to you, you have to direct
# any output to /dev/null.  We'll do this here since these jobs should run
# properly on a newly installed system.  If a script fails, run-parts will
# mail a notice to root.
#
# Run the hourly, daily, weekly, and monthly cron jobs.
# Jobs that need different timing may be entered into the crontab as before,
# but most really don't need greater granularity than this.  If the exact
# times of the hourly, daily, weekly, and monthly cron jobs do not suit your
# needs, feel free to adjust them.
#
# Run hourly cron jobs at 47 minutes after the hour:
47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
#
# Run daily cron jobs at 4:40 every day:
40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null
#
# Run weekly cron jobs at 4:30 on the first day of the week:
30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null
#
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null

 

This problem has been solved. The issue was i edited the file with notepad. Now all works without this error.

@Squid I am writing in this thread because its the same issue, with the exception that I havent edited anything, standard docker install and backup setup following video

 

I now get the following errors by email:

/bin/sh: line 1: 31625 Killed /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null 

 

Output says:

# Generated docker monitoring schedule:
10 0 1 * * /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:
40 3 * * * /usr/local/sbin/mover &> /dev/null

# Generated parity check schedule:
0 5 * * 0 /usr/local/sbin/mdcmd check  &> /dev/null || :

# Generated plugins version check schedule:
10 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null

# Generated array status check schedule:
20 0 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null

# Generated Unraid OS update check schedule:
11 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null

# Generated cron settings for docker autoupdates
0 4 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1
# Generated cron settings for plugin autoupdates
0 4 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
# Generated ssd trim schedule:
0 20 * * * /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

# Refresh Recycle Bin trash sizes every minute:
* * * * * /usr/local/emhttp/plugins/recycle.bin/scripts/get_trashsizes &> /dev/null

 

And:

 

# If you don't want the output of a cron job mailed to you, you have to direct
# any output to /dev/null.  We'll do this here since these jobs should run
# properly on a newly installed system.  If a script fails, run-parts will
# mail a notice to root.
#
# Run the hourly, daily, weekly, and monthly cron jobs.
# Jobs that need different timing may be entered into the crontab as before,
# but most really don't need greater granularity than this.  If the exact
# times of the hourly, daily, weekly, and monthly cron jobs do not suit your
# needs, feel free to adjust them.
#
# Run hourly cron jobs at 47 minutes after the hour:
47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
#
# Run daily cron jobs at 4:40 every day:
40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null
#
# Run weekly cron jobs at 4:30 on the first day of the week:
30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null
#
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null
0 4 2 * * /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php &>/dev/null 2>&1

 

 

Any insight to this would be greatly appreciated

 

Edited March 26, 20197 yr by casperse

+1

i have the same issue clean install ... installed the plugin and now i have the same error spamming my logs

 

K

3 hours ago, Tradesignal said:

i have the same issue clean install ... installed the plugin and now i have the same error spamming my logs

Since this is not the support thread for any particular plugin, we don't know. Which plugin did you install?

 

On 9/10/2017 at 3:50 PM, Squid said:

There's an invalid entry in the cron file

 

What's the output of 

cat /etc/cron.d/root

and

crontab -l

 

 

fixed it ... the problem is that default there is a missing entry in the mover plugin . by default the field is empty as soon as you fill it with cron syntax it will no longer show you the error.

 

k

I think I am having the same issue.  Any ideas?  Outputs of commands below.

Thanks Joe.

 

root@Tower2:~# cat /etc/cron.d/root
# Generated docker monitoring schedule:
10 0 * * 1 /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:
0 0 1 * * /usr/local/sbin/mover |& logger

# Generated array status check schedule:
20 0 * * 1 /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null

# Generated Unraid OS update check schedule:
11 0 * * 1 /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null

# Generated Schedule for CA Auto Turbo Mode
01:00 /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 480 > /dev/null 2>&1
# Generated cron settings for docker autoupdates
0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1
# Generated cron settings for plugin autoupdates
0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1

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

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

# Purge recycle bin at 3:00 on the first day of the week:
0 3 * * 0 /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin cron &> /dev/null

# Refresh Recycle Bin trash sizes every minute:
* * * * * /usr/local/emhttp/plugins/recycle.bin/scripts/get_trashsizes &> /dev/null

 

root@Tower2:~# crontab -l
# If you don't want the output of a cron job mailed to you, you have to direct
# any output to /dev/null.  We'll do this here since these jobs should run
# properly on a newly installed system.  If a script fails, run-parts will
# mail a notice to root.
#
# Run the hourly, daily, weekly, and monthly cron jobs.
# Jobs that need different timing may be entered into the crontab as before,
# but most really don't need greater granularity than this.  If the exact
# times of the hourly, daily, weekly, and monthly cron jobs do not suit your
# needs, feel free to adjust them.
#
# Run hourly cron jobs at 47 minutes after the hour:
47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
#
# Run daily cron jobs at 4:40 every day:
40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null
#
# Run weekly cron jobs at 4:30 on the first day of the week:
30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null
#
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null
0 3 * * 6 /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php &>/dev/null 2>&1

 

9 hours ago, Joe said:

I think I am having the same issue.

This thread was marked solved many months ago. Have you tried the solution already mentioned?

I am not sure what is the missing entry in the default field mentioned.

Hi, what is the exact solution here? Can someone please describe this in more detail. That would be super nice. Thanks a lot

On 8/15/2019 at 9:20 AM, Tradesignal said:

mover plugin

Everybody that revived this old thread:

 

Do you still have any problems if you remove the mover plugin?