NAGIOS 2.3.1 version issues

[srikalyan tangirala]

Hi all:
             As I'm trying to verify the configuration file, I'm getting
this error message. We have this HP Cluster setup and NAGIOS is installed
there. There are 18 nodes(n1 through n18) n18 being the main node. All the
nodes are up and running. Can any one help me out?

Best,
Sri








-bash-3.00# /opt/hptc/nagios/bin/nagios -v /opt/hptc/nagios/etc/nagios.cfg

Nagios 2.3.1
Copyright (c) 1999-2006 Ethan Galstad (http://www.nagios.org)
Last Modified: 05-15-2006
License: GPL

Reading configuration data...

Warning: Could not get group entry for 'nagios'
Error: Could not find any host matching 'n1'
Error: Could not expand member hosts specified in hostgroup (config file
'/opt/hptc/nagios/etc/xc-hostgroups.cfg', starting on line 90)

***> One or more problems was encountered while processing the config
files...

     Check your configuration file(s) to ensure that they contain valid
     directives and data defintions.  If you are upgrading from a previous
     version of Nagios, you should be aware that some variables/definitions
     may have been removed or modified in this version.  Make sure to read
     the HTML documentation regarding the config files, as well as the
     'Whats New' section to find out what has changed.

On 3/5/07, srikalyan tangirala <srikalyan.tangirala at gmail.com> wrote:
>
> Hi All:
>              I'm using NAGIOS 2.3.1 version.Installed and configured it
> with authenticated users as nagiosadmin and guest. Now, when I logged in as
> nagiosadmin and trying to  check if the services under Monitoring list
> works, they dont seem to work and the information that it provides is the
> below. I configured the additional permissions to CGI also with system
> information, commands, all hosts,services according to the documentation. It
> does not seem to work. Can anyone help me? I'm a newbie and need some help.
>
> Whoops!
>
> *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
>
>
>
> thanks
> sri
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070307/2610e0f7/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
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
-------------- next part --------------
_______________________________________________
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