Xymon Mailing List Archive search

xymonnet sending status to Xymon 4.3.0~beta2

3 messages in this thread

list Thomas · Thu, 9 Oct 2014 11:32:47 +0200 ·
Hi,

I am trying to send status messages from xymonnet (4.3.17) to another Xymon
server still running 4.3.0~beta2.

Status messages are transferred via network, no errors are reported in the
logfiles. However the status isn't updated on the receiving Xymon
server.

Sending messages from bbtest-net (4.3.0~beta2) to the receiving server
mentioned above works fine. Did the protocol changed between those
versions or do you have any other ideas why it isn't working? 

Best regards
Thomas
list Glauber Ribeiro · Thu, 9 Oct 2014 15:33:05 +0000 ·
Have you checked your ghost clients (on the server, "Reports" menu). In my experience, many times this is caused by the client reporting a name that doesn't match what's in hosts.cfg. If that's the problem, it can be fixed in the client side (command line override or just edit xymon.sh), or on the server side (with an alias in hosts.cfg).

g
quoted from Thomas

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Thomas
Sent: Thursday, October 09, 2014 04:33
To: xymon at xymon.com
Subject: [Xymon] xymonnet sending status to Xymon 4.3.0~beta2

Hi,

I am trying to send status messages from xymonnet (4.3.17) to another Xymon
server still running 4.3.0~beta2.

Status messages are transferred via network, no errors are reported in the
logfiles. However the status isn't updated on the receiving Xymon
server.

Sending messages from bbtest-net (4.3.0~beta2) to the receiving server
mentioned above works fine. Did the protocol changed between those
versions or do you have any other ideas why it isn't working? 

Best regards
Thomas
list Thomas · Mon, 13 Oct 2014 09:45:12 +0200 ·
Hi Glauber,
quoted from Glauber Ribeiro

On Thu, Oct 09, 2014 at 03:33:05PM +0000, Ribeiro, Glauber wrote:
Have you checked your ghost clients (on the server, "Reports" menu).
In my experience, many times this is caused by the client reporting a
name that doesn't match what's in hosts.cfg. If that's the problem, it
can be fixed in the client side (command line override or just edit
xymon.sh), or on the server side (with an alias in hosts.cfg).
thank you very much for your response. I've checked ghost clients and
the log files and verified that packets are transferred on port 1984.
Everything looks good.
Unfortunately the status on the receiving Xymon server isn't updated or
shown.

I've tested it the other way round, i.e. sending from the old version to
the new one. This works fine. 

Probably the protocol has slightly changed preventing the older version
from accepting messages from Xymon 4.3.17.

Best regards
Thomas