This is a discussion on Re: 4.1.9, S10, mystery reboot within the IPFilter forums, part of the System Security and Security Related category; nothing other than the usual stuff you see after the start of a reboot. Nothing unusual before that. I stared ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
nothing other than the usual stuff you see after the start of
a reboot. Nothing unusual before that. I stared at it, looking for a panic or hardware error, eg ECC problem. Nada. Jeff On Thu, 18 Aug 2005, Darren Reed wrote: > Date: Thu, 18 Aug 2005 09:59:53 +1000 (EST) > From: Darren Reed <darrenr@reed.wattle.id.au> > To: Jeff A. Earickson <jaearick@colby.edu> > Cc: ipfilter@coombs.anu.edu.au > Subject: Re: 4.1.9, S10, mystery reboot > >> Gang, >> >> I'll throw this out FWIW. I upgraded my Solaris 10 box, >> a V210, from 4.1.8 to 4.1.9 yesterday. It had been rock >> solid with 4.1.8. I upgraded by building 419 with Sun >> cc Forte 9 compiler, stopping ipfilter via /etc/init.d/ipfboot, >> doing a pkgrm of ipfx and ipf, installing the new version >> via "make package", then restarting via ipfboot. >> >> This morning I found that the machine had rebooted itself >> in the middle of the night, with no crash dump. Savecore >> is enabled. One of my Volume manager metadevices needed >> maintenance. Hmmmmm. I'm doing a "metareplace -e" to fix >> the metadevice. I'll keep an eye on it to see if it falls >> over again. If so, I may roll back to 4.1.8. > > What about output in dmesg or /var/adm/messages ? > > Darren > |