The use of option : use_aggressive_host_checking=1 in the nagios.cfg file will make any difference??? Sujith Bangalore <div>On 2/28/07, Andy Shellam (Mailing Lists) <<a href="mailto:andy.shellam-lists@mailnetwork.co.uk">andy.shellam-lists@mailnetwork.co.uk</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div bgcolor="#ffffff" text="#000000"> sujith h wrote: <blockquote cite="http://mide4a2c74c0702280222l2259ed83y70d1f36eb58b08@mail.gmail.com" type="cite">I think i foregot to explain a crucial point that nagios is running in my router not in my machine. If i had told u my machine, then I really apolagise for stealing your precious time. </blockquote> No, I understand that. <blockquote cite="http://mide4a2c74c0702280222l2259ed83y70d1f36eb58b08@mail.gmail.com" type="cite">And is there anyway that I can trigger the check_uptime (plugin written by me) all the time when the router is up???</blockquote> Yes. Define it as a service for your host that runs, say, every 5 minutes 24x7. <blockquote cite="http://mide4a2c74c0702280222l2259ed83y70d1f36eb58b08@mail.gmail.com" type="cite">. If so please do tell me. If the router is down and nagios doesnt run then its ok for me. Since that is a different issue. But from your reply I came to understand that check_uptime will be called for the first time when the nagios is started and then if any of the services fails then again the check_uptime is called. </blockquote> Yes. Nagios only checks a host status when it absolutely needs to, not any other time. This is usually when a service fails, or a network blockage is detected. check_ping to <a href="http://127.0.0.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">127.0.0.1</a> on this check would work fine in your case. Andy. <blockquote cite="http://mide4a2c74c0702280222l2259ed83y70d1f36eb58b08@mail.gmail.com" type="cite"> Sujith Bangalore. <div>On 2/28/07, Andy Shellam (Mailing Lists) <<a href="mailto:andy.shellam-lists@mailnetwork.co.uk" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">andy.shellam-lists@mailnetwork.co.uk</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div bgcolor="#ffffff" text="#000000">Again, as I and Patrick have said, your host's check_command is only getting run when a service is deemed to have problems. You're getting the difference in the uptime output in Nagios and the console because Nagios hasn't run the uptime command for the host for over a day. If you're not retaining status information, then when you restart Nagios, it re-runs all it's checks, hence why it then gets updated. After that it is only run when a service fails. What I still don't understand is how your uptime command ensures the router is up? If the router is not up, then Nagios won't be running (as you're running it on the same host) so it seems quite pointless really. If the Lanlink checks that the LAN interface is up and connected - that makes sense, but then a check_ping to <a href="http://127.0.0.1" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">127.0.0.1</a> as your host check_command would give the same result as the uptime, then you could have an "Uptime" service with your check_uptime command. That way you could be confident that the status detail in Nagios is reasonably up-to-date. Andy. </div> </blockquote> </div> </blockquote> </div> </blockquote></div>