[Xymon] 4.3.4 proxy to a 4.2.3 server

Root, Paul Paul.Root at CenturyLink.com
Wed Aug 24 21:32:08 CEST 2011


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.



More information about the Xymon mailing list