- Minor
The mover does not run at times and errors out.
Feb 24 04:40:48 MediaServer crond[1767]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
From the mover script, this error is from the mover supposedly already running.
start() {
if [ -f $PIDFILE ]; then
if ps h $(cat $PIDFILE) | grep mover ; then
echo "mover: already running"
exit 1
fi
fi
According to the log, the mover is not running. This is the contents of /var/run/. There is no mover.pid.
-rw-r--r-- 1 root root 5 Feb 23 06:11 acpid.pid
srw-rw-rw- 1 root root 0 Feb 23 06:11 acpid.socket=
-rw-r--r-- 1 root root 6 Feb 24 04:40 apcupsd.pid
-rw-r--r-- 1 root root 5 Feb 23 06:11 atd.pid
drwxr-xr-x 2 root root 80 Feb 23 06:11 dbus/
drwx------ 6 root root 140 Feb 23 06:12 docker/
srw-rw---- 1 root docker 0 Feb 23 06:12 docker.sock=
-rw-r--r-- 1 root root 4 Feb 23 06:12 dockerd.pid
srw-rw-rw- 1 root root 0 Feb 23 06:11 emhttpd.socket=
-rw-rw-rw- 1 root root 4 Feb 23 06:11 haveged.pid
-rw-rw-rw- 1 root root 5 Feb 23 06:12 inetd.pid
drwxr-xr-x 8 root root 360 Feb 23 06:12 libvirt/
-rw-rw-rw- 1 root root 24 Feb 23 06:12 nginx.origin
-rw-r--r-- 1 root root 5 Feb 23 06:12 nginx.pid
srw-rw-rw- 1 root root 0 Feb 23 06:12 nginx.socket=
-rw-r--r-- 1 root root 5 Feb 23 06:12 nmbd.pid
drwxr-xr-x 2 root root 40 Aug 3 2018 nscd/
-rw-r--r-- 1 root root 4 Feb 23 06:11 ntpd.pid
-rw-r--r-- 1 root root 4 Feb 23 06:12 php-fpm.pid
srw-rw---- 1 root users 0 Feb 23 06:12 php5-fpm.sock=
drwxr-xr-x 2 root root 60 Feb 24 06:37 recycle.bin/
-rw-rw-rw- 1 rpc rpc 5 Feb 23 06:11 rpc.statd.pid
drwxr-xr-x 2 rpc root 40 Nov 15 13:00 rpcbind/
-r--r--r-- 1 root root 0 Feb 23 06:11 rpcbind.lock
srw-rw-rw- 1 root root 0 Feb 23 06:11 rpcbind.sock=
-rw-r--r-- 1 root root 4 Feb 23 06:12 rsyslogd.pid
-rw-r--r-- 1 root root 1 Feb 23 06:11 runlevel
drwxr-xr-x 5 root root 100 Feb 23 06:11 samba/
-rw------- 1 root root 5 Feb 23 06:11 sm-notify.pid
-rw-r--r-- 1 root root 5 Feb 23 06:12 smbd.pid
-rw-r--r-- 1 root root 5 Feb 23 06:12 sshd.pid
-rw-r--r-- 1 root root 4 Feb 23 06:12 syslogd.pid
srwxrwxrwx 1 root root 0 Feb 23 06:12 ttyd.sock=
-rw-rw-r-- 1 root utmp 4608 Feb 24 06:35 utmp
-rw-r--r-- 1 root root 5 Feb 23 06:12 winbindd.pid
Contents of /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:
40 3 * * * /usr/local/sbin/mover &> /dev/null
# Generated parity check schedule:
0 9 1 * * /usr/local/sbin/mdcmd check NOCORRECT &> /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 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null
# Generated Unraid OS update check schedule:
11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null
# Generated local master browser check:
*/1 * * * * /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null
# Generated ssd trim schedule:
30 5 * * * /sbin/fstrim -a -v | logger &> /dev/null
# Purge recycle bin at 3:00 every day:
0 3 * * * /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
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
The mover then does not run and files are left on the cache. I'm pretty sure that there aren't any plugins interfering with the mover cron.