Dear Jeremy, dear all,
What is the status of the xymonnet test page for your Xymon server? (This will probably show the most recent messages from the xymonnet.log file, among other info.)
xymonnet is green, nothing peculiar
I added a http check http://our_xymon_server/xymon-cgi/svcstatus.sh?HOST=our_xymon_server&SERVICE... for our xymon server (no certifcate, no https) and the result is interesting. It alternates between less than 1 second and timeout
[X]
This seems to show a failure and then 6 seconds later a success. It's like there are two xymonnet processes, one reporting a failure and the other reporting success.
Can you please take a look at two status messages (click on the red/green dot) that are a few seconds apart, and for each, check the IP address in the message near the bottom that says, "Status message received from <IP>" and see if they're both the same, and confirm that they are of the Xymon server?
Yes, both from xymon servers IP I'm not sure what's going on here. But I would try running a packet trace (eg tcpdump) and inspecting the traffic for the two connections - one that works and one that doesn't - and compare.
we did a (general) tcpdump but couldn't detect something. Well, noone here is specialist in this. I'll try this again more precisely.
I would exclude DNS as Solaris looks first in /etc/hosts before asking a nameserver and some of the adressesare included in /etc/hosts. As well, ping works fine.
Thank you for your help, Jeremy, I think, this is really a very special and local problem. I'll try to get our network specialists involved. It is difficult they are more than busy in times where everything happens online :-)
We'll use another machine for xymon and I am afraid we have to live with the fact that this machine isn't totally realiable any more,
cheers
Rolf
Also perhaps try running xymonnet manually again, but many times, to see if it's an intermittent fault.
Check the execution parameters in tasks.cfg for the [xymonnet] section, and make sure you're running xymonnet with the same parameters.
The problem might also be a DNS lookup issue. Try setting "testip" for the web server in your hosts.cfg file and see if the delay goes away.
-- Rolf Schrittenlocher
LBS-IT Systembetreuung lbs-it at ub.uni-frankfurt.de<mailto:lbs-it at ub.uni-frankfurt.de> Sammelnummer LBS-IT: 069 798-28830 Pers?nlich schritte at ub.uni-frankfurt.de<mailto:schritte at ub.uni-frankfurt.de> Direkt: 069 798-28908