cause of reboot
Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org smime.p7s Description: S/MIME cryptographic signature
Re: cause of reboot
On Mon, 30 Sep 2013 17:24:18 +0300 Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ That's likely something in the daily run going wrong, try disabling items in there one by one (by editing /etc/periodic.conf - which probably doesn't yet exist so create it and look in /etc/defaults/periodic.conf for details) until you get through a night without a reboot. Then the next step is to figure out why whatever is crashing the system does so, but first let's find out what. -- Steve O'Hara-Smith st...@sohara.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
Yes I checked also it , such as ; grep -i 'reboot' /root/scripts/* -R grep -i 'halt' /root/scripts/* -R grep -i 'shutdown' /root/scripts/* -R 30.09.2013, 17:33, Jason Hellenthal jhellent...@dataix.net: Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
And /etc/ ? And /var/cron ? On Sep 30, 2013, at 11:00, Emre Çamalan mail...@yandex.com wrote: Yes I checked also it , such as ; grep -i 'reboot' /root/scripts/* -R grep -i 'halt' /root/scripts/* -R grep -i 'shutdown' /root/scripts/* -R 30.09.2013, 17:33, Jason Hellenthal jhellent...@dataix.net: Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org smime.p7s Description: S/MIME cryptographic signature
Re: cause of reboot
Also . . . grep -ri . . . On Sep 30, 2013, at 11:06, Jason Hellenthal jhellent...@dataix.net wrote: And /etc/ ? And /var/cron ? On Sep 30, 2013, at 11:00, Emre Çamalan mail...@yandex.com wrote: Yes I checked also it , such as ; grep -i 'reboot' /root/scripts/* -R grep -i 'halt' /root/scripts/* -R grep -i 'shutdown' /root/scripts/* -R 30.09.2013, 17:33, Jason Hellenthal jhellent...@dataix.net: Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org smime.p7s Description: S/MIME cryptographic signature
Re: cause of reboot
On 9/30/13 11:08 PM, Jason Hellenthal wrote: Also . . . grep -ri . . . On Sep 30, 2013, at 11:06, Jason Hellenthal jhellent...@dataix.net wrote: And /etc/ ? And /var/cron ? On Sep 30, 2013, at 11:00, Emre Çamalan mail...@yandex.com wrote: Yes I checked also it , such as ; grep -i 'reboot' /root/scripts/* -R grep -i 'halt' /root/scripts/* -R grep -i 'shutdown' /root/scripts/* -R 30.09.2013, 17:33, Jason Hellenthal jhellent...@dataix.net: Did you check for the command reboot in all of the periodic scripts and cron jobs as well as the command shutdown ? On Sep 30, 2013, at 10:24, Emre Çamalan mail...@yandex.com wrote: Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ I checked dmesg -a , it has only generic things no other things. I checked /var/log/messages I wrote script and checked swapinfo , cpu and memory but all of them was normal before reboot. I checked crontab and scripts. I checked crashinfo but no dump from kernel. I didn't find any useful info from this commands. I checked praudit /var/audir/20130930..CrashRecovery and I didn't understand very well from this file but I think this means my machine crash and reboot isn't it?? And How can I understand what is the reason of rebooting my FreeBSD8.3 server. Please help I need to find cause of reboot.. ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org Firstly, does this machine have the kernel debugger installed? if not then a kernel page fault will look like a reboot. if you know when this is going to occur, then I suggest that you set up some logging of every new process run, to a second machine, or possibly you might just ssh int the machine and leave 'top' running when it reboots you shoud get a snapshot of what's going on. you could just rename 'reboot' and see if it still happens. If not, then replace reboot (and friends) with a script that reports who called it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
Le Mon, 30 Sep 2013 17:24:18 +0300, Emre Çamalan mail...@yandex.com a écrit : Hi, my server reboots every night and same o'clock last 10 days. But this machine's uptime was 96days. Suddenly reboot this machine and now this continue every night again and again. I didn't find any reason and I didn't change anything else. I looked last command, reboot ~ ~ AM 03.15 ~ The last time It happened (one month ago) to me it was the hard disk (periodic scripts read a large part of the disk). If the disk is smart capable try a full test with smartctl (sysutils/smartmontools) HTH, regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
Patrick Lamaiziere wrote: [snip] I looked last command, reboot ~ ~ AM 03.15 ~ The last time It happened (one month ago) to me it was the hard disk (periodic scripts read a large part of the disk). If the disk is smart capable try a full test with smartctl (sysutils/smartmontools) My gateway/firewall/mail/ids router box at home has 2 GB RAM in it, so normally it has enough extra room that nothing ever pushes over into swap with one exception: the periodic run at 0300. It is generally never more than just a few kilobytes, but I find it slightly surprising nonetheless. If a sector (or more) on the drive that is backing the swap partition has gone bad it might not even be noticeable until something pages out to swap (like my 0300 periodic run). If the drive is a WD the 'Quick' test using the manufacturers' wddiags utility should spot it, and is non-destructive. I have occasionally seen the full test not destroy data - but I wouldn't count on it being non- destructive. However, as long as the remap area isn't full the long test will repair the drive by relocating and mapping out the bad spot. When this silent fading away of magnetic media occurs wrt to higher-end RAID controllers the scrub function in the controller BIOS is where you would want to go. The other problem relative to this that I've run into is the apple before the cart syndrome around backups. I have seen dump fail to allow for backing up data prior to using the full wddiags to repair a drive so you kinda get stuck. If the full test is going to wipe the drive and you can't generate a fresh current backup you're stuck only being able to restore whatever is the last good backup you have on hand. Wouldn't surpise me at all if this were to turn out to be the drive just recently grew one or more bad spots. A bad spot or few on an old drive that gets repaired I might continue to use the drive for a while, maybe even for like a year time-frame wise. If 2 months later it starts growing more bad spots the drive goes in the rubbish bin. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
kpn...@pobox.com wrote: [snip] While we're throwing ideas onto the table let me mention power supplies. Power supplies and hard drives are in a race to see which one will fail first. It may be that the power supply is marginal and added load from the drives being hit hard may send it over the edge. How heavily loaded is the machine in question? Absolute and total agreement with this. As they age and the filter caps leak and dry out more it will eventually become apparent. But in the meantime the output DC can just about meet spec up until really loaded. Then the ripple becomes so excessive it's not quite DC any longer. You can clearly see it using an oscilloscope. The 0300 AM periodic does hammer a machine enough to possibly push a marginal power supply over the edge. I once had a box where the RAM chips would sing with a high-pitched whistle only during the 0300 periodic run. It sounded just like the horizontal output on a television right before destruction. :-) [snip] -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cause of reboot
On Mon, 30 Sep 2013 20:32:39 -0400, Michael Powell wrote: kpn...@pobox.com wrote: [snip] While we're throwing ideas onto the table let me mention power supplies. Power supplies and hard drives are in a race to see which one will fail first. It may be that the power supply is marginal and added load from the drives being hit hard may send it over the edge. How heavily loaded is the machine in question? Absolute and total agreement with this. The idea of a hardware problem looks more and more obvious here. A software configuration problem could be located by diff'ing the currently used files against stock files, or by checking the logs of a versioning system (if you use one to track your local configuration file changes, for example in a CVS reposi- tory). It could be a matter of power (by more than usual drain when the machine is heavily loaded), but also a file system inconsis- tency is possible. In case the machine is using a background fsck that silently fails to deal with a specific damage, using background_fsck=NO in /etc/rc.conf to _definitely_ bring the file systems up _clean_ prior to multi-user mode booting would probably be a good idea. Using smartctl to check the hard disks SMART data would make sure the disk is not dying (and the reboot is an effect of that). Monitoring the server when (or while) it reboots would surely be interesting. Maybe open some sessions to have a close look at programs like top, systat -v and mbmon (to check for temperatures and voltages) - and when run at 1 second intervals, it should be possible to obtain a good system status diagram of the last state before reboot, when the connection drops. I once had a box where the RAM chips would sing with a high-pitched whistle only during the 0300 periodic run. It sounded just like the horizontal output on a television right before destruction. :-) I have heared something comparable from a graphics card when developing some OpenGL demo stuff. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
