Bug with two nagios services starting

[mguthrie]

Thanks for the heads up. Our goal is to have this fixed for good in our next update.

[niebais]

We may have found the core cause of the multiple Nagios instances problem. The database might have been corrupted somehow. The multiple Nagios instances problem seems to have gone away for several days after we ran this command:

service ndo2db stop
service nagios stop
service mysqld stop
/usr/local/nagiosxi/scripts/repairmysql.sh nagios *


(note I changed the repairmysql.sh script a little to look like this: $cmd --safe-recover -r $t)

Once I ran that command, I killed all our nagios processes, and restarted Nagios. About 3 problems I had posted went away (for now). It's quite possible that something corrupted our database in Nagios and that part I'm still worried about, but if weird stuff starts happening, rebuilding the database might be the best solution.

[mguthrie]

We did discover a bug that was implemented in 2011R1.1 that increased the probability of table corruption in mysql. It was fixed in 2011R1.2 as soon as we found it because of the wide range of problems that could create.

Our lead developer also just revised the init script, which should take care of the multiple instances issue for good. This should take effect starting in 2011R1.4 when it is released. The bug that was discovered in the init script and multiple instances may have also your other issue with the host names not being updated correctly.

[niebais]

Ok,
Version 2011R1.5 seems to have fixed this problem as well. Great work guys!

[mguthrie]

Thanks for the update! That's good new!