This was done on centos 7 minimal install. I'm documenting the entire process for a project I'm working on (we're upgrading from hobbit) and it take only a few minutes from bare-metal to functioning xymon server. I highly recommend using the packages.

You may not need the other packages, but I wanted them for my purposes. It is VERY convenient to use the Terabithia packages instead of installing from source.

I don't know if this helps you or not (or even if it's the right way to do this) since I'm relatively new to all of this but... This is how I did it (assuming you're setting up a new system, perform these commands as root or using sudo):

yum -y install epel-release wget telnet lz4 wget --directory-prefix=/etc/yum.repos.d http://terabithia.org/rpms/xymon/terabithia-xymon.repo yum -y install xymon systemctl enable httpd systemctl start httpd.service systemctl start xymonlaunch.service firewall-cmd --permanent --zone=public --add-service=http firewall-cmd --reload

Your xymon apache config will be here: /etc/httpd/conf.d/xymon.conf (works out of the box) The rest of the xymon config will be in /etc/xymon (also works out of the box)

-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of J.C. Cleaver Sent: Tuesday, February 9, 2016 5:17 PM To: Galen Johnson <Galen.Johnson at sas.com> Cc: xymon at xymon.com Subject: Re: [Xymon] terabithia vs self compiled

On Tue, February 9, 2016 2:36 pm, Galen Johnson wrote:

Hey,

I'm considering switching over to using the RPMs that JC provides through Terabithia rather than compiling from scratch. I'm assuming it should as simple as just copying over the RPMs and yum installing them. Any gotcha's to look out for? Just want to be sure that my tweaks to the various configs will work and the best way to handle the client tests. I use include and directory a fair bit.

For a general overview of the changes, see http://terabithia.org/rpms/xymon/xymon.README.terabithia. I'd definitely advise testing first.

The biggest immediately-visible difference between the two is that everything's in FHS locations in the RPM, and $XYMON(CLIENT)HOME is de-emphasized throughout. On the client the RPM version of xymonclient.cfg does an "include" on /etc/sysconfig/xymon-client to bring in the destination server (which on a msgscache-enabled box would be 127.0.0.1). If you're deploying straight over an existing install your xymonclient.cfg won't be replaced, so you'll need to bring that line in by hand. (This is somewhat inverted from the runclient.sh logic.)

include and directory should work as expected for the rest of your configurations. The RPM creates ".d" directories for most of the configs and includes them. I tend to leave the main configs untouched.

On the main xymon server, you'll want both the "xymon" and "xymon-client" RPMs. The "local client" on the main server is handled with an include in xymonserver.cfg to the xymonclient.cfg file, which is then handled like normal. (This lets your main xymon server report its own data to multiple locations like any other client.)

I've never exactly been clear on 'local' mode but the majority of my monitored systems use msgcache/pulldata so I'm not sure which client rpm makes the most sense.

"local" mode is when thresholds are being evaluated on the client itself instead of by your main xymond server. This means the client is taking the raw data and sending it to a local copy of xymond_client to, using your configs in localclient.cfg, turn that into red/yellow/green status messages for the xymon server (for example, for CPU load).

In xymon's "server" mode (which is the default), all of this processing happens centrally according to rules specified at the xymond server in analysis.cfg.

If you're running a client in "local" mode using the RPMs, you'll also want the "xymon-client-local" package on top of "xymon-client". (It's broken up this way because xymond_client needs PCRE, so that's another dependency.)

Also, is there a repository definition I can add that will let me just run 'yum update' and it can bring in the updated rpms? I didn't see anything obvious on the terabithia site (or I could just be blind).

This should be what you need: http://terabithia.org/rpms/xymon/terabithia-xymon.repo

HTH,

-jc

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

Thanks, JC. I figured it would be FHS (I do so love the simplicity of /usr/local, though). I'm going to have to refactor git and ansible (fortunately not fully baked yet) to accommodate this but it should be worth the effort to be able to just 'yum update'.

Thanks for clarifying "local". Not my setup but I can see how it is helpful.

=G=

From: J.C. Cleaver <cleaver at terabithia.org> Sent: Tuesday, February 9, 2016 6:17 PM To: Galen Johnson Cc: xymon at xymon.com Subject: Re: [Xymon] terabithia vs self compiled

On Tue, February 9, 2016 2:36 pm, Galen Johnson wrote:

Hey,

I'm considering switching over to using the RPMs that JC provides through Terabithia rather than compiling from scratch. I'm assuming it should as simple as just copying over the RPMs and yum installing them. Any gotcha's to look out for? Just want to be sure that my tweaks to the various configs will work and the best way to handle the client tests. I use include and directory a fair bit.

For a general overview of the changes, see http://terabithia.org/rpms/xymon/xymon.README.terabithia. I'd definitely advise testing first.

The biggest immediately-visible difference between the two is that everything's in FHS locations in the RPM, and $XYMON(CLIENT)HOME is de-emphasized throughout. On the client the RPM version of xymonclient.cfg does an "include" on /etc/sysconfig/xymon-client to bring in the destination server (which on a msgscache-enabled box would be 127.0.0.1). If you're deploying straight over an existing install your xymonclient.cfg won't be replaced, so you'll need to bring that line in by hand. (This is somewhat inverted from the runclient.sh logic.)

include and directory should work as expected for the rest of your configurations. The RPM creates ".d" directories for most of the configs and includes them. I tend to leave the main configs untouched.

On the main xymon server, you'll want both the "xymon" and "xymon-client" RPMs. The "local client" on the main server is handled with an include in xymonserver.cfg to the xymonclient.cfg file, which is then handled like normal. (This lets your main xymon server report its own data to multiple locations like any other client.)

I've never exactly been clear on 'local' mode but the majority of my monitored systems use msgcache/pulldata so I'm not sure which client rpm makes the most sense.

"local" mode is when thresholds are being evaluated on the client itself instead of by your main xymond server. This means the client is taking the raw data and sending it to a local copy of xymond_client to, using your configs in localclient.cfg, turn that into red/yellow/green status messages for the xymon server (for example, for CPU load).

In xymon's "server" mode (which is the default), all of this processing happens centrally according to rules specified at the xymond server in analysis.cfg.

If you're running a client in "local" mode using the RPMs, you'll also want the "xymon-client-local" package on top of "xymon-client". (It's broken up this way because xymond_client needs PCRE, so that's another dependency.)

Also, is there a repository definition I can add that will let me just run 'yum update' and it can bring in the updated rpms? I didn't see anything obvious on the terabithia site (or I could just be blind).

This should be what you need: http://terabithia.org/rpms/xymon/terabithia-xymon.repo

HTH,

-jc