Antwort: Nagios 3.0.x - Service SOFT/HARD status issue

Sascha.Runschke at gfkl.com Sascha.Runschke at gfkl.com
Wed Jun 18 11:00:35 CEST 2008


nagios-users-bounces at lists.sourceforge.net schrieb am 18.06.2008 10:41:59:

> Since Nagios version 3.0 I've a strange service status issue.
> 
> When a host become (temporaly) unreachable he goes in down soft1 (first 
try).
> The service check following is directly in a HARD state ! Is it a bug ? 
> Should it not also follow the retry process before going to hard state ?
> 
> config is 3 retries for host & 3 retries for service.
> 
> 1. Host    - Down     - Soft1
> 2. Service - Unknown  - HARD1
> 3. Host    - Up       - Soft2
> 4. Service - OK       - HARD1

It depends on how you configured the max_check_attempts of the service 
checks.
Did you happen to have it set to 1?

It's kinda hard to guess...

Regards,
        Sascha

-- 
Sascha Runschke
Netzwerk-  und  Systemmanagement
Telefon : +49 (201) 102-1879 Mobil : +49 (173) 5419665 Fax : +49 (201) 
102-1102105



GFKL Financial Services AG
Vorstand: Dr. Peter Jänsch (Vors.), Jürgen Baltes, Dr. Till Ergenzinger, Dr. Tom Haverkamp
Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma
Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080618/04ebbad7/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
-------------- next part --------------
_______________________________________________
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