Chapter 14. Configuring kdump in the web console

Procedure

1. In the web console, open the Kernel dump tab and start the kdump service by setting the Kernel crash dump switch to on.

2. Configure the kdump memory usage in the terminal, for example:

   $ sudo grubby --update-kernel ALL --args crashkernel=512M

   Restart the system to apply the changes.

3. In the Kernel dump tab, click Edit at the end of the Crash dump location field.

   

4. Specify the target directory for saving the vmcore dump file:

   • For a local filesystem, select Local Filesystem from the drop-down menu.

     

   • For a remote system by using the SSH protocol, select Remote over SSH from the drop-down menu and specify the following fields:

     • In the Server field, enter the remote server address.
     • In the SSH key field, enter the SSH key location.
     • In the Directory field, enter the target directory.

   • For a remote system by using the NFS protocol, select Remote over NFS from the drop-down menu and specify the following fields:

     • In the Server field, enter the remote server address.
     • In the Export field, enter the location of the shared folder of an NFS server.

     • In the Directory field, enter the target directory.

       Note

       You can reduce the size of the vmcore file by selecting the Compression checkbox.

5. Optional: Display the automation script by clicking View automation script.

   A window with the generated script opens. You can browse a shell script and an Ansible playbook generation options tab.

6. Optional: Copy the script by clicking Copy to clipboard.

   You can use this script to apply the same configuration on multiple machines.

Verification

1. Click Test configuration.

   

2. Click Crash system under Test kdump settings.

   Warning

   When you start the system crash, the kernel operation stops and results in a system crash with data loss.