Hi Markus, don't know how to prevent this (at least not at the moment), but one hint:
You don't have to reload/restart your whole OMD site after config updates done in dot-mk files (manually or via WATO), only nagios. This can be done with 'cmk -O' (reload) or 'cmk -R' (restart). Same happens when changes are applied in multisite/WATO. Have you tried this? HTH, Marcel 2013/3/4 Markus Joosten <[email protected]> > ** > > Hello list, > > > > i have been encountering a strange behaviour while using "omd reload" on > my sites (using both Ubuntu 10.04 and 12.04, tested with omd-0.46, omd-0.52 > and omd-0.56): > > Every 2nd time i issue said command, my omd site ends up with Nagios in a > "stopped" state. > > > > To reproduce, issue the following command at least twice: > > omd reload; omd status > > > > It doesn't matter, if i issue that command as root or as the user of my > site (in my case: "nagios"). > > > > Is that a known problem? What can be done in order to prevent reloading > causing a stop of my OMD sites? > > I'd like to use reload in favour of restart, because restarts can take > quite a long time.. > > > > Regards, > > Markus > > _______________________________________________ > omd-users mailing list > [email protected] > http://lists.mathias-kettner.de/mailman/listinfo/omd-users > >
_______________________________________________ omd-users mailing list [email protected] http://lists.mathias-kettner.de/mailman/listinfo/omd-users
