ctdb - public ip is assigned to us but not on an interface - error

[Martin Schwenke]

On Sat, 28 Jan 2017 15:12:52 +0000, lejeczek <peljasz at yahoo.co.uk>
wrote:

> > On 27/01/17 23:52, Martin Schwenke wrote:  

> >> Perhaps the 10.interface event script is not enabled.  It 
> >> actually adds
> >> the IP to the interface.  What does the following say?
> >>
> >>    ctdb scriptstatus takeip

> got it. After I stopped looking at/for trivial things long 
> ago, now when I got my eyes tired, I had another look at 
> trivial stuff..
> a few event scripts lost(?) exec flags, namely: 10.external, 
> 11.routing and 10.interface ... why? how? (and if it was rpm 
> update the culprit then why only VM cluster??)
> at times like this I think: gee... [...] cosmic radiation.

Sometimes it does seem like that.

"rpm -V ctdb" should be able to tell you.  However, if you have already
re-enabled it then that won't tell you much.

You can enable it using "ctdb enablescript 10.interface".

Note that 10.external should be disabled by default.  It can be enabled
(and 10.interface enabled) if you're doing failover some other way.

If you find that 10.interface and 11.routing are not enabled by default
in the RPM package then I would encourage you to file a distro bug,
because this would affect a lot of people.

I'm glad you have worked it out...  :-)

peace & happiness,
martin