hello -

 

I recently upgraded to 6.2 from 6.1.9 (I believe) and now notice that I'm getting log entries about every minute:

 

Sep  8 09:03:16 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null

Sep  8 09:04:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep  8 09:04:16 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null

Sep  8 09:05:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

 

the syslog attached is from a reboot and captures the bootup and a few minutes of these errors.

 

I have an old docker.img that I don't use anymore, and would be happy to delete that if it is causing any problems.

 

thanks for any help or pointers.

syslog.txt

hello -

 

I recently upgraded to 6.2 from 6.1.9 (I believe) and now notice that I'm getting log entries about every minute:

 

Sep  8 09:03:16 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null

Sep  8 09:04:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep  8 09:04:16 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null

Sep  8 09:05:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

 

the syslog attached is from a reboot and captures the bootup and a few minutes of these errors.

 

I have an old docker.img that I don't use anymore, and would be happy to delete that if it is causing any problems.

 

thanks for any help or pointers.

 

Go to Settings -> Notification settings and disable / enable System notifications. This will correct the typo you are experiencing.

 

hi -

 

thanks very much for the quick response. it looks like that fixed 50% of my problem (instead of two different errors, I'm now just getting this one).

 

 

 

Sep 8 17:34:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep 8 17:35:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep 8 17:36:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep 8 17:37:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep 8 17:38:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep 8 17:39:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep 8 17:40:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep 8 17:41:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Sep 8 17:42:01 Tower crond[1462]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

so it appears that this directory doesn't exist: /usr/local/emhttp/plugins/dynamix.system.stats/scripts. Perhaps it was carried over from the prior version?

 

root@Tower:/usr/local/emhttp/plugins# ls -altr     

total 0

drwxr-xr-x  4 root root  120 Feb 12  2016 tablesorter/

drwxr-xr-x  6 root root  240 Jun 19 00:41 dynamix.apcupsd/

drwxr-xr-x  8 root root  360 Jun 19 09:45 speedtest/

drwxr-xr-x 12 root root  240 Jun 19 09:45 ./

drwxr-xr-x  6 root root  220 Jun 27 13:52 dynamix.plugin.manager/

drwxr-xr-x  9 root root  360 Jul 24 12:02 dynamix.vm.manager/

drwxr-xr-x  7 root root  200 Aug 26 10:05 dynamix.cache.dirs/

drwxr-xr-x  8 root root 1960 Sep  4 11:58 dynamix/

drwxr-xr-x  4 root root  160 Sep  4 13:36 unRAIDServer/

drwxr-xr-x  9 root root  460 Sep  7 11:04 community.applications/

drwxr-xr-x  8 root root  320 Sep  8 08:58 dynamix.docker.manager/

drwxr-xr-x  3 root root  280 Sep  8 09:22 ../

root@Tower:/usr/local/emhttp/plugins#

 

may I just delete this offending command from the cron job list? if so, what's the recommended way to do that?