The only thing worse than a crash is not knowing why it happened. Insights can make sure kdump is there for you.
Recovery is by far the most important first step to take after a system goes down. However, after your systems have recovered, you'll want to perform some level of root cause analysis in order to understand why the crash happened and how to prevent future similar events. This type of analysis is impossible to perform without access to pre-crash system information.
Several weeks ago we published a blog entitled Disaster Recovery, which outlined how many systems would be unable to properly generate a vmcore at the point of failure. You don’t want to be in this situation, which is why Red Hat Insights has developed rules to make sure that kdump is fully functional. Checkout the rules below, which detect common misconfigurations of kdump.
| Rule | Description | Reference |
|---|---|---|
| Failure to generate a vmcore when kdump and HP ASR are both enabled | There is a conflict between the HP Advanced Server Recovery Daemon (ASRD) and the kdump utility which can result in a system restart if vmcore collection exceeds the ASR timeout. | How can I disable Automatic System Recovery (ASR) on HP systems |
| Failure to generate a vmcore when tab characters exist in kdump configuration file | When tab characters exist in the kdump configuration file, kdump fails to generate a vmcore. | Why does kdump not work and I see "msh: can't execute 'makedumpfile': No such file or directory" in the kdump output? |
| Failure to generate a vmcore over the network when missing bonding option parameter in kdump configuration file | When there is no bonding option parameter specified in kdump.conf and kdump is configured to dump vmcores over the network, vmcore generation will fail. | kdump doesn't accept module options from ifcfg-* files |
| Failure to generate a vmcore when systems are configured with 250 or more LUNs | When kdump is enabled and the system is configured with 250 or more LUNs, kdump fails to generate a vmcore. | RHEL6: kdump on a system with many LUNs never finishes, or shows "soft lockups" |
| Failure to generate a vmcore when inline comments exist in kdump configuration file | When inline comments exist in the kdump configuration file, kdump fails to generate a vmcore. | Red Hat Enterprise Linux kdump not creating a vmcore file when inline comments are used in /etc/kdump.conf |
| Failure to generate a vmcore when Intel IOMMU extensions are enabled | When Intel IOMMU extensions are enabled in the kernel, kdump fails to generate a vmcore. | Cannot collect a vmcore with kdump while Intel IOMMU is enabled |
| Failure to generate a vmcore when using older P410i/P220i controller firmware versions on HP BL460C G7 systems | When using older P410i/P220i controller firmware versions on HP BL460C G7 systems, kdump fails to generate a vmcore. | Why Kdump fails/ hangs on "HP BL460c G7" using "P220i/P410i" controller? |
| Failure to generate a vmcore when kdump is configured to save to local storage using HPSA or CCISS drivers | When kdump is configured to save the core dump to local storage using HPSA or CCISS drivers, it fails to generate a vmcore. | Why does kdump fail on HP system using the 'hpsa' driver for storage in Red Hat Enterprise Linux 6? |
| Failure to generate a vmcore on CCISS targets when firmware version is prior to v5.06 | When kdump is configured to save the core dump to a CCISS target, it fails if the firmware version is prior to v5.06. | kdump failed to dump core file to cciss target running firmware versions lower than v5.06 |
| Failure to generate a vmcore when saving to an SSH/NFS resource | When kdump is configured to save a core dump to an SSH/NFS resource when using a static IP and no DNS setting, it fails to generate a vmcore. | Kdump over network requires DNS1 variable set when static IP address is used. |
Register your machines now and always have the necessary information to diagnose a crashed system.
About The Author
Red Hat
Comments