Translated message

A translation of this page exists in English.

kdump.conf の default halt が動作せず、vmcore ファイルをダンプしたあとシステムが再起動する

Solution Unverified - Updated -


  • kdump.conf の "default halt" が動作せず、vmcore ファイルをダンプしたあとシステムが再起動します。


path /var/crash
core_collector makedumpfile -c -l --message-level 1 -d 31
default halt
  • /etc/kdump.conf ファイルのパラメーターの定義によると、デフォルトのアクションが停止した場合は成功か失敗に関わらずクラッシュしてシステムが停止します。
# 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
  • kexec-tools

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content