[Xymon] Ghost client problems

Pavel Traian paveltraian at yahoo.com
Thu Feb 23 14:51:08 CET 2012


Hi,
I have removed the second instance and it works ok now.
Thanks for your time.
Regards,
Traian.

--- On Thu, 2/23/12, Steven Carr <sjcarr at gmail.com> wrote:

From: Steven Carr <sjcarr at gmail.com>
Subject: Re: [Xymon] Ghost client problems
To: "Pavel Traian" <paveltraian at yahoo.com>
Cc: xymon at xymon.com
Date: Thursday, February 23, 2012, 2:15 PM

What processes are running or have open files containing xymon...

ps -ef | grep xymon
lsof | grep xymon

If any of those processes are not the ones you have started (or are running as root) then that is your culprit.


Steve



On 23 February 2012 12:03, Pavel Traian <paveltraian at yahoo.com> wrote:


Hi,
This is my original question.
If i knew the answer i shouldn't ask for help.
I don't know where to check and what to check.

Regards,
Traian.


--- On Thu, 2/23/12, Steven Carr <sjcarr at gmail.com> wrote:


From: Steven Carr <sjcarr at gmail.com>
Subject: Re: [Xymon] Ghost client problems
To: "Pavel Traian" <paveltraian at yahoo.com>, xymon at xymon.com

Date: Thursday, February 23, 2012, 1:43 PM

Why are the FQDN named files owned by root? this would seem to indicate that root is running commands to output those files? xymon client should be running as the xymon user only. Is something else on your system starting up a second instance of the client?



Steve




On 23 February 2012 11:30, Pavel Traian <paveltraian at yahoo.com> wrote:


Hi,
I have manually compiled it.
I start it using ./runclient.sh --hostname=otpproxy1 start command.(otpproxy1 is the client name in hosts.cfg)


Here you have the commands i gave:

[xymon at otpproxy1 tmp]$ rm -f *
[xymon at otpproxy1 tmp]$ ls -l
total 0
[xymon at otpproxy1 tmp]$
[xymon at otpproxy1 tmp]$
[xymon at otpproxy1 tmp]$
[xymon at otpproxy1 tmp]$ cd ..


[xymon at otpproxy1 client]$ ./runclient.sh --hostname=otpproxy1 start
Xymon client for linux started on otpproxy1
[xymon at otpproxy1 client]$ cd tmp
[xymon at otpproxy1 tmp]$ ls -l
total 44
-rw-rw-r-- 1 xymon xymon    41 Feb 23 13:13 logfetch.otpproxy1.cfg


-rw-rw-r-- 1 xymon xymon 33175 Feb 23 13:13 msg.otpproxy1.txt
-rw-rw-r-- 1 xymon xymon   246 Feb 23 13:12 xymon_vmstat.otpproxy1.7180
[xymon at otpproxy1 tmp]$ ls -l
total 84
-rw-rw-r-- 1
 xymon xymon    41 Feb 23 13:18 logfetch.otpproxy1.cfg
-rw-rw-r-- 1 xymon xymon    35 Feb 23 13:18 logfetch.otpproxy1.status
-rw-r--r-- 1 root  root  32347 Feb 23 13:17 msg.otpproxy1.temenosgroup.com.txt
-rw-rw-r-- 1 xymon xymon 35555 Feb 23 13:18 msg.otpproxy1.txt


-rw-rw-r-- 1 xymon xymon   246 Feb 23 13:17 xymon_vmstat.otpproxy1.7262
-rw-r--r-- 1 root  root    246 Feb 23 13:16 xymon_vmstat.otpproxy1.temenosgroup.com.7223
[xymon at otpproxy1 tmp]$

After i start it i have only msg.otpproxy1.txt file in tmp folder but after a while i have also msg.otpproxy1.temenosgroup.com.txt file.


Why does it happen? What do i do wrong?
Regards,
Traian.



--- On Thu, 2/23/12, Steven Carr <sjcarr at gmail.com> wrote:



From: Steven Carr
 <sjcarr at gmail.com>
Subject: Re: [Xymon] Ghost client problems
To: "Pavel Traian" <paveltraian at yahoo.com>


Cc: xymon at xymon.com
Date: Thursday, February 23, 2012, 12:36 PM

How did you install the client, manual compilation or from one of the RPMs that others have built?



If you did it manually then in your init script add --hostname=XYZ as a parameter to runclient.sh (this does appear to map to the MACHINEDOTS variable inside runclient.sh).


Steve


On 23 February 2012 10:29, Pavel Traian <paveltraian at yahoo.com> wrote:



Hi,
I don't find any CLIENTNAME variable, but i have MACHINEDOTS variable in the runclient.sh which is said to be "# This systems hostname".



I changed it to use 'hostanme -s' and still the same result as in the first message.
I have these files in tmp folder:

> -rw-rw-r-- 1 xymon xymon    41 Feb 22 13:17

> logfetch.otpproxy1.cfg

