Error: Could not read host and service status information

James R. Marcus jmarcus at mvalent.com
Thu Aug 25 15:58:19 CEST 2005


Gladly:

ncheck / # grep nagios /etc/group
apache:x:81:nagios,monarch
nagios:x:407:monarch,apache


ncheck / # ls -al /etc/nagios/
total 104
drwxrwx---   2 nagios nagios 4096 Aug 24 08:09 .
drwxr-xr-x  51 root   root   4096 Aug 24 18:24 ..
-rw-r--r--   1 nagios nagios    0 Aug 16 17:28 .keep
-rwxrwxr-x   1 nagios nagios 1887 Aug 24 17:03 cgi.cfg
-rwxrwxr-x   1 nagios nagios 2690 Aug 24 17:03 checkcommands.cfg
-rwxrwxr-x   1 nagios nagios 1381 Aug 24 17:03 contact_templates.cfg
-rwxrwxr-x   1 nagios nagios  956 Aug 24 17:03 contactgroups.cfg
-rwxrwxr-x   1 nagios nagios 1243 Aug 24 17:03 contacts.cfg
-rwxrwxr-x   1 nagios nagios 1663 Aug 10 01:28 dependencies.cfg
-rwxrwxr-x   1 nagios nagios  748 Aug 24 17:03 escalation_templates.cfg
-rwxrwxr-x   1 nagios nagios  330 Aug 24 17:03 escalations.cfg
-rwxrwxr-x   1 nagios nagios 1265 Aug 24 17:03 host_templates.cfg
-rwxrwxr-x   1 nagios nagios  854 Aug 24 17:03 hostgroups.cfg
-rwxrwxr-x   1 nagios nagios  687 Aug 24 17:03 hosts.cfg
-rw-r--r--   1 root   root     15 Aug 18 18:20 htpasswd.group
-rw-r--r--   1 root   root     21 Aug 18 18:18 htpasswd.users
-rwxrwxr-x   1 nagios nagios 2418 Aug 24 17:03 misccommands.cfg
-rwxrwxr-x   1 nagios nagios 4192 Aug 24 17:03 nagios.cfg
-rwxrwxr-x   1 nagios nagios 3501 Aug 16 17:29 nrpe.cfg
-rwxrwxr-x   1 nagios nagios 4960 Aug 18 18:09 nsca.cfg
-rwxrwxr-x   1 nagios nagios 2981 Aug 10 14:10 resource.cfg
-rwxrwxr-x   1 nagios nagios 1628 Aug 16 17:24 send_nsca.cfg
-rwxrwxr-x   1 nagios nagios 4022 Aug 24 17:03 service_templates.cfg
-rwxrwxr-x   1 nagios nagios  741 Aug 24 17:03 services.cfg
-rwxrwxr-x   1 nagios nagios 1459 Aug 24 17:03 timeperiods.cfg

ncheck / # ls -l /var/nagios/
total 20
drwxr-xr-x  2 nagios nagios 4096 Aug 25 00:00 archives
-rw-r--r--  1 root   apache    5 Aug 24 17:03 nagios.lock
-rw-r--r--  1 nagios nagios   33 Aug 25 00:00 nagios.log
-rw-r--r--  1 root   root      2 Aug 25 09:54 nagios_seek.tmp
drwxr-xr-x  2 nagios apache 4096 Aug 16 17:28 rw
-rw-r--r--  1 nagios nagios    0 Aug 24 17:03 status.sav

ncheck / # grep -i not /var/nagios/nagios.log 
ncheck / #  

Apache2:

###
### Nagios Stuff
###
ScriptAlias /nagios/cgi-bin/ /usr/nagios/sbin/
 Alias /nagios/ /usr/nagios/share
<Directory "/usr/nagios/sbin">
    AllowOverride AuthConfig
    Options +ExecCGI
    Order allow,deny
    Allow from all
</Directory>
 
<Directory "/usr/nagios/share">
    Options None
    AllowOverride AuthConfig
    Order allow,deny
    Allow from all
</Directory>

Thanks,
James


-----Original Message-----
From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Marc
Powell
Sent: Thursday, August 25, 2005 12:03 AM
To: nagios-users at lists.sourceforge.net
Subject: RE: [Nagios-users] Error: Could not read host and service
status information

