Red Hat Bugzilla – Bug 457758
/sbin/mkdumprd parses comment lines of /etc/mdadm.conf
Last modified: 2009-09-09 01:14:18 EDT
Description of problem:
/sbin/mkdumprd confuses itself by parsing comment lines in /etc/mdadm.conf. A user had "level=0" instead of "level=radi0" in a commented-out line of /etc/mdadm.conf (he had been trying to set up a raid0 array). Then he made a change to /etc/kdump.conf to add a needed kdump_pre script. Then he tried to do service kdump restart. /etc/mkdumprd got:
No module 0 found for kernel 2.6.18-92.el5, aborting.
Failed to run mkdumprd
Starting kdump: [FAILED]
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add a commented-out line to /etc/mdadm containg "level=0".
2. Edit /etc/kdump.conf.
3. service kdump restart
You get the error shown above. Then you spend a long time trying to figure out what module "0" is... Then you eventually find the comment line in /etc/mdadm.conf and delete it.
/sbin/mkdumprd should ignore comment lines.
Created attachment 313385 [details]
patch to correct parsing of mdadm.conf
Please try this patch and confirm that it fixes the problem. Thanks!
Looks like the patch works. The original user has already reinstalled his system; I hacked up the mdadm.conf on my system to have a comment line of the problematical sort and then edited /etc/kdump.conf and did service kdump restart. It now successfully ignores the comment. Thanks!
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Fixed in -30.el5. 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.