Ignore my last mail please, just found the problem: status_file= in nagios.cfg was pointing to a location where Nagios wasn't allowed to write on the new system. Stupid me.
Funny that Nagios doesn't complain at all, neither in the logs or when starting up in console mode about this? Anyway, thanks and regards, Carsten -----Original Message----- From: Schmitz, Carsten Sent: Tuesday, November 08, 2005 2:42 PM To: nagios-users@lists.sourceforge.net Subject: Problem getting CGIs to work after upgrade to 2.0b4 Hi fellow Nagiosians (if thats even a word ;) I have a problem with my CGIs, they don't work. Thats ALL of them, not just some. What I get is (for example for the service status): Whoops! Error: Could not read host and service status information! [...] As for the things addressed further down in the (long) error message: - Yes, Nagios is running (in daemon mode, I see it in ps -ef) - there are no CGI errros in the log file (some other errors that result from my upgrade, I explain below) - I verified my nagios config files with -v, and get no errors (some warnings but no errors) - I used the rhel rpm (don't ask), so I am sure main program and GCI using the same data store Here's what led to the error: - I have a working self-compiled nagios 1.x installation on machine #1 in /usr/local/nagios (the box is RH 7.3 - shame on me) - I installed nagios 2.x on machine #2 from the "official" rhel 4 rpm (this is the installation where the problem occurs), the box runs CentOS 4.2 (OS built from RHEL 4 patch 2 sources) - I can not rewrite all my host and service definitions at this time, so I decided to remove /etc/nagios and copy the contents of my machine #1's /usr/local/nagios/etc to /etc/nagios (please read on, I HAVE read the "Whats New in 2.x" and I am taking the config file format changes into account!) - I adjusted all the path names to match the path names in my new installation (perl one liner and verified twice) in all config files (nagios.cfg, cgi.cfg etc). - I stripped the contact_groups from the host group definitions according to the Nagios 2.x "Whats New" change document - I fixed some other small things where Nagios 2.x seems more picky than 1.x (in a good way ;) - I verified my config with -v, I ran nagios in console mode and watched it performing checks and sending emails, and I verified with ps -ef that it starts up in daemon mode. - I did NOT so far change any macros (!) to 2.x standards but that should not impact the CGIs from showing up, should it? - I should mention that I see some service checks fail in the log file (or console) because I am not yet finished copying and adjusting all of my custom plugins. - There are no errors in my apache error log. I DO see the access to the CGIs in the access log, but no errors. Still, the CGIs don't work. Would anyone kindly have a pointer for me what else to check for? Many thanks, Carsten ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ 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