top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Make server reboot by itself instead of dropping to kernel debugger

+1 vote
380 views

on OpenBSD if you put ddb.panic=0 into /etc/sysctl.conf, the server won't drop into debugger on kernel panic. Is there a similar setting for CentOS 6.4 / 64 bit?

posted Aug 23, 2013 by Dewang Chaudhary

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
I've ended up doing this (hope it's valid for CentOS 6.4):

# echo 10 > /proc/sys/kernel/panic
# echo "kernel.panic=10" >> /etc/sysctl.conf
commented Aug 23, 2013 by anonymous

1 Answer

+1 vote

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.

answer Aug 23, 2013 by Mandeep Sehgal
Similar Questions
0 votes
CentOS 6 guest OS does not detect reboot/shutdown signal from virt-manager

My setup is as follows:

Host OS: Debian Wheezy amd64 stock kernel (3.2), virt-manager v0.9.1

Guest VMs: A bunch of Linux based servers - CentOS 6, Debian 6/7, Ubuntu 12.04 (all amd64 with stock kernel). All of them defined using virt-manager GUI interface.

From the virt-manager, I am able to shutdown/reboot the Debian and Ubuntu guest OSs but not the CentOS 6 guests.

For the CentOS 6 guests, I have to resort to "Force off"

I have looked at the syslog and messages log files but do see anything to correlate between host and guest OS.

0 votes
device in use after a reboot in centos

I have a server with an 17tb scsi-storage. In past, the storage has a "jfs"-filesystem. Now i want to create a "ext4"-filesystem. I have update the e2fsprogs from 1.41 to 1.42 (16tb limit >1.41).

Now I have an 17tb-storage as /dev/sda1 with ext4. I can mount this device as /home/ (/etc/fstab /dev/sda1 /home/ ext4 defaults 1 2". Now I start a e2fschk /dev/sda1 (umounted). No error-messages are in
the screen.

If I now reboot the server, the server does not started:

I think thats can be a problem with the e2fsprogs 1.42, now i reinstall the server with the default e2fsprogs 1.41 from CentOS 6.4 and create only a 16tb /dev/sda1 partition with ext4. But if i start a "e2fschk
/dev/sda1" and reboot the server, i have the same message in the boot-screen and the server does not boot.

Why the system thinks that the device still be in use? How can i change this?

+1 vote
Forcing linux kernel 3 to recognize cdrom as hdX on centos

I have a problem with older version of anaconda linux installer. I have upgraded kernel in my distro, but, when this anaconda boot with new 3.4.52 kernel, can NOT find cdrom. As far as I understand, this is because the new kernel recognize cd drive as srX, scdX instead of older hdX with 2.6.18. At the moment I can not upgrade anaconda and forced this kernel to recognize it as before.

Are there any kernel command line argument, kernel config or something else for kernel 3.4.52 to recognize this cdrom as hdX?

0 votes
Diameter: What a Diameter agent does after the reboot of itself for pending answers ?

When a Diameter Agent forwards a request to the next-hop, it adds Route-Record AVP to the message before forwarding. And it also stores the request and later uses those the stored request to forward back the answer to originator of the request.
I want to know what a Diameter agent does with the stored request if it reboots ?

...