Does anyone have a clue as to why an OpenServer 5.0.6 system would autoboot during the night, sometimes multiple times, without intervention or instructions from cron? Root has mail everyday notifying us about it, but the autoboot log does not have enough info for us to troubleshoot.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Unscheduled autoboot problem in OpenServer 5.0.6
- Thread starter SteveS815
- Start date
stanhubble
MIS
Are there any shutdown messages in /usr/adm/syslog?
(most daemons will log that they received a kill signal)
if not then tell the cleaning staff to stop plugging the vaccuum into your ups.
(most daemons will log that they received a kill signal)
if not then tell the cleaning staff to stop plugging the vaccuum into your ups.
Chances are, you kernel might have paniced, and restarted your system. Check /etc/default/boot for the PANICBOOT setting. If set to YES, then the system will autoreboot when a panic occurs. The problem with this is that you cannot properly diagnose why. I would set this to YES, and look at the autoboot messages for the time, and hang out when it happens, and then follow the link below to figure out why this is happening.
If the kernel panics everynight, it's possible that you have faulty hardware, which would explain why this happens at night (if your system is scheduled to backup during the night) Or it is some SCSI issue, which could mean lots of different things, like cables, termination etc..
Bruce Garlock
bruceg@tiac.net
If the kernel panics everynight, it's possible that you have faulty hardware, which would explain why this happens at night (if your system is scheduled to backup during the night) Or it is some SCSI issue, which could mean lots of different things, like cables, termination etc..
Bruce Garlock
bruceg@tiac.net
- Status
Similar threads
- Question