Hi, I have a small installation of Icinga 1.7 on Debian stable with around a hundred hosts and 350 services. All checks are active and locally done by Icinga itself, I do not (yet) use things like passive checks, check_ssh and/or check_nrpe. Event handlers are not in use either. Icinga reports to Icinga-Web via ido, but I usually use the "old" CGIs for historic reasons.
When I reload Icinga, it stops doing checks and updating the "old" CGIs data for about a minute while the disk keeps churning away at maximum usage, writing to /var. After about a minute, normal operation resumes. What is Icinga doing in that period? I am curious because it is mildly annoying that one has to wait for this period to happen before one sees the results of a configuration change, and that no checks are done in this time (which is a rather minor issue in my environment). Can anybody explain what is going on here? Thanks in advance. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users
