Hmm, no ideas guys?
Should I open up a bug report for this?
Thanks,
-PJ
On Mon, Apr 22, 2013 at 11:29 AM, P J <pauljflists@xxxxxxxxx> wrote:
> Howdy,
>
> Running a round of updates from 6.3 to 6.4 and I'm seeing the following on
> all the servers.
>
> Want to make sure I'm not going to end up with a kernel panic if I reboot
> into the new kernel or have any other issues.
>
> Apr 22 11:10:21 www kdump: kexec: unloaded kdump kernel
> Apr 22 11:10:21 www kdump: stopped
> Apr 22 11:10:21 www kdump: mkdumprd: failed to make kdump initrd
> Apr 22 11:10:21 www kdump: failed to start up, config file incorrect
>
> I've never touched kdump.conf, or really used kdump at all..
>
> /etc/kdump.conf shows:
>
> #raw /dev/sda5
> #ext4 /dev/sda3
> #ext4 LABEL=/boot
> #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
> #net my.server.com:/export/tmp
> #net user@xxxxxxxxxxxxx
> path /var/crash
> core_collector makedumpfile -c --message-level 1 -d 31
> #core_collector scp
> #core_collector cp --sparse=always
> #extra_bins /bin/cp
> #link_delay 60
> #kdump_post /var/crash/scripts/kdump-post.sh
> #extra_bins /usr/bin/lftp
> #disk_timeout 30
> #extra_modules gfs2
> #options modulename options
> #default shell
> #debug_mem_level 0
> #force_rebuild 1
> #sshkey /root/.ssh/kdump_id_rsa
>
> Thanks in advance for any help or feedback.
> -PJ
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
