distributed monitoring setup - ocsp_command not being executed
jason
jchambers at shaw.ca
Wed Oct 29 21:56:15 CET 2003
more info
----- Original Message -----
From: "jason" <jchambers at shaw.ca>
To: <nagios-users at lists.sourceforge.net>
Sent: Wednesday, October 29, 2003 1:40 PM
Subject: Re: [Nagios-users] distributed monitoring setup - ocsp_command not
being executed
>
> ----- Original Message -----
> From: "Marc Powell" <mpowell at ena.com>
> To: "jason" <jchambers at shaw.ca>; <nagios-users at lists.sourceforge.net>
> Sent: Wednesday, October 29, 2003 8:17 AM
> Subject: RE: [Nagios-users] distributed monitoring setup - ocsp_command
not
> being executed
>
>
>
>
> > -----Original Message-----
> > From: jason [mailto:jchambers at shaw.ca]
> > Sent: Tuesday, October 28, 2003 5:18 PM
> > To: nagios-users at lists.sourceforge.net
> >
> > Hey all,
> > I am trying to setup distributed monitoring and I am running
> > into
> > wall.
> > After following the steps describing setting up the distributed
> > server,
> > I don't see the ocsp_command getting executed. I can execute the
> > submit_check_result script manually.
>
> At first glance your command and nagios config information looks
> correct. One thing that you don't mention, and is important, is whether
> you have enabled the obsess_over_service option for each service you
> wish to submit results for? Here is what I use --
>
> Thanks marc,
> I've tried embedding the obsess_over_service even at a per service
> definition and still don't see desired results
> (don't see updates on the central server), but when I run the
> submit_check_result command via command line I do see the update...
>
> here is the services.cfg:
>
> define service {
> name generic-service
> active_checks_enabled 1
> passive_checks_enabled 1
> parallelize_check 1
> obsess_over_service 1
> check_freshness 0
> notifications_enabled 0
> event_handler_enabled 1
> flap_detection_enabled 1
> process_perf_data 1
> retain_status_information 1
> retain_nonstatus_information 0
> register 0
> }
>
> define service {
> name alt-service
> use generic-service
> check_period 24x7
> max_check_attempts 5
> normal_check_interval 5
> retry_check_interval 1
> obsess_over_service 1
> event_handler_enabled 1
> contact_groups jason
> notification_interval 60
> notification_period 24x7
> notification_options c,r
> register 0
> }
> #
> define service {
> use alt-service
> host_name host1
> service_description Ping - Internal
> check_command check_ping!10.0.0.6!200!20%!800!60%
> }
>
as well, when i use the web interface to look at configuration, services...
this is what nagios sees
Service
Host Description Max. Check Attempts Normal Check Interval Retry Check
Interal Check Command
host1 Ping - Internal 5 0h 5m 0s 0h 1m 0s
check_ping!10.0.0.6!200!20%!800!60%
Check Period Parallelize Volatile Obsess Over Enable Active Checks
Enable Passive Checks
24x7 Yes No Yes Yes Yes
Check Freshness Freshness Threshold Default Contact Groups Enable
Notifications Notification Interval
No Auto-determined value snms, rsc No 1h 0m 0s
Notification Options Notification Period Event Handler Enable Event
Handler Stalking Options
Critical, Recovery 24x7 Yes None
Enable Flap Detection Low Flap Threshold High Flap Threshold Process
Performance Data Enable Failure Prediction Failure Prediction Options
Retention Options
Yes Program-wide value Program-wide value Yes Yes None
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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