[Xymon] Ghost client problems
Don Kuhlman
Don.Kuhlman at schawk.com
Wed Feb 29 15:40:58 CET 2012
One other thing I learned the hard way is that as well as making sure that the "XYMSRV="XYMON SERVER NAME OR IP" is set correctly in the xymonclient.cfg file, I had to go in to the clientlaunch.cfg file in the same directory as xymonclient.cfg and remove the —local value from the file.
Remove the words "--local" from the line that looks like this (for Unix clients)
CMD $XYMONCLIENTHOME/bin/xymonclient.sh —local
For Windows clients make sure it says "central" for the "value =" in the line below in the bbwin.cfg file:
<!-- bbwin mode local or central -->
<setting name="mode" value="central" />
<setting name="configclass" value="win32" />
I didn't build the agent installs and when our Unix admin compiled them, they defaulted to —local. As soon as I changed both the Unix and Windows agent settings in this manner, (making sure the xymon server value is right), they started sending their cpu, disk, etc. values right over.
Next thing for us is to either customize the files or redo the install so it has these values set from the beginning.
Hope that helps.
Don K
From: Jamison Maxwell <jamison at newasterisk.com<mailto:jamison at newasterisk.com>>
Date: Wed, 29 Feb 2012 05:51:25 +0000
To: "xymon at xymon.com<mailto:xymon at xymon.com>" <xymon at xymon.com<mailto:xymon at xymon.com>>
Subject: Re: [Xymon] Ghost client problems
One thing I forgot:
d. the client is not running…. ps –A | grep xymon
From: xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com> [mailto:xymon-bounces at xymon.com] On Behalf Of Jamison Maxwell
Sent: Tuesday, February 28, 2012 7:40 PM
To: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] Ghost client problems
>> I'd seriously suggest using a prebuilt RPM (search the archives for this/last month, there are a few posts), it puts various config files in /etc that are easier to diagnose configuration issues with than hand compiled installs.
I’d suggest the opposite. When you compile the client it specifically asks you where the Xymon server is running. All of the configuration files are placed in /home/xymon/client, all right there easy to configure, thus I don’t see why using pre-built RPMs is easier because the ones that I have tried have a tendency to scatter them, IMO. Either way you go, find one way to do it in you environment and stick to it.
If the server is not displaying, or has purple ‘alerts’ in place of disk, memory, etc., then the server is not receiving the data from your client. The only three possible reasons that I can see is that the a. the client cannot reach the server for either DNS (if hostname was used) or network related problems, b. the client is pointed at the wrong server or no server, c. there is a firewall on the server that is not allowing the connection attempt.
I would suggest disabling iptables to troubleshoot and ensure that the latter is not the issue, to make sure you instantaneously know whether or not you are receiving data, do a packet capture with ‘tcpdump dst port 1984’. If you get packets from the client, then the firewall is the problem, if you don’t you have to keep going. Ensure that the correct system is specified in the first line of /home/Xymon/client/etc/xymonclient.cfg. It should read “XYMSRV="YOUR SERVER’S IP OR HOSTNAME" # IP address of the Xymon server”. If you specified the hostname, add it to /etc/hosts and see if that remediates.
Seriously though, these are all basic troubleshooting steps and anything that is above that is found in the man pages on the Xymon server. Please, do this list a favor and read them, alternatively, you can contact me directly and I’ll set it up for you provided you pay my consulting fee. ; )
--Jamison Maxwell
From:xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com> [mailto:xymon-bounces at xymon.com]<mailto:[mailto:xymon-bounces at xymon.com]> On Behalf Of Steven Carr
Sent: Monday, February 27, 2012 9:40 AM
To: Pavel Traian; xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] Ghost client problems
Conn is checked from the server side, not the client side. It sounds like you haven't told the client where to connect to. Where did you configure the xymon server IP address?
I'd seriously suggest using a prebuilt RPM (search the archives for this/last month, there are a few posts), it puts various config files in /etc that are easier to diagnose configuration issues with than hand compiled installs.
Steve
On 27 February 2012 13:56, Pavel Traian <paveltraian at yahoo.com<mailto:paveltraian at yahoo.com>> wrote:
Hi,
Conn, info and trends are green as always.
cpu, disk, memory, msgs, ports and procs are purple.
Regards,
Traian.
--- On Mon, 2/27/12, Chris.Morris at rwe.com<mailto:Chris.Morris at rwe.com><Chris.Morris at rwe.com<mailto:Chris.Morris at rwe.com>> wrote:
From: Chris.Morris at rwe.com<mailto:Chris.Morris at rwe.com> <Chris.Morris at rwe.com<mailto:Chris.Morris at rwe.com>>
Subject: RE: [Xymon] Ghost client problems
To: paveltraian at yahoo.com<mailto:paveltraian at yahoo.com>
Date: Monday, February 27, 2012, 3:49 PM
So - your network tests ( server to client ) are green and current? Server to client comms OK.
Your client tests are purple, no ghosts, no logfetch.* files? Client to server comms NOTOK.
________________________________
From: Pavel Traian [mailto:paveltraian at yahoo.com<mailto:paveltraian at yahoo.com>]
Sent: 27 February 2012 13:24
To: xymon at xymon.com<mailto:xymon at xymon.com>; Morris, Chris (SS-IS)
Subject: RE: [Xymon] Ghost client problems
Hi,
Do you have anything under Ghost reports on the xymon server?
I don't have anything under ghost report.
Are the client and server on the same or different hosts?
They are running on different hosts.
Is the client pointing at the correct address and port for the xymon server
Yes it is pointing the correct address and port.
How do you know files are missing from ~/client/tmp directory .. what are you expecting to see there?
When the client functioned(the test were green in xymon server) correctly i saw two more files there logfetch.clientname.cfg and logfetch.clientname.status.
Have you checked the clientlaunch.log and xymonclient.log files for errors in ~/client/logs?
I see no errors.
Regards,
Traian.
--- On Mon, 2/27/12, Chris.Morris at rwe.com<mailto:Chris.Morris at rwe.com> <Chris.Morris at rwe.com<mailto:Chris.Morris at rwe.com>> wrote:
From: Chris.Morris at rwe.com<mailto:Chris.Morris at rwe.com> <Chris.Morris at rwe.com<mailto:Chris.Morris at rwe.com>>
Subject: RE: [Xymon] Ghost client problems
To: paveltraian at yahoo.com<mailto:paveltraian at yahoo.com>
Cc: xymon at xymon.com<mailto:xymon at xymon.com>
Date: Monday, February 27, 2012, 2:49 PM
Do you have anything under Ghost reports on the xymon server?
Are the client and server on the same or different hosts?
Is the client pointing at the correct address and port for the xymon server
How do you know files are missing from ~/client/tmp directory .. what are you expecting to see there?
Have you checked the clientlaunch.log and xymonclient.log files for errors in ~/client/logs?
________________________________
From: Pavel Traian [mailto:paveltraian at yahoo.com<mailto:paveltraian at yahoo.com>]
Sent: 27 February 2012 12:05
To: xymon at xymon.com<mailto:xymon at xymon.com>; Morris, Chris (SS-IS)
Subject: RE: [Xymon] Ghost client problems
Hi,
That one i have solved it, but....
Now i have reinstallled the client and i started it using ./runclient.sh --hostname=host start command from xymon user.
On the xymon server web page all the tests(disk,cpu etc) appear in violet colour and i see there the last report i had from when it functioned ok.
On the client i have issued some commands and you have the output here:
[root at otpproxy1 tmp]# ps -ef | grep xymon
xymon 3785 1 0 09:44 ? 00:00:00 ./bin/xymonlaunch --config=./etc/clientlaunch.cfg --log=./logs/clientlaunch.log --pidfile=./logs/clientlaunch.otpproxy1.pid
xymon 5892 1 0 13:54 ? 00:00:00 sh -c vmstat 300 2 1>./tmp/xymon_vmstat.otpproxy1.5867 2>&1; mv ./tmp/xymon_vmstat.otpproxy1.5867 ./tmp/xymon_vmstat.otpproxy1
xymon 5894 5892 0 13:54 ? 00:00:00 vmstat 300 2
root 5902 5686 0 13:57 pts/0 00:00:00 grep xymon
[root at otpproxy1 tmp]# ps -e | grep xymon
3785 ? 00:00:00 xymonlaunch
[root at otpproxy1 tmp]# ls -l
total 36
-rw-rw-r-- 1 xymon xymon 32690 Feb 27 13:54 msg.otpproxy1.txt
-rw-rw-r-- 1 xymon xymon 246 Feb 27 13:54 xymon_vmstat.otpproxy1.5867
[root at otpproxy1 tmp]#
As i see there are some files missing from tmp directory. I don't understand why.
Can you please give me a hint?
Regards,
Traian.
****************************************************************************
The information contained in this email is intended only for the use of the intended recipient at the email address to which it has been addressed. If the reader of this message is not an intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination or copying of the message or associated attachments is strictly prohibited. If you have received this email in error, please contact the sender by return email or call 01793 877777 and ask for the sender and then delete it immediately from your system.Please note that neither the RWE Group of Companies nor the sender accepts any responsibility for viruses and it is your responsibility to scan attachments (if any).
*****************************************************************************
_______________________________________________
Xymon mailing list
Xymon at xymon.com<mailto:Xymon at xymon.com>
http://lists.xymon.com/mailman/listinfo/xymon
_______________________________________________ Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20120229/a7e5494f/attachment.html>
More information about the Xymon
mailing list