You can use the below instructions to configure kdump on a Bright managed cluster. These instructions should work on RHEL/CentOS 7 and 8.
1. Install required packages
Install the kexec-tools in the software image:
# yum install kexec-tools –installroot=/cm/images/<image-name>
2. Modify the software image
Configure the software image to allow crashkernel memory and update the exclude list to avoid wiping out the crash path:
% softwareimage use <image-name>
% append kernelparameters ” crashkernel=128M” # please make sure that the append starts with a blank space
% category use <category-name>
% set excludelistsyncinstall
(add the following lines to exclude; save changes and exit)
no-new-files: – /var/crash/*
3. Enable the kdump service in the software image:
# chroot /cm/images/<image name>
# chkconfig kdump on
4. Confirm kdump is configured correctly
Make sure that the kdump service is active when the node comes up after reboot.
[root@node001 ~]# cat /proc/cmdline
[root@node001 ~]# service kdump status
Kdump is operational
5. Generated a kernel panic to test.
You can then try to generate a kernel panic with “echo c > /proc/sysrq-trigger” and see if the crash report will be generated
successfully “WARNING this will crash the node and cause a kernel panic”: