status.cgi mixing services up?

[nagios at gnarg.org]

Hi gang,

I have found a slightly disturbing behaviour in status.cgi: Sometimes it 
duplicates the status of a service onto another. I discovered this once 
and can since reproduce it using the reload button of my browser. This 
is Nagios 2.3.1 and NRPE 2.5.1.

Right operation:
(I cranked the warning % up on the Backup Partition to speed up optical 
recognition)
------------------------------------------------------------------------
Remote Backup Partition
WARNING 05-24-2006 16:27:09 	0d 0h 10m 14s 	4/4 	DISK WARNING -
free space: /server2 21300 MB (55% inode=99%):

Remote Root Partition
OK 	05-24-2006 16:27:18 	0d 0h 12m 5s 	1/4 	DISK OK -
free space: / 12780 MB (72% inode=94%):
------------------------------------------------------------------------

Wrong operation:
------------------------------------------------------------------------
Remote Backup Partition
OK 	05-24-2006 16:27:51 	1d 20h 38m 11s 	1/4 	DISK OK -
free space: / 12780 MB (72% inode=94%):
	
Remote Root Partition
OK 	05-24-2006 16:29:00 	1d 20h 37m 2s 	1/4 	DISK OK -
free space: / 12780 MB (72% inode=94%):
------------------------------------------------------------------------

The Durations are funny, too.

To reproduce hit reload a couple times. It takes 10 - 20 clicks until it 
shows the wrong behaviour which persists about 3 clicks, assuming 
roughly 1 second per click.

What can this be?

Thanks,
	Chris


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null