[Nagios-devel] Possible bug in Nagios 2.12?
Posted: Tue Apr 07, 2009 7:00 pm
Hi Everyone,
I've been working on porting a nagios event broker module from 2.7 to 2.12.
In the process of doing so I've noticed that on my test system that service=
check latency tends to climb, and at the same time, completed service chec=
ks are trending downwards.
Since latency was the first clue there might be a problem, I set off to fin=
d out where latency is calculated and it turns out that latency is calculat=
ed in the event_execution loop in events.c
While in there I noticed something interesting or actually I noticed a lack=
of something.
=20=20
I'm not seeing anywhere that (event_list_low =3D event_list_low->next) unle=
ss the event actually runs.
To me this looks like a bug. As far as i can tell unless the current event_=
list_low item executes, the next item on the list could never execute.
Now I am working on a slightly patched version of nagios 2.12 so it is poss=
ible something went goofy with the patching process, but I keep looking ove=
r and over at the same lines of code and I don't see how it gets past this.
Would someone mind taking a look at events.c in nagios 2.12 and see if I'm =
correct here?
Thanks in advance!
Sincerely,
Steve=20
NOTICE: This email message is for the sole use of the intended recipient(s=
) and may contain confidential and privileged information. Any unauthorized=
review, use, disclosure or distribution is prohibited. If you are not the =
intended recipient, please contact the sender by reply email and destroy al=
l copies of the original message.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
I've been working on porting a nagios event broker module from 2.7 to 2.12.
In the process of doing so I've noticed that on my test system that service=
check latency tends to climb, and at the same time, completed service chec=
ks are trending downwards.
Since latency was the first clue there might be a problem, I set off to fin=
d out where latency is calculated and it turns out that latency is calculat=
ed in the event_execution loop in events.c
While in there I noticed something interesting or actually I noticed a lack=
of something.
=20=20
I'm not seeing anywhere that (event_list_low =3D event_list_low->next) unle=
ss the event actually runs.
To me this looks like a bug. As far as i can tell unless the current event_=
list_low item executes, the next item on the list could never execute.
Now I am working on a slightly patched version of nagios 2.12 so it is poss=
ible something went goofy with the patching process, but I keep looking ove=
r and over at the same lines of code and I don't see how it gets past this.
Would someone mind taking a look at events.c in nagios 2.12 and see if I'm =
correct here?
Thanks in advance!
Sincerely,
Steve=20
NOTICE: This email message is for the sole use of the intended recipient(s=
) and may contain confidential and privileged information. Any unauthorized=
review, use, disclosure or distribution is prohibited. If you are not the =
intended recipient, please contact the sender by reply email and destroy al=
l copies of the original message.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]