This repository is focused on setting up kdump on OpenShift nodes. We created it to address situations where worker nodes freeze without warning, preventing us from troubleshooting the underlying cause. With kdump we can capture detailed crash dumps, providing the insights needed to diagnose and prevent these issues from recurring.
-
The importance of configuring kernel dumps <-- Recommended
-
Configuring kdump on the command line (RHEL8 CoreOS 4.12 and lower)
-
Configuring kdump on the command line (RHEL9 CoreOS 4.13 and upper)
-
Supported kdump configurations and targets (RHEL8 CoreOS 4.12 and lower)
-
Supported kdump configurations and targets (RHEL9 CoreOS 4.13 and upper)
-
A vmcore for your system may be smaller than you think! <-- Recommended
-
Untestand the Machine Config Pool (OpenShift Container Platform 4.x)
-
White Paper: Crash Utility by David Anderson <-- Recommended
-
Common kdump Configuration Mistakes <-- Recommended
-
How do I configure kdump for use with the RHEL 6, 7, 8 High Availability Add-On?
-
Setting up kdump in Red Hat Openshift Container Platform and Red Hat CoreOS
-
How to troubleshoot kernel crashes, hangs, or reboots with kdump on Red Hat Enterprise Linux
-
How to extract/unpack/uncompress the contents of the initramfs boot image on RHEL 7,8,9 ?
-
Kdump failes with "kdump: get_host_ip exited with non-zero status!"
-
kdump failure when network requires multiple nics to reach dump target
NOTE: The links provided below are for reference only, Always refer to the manual pages specific to your CoreOS version to ensure compatibility!