[icinga-users] Problems with passive checks in icinga

Wolfgang wnd at gmx.net
Tue Oct 5 20:04:33 CEST 2010


  Am 05.10.2010 13:29, schrieb Fritjof Bornebusch - Skyfillers:
>
> Hi Gerald,
>
> I have added that but that was not the point.
>
> Regards,
>
> Fritjof
>
> *Von:* Ortner, Gerald [mailto:Gerald.Ortner at gespag.at]
> *Gesendet:* Dienstag, 5. Oktober 2010 11:39
> *An:* icinga-users at lists.sourceforge.net
> *Betreff:* Re: [icinga-users] Problems with passive checks in icinga
>
> Hi Fritjof,
>
> You've disabled the freshness check in your service template:
>
> template.cfg
>
> define service{
>
> ...
>
> check_freshness                 0
>
> ...
>
> }
>
> ;D
>
> regards,
>
> gerald
>
> *Von:* Fritjof Bornebusch - Skyfillers 
> [mailto:F.Bornebusch at skyfillers.com]
> *Gesendet:* Dienstag, 05. Oktober 2010 11:27
> *An:* icinga-users at lists.sourceforge.net
> *Betreff:* [icinga-users] Problems with passive checks in icinga
>
> Hi guys,
>
> I use passive checks to check some servers behind a firewall.
>
> It works good so far, but the check_service_freshness command doesn't 
> work.
>
> icinga.cfg:
>
> accept_passive_checks = 1
>
> check_service_freshness = 1
>
> service_freshness_check_interval = 30
>
> additional_freshness_latency = 15
>
> template.cfg
>
> define service{
>
>         use                             generic-service
>
>         name                            kunde_passive_service
>
>         active_checks_enabled           0
>
>         passive_checks_enabled          
> 1                               # We want only passive checking
>
>         flap_detection_enabled          1
>
>         register                        
> 0                               # This is a template, not a real service
>
>         is_volatile                     1
>
>         check_period                    none
>
>         max_check_attempts              1
>
>         normal_check_interval           1
>
>         retry_check_interval            1
>
>         check_freshness                 0
>
>         freshness_threshold             30
>
>         contact_groups                  test
>
>         check_command                   check-nsca-alive!2
>
>         notification_interval           120
>
>         notification_period             24x7
>
>         notification_options            w,u,c,r
>
>         stalking_options                w,c,u
>
> }
>
> I have a server where is the last check from 09-27-2010 13:46:56 and 
> the services are still OK.
>
> I get the values like CPU, RAM, HDD etc from the NSCA daemon so the 
> passive checks are working.
>
> Does someone know a solution for that?
>
> Regards,
>
> Fritjof
>
>
The freshness values mean "seconds", not minutes.
Are there any messages in nagios.log?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.icinga.org/pipermail/icinga-users/attachments/20101005/83e4df72/attachment-0001.html>


More information about the icinga-users mailing list