> -rw-rw-r-- 1 xymon xymon    41 Feb 22 13:17

> logfetch.otpproxy1.status

> -rw-r--r-- 1 root  root  35787 Feb 22 13:17

> msg.otpproxy1.temenosgroup.com.txt

> -rw-rw-r-- 1 xymon xymon 37183 Feb 22 13:17

> msg.otpproxy1.txt

> -rw-rw-r-- 1 xymon xymon   246 Feb 22 13:17

> xymon_vmstat.otpproxy1.2637

> -rw-rw-r-- 1 xymon xymon   246 Feb 22 13:14

> xymon_vmstat.otpproxy1.temenosgroup.com.2597

> -rw-r--r-- 1 root  root    246 Feb 22 13:17

> xymon_vmstat.otpproxy1.temenosgroup.com.2681
 

Do you have any explanation why i have all these files? Shouldn't it be only one named msg.otpproxy1.txt and not the second named msg.otpproxy1.temenosgroup.com.txt?
Regards,
Traian.




--- On Thu, 2/23/12, Steven Carr <sjcarr at gmail.com> wrote:




From: Steven Carr <sjcarr at gmail.com>
Subject: Re: [Xymon] Ghost client problems
To: "Pavel Traian" <paveltraian at yahoo.com>, xymon at xymon.com



Date: Thursday, February 23, 2012, 12:17 PM

To use the shortname just change the CLIENTHOSTNAME variable to be the shortname, you can use whatever you want aslong as it matches with what you have in the main bb-hosts/hosts.cfg.




Steve




On 23 February 2012 09:51, Pavel Traian <paveltraian at yahoo.com> wrote:




Hi,
If i want to use the short name how do i proceed?
What config files from the client installation should I modify? 




Regards,
Traian.


--- On Thu, 2/23/12, Steven Carr <sjcarr at gmail.com> wrote:





From: Steven Carr <sjcarr at gmail.com>
Subject: Re: [Xymon] Ghost client problems
To: "Pavel Traian" <paveltraian at yahoo.com>, xymon at xymon.com




Date: Thursday, February 23, 2012, 11:02 AM

On all of our systems I force the client to use it's FQDN, in /etc/sysconfig/xymon I configure the CLIENTHOSTNAME variable to be the FQDN e.g. as part of our build script it runs:





sed -i "s/# CLIENTHOSTNAME=\"\"/CLIENTHOSTNAME=\"`hostname -f`\"/g" /etc/sysconfig/xymon


Steve



On 23 February 2012 08:45, Pavel Traian <paveltraian at yahoo.com> wrote:





Hi,

I have added the short name to hosts.cfg otpproxy1 not otpproxy1.temenosgroup.com. On the Xymon page i have the conn, disk, cpu, procs... all the tests are active there(it means the server receives the client data report).






But the client seems to send the data report using the FQDN also and the server sees it like ghost client.

How can i do to prevent it.

Regards,

Traian.







Simple stuff first, do you have the client listed in ~/server/etc/hosts.cfg ?



A little clarification: ghost clients are generally clients that are sending data to the server, but the server is not configured to display them.



--- On Wed, 2/22/12, Pavel Traian <paveltraian at yahoo.com> wrote:



> From: Pavel Traian <paveltraian at yahoo.com>

> Subject: Ghost client problems

> To: xymon at xymon.com

> Date: Wednesday, February 22, 2012, 1:51 PM

> Hi,

> I have installed a xymon client on a CentOS 6 x64 server.

> Everything looks good except the fact that even the Xymon

> server receives data and its' page is OK(the client is there

> diplayed with its' short name) i have the same client

> displayed in Ghost Clients(this time with its' FQDN).

> I have checked on the client and i have too many files in

> xymon/client/tmp folder.

> It looks something like this:

>

> -rw-rw-r-- 1 xymon xymon    41 Feb 22 13:17

> logfetch.otpproxy1.cfg

> -rw-rw-r-- 1 xymon xymon    41 Feb 22 13:17

> logfetch.otpproxy1.status

> -rw-r--r-- 1 root  root  35787 Feb 22 13:17

> msg.otpproxy1.temenosgroup.com.txt

> -rw-rw-r-- 1 xymon xymon 37183 Feb 22 13:17

> msg.otpproxy1.txt

> -rw-rw-r-- 1 xymon xymon   246 Feb 22 13:17

> xymon_vmstat.otpproxy1.2637

> -rw-rw-r-- 1 xymon xymon   246 Feb 22 13:14

> xymon_vmstat.otpproxy1.temenosgroup.com.2597

> -rw-r--r-- 1 root  root    246 Feb 22 13:17

> xymon_vmstat.otpproxy1.temenosgroup.com.2681

>

> It seems like the client is started al least twice....

> How can I set it right?

> Regards,

> Traian.

>

_______________________________________________

Xymon mailing list

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/20120223/3b648ce3/attachment.html>


More information about the Xymon mailing list