Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ 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)
How reproducible:
kernel crashdump
Steps to Reproduce:
/etc/kdump.conf:
...
path /tmp/
...
Actual results:
It created vmcore into /var/crash/127.0.0.1-xxxxxx.
Expected results:
It created vmcore into /tmp/ (arbitrary directory).
Please fix the kdump script.
--- Additional comment from maeno.masaki.co.jp 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 robotsari on 2010-07-15 16:16:16 EDT ---
Hi,
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.
Test case:
/etc/kdump.conf:
...
path /var/dump
...
echo c > /proc/sysrq-trigger
Actual results:
Full, readable core created in /var/dumps/2010-07-14-18\:14/vmcore
--- Additional comment from amwang on 2010-07-16 01:32:30 EDT ---
Sarina, your patch looks fine for me, I will take it. Thanks!
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.
http://rhn.redhat.com/errata/RHBA-2011-0736.html