• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • VCS
  • Interview Questions
  • Database
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

Configuring Kdump Output Location in CentOS/RHEL 9

by admin

Kernel crashes are inevitable in any computing environment, and having a reliable mechanism to capture diagnostic information is crucial for effective troubleshooting and system recovery. In Red Hat Enterprise Linux (RHEL) 9, the Kdump feature provides a powerful solution for capturing kernel crash data. While Kdump is installed by default in RHEL 9, configuring the output location ensures that crash dumps are stored in a location that best suits your environment’s needs.

By default, Kdump files are stored in the /var/crash directory in RHEL 9. However, administrators may want to save crash dumps to other locations, such as NFS mounts, externally mounted drives, or remote file servers. This can be achieved by editing the /etc/kdump.conf file.

To configure the Kdump output location in RHEL 9, follow these steps:

1. Edit the kdump.conf File:
Open the /etc/kdump.conf file in a text editor and remove the # comment character at the beginning of each line that you want to enable. This allows you to specify alternative output locations for Kdump files.

2. Define Output Locations:
Use the path keyword to specify a new directory location for storing Kdump files. For example, to save crash dumps to the /usr/local/cores directory, add the following line to the kdump.conf file:

path /usr/local/cores

Additionally, you can use the raw keyword to output directly to a specific device in the /dev directory. You can also specify the output file system for a particular device using its label, name, or UUID.

For Example:

ext4 UUID=5b065be6-9ce0-4154-8bf3-b7c4c7dc7365

3. Transfer Kdump Files Over SSH:
Kdump files can also be transferred over a secure shell (SSH) connection. To configure this, specify the SSH connection details and SSH key in the kdump.conf file.

For Example:

$ ssh user@example.com
$ sshkey /root/.ssh/mykey

4. Export Kdump Files to a Network Share:
Another option is to export Kdump files to a compatible network share. This can be achieved by specifying the NFS server and directory in the kdump.conf file.

nfs example.com:/output

5. Enable the Kdump Service:
After configuring the output location for Kdump, enable the kdump service to apply the changes.

$ sudo systemctl enable --now kdump.service

By following these steps, administrators can customize the Kdump output location in RHEL 9 to best suit their environment’s requirements. Whether saving crash dumps locally, on remote servers, or network shares, configuring the Kdump output location ensures that critical diagnostic information is readily available for troubleshooting kernel crashes.

Filed Under: Linux

Some more articles you might also be interested in …

  1. cmctl: A CLI tool that can help you to manage cert-manager resources inside your cluster
  2. duplicacy: A lock-free deduplication cloud backup tool
  3. nautilus Command Examples in Linux
  4. “git svn” Command Examples
  5. CentOS / RHEL : How to setup session idle timeout (inactivity timeout) for ssh auto logout
  6. “hg commit” Command Examples
  7. git authors: Generate a list of committers of a Git repository
  8. id Command Examples in Linux
  9. pihole Command Examples in Linux
  10. idnits Command Examples

You May Also Like

Primary Sidebar

Recent Posts

  • Vanilla OS 2 Released: A New Era for Linux Enthusiasts
  • mk Command Examples
  • mixxx Command Examples
  • mix Command Examples

© 2025 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright