CTDB We are still serving a public address...

[patrick medina]

Hello everyone,

I thought I had CTDB down, but it looks like I'm running into another
issue.

I have 2 nodes with 2 public addresses this way I can RRDNS, this worked
fine and was tested for  until I thought it was good to go.  Last night one
of our nodes went down and after the reboot and I'm getting the following
in the logs:  (The 2nd node is up and happy, but this guy remains on
unhealthy)


2012/10/27 19:53:00.678119 [ 1510]: server/ctdb_takeover.c:813 release_ip
of IP x.x.x.x is
known to the kernel, but we have no interface assigned, has someone
manually configured it? Igno
re for now.
2012/10/27 19:53:00.678203 [ 1510]: server/ctdb_takeover.c:813 release_ip
of IP x.x.x.x is
known to the kernel, but we have no interface assigned, has someone
manually configured it? Igno
re for now.
2012/10/27 19:53:00.679001 [ 1510]: Forced running of eventscripts with
arguments ipreallocated
2012/10/27 19:53:00.817548 [ 1510]: CTDB_WAIT_UNTIL_RECOVERED
2012/10/27 19:53:00.817622 [ 1510]: server/ctdb_monitor.c:257 wait for
pending recoveries to end
. Wait one more second.
2012/10/27 19:53:00.850736 [ 1510]: Recovery has finished
2012/10/27 19:53:01.818042 [ 1510]: CTDB_WAIT_UNTIL_RECOVERED
2012/10/27 19:53:01.818115 [ 1510]: server/ctdb_monitor.c:257 wait for
pending recoveries to end
. Wait one more second.
2012/10/27 19:53:01.863591 [recoverd: 1649]: We are still serving a public
address 'x.x.x.x
' that we should not be serving.
2012/10/27 19:53:01.863630 [recoverd: 1649]: We are still serving a public
address 'x.x.x.x
' that we should not be serving.

Did I configure RRDNS wrong, on my dev box this worked like a charm but
once I went production it's not so happy.  :/

Thanks,
PM