I encountered an odd bug in OMD 0.56 setup, not sure if this is known or a normal way it operates.
Steps to reproduce. - Setup a testsite with nagios as core. - Enable livestatus TCP socket option. - setup the host system to run mk agent - Start the site ; - use check_mk to add and register localhost to nagios (check_mk -I localhost ; check_mk -O localhost) - Verify correct operation through thruk/check_mk_multisite web interface. - Stop the site. - Switch to shinken as core. - Start the site. Socket tmp/run/live exists only when site is stopped, regardless of tmpfs settings or whether you erase the tmp/ completely before starting the site. This means that check_mk_multisite and thruk are completely useless and report problems about lack of socket or no available backends. After issuing omd stop, the socket reappears. I had no luck tracing what restores it, i only know that omd recreates /tmp contents on startup and removes stale sockets. Disabling the TCP socket option for livestatus makes it appear correctly after omd start with shinken as core. However passive check_mk results no longer update in any of the interfaces (except for the one service with active check). I can see all the services in shinken or other interfaces, but only the one with active checks updates - the rest slowly becomes outdated. Switching back to nagios, regardless of TCP socket settings restores proper operation. Is there any way to make those two work together?
_______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users
