Bug in avail.c

[Michael Bierenfeld]

Hello there,

I think we found an bug in avail.c. The following is the debug output from a uncorrect availabilty

Reading archive #0 Archive name: '/usr/local/var/nagios.log' --- BEGINNING/MIDDLE SECTION ---
SETTING LAST KNOWN STATE=6
SKIPPING PRE-EVENT: 6 @ 1140735600
SERVICE 'HTTP' ON HOST 'zeus'... COMPUTING 6->2 FROM 1140735600 to 1140736526 (926 seconds) FOR SERVICE
PASSED TIME CHECKS, CLIPPED VALUES: START=1140735600, END=1140736526 SERVICE 'HTTP' ON HOST 'zeus'... COMPUTING 2->2 FROM 1140736526 to 1140736526 (0 seconds) FOR SERVICE
PASSED TIME CHECKS, CLIPPED VALUES: START=1140736526, END=1140736526 SERVICE 'HTTP' ON HOST 'zeus'... COMPUTING 2->9 FROM 1140736526 to 1140767798 (31272 seconds) FOR SERVICE
PASSED TIME CHECKS, CLIPPED VALUES: START=1140736526, END=1140767798 SERVICE 'HTTP' ON HOST 'zeus'... COMPUTING 9->1 FROM 1140767798 to 1140770478 (2680 seconds) FOR SERVICE
PASSED TIME CHECKS, CLIPPED VALUES: START=1140767798, END=1140770478 SERVICE 'HTTP' ON HOST 'zeus'... COMPUTING 1->2 FROM 1140770478 to 1140770766 (288 seconds) FOR SERVICE
PASSED TIME CHECKS, CLIPPED VALUES: START=1140770478, END=1140770766 --- END SECTION ---
SERVICE 'HTTP' ON HOST 'zeus'... COMPUTING 2->6 FROM 1140770766 to 1140775193 (4427 seconds) FOR SERVICE
PASSED TIME CHECKS, CLIPPED VALUES: START=1140770766, END=1140775193
[ Availability report completed in 0 min 0 sec ]

The HTML Table looks like

[ View full log entries ]
Event Start Time	Event End Time	Event Duration	Event/State Type	Event/State Information
02-24-2006 00:00:00	02-24-2006 00:15:26	0d 0h 15m 26s	SERVICE OK (HARD)	HTTP OK HTTP/1.1 200 OK - 1897 bytes in 0.003 seconds
02-24-2006 08:56:38	02-24-2006 09:41:18	0d 0h 44m 40s	SERVICE CRITICAL (HARD)	Connection refused

Nagios.log contains the following entries for that services

[1140768451] SERVICE ALERT: zeus;HTTP;CRITICAL;SOFT;2;Connection refused
[1140768471] SERVICE ALERT: zeus;/web/tomcat/rk;OK;SOFT;4;DISK OK - free space: /web/tomcat/rk 23090 MB (70%):
[1140768501] SERVICE ALERT: zeus;TSM Scheduler;OK;HARD;5;OK - TSM Scheduler is running, 24.02.06 23:00:00
[1140768511] SERVICE ALERT: zeus;HTTP;CRITICAL;SOFT;3;Connection refused
[1140768571] SERVICE ALERT: zeus;HTTP;OK;SOFT;4;HTTP OK HTTP/1.1 200 OK - 1897 bytes in 0.059 seconds
[1140768761] SERVICE ALERT: zeus;Inhouse Browser;OK;HARD;5;TCP OK - 0.011 second response time on port 9000
[1140768926] Auto-save of retention data completed successfully.


The machine zeus was rebooted today. And since then the last known state of zeus:HTTP is "zeus;HTTP;CRITICAL .. connection refused and not "zeus;HTTP;OK"

I can provide the full nagios.log if neccessary.

Regards

Michael


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642