Red Hat Bugzilla – Bug 626746
Please reflect the setting of "path" line in /etc/kdump.conf
Last modified: 2015-01-04 17:59:42 EST
+++ This bug was initially created as a clone of Bug #379521 +++
Description of problem:
The setting of "path" line on /etc/kdump.conf is not reflected.
The dumpfile is always saved to "/var/crash".
Please fix to reflect the setting of "path" line by correcting
the "/etc/init.d/kdump" script.
Version-Release number of selected component (if applicable):
kexec-tools: RHEL5.0 - RHEL5.1 (1.101-194.4.el5)
Steps to Reproduce:
It created vmcore into /var/crash/127.0.0.1-xxxxxx.
It created vmcore into /tmp/ (arbitrary directory).
Please fix the kdump script.
--- Additional comment from firstname.lastname@example.org on 2007-11-18 21:07:37 EST ---
If "ext3" line is "another partition (ex: /dev/cciss/c0d0p6)" and
"path" line is "/crash1", I confirmed that I could get a dumpfile.
If "ext3" line is "rootfs partition (ex: /dev/cciss/c0d0p1)" and
"path" line is "/crash2", I could get a dumpfile.
If "ext3" line is "not set" and
"path" line is "/crash3", I could not get a dumpfile.
The system causes "kernel panic on 2nd kdump kernel" or "reboot without get a
dumpfile on 2nd kdump kernel".
However, it is not possible to set it by "system-config-kdump" like it.
Therefore, its problem is not a major problem.
Please close this issue.
--- Additional comment from email@example.com on 2010-07-15 16:16:16 EDT ---
I have also encountered the problem described in the original comment, but it is really easy to fix by inserting a few lines in kdump.init. I have attached my proposed patch. It tests and works on my system.
echo c > /proc/sysrq-trigger
Full, readable core created in /var/dumps/2010-07-14-18\:14/vmcore
--- Additional comment from firstname.lastname@example.org on 2010-07-16 01:32:30 EDT ---
Sarina, your patch looks fine for me, I will take it. Thanks!
Verified in kexec-tools-2.0.0-145.el6 and by code review.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.