opentoe Posted September 10, 2015 Share Posted September 10, 2015 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 Link to comment
opentoe Posted September 10, 2015 Author Share Posted September 10, 2015 Searched and seems related to system notifications. I disabled them and will give check. Link to comment
itimpi Posted September 10, 2015 Share Posted September 10, 2015 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. Link to comment
opentoe Posted September 10, 2015 Author Share Posted September 10, 2015 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! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.