Hi, it's me again ;) Your fix is working. But now there is something else with the current version:
When I do a arbiter restart the hosts are tagged as "notifications for this host is disabled", as "commented" or somethimes even as "checks for this host have been disabled" in Thruk. When I do a shinken restart Thruk blames that there is no backend available. But after one minute (one minute after shinken started) its working (I reloaded the page during that minute several times). When I stop shinken and than start it, everything is fine. Even the states in Thruk are immediately updated (so I see no "no backend available" or in worstcase for a minimum of some seconds) markus Am Mittwoch, den 18.05.2011, 15:11 +0200 schrieb nap: > > > On Wed, May 18, 2011 at 2:26 PM, nap <napar...@gmail.com> wrote: > > > On Wed, May 18, 2011 at 2:19 PM, Markus Elger > <markus.el...@unister.de> wrote: > > Hi, > > There are two hosts with one service for each defined. > When I delete one host (and his service) and then do a > "arbiter restart" > the host and service stays in shinken. Only when I do > a complete > "shinken restart" everything is normal and the > host/service is gone. > > When I do this the other way around (adding a host and > do a "arbiter > restart") it works. > > markus > > Hi, > > It's very very strange. There is hosts and services property > but they are not tagged as "retention", and even if they were, > an host cannot be add in hte "global host list" with just > retention. > > I'll try to reproduce it, but the problem should be somewhere > else than retention I think (or I hope...). > > > Hi, > > I reproduced it, and in fact the problem was in the LiveStatus module > (yes, hard to find ;) ). > > This last one get all creation and update data and re-create host and > service objects. But it just add new ones when it got a message from a > new scheduler run (like your arbiter restart did produce). Now, it > clean all previously added hosts and service from this run before > re-push them. So we are sure that deleted ones will not be still > present. > > Now it's fixed :) > > > Jean > > ------------------------------------------------------------------------------ > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applications - including clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ Shinken-devel mailing list > Shinken-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shinken-devel ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
