Red Hat Bugzilla – Bug 239788
kdump (scp, NFS) fail if you don't set Default Gateway
Last modified: 2007-11-30 17:07:44 EST
Description of problem:
kdump (scp,NFS) fail if you don't set Default Gateway.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure kdump (scp or NFS) on your local LAN.
In this example, I use NFS.
2. Remove Gateway setting from both /etc/sysconfig/network and
3. Test kdump.
# echo c > /proc/sysrq-trigger
ifup failed to setup network, so the kdump(NFS) failed to mount
NFS share. Following lines are log from serial console.
Full log is attached in next comment.
Creating block device ram6
Creating block device ram7
Creating block device ram8
Creating block device ram9
mapping eth0 to eth0
ifup: option with empty value " gateway"
eth0 failed to come up
Saving to remote location 192.168.1.145:/var/crash
mount: RPC: Unable to send; errno = Network is unreachable
mount: nfsmount failed: Bad file descriptor
mount: Mounting 192.168.1.145:/var/crash on /mnt failed: Bad file descriptor
Out of memory: Killed process 1025 (exe).
umount: Couldn't umount /mnt: Invalid argument
Creating root device.
Out of memory: Killed process 1033 (msh).
a) kdump (scp / NFS) should finish succesfully, even if the
system doesn't have Default Gateway setting.
Created attachment 154532 [details]
serial console ouput of kdump without default gateway setting
In short, don't do that.
Looking at your above description, I'm guessing that you have a step that you
omitted from your recreation:
1) Configure kdump (scp or NFS) on your local LAN.
2) Remove Gateway setting from both /etc/sysconfig/network and
=>3) Issue service kdump [re]start
4) echo c> /proc/sysrq-trigger
If you configure kdump to use a dump target that requires network services to
function, and that in turn requires a correct network configuration (which kdump
queries at service start time). If you break your network configuration, you
can't expect services that need that configuration to work properly, no more
than you would expect your network to come up if you had removed your router
configuration line and rebooted your system.
I'll add some logic to drop you to a shell prompt in the initramfs if ifup
doesn't succede, so as to avoid the cascade of failures that otherwise results,
but regardless of the resultant behavior, a broken configuration only results in
a non-functional service. This isn't a bug.