4.3.4 proxy to a 4.2.3 server

7 messages in this thread

list Paul Root · Wed, 24 Aug 2011 14:32:08 -0500 ·

I have 2 proxy servers forwarding up to a main server. One has been upgraded to 4.3.4 and the other is still 4.2.3.

I went to upgrade the second server today, and it went badly. I got a huge amount of purple faces. Mostly on conn for my devmon clients and ntp for my regular clients.

The devmon clients are noconn on the server, for various reasons, and the regular servers have ntp in the proxy's hosts.cfg/bb-hosts file, but not in the servers bb-hosts file, due to firewalling issues.

Anyway, I'm starting to think that my 4.3.4 proxy is not actually proxying up to the main server. It proxies to itself (on 1985) and a 4.3.4 test server just fine.

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

I also just found some other information, on the 4.3.4 in the log files:

rrd-data.log:
2011-08-24 14:20:52 Peer not up, flushing message queue
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
2011-08-24 14:20:52 Peer at 0.0.0.0:0 failed: Broken pipe
2011-08-24 14:21:09 Peer not up, flushing message queue
2011-08-24 14:21:09 Peer not up, flushing message queue
2011-08-24 14:21:09 Peer not up, flushing message queue
2011-08-24 14:21:11 Peer not up, flushing message queue
2011-08-24 14:21:11 Peer not up, flushing message queue
2011-08-24 14:21:11 Peer not up, flushing message queue

And rrd-status.log is the same.

And so I look at the web of the 4.3.4 server and there are no graphs. There are graphs on the test server.

Any ideas?

Paul Root - Engineer III - Qwest is now CenturyLink

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.

list Henrik Størner · Wed, 24 Aug 2011 22:17:34 +0200 ·

▸ quoted from Paul Root

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 ?

▸ quoted from Paul Root

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

list Paul Root · Wed, 24 Aug 2011 15:24:00 -0500 ·

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

▸ quoted from Henrik Størner


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.

list Paul Root · Thu, 25 Aug 2011 11:08:38 -0500 ·

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.

▸ quoted from Paul Root



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

▸ quoted from Paul Root

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.

list Paul Root · Thu, 25 Aug 2011 11:57:23 -0500 ·

So I removed xymon completely from my test server, and reinstalled 4.2.3. It only gets it's info from the 4.3.4 proxy server not both.

Works fine.

Which just goes to confuse me more.

▸ quoted from Paul Root



Paul Root    - Engineer III  - Qwest is now CenturyLink

-----Original Message-----
From: Root, Paul
Sent: Thursday, August 25, 2011 11:09 AM
To: Root, Paul; 'Henrik Størner'; xymon at xymon.com
Subject: RE: [Xymon] 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

▸ quoted from Paul Root


[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.

list Paul Root · Thu, 25 Aug 2011 12:41:17 -0500 ·

I spoke to soon. Which is good. At least I have some consistency.

The test box was able to ping the DEVMON machines, so no purple. I put noconn in the bb-hosts file, and that brought the blanket purple across the whole devmon machines. I also noticed that there was no ntp columns anywhere. The test server doesn't run the ntp test, just the proxy.

So, here's what I know: The 4.3.4 proxy server does not forward  conn and ntp tests to its servers.

And that almost makes sense. Those two tests would be run in the server part of the server, not the client or the proxy, so it probably never tells the proxy anything about them, and therefore it doesn't propagate.

So, now the question is, why does the 4.2.3 server propagate those tests through the proxy? And why are other tests like http not show this problem?

Actually, may it does, but I have http in all bb-hosts/hosts.cfg files. I'll test that next.

And lastly, how to I get the proxy to propagate those tests? Because, the main server can't get through the firewall for much of that.

Paul.

▸ quoted from Paul Root


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: Thursday, August 25, 2011 11:57 AM

▸ signature

To: 'Henrik Størner'; xymon at xymon.com
Subject: Re: [Xymon] 4.3.4 proxy to a 4.2.3 server

So I removed xymon completely from my test server, and reinstalled
4.2.3. It only gets it's info from the 4.3.4 proxy server not both.

Works fine.

Which just goes to confuse me more.

Paul Root    - Engineer III  - Qwest is now CenturyLink

-----Original Message-----

▸ quoted from Paul Root

From: Root, Paul
Sent: Thursday, August 25, 2011 11:09 AM
To: Root, Paul; 'Henrik Størner'; xymon at xymon.com
Subject: RE: [Xymon] 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

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

▸ quoted from Paul Root

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.

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.

list Paul Root · Thu, 25 Aug 2011 13:36:04 -0500 ·

You can almost hear the gears slowly turning in my brain.

Bbtest-net (now xymonnet) does the tests, not xymond.

So, the secret was that I had BBPORT=1984 in the cmd line. Xymonnet wants XYMONDPORT.

 [xymonnet]
        ENVFILE /usr/lib64/xymon/server/etc/xymonserver.cfg
        NEEDS xymond
        CMD XYMONDPORT=1984 bbtest-net --report --ping --checkresponse
        LOGFILE $BBSERVERLOGS/bb-network.log
        INTERVAL 5m

 [xymonnetagain]
        ENVFILE /usr/lib64/xymon/server/etc/xymonserver.cfg
        NEEDS xymond
        CMD XYMONDPORT=1984 $BBHOME/ext/bbretest-net.sh
        LOGFILE $BBSERVERLOGS/bb-retest.log
        INTERVAL 1m

▸ quoted from Paul Root



Paul Root    - Engineer III  - Qwest is now CenturyLink

-----Original Message-----
From: Root, Paul
Sent: Thursday, August 25, 2011 12:41 PM
To: Root, Paul; 'Henrik Størner'; xymon at xymon.com
Subject: RE: [Xymon] 4.3.4 proxy to a 4.2.3 server

I spoke to soon. Which is good. At least I have some consistency.

The test box was able to ping the DEVMON machines, so no purple. I put
noconn in the bb-hosts file, and that brought the blanket purple across
the whole devmon machines. I also noticed that there was no ntp columns
anywhere. The test server doesn't run the ntp test, just the proxy.

So, here's what I know: The 4.3.4 proxy server does not forward  conn
and ntp tests to its servers.

And that almost makes sense. Those two tests would be run in the server
part of the server, not the client or the proxy, so it probably never
tells the proxy anything about them, and therefore it doesn't
propagate.

So, now the question is, why does the 4.2.3 server propagate those
tests through the proxy? And why are other tests like http not show
this problem?

Actually, may it does, but I have http in all bb-hosts/hosts.cfg files.
I'll test that next.

And lastly, how to I get the proxy to propagate those tests? Because,
the main server can't get through the firewall for much of that.

Paul.

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: Thursday, August 25, 2011 11:57 AM
To: 'Henrik Størner'; xymon at xymon.com
Subject: Re: [Xymon] 4.3.4 proxy to a 4.2.3 server

So I removed xymon completely from my test server, and reinstalled
4.2.3. It only gets it's info from the 4.3.4 proxy server not both.

Works fine.

Which just goes to confuse me more.

Paul Root    - Engineer III  - Qwest is now CenturyLink

-----Original Message-----
From: Root, Paul
Sent: Thursday, August 25, 2011 11:09 AM
To: Root, Paul; 'Henrik Størner'; xymon at xymon.com
Subject: RE: [Xymon] 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

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.

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.

4.3.4 proxy to a 4.2.3 server 🔗 link

4.3.4 proxy to a 4.2.3 server