Date: Thu, 13 Jan 2005 20:26:58 +1030 From: Shane Ambler <Shane@007Marketing.com> To: Ted Mittelstaedt <tedm@toybox.placo.com>, FreeBSD Mailing Lists <freebsd-questions@freebsd.org> Subject: Re: 4.9 rebooting Message-ID: <BE0C8A12.21DB1%Shane@007Marketing.com> In-Reply-To: <LOBBIFDAGNMAMLGJJCKNOEAKFAAA.tedm@toybox.placo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I would agree with looking into hardware problems - I have a MSI-694 dual proc machine that about two or three months ago started rebooting once or twice a week for no apparent reason, then one hot day it became several times a day and I shut it down before going away for xmas. Now it won't even attempt to start with both cpu's - with one it will boot but at one of the hardware probes (just after keyboard) it restarts, as if someone is hitting the reset button. If it is failing hardware you may find no indication of the fault - the faulty hardware may cause the same effect as someone pressing the reset button - your logs would show normal operation then dmesg would show system boot with disks unmounted properly and starting (or delaying) fsck. On 13/1/05 8:06 AM, "Ted Mittelstaedt" <tedm@toybox.placo.com> wrote: > If this was something like a kernel panic there would be a > message in /var/log/messages > > If nothing is in there then it's probably failing hardware. > My experiences in those cases is that no matter what logging you > turn on, nothing gets logged, the machine just reboots. > > If it's a remote colocated server maybe the UPS it's on > is shot, and it's getting power fluctuations. Or maybe > it's overheating or it's clogged with dust. > > Ted > >> -----Original Message----- >> From: owner-freebsd-questions@freebsd.org >> [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Jim Pazarena >> Sent: Wednesday, January 12, 2005 10:40 AM >> To: freebsd-questions@freebsd.org >> Subject: 4.9 rebooting >> >> >> I have a remote server which has begun re-booting every few days. >> >> Are there any logs which I can examine that may provide a clue as to >> the reason? Or any logging I can turn "on/up" ? I realize that >> during a reboot, logs are seldom "up-to-date", but any clue would >> be handy. >> >> This is a remote co-located server which will take a fairly >> expensive trip to get hands-on with. I'd like to have ammunition >> at hand before I commit to the trip. >> >> Thanks, >> Jim >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- Shane Ambler Sales Department 007Marketing.com Shane@007Marketing.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BE0C8A12.21DB1%Shane>