- "default halt" in kdump conf doesn't work and the system reboots after dumping a vmcore file.
path /var/crash core_collector makedumpfile -c -l --message-level 1 -d 31 default halt
- As per the parameter definition in /etc/kdump.conf file, if the default action is halt the system should halt after a crash regardless of success or failure.
# default # - Action to preform in case dumping to intended target # fails. If no default action is specified, "reboot" # is assumed default. # reboot: If the default action is reboot simply reboot # the system and loose the core that you are # trying to retrieve. # halt: If the default action is halt, then simply # halt the system after attempting to capture # a vmcore, regardless of success or failure. # poweroff: The system will be powered down # shell: If the default action is shell, then drop to # an shell session inside the initramfs from # where you can try to record the core manually. # Exiting this shell reboots the system. # Note: kdump uses bash as the default shell. # dump_to_rootfs: If non-root dump target is specified, # the default action can be set as dump_to_rootfs. # That means when dump to target fails, dump vmcore # to rootfs from initramfs context and reboot.
- Red Hat Enterprise Linux 7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.