The CTDB IP address doesn't fail-over correctly when rebooting a Red Hat Storage peer node

Solution Unverified - Updated -

Issue

  • When a Red Hat Storage node running Clustered Trivial DataBase (CTDB) is hung and rebooted, the CTDB configured IP address does not fail-over to the other configured running nodes.

  • The following messages may be seen in the /var/log/log.ctdb log file:

...
2013/05/06 09:57:05.999968 [19435]: We are still serving a public address 'X.X.X.X' that we should not be serving.
2013/05/06 09:57:06.000010 [19435]: Trigger takeoverrun
2013/05/06 09:57:07.465090 [19435]: We are still serving a public address 'X.X.X.X' that we should not be serving.
2013/05/06 09:57:07.465135 [19435]: Trigger takeoverrun
2013/05/06 09:57:07.472498 [19380]: server/ctdb_takeover.c:787 release_ip of IP X.X.X.X is known to the kernel, but we have no interface assigned, has someone manually configured it?banning ourself
2013/05/06 09:57:07.472524 [19380]: Banning this node for 300 seconds
...

Environment

  • Red Hat Storage Server (RHSS) 2.1

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