4.3.4 proxy to a 4.2.3 server

Ok, I fixed the rrd issue, and I'm getting graphs again. So that's good.

I stopped the second proxy for testing and sure enough, 15-20 minutes later, the conn's for all the devmon routers went purple. All the tests seemed fine just the conn.
Also, ntp went purple on a bunch as well.

I was starting to thing devmon was reporting straight to the server port instead of the proxy, but the test server is getting updates. So I'm kind of stumped.

This is my tasks.cfg entry:
[xymond]
        ENVFILE /usr/lib64/xymon/server/etc/xymonserver.cfg
        CMD xymond --listen=0.0.0.0:1985 --pidfile=$XYMONSERVERLOGS/xymond.pid --restart=$XYMONTMP/xymond.chk --checkpoint-file=$XYMONTMP/xymond.chk --checkpoint-interval=600 --log=$XYMONSERVERLOGS/xymond.log --admin-senders=127.0.0.1,$XYMONSERVERIP --store-clientlogs=!msgs

[xymonproxy]
        ENVFILE /usr/lib64/xymon/server/etc/xymonserver.cfg
        CMD $XYMONHOME/bin/xymonproxy --server=127.0.0.1:1985,172.28.96.89,192.168.141.212 --listen=0.0.0.0:1984 --report=$MACHINE.xymonproxy --no-daemon --pidfile=$XYMONSERVERLOGS/xymonproxy.pid
        LOGFILE $XYMONSERVERLOGS/xymonproxy.log

I see connections with netstat -a on the server, and tcpdump port 1984 and hostname stnxymproxy gives me lots of output.


Paul Root    - Engineer III  - Qwest is now CenturyLink

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On
Behalf Of Root, Paul
Sent: Wednesday, August 24, 2011 3:24 PM
To: 'Henrik Størner'; xymon at xymon.com
Subject: Re: [Xymon] 4.3.4 proxy to a 4.2.3 server

Ok, thanks.

I'll check the primary, I thought I saw traffic from the 4.3.4 machine,
maybe not.

Ah, ha! Right, the test server has rrd 1.4.5, I don't have that on the
proxy.

Paul Root    - Engineer III  - Qwest is now CenturyLink

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On
Behalf Of Henrik Størner
Sent: Wednesday, August 24, 2011 3:18 PM
To: xymon at xymon.com
Subject: Re: [Xymon] 4.3.4 proxy to a 4.2.3 server

On 24-08-2011 21:32, Root, Paul wrote:

Is there an issue with a 4.3.4 sending proxy data to an older
server?

Don't think so. There has only been two changes in the proxy code
going
from 4.2.3 -> 4.3.4:

a) the proxy will no longer forward "page" messages as sent by old

(Big

Brother style) clients - Xymon doesn't use these at all.

b) the "--hobbitd" option has been removed; xymonproxy always assumes
it
is sending data to a Xymon server, so it re-packages combo-messages
and
adds information about what proxy the message passed through.

I don't see either of these changes breaking compatibility with a

4.2.x

server. On the old Hobbit server, do you see any connections from the
proxy (check with netstat) ? Does the proxy log show that it is
sending
data to the old server ?

I also just found some other information, on the 4.3.4 in the log
files:
2011-08-24 14:20:52 Peer not up, flushing message queue
xymond_rrd: error while loading shared libraries: librrd.so.4:

cannot

open shared object file: No such file or directory

The rrdtool libraries are missing from the server where you are
running
Xymon, or at least xymond_rrd cannot find them. My guess is that
you've
compiled the Xymon server software on another system than where you
are
running it. Make sure you have rrdtool installed, with the same major
version as you had on the system where it was compiled.


Regards,
Henrik

This communication is the property of CenturyLink and may contain
confidential or privileged information. Unauthorized use of this
communication is strictly
prohibited and may be unlawful.  If you have received this
communication
in error, please immediately notify the sender by reply e-mail and
destroy
all copies of the communication and any attachments.

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.