Nagios for Dummies

[Jeremy Russell]

Do you maybe have the nagios.cfg to use a sql db, but have it commented
out in the resource.cfg?  That is one thing to check.
 
-----Original Message-----
From: Fernando Gomes Lima [mailto:flima at slb.com] 
Sent: Tuesday, May 27, 2003 10:03 AM
To: Nagios
Subject: [Nagios-users] Nagios for Dummies
 
 
    Hi guys,
 
I still receiving the error messages. Here is the message when i try to
start Nagios:
 
Attached I'm sending the resource.cfg file and the output of
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
 
I appreciate to receive some help from you guys that work and has some
knowledge of Nagios instead others that use the list to sell services. I
work on security environment and always helped others (you can check on
phoneboy (list to Firewall-1 users)) in trouble situation.
 
Best Regards,
- Fernando the dummy without shame to learn and ask ;-)
 
 
Nagios 1.0
Copyright (c) 1999-2002 Ethan Galstad (nagios at nagios.org)
Last Modified: 11-24-2002
License: GPL
Reading configuration data...
Error: Unexpected token or statement in file
'/usr/local/nagios/etc/resource.cfg' on line 24.
 
***> 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 on the main and host config files, as well as the
'Whats New' section to find out what has changed.
And on my resource.cfg (that has only one line uncommented (that's on
24th line position)) has the following statement:
########################################################################
###
#
# RESOURCE.CFG - Sample Resource File for Nagios 1.0
#
# You can define $USERx$ macros in this file, which can in turn be used
# in command definitions in your host config file(s). $USERx$ macros are
# useful for storing sensitive information such as usernames, passwords,

# etc. They are also handy for specifying the path to plugins and 
# event handlers - if you decide to move the plugins or event handlers
to
# a different directory in the future, you can just update one or two
# $USERx$ macros, instead of modifying a lot of command definitions.
#
# The CGIs will not attempt to read the contents of resource files, so
# you can set restrictive permissions (600 or 660) on them.
#
# Nagios supports up to 32 $USERx$ macros ($USER1$ through $USER32$)
#
# Resource files may also be used to store configuration directives for
# external data sources like MySQL...
#
########################################################################
###
# Sets $USER1$ to be the path to the plugins
$USER1$=/usr/local/nagios/libexec     <== Line 24!!!
# Sets $USER2$ to be the path to event handlers
#$USER2$=/usr/local/nagios/libexec/eventhandlers
# Store some usernames and passwords (hidden from the CGIs)
#$USER3$=someuser
#$USER4$=somepassword
 
Fernando Gomes
SchlumbergerSema
Network & Infrastructure Solutions
Security Engineer
flima at slb.com

Trab: +55 21 3824 6954
Cel. : +55 21 9888 9046
(GMT: -03:00) 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20030527/c1874a00/attachment.html>