On Sun, 29 Jul 2012, Marc Haber wrote:
> I see. It should log this so that one can immediately know what is
> going on there.
It does -- indirectly. If one examines the icinga.log file,
one will see a line of "Event loop started..."; this indicates that
the main event loop has started and scheduled events will now happen
as expected. Before that, they don't as the database is being
rebuilt (the first thing that ido2db does is delete much of the
data that matches its own instance_id).
The actual delay at startup is dependent on many factors
including, but not restricted to, the number of hosts/services in
the instance in question, network latency between the monitoring
host and the database host, and contention on the database proper.
In my simple instance at home (9 hosts/43 services) with the
database running on the same host as Icinga, the delay is three
seconds; on the much bigger one I run at work (1271 hosts/7340
services) that has contention on the database from three other
Icinga instances, the startup can take three or more minutes,
and, in the case where all instances are starting at the same
time (e.g. after a reboot of the system), close to fifteen.
> That does not sound good. Is there a way to mitigate this? In a big
> installation, this means being blind for several minutes, or one would
> have to run multiple instances of Icinga, take care not to reload both
> at once and live with a number of weird issues that need explaining to
> end users.
To the best of my knowledge, not at the moment; if one is using
the ido2db facility that's "just the way it works".
> Is a possibility to keep scheduler and event handler running while the
> IDO database is rebuilt on the Icinga roadmap?
It might be possible if one eschews the use of ido2db directly and
periodically runs "log2db" using the icinga.log file as input. This,
however, would put a noticible delay into icinga-web that would not
be present in the "classic" CGIs (which use status.dat). I have NOT
tried this in any of the environments I manage and present it as pure
speculation, but it would remove the startup delay as the instance
would not wait for a database rebuild.
Cheers!
+------------------------------------------------+---------------------+
| Carl Richard Friend (UNIX Sysadmin) | West Boylston |
| Minicomputer Collector / Enthusiast | Massachusetts, USA |
| mailto:[email protected] +---------------------+
| http://users.rcn.com/crfriend/museum | ICBM: 42:22N 71:47W |
+------------------------------------------------+---------------------+
------------------------------------------------------------------------------
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
