Make Server Reboot By Itself Instead Of Dropping To Kernel Debugger

Home » CentOS » Make Server Reboot By Itself Instead Of Dropping To Kernel Debugger
CentOS 5 Comments

Hello,

on OpenBSD if you put ddb.panic=0
into /etc/sysctl.conf, the server won’t drop into debugger on kernel panic.

Is there please a similar setting for CentOS 6.4 / 64 bit?

The background is that I have a new dedicated server with Haswell CPU
and once a month it is stuck, displaying kernel trace (the other users at my hoster have similar problems).

So the users of my web site complain.

I’d prefer my web server to just reboot

Thank you Alex

5 thoughts on - Make Server Reboot By Itself Instead Of Dropping To Kernel Debugger

  • I’ve ended up doing this (hope it’s valid for CentOS 6.4):

    # echo 10 > /proc/sys/kernel/panic
    # echo “kernel.panic” >> /etc/sysctl.conf

  • If your servers have a watchdog timer (most with IPMI/iLO/iDRAC/etc do), you can enable it. The OS will then have to kick the timer periodically to restart it’s counter. If the OS panic’s, it won’t be able to reset the timer. Once the timer expires, it reboots.

  • Thank you, I have this

    # dmesg|grep -i watch NMI watchdog enabled, takes one hw-pmu counter. iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07rh

    do you have any tips or doc pointers?

  • I am not sure though, if I need to start the watchdog daemon at all –
    because I altready have these lines in my dmesg:

    iTCO_vendor_support: vendor-support=0
    iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07rh iTCO_wdt: Found a Lynx Point TCO device (Version=2, TCOBASE=0x1860)
    iTCO_wdt: initialized. heartbeat0 sec (nowayout=0)

    Does it mean there is some “hardware watchdog”
    active at my CentOS 6.4 / 64 bit (Haswell CPU) server already?

    Thank you for any hints Alex

LEAVE A COMMENT