[Newbie] Understanding client-server configuration (terabithia's rpm 4.3.10-1.fc17) 🔗 link

Hello.

I attempt to setup xymon from terabithia's packages
(rebuilded 4.3.10-1.fc17.src.rpm with small changes for ALT Linux)

Xymon's server works and ready for receive data from clients I think:
tcp   0   0 0.0.0.0:1984    0.0.0.0:*        LISTEN      3557/xymond         
Web pages generated correctly. All server's tests works.

Now I attempt to setup client. So, 3 questions. 

1. I need to make some network's tests on client and transfer results
to server. Should I setup client installation or server installation
in this case ?

2. I found a bug in packages. xymon and xymon-client packages contains
/usr/libexec/xymon-client/xymonclient.sh with code:
Is this script need always ?
if test "$LOCALMODE" = "yes"; then
        echo "@@" >> $MSGTMPFILE
        /usr/libexec/xymon-client/xymond_client --local <$MSGTMPFILE
else

xymond_client exist in xymon package only and by another path:
/usr/libexec/xymon/xymond_client

Is this script need always ? Could this be the cause of problems in the
client ?

3. About package. 
xymon package contains xymonclient-*.sh for non linux. All this removed
from xymon-client. Are they forgotten in xymon package or they needed ?

-- 
Regards, Sergey

On Wednesday 27 of February 2013 13:24:01 Sergey wrote:

/usr/libexec/xymon-client/xymonclient.sh with code:

if test "$LOCALMODE" = "yes"; then
        echo "@@" >> $MSGTMPFILE
        /usr/libexec/xymon-client/xymond_client --local <$MSGTMPFILE
else

"Is this script need always ?" - unfortunate copy-and-paste before
code block...

-- 
Regards, Sergey

On 27 February 2013 20:24, Sergey <user-b81e5492d2d9@xymon.invalid> wrote:

It depends on the network tests you want to run.  If they are standard
xymonnet checks, such as ssh or dns, then you only need to configure them
on the server in hosts.cfg.  Can you tell us what network tests you want to
run?

I've never run in localmode, so not sure.  But it would seem that
xymond_client binary only exists in the Xymon server package, and not in
the Xymon client package.  My Xymon clients (that aren't servers) don't
have xymond_client anywhere.  From reading the localclient.cfg file, it
would seem that the "--local" option is only for use on Xymon clients that
are also Xymon servers.

xymond_client exist in xymon package only and by another path:

/usr/libexec/xymon/xymond_client

On my system, the line that calls this in xymonclient.sh is:

        $XYMONHOME/bin/xymond_client --local
--config=$XYMONHOME/etc/localclient.cfg <$MSGTMPFILE

I think your package's xymonclient.sh is incorrect, and probably should be
using this:

        /usr/libexec/xymon/xymond_client --local <$MSGTMPFILE

Is this script need always ?


No, only in "local" mode.

Could this be the cause of problems in the
client ?

Only if you're running it in local mode, by specifying "--local" in the
"[xymonclient]" section of tasks.cfg.

Nope, they're not needed.  But they're always there.  It makes it easy to
copy the files to another server and run them.  The original BB was
generally copied around in this way, before packaging became popular, so
perhaps this is a legacy of Xymon's origins.

J

On Thursday 28 February 2013, Jeremy Laidman wrote:

I need connections tests to another hosts. If I understood correctly, I need
to install the server in this case. Ok. I attempted to do it now. Secondary
server sending self data (cpu, disk e.t.c.) to main server, but not sending
information about connection.  hosts.cfg of secondary server:

0.0.0.0         xymon-client.my.dom                # bbd
172.30.1.10     server2.my.dom                     #

I see only  "xymon-server.my.dom" and "xymon-client.my.dom" (with their
tests) on information web page of mail server. Is there a chance to see
"server2.my.dom" on the main server ?

Ok, thanks. I will try to verify with it later.

Thanks again.

It makes it easy to copy the files to another server and run them.

But xymon contains binary files. They should be rebuild for another
system...

-- 
Regards,
Sergey

On 28 February 2013 23:28, Sergey <user-b81e5492d2d9@xymon.invalid> wrote:

No, you only need to install the Xymon server software where you want to
collect and display the test results. With this alone, the Xymon server can
display the results of any network tests (conn=ping, ssh, smtp, dns, http)
sent to any other server.  No other software is required, just the Xymon
server software.

If the Xymon server needs to monitor its own OS parameters (CPU, memory,
disk), it also needs to have the Xymon client software installed and
running.

If the Xymon server needs to monitor another host's OS parameters (CPU,
memory, disk), the Xymon client software needs to be installed onto the
other host.

No, because connections are tested by the Xymon server, not the other
server.

 hosts.cfg of secondary server:

No hosts.cfg is required on the secondary server, because it is only a
Xymon client.  It only needs the Xymon client software installed and
running.

I see only  "xymon-server.my.dom" and "xymon-client.my.dom" (with their

Yes.  Add server2.my.dom into hosts.cfg on the Xymon server.

Correct.  They are probably there just because they were always there.

J

On Friday 01 of March 2013 13:45:00 you wrote:

Possible I did not wrote correctly in  English... I will draw it. 

host 1 (Xymon server / web)
   |
   |
host 2 (Xymon server 2 or Xymon client ?)
   |
   |
host 3 

"host 3" is not avaliable from "host 1". "host 2" should make ping test
and send result to "host 1".

I.e. "host 2" should contains Xymon server installation because the
"ping test" is not of the OS parameter. Yes ?

"ping test" for "host 3" will be unsuccessful from main Xymon server
(host 1). :-(

-- 
Regards, Sergey

On Friday 01 of March 2013 12:17:05 Sergey wrote:

It works! :-)

hosts.cfg on "host 1":

172.30.1.10      server2.my.dom              # noconn

hosts.cfg on "host 2":

172.30.1.10      server2.my.dom              #

"server2.my.dom" is the "host 3".

The problem was in the following. xymonserver.cfg contains

# General settings
XYMONDPORT="1984"               # Portnumber where xymond listens
XYMSRV="0.0.0.0"                # IP of a single Xymon server
XYMSERVERS="$XYMONSERVERIP"     # IP of multiple Xymon servers. If used, XYMSRV must be 0.0.0.0

I attempted to configure Xymon on "host 2" via XYMSERVERS variable
and it did not work. The "ping test" data begin transmitted to the
"host 1" when I used the variable XYMSRV as point to "host 1".
This is probably a bug Xymon or xymon's rpm package...

-- 
Regards, Sergey

Host 3 would have the xymon client on it. 
Host 2 would have the xymon server on it, configured as a proxy. You may also have the server on it on a separate port, if you want.

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Sergey
Sent: Friday, March 01, 2013 2:17 AM
To: xymon at xymon.com
Subject: Re: [Xymon] [Newbie] Understanding client-server configuration (terabithia's rpm 4.3.10-1.fc17)

On Friday 01 of March 2013 13:45:00 you wrote:

Possible I did not wrote correctly in  English... I will draw it. 
host 1 (Xymon server / web)
   |
   |
host 2 (Xymon server 2 or Xymon client ?)
   |
   |
host 3 
"host 3" is not avaliable from "host 1". "host 2" should make ping test and send result to "host 1".

I.e. "host 2" should contains Xymon server installation because the "ping test" is not of the OS parameter. Yes ?

"ping test" for "host 3" will be unsuccessful from main Xymon server (host 1). :-(

--
Regards, Sergey

On Friday 01 of March 2013 14:09:09 Root, Paul wrote:

I would like to consider the situation when the "host 3" is a switch
or any other host where I can not install software.

Proxy can be good idea for some other cases, thanks.

-- 
Regards, Sergey

On Friday 01 March 2013, Sergey wrote:

host 1 (Xymon server / web)
   |
   |
host 2 (Xymon server)
   |
   |
host 3 

It works! :-)

 
Hm... It not only works... :-)
I found in reports.log on "host 2":

2013-03-06 01:03:58 Weird file '/var/lib/xymon/hist/hostX.telnet' skipped
2013-03-06 01:03:58 Weird file '/var/lib/xymon/hist/hostX.ssh' skipped
2013-03-06 01:03:58 Weird file '/var/lib/xymon/hist/hostX.ftp' skipped
2013-03-06 01:03:58 Weird file '/var/lib/xymon/hist/hostX.bbd' skipped
2013-03-06 01:03:58 Weird file '/var/lib/xymon/hist/hostX.conn' skipped

hostX is checking from "host 1". Xymon's servers are exchanging
of information ? Can I disable transfer from host 1 to host 2 ?

-- 
Regards,
Sergey