Cheshire Cat Computing

Hi we followed the install to step 6 but got stuck:
We appended the unix and nt templates to /usr/local/nagios/pcs/wil.cfg

# Receive passive notification from BIG BROTHER Windows agent
#

define service {
use svc-bigbrother
service_description disk
; contact_groups %CONTACT%
host_name EMAIL
}
define service {
use svc-bigbrother
service_description cpu
; contact_groups admins
host_name EMAIL
}
define service {
use svc-bigbrother
service_description procs
; contact_groups %CONTACT%
host_name EMAIL
max_check_attempts 1
}
define service {
use svc-bigbrother
service_description msgs
; contact_groups %CONTACT%
host_name EMAIL
}


Then we tried to restart nagios:
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

Nagios 2.0b3
Copyright (c) 1999-2005 Ethan Galstad (http://www.nagios.org)
Last Modified: 04-03-2005
License: GPL

Reading configuration data...

Error: Invalid max_attempts, check_interval, retry_interval, or notification_interval value for service 'cpu' on host 'EMAIL'
Error: Could not register service (config file '/usr/local/nagios/etc/pcs/wil.cfg', starting on line 420)

***> 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.

[root@alert-2 ~]#


Please let us know what to do ti fix this ERROR we are excited to use this tool. Stuck on point 6 of the install.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

we have in
/usr/local/nagios/etc/templates/services.cfg

[root@alert-2 nagios]# vi /usr/local/nagios/etc/templates/services.cfg
check_freshness 0 ; Default is to NOT check service 'freshness'
notifications_enabled 1 ; Service notifications are enabled
event_handler_enabled 1 ; Service event handler is enabled
flap_detection_enabled 1 ; Flap detection is enabled
failure_prediction_enabled 1 ; Failure prediction is enabled
process_perf_data 1 ; Process performance data
retain_status_information 1 ; Retain status information across program restarts
retain_nonstatus_information 1 ; Retain non-status information across program restarts
register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
}

define service{
name default-service
use generic-service
is_volatile 0
check_period 24x7
max_check_attempts 4
normal_check_interval 5
retry_check_interval 1
contact_groups admins
notification_interval 960
notification_period 24x7
register 0
}

define service {
name svc-bigbrother
service_description Big Brother Check
active_checks_enabled 1
check_period none
passive_checks_enabled 1
flap_detection_enabled 0
max_check_attempts 4 ; number of fails before alert
notification_options w,c,r ; don't alert on unknown
check_freshness 1
freshness_threshold 900 ; 15 mins
check_command unknown!No status info received for more than 15min
stalking_options w,c ; check for changes and new messages
register 0
}

Your definition of svc-bigbrother does not include 'use generic-service'. This means it has not inherited the various check_interval etc settings, so you are getting the error.

Did I miss this out in the templates?

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Mike Morgan here found that the services.cfg entry is incomplete when added from your install services.cfg

MISSING
retry_check_interval 1
notification_interval 960
notification_period 24x7


AND INCORRECT
check_period none (should be 24x7)


Now it is closer to working (minor warnings)

Steve,

We have put bb2ns.xinetd in /etc/xinetd.d and compiled bb2ns with no errors and put it in /usr/local/nagios/bin/ but it doesn't launch when we restart xinetd or reboot for that matter. The file still looks like this:

#service bb-test
service bb
{
flags = REUSE
socket_type = stream
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/bb2ns
server_args = -i -l /var/tmp/bb2ns.log
# -i : inetd mode
# -d x: add detailed debug logging -- requires -l
# x=0 errors (default), 1 basic, 2 detail, 3 data (lots and lots)
disable = no
instances = 60
# conn. per sec, seconds to disable for when exceeded
cps = 120 5
}
"bb2ns.xinetd" 19L, 547C

Here are permissions:

[root@alert-2 xinetd.d]# ll bb2ns.xinetd
-rw-r--r-- 1 root root 547 Feb 6 14:23 bb2ns.xinetd

From /var/log/messages during the reboot:

Jun 21 18:13:53 alert-2 xinetd[2291]: xinetd Version 2.3.13 started with libwrap loadavg options compiled in.
Jun 21 18:13:53 alert-2 xinetd[2291]: Started working: 0 available services

Everything else in /etc/xinetd.d is disabled.

Port 1984 is definitely closed:

Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2006-06-21 18:52 PDT
Interesting ports on alert-2 (172.16.100.18):
PORT STATE SERVICE
1984/tcp closed bigbrother

Any Ideas?

See subject.

Steve,

Is there a line command that will launch bb2ns in a mode that can be used with Nagios?

Steve,

The server we are failing to launch bb2ns on is running:

Red Hat Enterprise Linux ES release 4 (Nahant Update 3)

Are you aware of any issues running bb2ns on this release?

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11