Would you be willing to send ls -al's on ~nagios/etc and ~nagios/var as
well as the user/group that nagios and your web server run under? It
does sound like it might be a permissions issue and another set of eyes
can't hurt. Additionally, do you see and 'could not update' errors in
nagios.log?

--
Marc

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of James R. Marcus
> Sent: Wednesday, August 24, 2005 9:18 PM
> To: Lori Adams; nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Error: Could not read host and service
status
> information
> 
> Hi,
> Yes I have killed all the Nagios processes and restarted.  I don't
have a
> status.log, I have nagios.log, it was my understanding that when you
use
> mySQL and Nagios the status.log isn't written.  I have run nagios -v
and
> although I have had warnings, which I corrected,  nothing has really
> changed.  I have double checked permissions.
> 
> The other interesting thing to note is that according the log, it
looks
> like it is doing the checks correctly.
> 
> I guess it is back to the doc :-)
> 
> James
> 
> ________________________________
> 
> From: Lori Adams [mailto:ladams at cloudmark.com]
> Sent: Wed 8/24/2005 6:08 PM
> To: James R. Marcus; nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Error: Could not read host and service
status
> information
> 
> 
> 
> Have you tried killing off all nagios processes?  Make sure there are
no
> more, and then restart your nagios.
> 
> 
> 
> Below is the error I get if nagios is not running. I assume you got
this
> entire message too.  Follow all instructions when setting up your
nagios.
> More specifically make sure that you have a status.log (see
nagios.cfg).
> 
> 
> 
> Did you try all of these steps?  Definitely try
/your/nagios/dir/nagios -v
> to make sure there's no errors.
> 
> 
> 
> Error: Could not read host and service status information!
> 
> 
> 
> The most common cause of this error message (especially for new
users), is
> the fact that Nagios is not actually running. If Nagios is indeed not
> running, this is a normal error message. It simply indicates that the
CGIs
> could not obtain the current status of hosts and services that are
being
> monitored. If you've just installed things, make sure you read the
> documentation on starting Nagios.
> 
> 
> 
> Some other things you should check in order to resolve this error
include:
> 
> 
> 
>             1. Check the Nagios log file for messages relating to
startup
> or status data errors.
> 
>             2. Always verify configuration options using the -v
command-
> line option before starting or restarting Nagios!
> 
> 3. Make sure you've compiled the main program and the CGIs to use the
same
> status data storage options (i.e. text file or database). If the main
> program is storing status data in a text file and the CGIs are trying
to
> read status data from a database, you'll have problems.
> 
> 
> 
> Make sure you read the documentation on installing, configuring and
> running Nagios thoroughly before continuing. If all else fails, try
> sending a message to one of the mailing lists. More information can be
> found at http://www.nagios.org <http://www.nagios.org/> .
> 
> 
> 
> -Lori
> 
> 
> 
> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of James R. Marcus
> Sent: Wednesday, August 24, 2005 12:39 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Error: Could not read host and service status
> information
> 
> 
> 
> 
> 
> I have been looking at old posts and the FAQ to find a solution to
this
> 
> issue:
> 
> 
> 
> Error: Could not read host and service status information!
> 
> 
> 
> All I get in my log file is:
> 
> [1124913728] Warning: Contact group 'switch-admins' is not used in any
> 
> hostgroup/service definitions or host/hostgroup/service escalations!
> 
> [1124913728] Warning: Contact group 'win-admins' is not used in any
> 
> hostgroup/service definitions or host/hostgroup/service escalations!
> 
> [1124913728] Finished daemonizing... (New PID=6184)
> 
> 
> 
> I think I have done a pretty good job of reviewing permissions etc.
> 
> There are no errors in the Apache2 logs.
> 
> 
> 
> I'm running Gentoo, Nagios 1.2 and Monarch for configuration.
> 
> 
> 
> Can anyone point me to a better way of troubleshooting this issue?
> 
> 
> 
> 
> 
> Thanks,
> 
> James
> 
> 
> 
> 
> 
> -------------------------------------------------------
> 
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> 
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> 
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing
& QA
> 
> Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
> 
> _______________________________________________
> 
> Nagios-users mailing list
> 
> Nagios-users at 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
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing
& QA
> Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing &
QA
Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
Nagios-users mailing list
Nagios-users at 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


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Nagios-users mailing list
Nagios-users at 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





More information about the Users mailing list