I have a couple FreeBSD clients that go purple if /tmp goes to 100%.
Paul Root - Senior Engineer Managed Services Systems - CenturyLink
-----Original Message----- From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of cleaver at terabithia.org Sent: Monday, July 09, 2012 1:03 PM To: John Horne Cc: xymon at xymon.com Subject: Re: [Xymon] Xymon on RHEL3 - not working?
Does it go green when you restart the client, then eventually go purple again? If so, it seems like something stuck in xymonlaunch -- the client itself is just a shell script.
Can you try running xymonlaunch with --debug to see what's happening, or strace it as it's running and send the output?
-jc
Hello,
I have Xymon 4.3.7 running as server on a CentOS 6 box - no problems. I have a mixture of RHEL3, 4, 5 and 6, and CentOS 5 & 6 clients. These all work fine except for the RHEL3 client. That one shows purple for the cpu, disk, files, memory and procs tests. The tests seem to have picked up some data from the first run after starting up, but since then they seem to have reported nothing (and hence purple).
I have been looking into this for a while now, and am at a bit of a loss as to why just this one client is having a problem. I have stopped the firewall on both client and server, but that makes no difference. A tcpdump shows that data is being sent to/from the client/server. I can see no obvious difference between this client and any of the others.
Anyone any ideas about this?
Thanks,
John.
-- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK Fax: +44 (0)1752 587001
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.