Discussion:
[Xymon] client not sending to both servers
Ian Diddams via Xymon
2018-11-20 17:00:08 UTC
Permalink
client config in ~xymon/client/etc/hobbitclient.cfg
..BBDISP="0.0.0.0"             # IP address of the Hobbit serverBBDISPLAYS="192.168.55.243 192.168.52.64"                   # IP of multiple Hobbit servers. BBDISP must be "0.0.0.0"....

the server on 192.168.55.243 received all the epxted disk, cpu etc info and displays it fine.
But the server in 192.168.52.64 - doesn;t.

Ive sniffed the 1984 port on the server (..52.64) and nothing comes in.
Ive done the same on the client but I can see it going out...



basic monitoring works (conn) fine

Ive tested a quick script that "writes" a status message to a TEST alert on ...52.64 and that appears.

I can telnet from the client to ...52.64 on port 1984 fine.
ghost client report has nothing in it that could be the client.

Its as if the client isn;t even sending it to the swerver anyway (tcpdump etc)

ass I see in the logs is

hobbitclient.log:
2018-11-20 16:38:57 Whoops ! bb failed to send message - timeout2018-11-20 16:38:57 Failed to get a message, terminating


repeated over and over and over.



anyone any ideas?
or how to increase the logging level to "see" more stuff?
or...  ?
Malcolm Hunter
2018-11-20 17:29:20 UTC
Permalink
What happens if you swap the servers around in BBDISPLAYS?

That's a pretty old client. Have you considered upgrading?

Malc
---------- Forwarded message ----------
Date: Tue, 20 Nov 2018 17:00:08 +0000 (UTC)
Subject: client not sending to both servers
client config in ~xymon/client/etc/hobbitclient.cfg
..
BBDISP="0.0.0.0" # IP address of the Hobbit server
BBDISPLAYS="192.168.55.243 192.168.52.64" # IP of
multiple Hobbit servers. BBDISP must be "0.0.0.0".
...
the server on 192.168.55.243 received all the epxted disk, cpu etc info
and displays it fine.
But the server in 192.168.52.64 - doesn;t.
Ive sniffed the 1984 port on the server (..52.64) and nothing comes in.
Ive done the same on the client but I can see it going out...
basic monitoring works (conn) fine
Ive tested a quick script that "writes" a status message to a TEST alert
on ...52.64 and that appears.
I can telnet from the client to ...52.64 on port 1984 fine.
ghost client report has nothing in it that could be the client.
Its as if the client isn;t even sending it to the swerver anyway (tcpdump etc)
ass I see in the logs is
2018-11-20 16:38:57 Whoops ! bb failed to send message - timeout
2018-11-20 16:38:57 Failed to get a message, terminating
repeated over and over and over.
anyone any ideas?
or how to increase the logging level to "see" more stuff?
or... ?
---------- Forwarded message ----------
Date: Tue, 20 Nov 2018 17:00:08 +0000 (UTC)
Subject: [Xymon] client not sending to both servers
_______________________________________________
Xymon mailing list
http://lists.xymon.com/mailman/listinfo/xymon
Ron Cohen
2018-12-03 12:13:29 UTC
Permalink
Had the same issue when using client 4.3.18 (on HPUX 11.23) to 4.3.28
(Linux) server. as advised, maybe try to run the same version of client and
server.
Ron
Post by Malcolm Hunter
What happens if you swap the servers around in BBDISPLAYS?
That's a pretty old client. Have you considered upgrading?
Malc
---------- Forwarded message ----------
Date: Tue, 20 Nov 2018 17:00:08 +0000 (UTC)
Subject: client not sending to both servers
client config in ~xymon/client/etc/hobbitclient.cfg
..
BBDISP="0.0.0.0" # IP address of the Hobbit server
BBDISPLAYS="192.168.55.243 192.168.52.64" # IP of
multiple Hobbit servers. BBDISP must be "0.0.0.0".
...
the server on 192.168.55.243 received all the epxted disk, cpu etc info
and displays it fine.
But the server in 192.168.52.64 - doesn;t.
Ive sniffed the 1984 port on the server (..52.64) and nothing comes in.
Ive done the same on the client but I can see it going out...
basic monitoring works (conn) fine
Ive tested a quick script that "writes" a status message to a TEST alert
on ...52.64 and that appears.
I can telnet from the client to ...52.64 on port 1984 fine.
ghost client report has nothing in it that could be the client.
Its as if the client isn;t even sending it to the swerver anyway (tcpdump etc)
ass I see in the logs is
2018-11-20 16:38:57 Whoops ! bb failed to send message - timeout
2018-11-20 16:38:57 Failed to get a message, terminating
repeated over and over and over.
anyone any ideas?
or how to increase the logging level to "see" more stuff?
or... ?
---------- Forwarded message ----------
Date: Tue, 20 Nov 2018 17:00:08 +0000 (UTC)
Subject: [Xymon] client not sending to both servers
_______________________________________________
Xymon mailing list
http://lists.xymon.com/mailman/listinfo/xymon
_______________________________________________
Xymon mailing list
http://lists.xymon.com/mailman/listinfo/xymon
Loading...