September 10, 201510 yr Just plopped in two different controllers. Whole different thread going on with that. I did notice multiple entries in my syslog. I don't want to perform a reboot, since it is doing a parity check now but can if needed. I know the cron daemon runs programs like a scheduler, but new to this entry. Anyone have a guess? Sep 9 20:35:01 SUN crond[1976]: exit status 127 from user root /usr/local/sbin/monitor &> /dev/null
September 10, 201510 yr Author Searched and seems related to system notifications. I disabled them and will give check.
September 10, 201510 yr Community Expert Searched and seems related to system notifications. I disabled them and will give check. It was reported in that one could get that sort of message after one of the 6.1 releases. The solution was to disable/enable notifications. I thought that was mentioned in the Release Notes, but I could be wrong.
September 10, 201510 yr Author Searched and seems related to system notifications. I disabled them and will give check. It was reported in that one could get that sort of message after one of the 6.1 releases. The solution was to disable/enable notifications. I thought that was mentioned in the Release Notes, but I could be wrong. Yea, I mentioned that in my previous post. Turn off notifications and turned them back on. No more 127 entry in my syslog. Thanks!
Archived
This topic is now archived and is closed to further replies.