I have noticed what I believe is a bug in b3.
Nagios Compiled with:
--with-template-objects --with-template-extinfo --with-default-perfdata
--with-default-comments --with-default-retention --with-default-downtime
--with-mysql-status.
I define a service with a max-check-attempt of 3.Then I submit a passive
check on that service (warning) and it immediately goes into warning 2/3
instead ofwarning 1/3 in the GUI.
In the nagios eventlog all is correct (ie warning soft 1 ) which makes me
think there is something wrong with the code that makes the insert into the
DB.
When I check the data in the DB I see that the 'current_attempt' goes
directly to '2' when submitting a passive check.
The bug is consistent with different settings of max-check-attempts. It
always goes directly into 2/X.
/Magnus
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: magnus.pettersson@eds.com