kdump_local

The kdump_local test crashes the host under test (HUT) and writes a vmcore file to the local /var/crash directory. You can run this test to verify that the kdump service successfully captures, stores, and validates critical diagnostic data after a system crash.

What the test covers
The kdump_local test uses kdump to verify that the system captures a valid vmcore file after a crash. It also confirms that the file is stored locally.
RHEL version supported
  • RHEL 8
  • RHEL 9
  • RHEL 10
What the test does

The test performs the following tasks:

  • Crashes the host under test (HUT).
  • Writes a vmcore file to the local /var/crash directory.
  • Validates the vmcore file.
Preparing for the test
Ensure the rhcertd process is running on the HUT.
Running the test
  1. Log in to the HUT.
  2. Run the following command:
    # rhcert-run
  3. Select the kdump_local test.
  4. Wait for the HUT to restart after the crash. The kdump service displays messages while saving the vmcore file to the /var/crash directory. After the vmcore file is saved, the HUT restarts.
  5. Log in to the HUT after reboot, the rhcert suite verifies if the vmcore file exists, and if it is valid. If the file does not exist or is invalid, the test fails.
Run time

The run time of the kdump_local test varies. Factors include the amount of RAM in the HUT, disk speed, and reboot time.

For example, consider a 2013-era workstation with 8 GB RAM, a 7200 RPM 6 Gb/s SATA drive, and a 1.5-minute reboot time. This configuration completes the test in about four minutes, including the reboot. Any other mandatory pre-and post-run tests contribute to the overall runtime.