Distributed checking (part 2)

[Jasmine]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there thanks for replying 
Erm I think I have not presented my problem properly and you have 
misinterpreted it. The problem that I am facing is that my distributed 
monitoring server is not supposed to check its own web services like SSH. I 
have configured it to return critical status "ERROR: checked actively by 
distributed server!" if it does. I want my central monitoring server to check 
these services actively. However, after I configured the service as passive 
on the distributed server, it still seems to check actively which I cant see 
why. Below is a snippet of my service definition. 

On the Central monitoring server
 define service{

        host_name                      		distributed monitoring server A
        service_description             	SSH
        check_command                   	check_ssh
        active_checks_enabled           	1        
        passive_checks_enabled          	0      
        parallelize_check               	1       
        obsess_over_service             	0       
        check_freshness                 	0       
        max_check_attempts              	3       
        normal_check_interval           	3       
        retry_check_interval            	2       
        check_period                    		24x7    
        notification_interval           		0	       
        notification_period             		24x7    
        notification_options            		u,c,r 
	contact_groups				admin
}

On the Distributed monitoring server
define service{
              host_name               		distributed monitoring server A
        service_description    	 		SSH
        check_command           		check_error_active
	active_checks_enabled           	0       
        passive_checks_enabled          	0       
        parallelize_check               	0       
        obsess_over_service             	0       
        check_freshness                 	0      
        max_check_attempts              	3       
        normal_check_interval           	1      
        retry_check_interval            	1      
        check_period                    		none    
        notification_interval           		10      
        notification_period             		24x7    
        notification_options            		n       
        contact_groups                 		admin
}

Jasmine

On Thursday 06 February 2003 07:01, Atul Gosain wrote:
> Hi
>
> The problem is simple.
> U have check_freshness variable set to 1. The effect of this is that
> whenever the passive service results does not reach nagios for some time
> (freshness_threshold ), it considers the result as stale and starts
> checking actively for that service. If u want that active checks are not
> executed when passive results are stale, then disable check_freshness
> variable.
> Just tell me in case ur problem is solved.
>
> Thanks
> Atul
>
> Jasmine wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >HI all.. i m still having this problem sorry. i thought i made a config
> >mistake, but that does not solve the problem.
> >
> >>>just a note that I am having about the same problem as you. Anyone has
> >>>any ideas?
> >>>
> >>>On Wednesday 05 February 2003 19:01, Jason Burnett wrote:
> >>>>o.k. I am using the distributed method with passive checks to monitor
> >>>>some hosts I have behind a firewall that I dont want to punch holes in.
> >>>>For some reason my central nagios server keeps running active checks on
> >>>>the hosts even though I have that disabled on a per service instance.
> >>>>So I end up with the service up when it gets the info via the passive
> >>>>tests then it goes critical when the central server tries to check it
> >>>>with an active test. Here is the service config from the central
> >>>>server:
> >>>>
> >>>>define service{
> >>>>    host_name           pinky
> >>>>    service_description     SSH
> >>>>    check_command           check_ssh
> >>>>    max_check_attempts      2
> >>>>    normal_check_interval       5
> >>>>    retry_check_interval        5
> >>>>    passive_checks_enabled      1
> >>>>    active_checks_enabled       0
> >>>>    check_period            24x7
> >>>>    flap_detection_enabled      1
> >>>>    process_perf_data       1
> >>>>    retain_status_information   1
> >>>>    retain_nonstatus_information    1
> >>>>    notification_interval       1
> >>>>    notification_period     24x7
> >>>>    notification_options        w,u,c,r
> >>>>    notifications_enabled       1
> >>>>    check_freshness         1
> >>>>    freshness_threshold     180
> >>>>    contact_groups          admins
> >>>>}
> >>>
> >>>--
> >>
> >>--
> >
> >- --
> >- --
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.2.1 (GNU/Linux)
> >
> >iD8DBQE+QlzYNgvTa7Hj2AURAsnYAJ0ZYWr9gecenetL1yZqC1E2Eh00ogCgriLV
> >lMIct+YBKB/6ZQUmDmKe6w8=
> >=q+Rf
> >-----END PGP SIGNATURE-----
> >
> >
> >
> >-------------------------------------------------------
> >This SF.NET email is sponsored by:
> >SourceForge Enterprise Edition + IBM + LinuxWorld
> > http://www.vasoftware.com _______________________________________________
> >Nagios-users mailing list
> >Nagios-users at lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/nagios-users

- -- 
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+Q9myNgvTa7Hj2AURAp4EAKCtPdcWiL720gfg34nA9ZrUSi653gCgpEpG
MjhXu1zMd26PzSuxN/cUQT0=
=upWA
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com