A quick update before I forget…
I mentioned that Nagios quit spitting out status information as it used to. I did make a change (but didn’t mention) which was the installation of Fruity. So, I dug around a bit within Fruity to see what might surface. I found something.
Not completely understanding the multi-layered facets of host and service checking, I disregarded the fact when drilling down into a host that the Checks and Services/Checks were different entities. Seems I had enabled Checks but not enabled Services/Checks. I enabled them and, viola, started getting some action out of Nagios.
But (there’s always a but) I was getting a a problem where Nagios wasn’t locating my plugin for check_http. In the log I noticed the path was:
/check_http -H www.host.com
Obviously my check_http isn’t in the root of my file system so I headed on over to the $USER1$ variable which preceeds every (?) plugin. According to Fruity my $USER1$ was empty. I added the following:
Restarted Nagios (after exporting from Fruity) and, yay, I got my first successful status of OK for check_http.
Finish configuring the Service information for my hosts and try some other plugins.
Be rid of the “Nagios is not running” error which is likely related to running in Test, not Dameon, mode.
Thanks to anyone who posted feedback. Having someone post a reply gave me encouragement and hints that kept me going and considering other things to try.
Edited Thu May 05 2005, 09:39PM ]