contents of /tmp/nagios /usr/local/nagios/libexec/check_load -w 5.0,4.0,3.0 -c 10.0,6.0,4.0 /usr/local/nagios/libexec/check_load -w -c /usr/local/nagios/libexec/check_load -w 5.0,4.0,3.0 -c 10.0,6.0,4.0 /usr/local/nagios/libexec/check_load -w -c /usr/local/nagios/libexec/check_load -w 5.0,4.0,3.0 -c 10.0,6.0,4.0 /usr/local/nagios/libexec/check_load -w -c /usr/local/nagios/libexec/check_load -w 5.0,4.0,3.0 -c 10.0,6.0,4.0 /usr/local/nagios/libexec/check_load -w -c So whatever you had me do, made the host down go away for the nagios host. When I sent the reload command however, all hosts start showing down. I have to stop nagios and kill the daemon running, the start it again before it will recognize the host services again. This causes major problems as it doesn't reflect current uptime in reports. Any ideas here? Another issue that could play into this, I still can't schedule downtime b/c I can't isue external commands. Someone mentioned htaccess files, but I have my httpd.conf file with the same contents. <div>On 8/3/06, Marc Powell <<a href="mailto:marc@ena.com">marc@ena.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">'nagios' is a file in '/tmp'. It's contents are modified every time check_local_load is executed if you've followed my directions. cd /tmp cat nagios -- Marc > -----Original Message----- > From: Justin Craig [mailto:<a href="mailto:jrcraig.email@gmail.com">jrcraig.email@gmail.com</a>] > Sent: Thursday, August 03, 2006 8:57 AM > To: Marc Powell > Cc: Nagios Users Mailinglist > Subject: Re: [Nagios-users] Warning threshold must be float or float > triplet! {Disarmed} {Fraud?} > > sorry, where is my /tmp/nagios directory. I do a find / -name > */tmp/nagios* I don't see anything. > > > On 8/2/06, Marc Powell <<a href="mailto:marc@ena.com">marc@ena.com</a>> wrote: > > > > > -----Original Message----- > > From: <a href="mailto:nagios-users-bounces@lists.sourceforge.net">nagios-users-bounces@lists.sourceforge.net</a> <mailto:<a href="mailto:nagios-">nagios-</a> > <a href="mailto:users-bounces@lists.sourceforge.net"> users-bounces@lists.sourceforge.net</a>> [mailto:<a href="mailto:nagios-users-">nagios-users-</a> > > <a href="mailto:bounces@lists.sourceforge.net">bounces@lists.sourceforge.net</a>] On Behalf Of Justin Craig > > Sent: Wednesday, August 02, 2006 3:36 PM > > To: Marc Powell > > Cc: Nagios Users Mailinglist > > Subject: Re: [Nagios-users] Warning threshold must be float or > float > > triplet! {Disarmed} {Fraud?} > > > > I sent the reload command and basically nagios is now telling me > 30 > hosts > > are down and that number is increasing? This is a problem. why > does > this > > What does the status information for the down hosts/services say. > That'll be a primary indicator of why it's happening. I can't begin > to > guess. > > > happen? And back to my original issue, nagios itself is still > showing > > down. I modified the command as you suggested, how do I verify > that? > > Look at the contents of /tmp/nagios. It should contain the command > line > that nagios would have executed for the check_local_load service. > Can > you successfully run that from the command line as the nagios user? > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash <a href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV </a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users"> https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </blockquote></div> -- - Justin