Exactly what I was thinking! I just asked, because older versions haven't introduce that delay. Moreover, I was searching if this was a "normal" nagios delay or a misconfiguration on my side (interoperability with some package installed or something I can't think at the moment)
Friday, December 18, 2009, 12:13:53 PM, you wrote: > Hi, > I'm experiencing exactly the same problem. I always thought, that > this behaviour is caused by ndo (which seems not to be the case). > Looking into the nagios log I recognized that the initial state > info is loaded within 9 seconds into nagios - so the cgi should be > ready to go. It's somehow strange: you cannot view the tactical > overview, host or service information. But during that 30 s you can have a > look at the Alert history. > Perhaps nagios needs the missing 20s to build up some internal data > structures, plan the scheduling or so ? > Thomas > Von: Brandino Andreas [mailto:[email protected]] > Gesendet: Freitag, 18. Dezember 2009 09:23 > An: Thomas Guyot-Sionnest > Cc: [email protected] > Betreff: Re: [Nagios-users] Nagios 30 seconds initial delay > Hi all, > my status_update_interval value: "status_update_interval=10" > Nagios need 35 seconds to show up... > Friday, December 18, 2009, 6:03:44 AM, you wrote: >> On 15/12/09 05:57 PM, Brandino Andreas wrote: >>> Hi all, >>> I am using Nagios 3.2.0 (I just upgrade from early 3.0 releases) >>> Every time I restart nagios I face a 30 seconds delay before the >>> various pages appear for first time (not before starting checks, 30 >>> seconds before displaying pages!!!) >>> >>> When I click a page I get the error "Error: Could not read host and >>> service status information!" . After 30 seconds, all pages appear >>> again!! >>> >>> - I don't have duplicated nagios service running >>> - This delay didn't show up to older versions >>> - My linux is Debian 5.0.3 (stable) >>> - This error appears every time I restart nagios >>> >>> Any idea what can cause this delay?? >> What is your status_update_interval (in nagios.cfg)? >> I'm guessing if it's set to 30 seconds then maybe status.dat isn't >> getting created until the first 30 seconds pass, which would explain this. >> Unless you have a large number of services you can set this pretty low >> without impacting performance, and a lower value gives better >> responsiveness on the CGI. > <> --- - - - --- <> > Brandino Andreas > [email protected] > <> --- - - - --- <> > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support A > streamlined, 14 day to market process makes app distribution fast > and easy Join now and get one step closer to millions of Verizon > customers http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Nagios-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null <> --- - - - --- <> Brandino Andreas [email protected] <> --- - - - --- <> ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
