Bill,
Please send your bb-hosts entries for those that have the downtime specified. Also, at the time this incident occurs (or when you discover it) and BEFORE you restart Hobbit, send the last several lines of the log file where you see the messages and a 'ls -l' of /var/log/hobbit (or whereever your log files live).
Send the recent messages from any log file that was updated on the current day (or the day the incident occurred).
Bill Hart wrote:
This is getting really annoying.
I added another DOWNTIME setting for a different machine.
This morning I came in early to find the system had died again.
The only entries I’m finding in the logs are the history.log that shows unable to access the historyfile for any of the systems. Restarting hobbit does the trick, and it always happens right around when an enable or disable is scheduled via downtime.
The error makes it seem like the files are just flat locked, I don’t know if there’s something in hobbit locking them all open or what.
Is there anything I can do to help troubleshoot this further ? I mean I’ve checked all the logs, half of them haven’t even had any logs added in weeks (no errors), others have some benign warnings (such as not able to find the disabled directory from bb-xsnmp), but nothing showing issues except the history side.
Thanks,
Bill Hart
Computer Support Supervisor
Burke Corporation
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007