Hi,
I ended up sending our culprit Windows host to another Xymon installation we have in-house – running 4.3.10. Here it shows up correctly so far. Even deleting the “svcs” history and making it start from scratch will get the wrong state in from the get go on the 4.3.7-installation.
I suspect the 4.3.10-installation is running CentOS 6.0+, but I cant really see that making a diff? Guess I’ll have to look in the change notes, if this was reported fixed in 4.3.10.
Regards, Carl Melgaard
Fra: Neil Simmonds [mailto:Neil.Simmonds at express-gifts.co.uk] Sendt: 20. september 2012 10:58 Til: xymon at xymon.com Cc: Carl Melgaard Emne: RE: [Xymon] bbwin Windows services state text delayed?
Hi Carl,
I also experience exactly this running Xymon 4.3.4 on Centos 5.6.
I’ve also just done some testing on another system running Xymon 4.3.4 on Centos 6.3.
I had to use services that were stopped/disabled and stopped/manual as I don’t have a test machine on that system where I could stop an automatic service but they reported the status correctly on Red.
When I changed them to monitor for status=stopped they also still reported ok. This obviously isn’t conclusive that it is different on Centos 6.3 as I haven’t actually changed the state of the services, just the monitoring.
I’d be very interested to know if there is a fix for this as we have our Operators making call outs based on Xymon alerts and something like this can cause confusion.
Cheers, Neil.
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Carl Melgaard Sent: 19 September 2012 15:18 To: 'xymon at xymon.com' Subject: [Xymon] bbwin Windows services state text delayed?
Hi,
Running Xymon 4.3.7 on CentOS 5.6 – just started using bbwin-0.13 for our Windows servers – I’m seeing some funny behaviour when a service I’m monitoring is changing state: