I don't think so because when I run the exact command that I put in the cgi.cfg from the command line as the nagios user (I copied and pasted to make sure it was identical), I got the right result as expected.
It was only when put in the cgi.cfg and run by Nagios that it always gave the same thing, saying nagios wasn't running. But when nagios isn't running the web interface doesn't come up properly, I get a whole different error. I also still receive alerts so Nagios must be running. The reason the status file can't be in the wrong place is because otherwise the test when executed from the command line would fail, whereas it passes. I think this is more likely a subtle bug, it's the only way that I can account for the difference. -h Hari Sekhon Guang Deng wrote: > > the status.log file is missing, they this: > > touch /var/nagios/status.log > ------------------------------------------------------------------------- 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 http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
