Why does kdump fail to capture a vmcore when BOOTPROTO=static is set in the slave interface configuration file?

Solution Verified - Updated -

Issue

  • Why does kdump fail to dump vmcore when BOOTPROTO=static is set in the slave interface configuration file?

Note: Following message is noticed on the console

enslaving eth0 to bond0
BusyBox v.1.2.0 multi-call binary

Usage ifconfig  [-a] <interfaces> [<address>]

Configure a network interface
--
--
--
enslaving eth1 to bond0
ip: RTNETLINK answers: File exists
ip: RTNETLINK answers: File exists
Saving to remote location nfs:/path

Environment

  • Red Hat Enterprise Linux 5 update 8
  • Network bonding
  • kexec-tools 0:1.102pre-154.el5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.