[Xymon] Client install gone wrong

Diep, David (OCTO-Contractor) David.Diep at dc.gov
Wed Dec 18 14:49:46 CET 2013


Tim was very good with the explanation.  I went and removed the previous configuration. I then configured it as a client:


./configure --client was what I originally tried, but for some reason that did not find the pcre libraries.

I'm good now... I have one machine configured as the server, with the client information. My second machine is configured only with the client.

Thanks for all your help.

David Diep

From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au]
Sent: Tuesday, December 17, 2013 8:56 PM
To: Diep, David (OCTO-Contractor)
Cc: Tim McCloskey; xymon at xymon.com
Subject: Re: [Xymon] Client install gone wrong

On 18 December 2013 10:47, Diep, David (OCTO-Contractor) <David.Diep at dc.gov<mailto:David.Diep at dc.gov>> wrote:

"configure" is this local? Or do you have to specify "./configure --server" or "./configure --client" or "./configure"
You can do any of these.  When you run "./configure" it simply  runs "./configure.server" for you.  If you run "./configure --server" it does the same thing also.

If you run "./configure --client" then the configure script simply runs "./configure.client".

So there are several different ways to do the same two things.  Running "./configure --client" is the official way.

You can also do the following, which ensures that it builds a client using server-side configuration, without being prompted about it:

$ CONFTYPE=server ./configure --client

*         "configure.server" allows for client configurations as well as server configuration all on one machine

*         "configure.client" this does not work very well
This works fine, as long as you use "server configuration" (central configuration).  If you use "client configuration" (local configuration) then you run into the compile problem.

I did "./configure --server" on two machines. I see now that I only needed it on one machine and one machine only. All I need to do is update hosts.cfg, alerts.cfg, etc...

The server build also has a client build included (a Xymon server should also be a Xymon client, so that it can watch itself).  So another option is to manually copy the "xymon/client" directory from your server to any host you want to monitor, then just create the xymon user/group, make sure the "tmp" and "log" directories are writeable by this user, and create an init script to run the "runclient.sh" script.

Alternatively, after building (but not installing) the server code (./configure --server), you can do a client-only install:

$ make install-client

This will copy only the client parts of the install.  You still need to create the xymon user/group and setup the init script for runclient.sh.

I agree that the main install doco is not as clear as it could be, and focuses almost exclusively on the server setup.  However, there's a README.CLIENT file in the source that is a much better guide for installing just the client "agent".


Look out for those in need this winter. When the temperature or wind chill is 32?F or below, the District issues a Hypothermia Alert. For assistance during an Alert, call the Shelter Hotline<http://dhs.dc.gov/page/hypothermia-alert-plan> at 1-800-535-7252 or 311.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20131218/9fac17ff/attachment.html>

More information about the Xymon mailing list