reload appears to cause skip of remaining attempts

[mckslim]

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 timed out to '10.48.242.68' after 160 seconds (user 'ibm_hlth_chk'). Expected prompt not found. Last output was ''. Attempt 1 of 14.
[2013-06-18 23:48:58] HOST ALERT: SV-SBH-GSOC-02;DOWN;SOFT;2;CRITICAL: Connection timed out to '10.48.242.68' after 160 seconds (user 'ibm_hlth_chk'). Expected prompt not found. Last output was ''. Attempt 2 of 14.
[2013-06-18 23:55:40] HOST ALERT: SV-SBH-GSOC-02;DOWN;SOFT;3;CRITICAL: Connection timed out to '10.48.242.68' after 160 seconds (user 'ibm_hlth_chk'). Expected prompt not found. Last output was ''. Attempt 3 of 14.
[2013-06-19 00:02:22] HOST ALERT: SV-SBH-GSOC-02;DOWN;HARD;1;CRITICAL: Connection timed out to '10.48.242.68' after 160 seconds (user 'ibm_hlth_chk'). Expected prompt not found. Last output was ''. Attempt 4 of 14.

i'll go ahead and create a ticket

[abrist]

Great, could you post the link to the ticket here?

[mckslim]

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

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

[abrist]

No idea. Core 4 is in beta and that is where the core devs are spending more of their time currently. You may also want to hit the nagios core mailing list to get your issues on their radar.
https://lists.sourceforge.net/lists/lis ... gios-users

[mckslim]

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

[abrist]

If it is up on tracker, then you have the best visibility for your issue. Additionally, you could go to the mailing list as well.