Kdump fails due to unrecognized option '--message_level' in /etc/kdump.conf file

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8

Issue

  • Vmcore is not getting captured at target location though suffice space is allotted.

Resolution

  • The /etc/kdump.conf should be configured with valid Kdump parameters.
  • The --message-level parameter is accountable to specify the message types. The Users can restrict outputs printed by specifying message_level option.

Root Cause

  • The /etc/kdump.conf, has been configured as below :

    # grep -v "#" /etc/kdump.conf 

core_collector makedumpfile -l --message_level 1 -d 31
path /var/crash

  • From Serial console logs, we able to see that makedumpfile parameter --message-level has been set as --message_level which results in no vmcore at target location.

    kdump: saving vmcore-dmesg.txt complete
kdump: saving vmcore
makedumpfile: unrecognized option '--message_level'                       -->>> Invalid parameter passed
Commandline parameter is invalid.
Try `makedumpfile --help' for more information.

makedumpfile Failed.
kdump: saving vmcore failed
[FAILED] Failed to start Kdump Vmcore Save Service.
See 'systemctl status kdump-capture.service' for details.

Diagnostic Steps

  • Modify the /etc/kdump.conf file as below:

    # grep -v "#" /etc/kdump.conf 

core_collector makedumpfile -l --message-level 1 -d 31
path /var/crash

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments