Nagios Support Forum

Hi again, is there any other way to get visibility to my problem I created on this issue, to have developers fix it in some 3.5.x release ?
thanks

Ticket link: http://tracker.nagios.org/view.php?id=461

What kind of timeframe might I expect for this to be worked on?

problem happens with 3.5.0 on stg? looks like it: $ cat /opt/nagios/var/nagios.log | grep 'HOST ALERT' | grep 'SV-SBH-GSOC-02' | format_log_ts.pl | L [2013-06-18 23:35:07] HOST ALERT: SV-SBH-GSOC-02;UP;HARD;1;sean up [2013-06-18 23:42:07] HOST ALERT: SV-SBH-GSOC-02;DOWN;SOFT;1;CRITICAL: Connection t...

I only find this happening when Nagios is reloaded.

max_attempts is 4 output: $ ps -aef | grep nagios.cfg nagios 5726 1 0 Jun14 ? 00:41:14 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 25239 5726 0 22:58 ? 00:00:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 25330 5726 0 22:58 ? 00:00:00 /opt/nagios/bin/nagios -d /opt/na...

no scheduled downtime has been in effect for this problem

'initial_state' is not set to anything
Remember that this is happening on a reload (I haven't examined what happens on a full restart).
thanks

Running 3.4.1: I see this strange anomaly, where a host check is in the middle of doing retries before hitting max_attempts, but after a server reload occurs, the next check is automatically forced to DOWN;HARD;1, as seen here: [2013-06-04 08:40:21] HOST ALERT: 5gt4;DOWN;SOFT;1;CRITICAL: Connection ...