Cluster service start up fails with: IPv4 address collision <Virtual IP Address>

Solution Verified - Updated -

Issue

  • starting a cluster service on one cluster node fails with following error message:
Jun  4 14:03:27 node2 rgmanager[30755]: Starting stopped service service:<service_name>
Jun  4 14:03:28 node2 rgmanager[864]: Adding IPv4 address 10.10.10.50/20 to bond0
Jun  4 14:03:28 node2 rgmanager[910]: IPv4 address collision 10.10.10.50
Jun  4 14:03:28 node2 rgmanager[30755]: start on ip "10.10.10.50" returned 1 (generic error)
Jun  4 14:03:28 node2 rgmanager[30755]: #68: Failed to start service:<service_name>; return value: 1
Jun  4 14:03:28 node2 rgmanager[30755]: Stopping service service:<service_name>
Jun  4 14:03:28 node2 rgmanager[30755]: Service service:<service_name> is recovering
  • The rg_test output is as below:
# rg_test test /etc/cluster/cluster.conf start service <service_name>
. . . . . . . .
Starting <service_name>...
<debug>  /dev/dm-7 already mounted
/dev/dm-7 already mounted
<debug>  /dev/dm-8 already mounted
/dev/dm-8 already mounted
<debug>  Link for bond0: Detected
Link for bond0: Detected
<info>   Adding IPv4 address 10.10.10.50/20 to bond0
Adding IPv4 address 10.10.10.50/20 to bond0
<debug>  Pinging addr 10.10.10.50 from dev bond0
Pinging addr 10.153.10.50 from dev bond0
<err>    IPv4 address collision 10.10.10.50
IPv4 address collision 10.10.10.50
Failed to start <service_name>

Environment

  • Red Hat Enterprise Linux (RHEL) 6 (with the High Availability or Resilient Storage Add Ons)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content