ips conflict?

[Oswald]

hi guys, 

have some of you seen such error before?

this "may be" is a real ip conflict????

2011/11/15 02:57:33  INFO     Removed role 'writer(172.24.4.80)' from host 'db1'

2011/11/15 02:57:33 ERROR Can't send offline status notification to 'db1' - killing it!

2011/11/15 02:57:33 FATAL Could not kill host 'db1' - there may be some duplicate ips now! (There's no binary configured for killing hosts.)

2011/11/15 02:57:34 ERROR Check 'mysql' on 'db1' has failed for 14 seconds! Message: ERROR: Connect error (host = 172.24.4.72:3306, user = mmm_monitor)! Can't connect to MySQL server on '172.24.4.72' (4)

After this, the system crashed.

[Mike!]

My guess is, that the host had already crashed. Since mmm_mond could
no longer reach mmm_agentd (on db1), there was no way that mmm_mond
could be sure that db1 had in fact released the writer IP. Ideally you
would have an alternative route to your db servers, or at least an
alternative way of "killing" them, to make sure an ip conflict could
never occur.

Mike

[Manuel Arostegui Ramirez]

2011/11/17 Mike! <nib...@gmail.com>

What I have is a killing_host script that shuts down the port in the switch if the mmm_agent cannot be reached. That way you are sure that there will be no duplicate IPs in production.

Hope this helps,

Manuel.