Dear,
We are running Xymon on a Sun Fire v100 with Solaris 10 installed. On several Oracle systems with Oracle VM (Red Hat Enterprise Linux Server release 5.5 (Tikanga)) with 64 bit we are running Hobbit clients (FC5-hobbit-client-4.2.0-1.i386.rpm). The hobbit clients are 32 bit because those are the only wants we could find.
Problem: sometimes several tests like procs/disk/cpu is giving weird values in the monitoring which makes Xymon red. However, everything is fine and after restarting the client or after next update (5 minutes default), Xymon becomes green again.
Data size should not be the reason as I can see all the client data clear including a complete process list. It's just broken on the output page at the procs test.
Do you have any clue what could be the reason for this?
Thanks a lot.
Kind regards,
Giel Boes Rhodix System Manager
In <1668554996.2003.1296047834503.JavaMail.root at bain.rhodix.nl> Giel Boes <giel.boes at rhodix.nl> writes:
We are running Xymon on a Sun Fire v100 with Solaris 10 installed. On several Oracle systems with Oracle VM (Red Hat Enterprise Linux Server release 5.5 (Tikanga)) with 64 bit we are running Hobbit clients (FC5-hobbit-client-4.2.0-1.i386.rpm). The hobbit clients are 32 bit because those are the only wants we could find.
Problem: sometimes several tests like procs/disk/cpu is giving weird values in the monitoring which makes Xymon red. However, everything is fine and after restarting the client or after next update (5 minutes default), Xymon becomes green again.
You don't mention what version of Xymon you are running on the Xymon server, but I'll assume it is one of the 4.2.x releases.
There is a known bug in the Xymon 4.2.x server that causes this behaviour. It is solved in the current 4.3.0 test-versions (the latest being the 4.3.0-RC1 that was made available a few days ago). It is a server-side problem, nothing to do with your Xymon clients.
Regards, Henrik
Hi Henrik,
Thanks for your quick answer!
We are using Xymon version "4.3.0-beta2 ".
Are you sure it is a server-side problem? It only happens on this environment. On another environment we've exactly the same server with same OS and Xymon version where everything works fine. However the clients are different there, they are compiled for Solaris 9 and 10.
So you suggest to compile and install the RC1 version on our Solaris servers? Do you know when the final/stable version will be available online?
Thanks a lot!
Vriendelijke groeten, Kind regards,
Giel Boes Rhodix Service Manager
----- Original Message ----- From: "Henrik \"Størner\"" <henrik at hswn.dk> To: xymon at xymon.com Sent: Wednesday, 26 January, 2011 3:32:11 PM Subject: Re: [xymon] Linux client broken output
In <1668554996.2003.1296047834503.JavaMail.root at bain.rhodix.nl> Giel Boes <giel.boes at rhodix.nl> writes:
We are running Xymon on a Sun Fire v100 with Solaris 10 installed. On several Oracle systems with Oracle VM (Red Hat Enterprise Linux Server release 5.5 (Tikanga)) with 64 bit we are running Hobbit clients (FC5-hobbit-client-4.2.0-1.i386.rpm). The hobbit clients are 32 bit because those are the only wants we could find.
Problem: sometimes several tests like procs/disk/cpu is giving weird values in the monitoring which makes Xymon red. However, everything is fine and after restarting the client or after next update (5 minutes default), Xymon becomes green again.
You don't mention what version of Xymon you are running on the Xymon server, but I'll assume it is one of the 4.2.x releases.
There is a known bug in the Xymon 4.2.x server that causes this behaviour. It is solved in the current 4.3.0 test-versions (the latest being the 4.3.0-RC1 that was made available a few days ago). It is a server-side problem, nothing to do with your Xymon clients.
Regards, Henrik
To unsubscribe from the xymon list, send an e-mail to xymon-unsubscribe at xymon.com
In <1852298914.2135.1296053879652.JavaMail.root at bain.rhodix.nl> Giel Boes <giel.boes at rhodix.nl> writes:
Thanks for your quick answer!
We are using Xymon version "4.3.0-beta2 ".
Are you sure it is a server-side problem? It only happens on this environme= nt. On another environment we've exactly the same server with same OS and X= ymon version where everything works fine. However the clients are different= there, they are compiled for Solaris 9 and 10.=20
From your description, I am 99% certain this is a server-side problem, yes.
The bug is difficult to trigger in most cases. It depends on the number of updates from clients arriving, the size of the updates, and the sequence in which they are processed. All of which can vary from one installation to another, and also from time to time on the same installation.
So you suggest to compile and install the RC1 version on our Solaris server= s?=20 Do you know when the final/stable version will be available online?=20
I recommend an update, yes. Note that there have been some major changes from the beta-2 version to RC1 - so if you do upgrade, read the "docs/upgrade-to-430.txt" document carefully.
I expect the final 4.3.0 version to be released sometime in February, but it will of course depend on how many bugs are reported over the next couple of weeks.
Regards, Henrik
participants (2)
-
giel.boes＠rhodix.nl
-
henrik＠hswn.dk