Ok - been trying my BEST to track down this issue, but simple of it is we are upgrading a proxy Going from Centos 5.11 (or 7) and from xymon 4.3.10 to Centos 6.7 and xymon 4.3.21 Should be (you would think) as simple as making sure config files are same, or basically copy the /etx/xymon over, bring down old, bring up new on old ip. What is just absolutely weird, that I have YET to track down as to why or what, suddenly now conn, ntp, http, bbd are no longer updated. Everything else seems to be working and updating from proxy to main. What I need help with is why did THOSE just stop? I've been going through the mailing list archives - I've setup a smaller "test system(s)" at the house (all on vm), can get everything working there, but NOT on this.Just any direction on what I could specifically debug to find this problem would be a help. Thanks Keith Dowell
A little more info. The proxy appears to be working. It does proxy some things, but it will not send xymonnet activity. As near as I can tell.
[xymonnet] ENVFILE /etc/xymon/xymonserver.cfg NEEDS xymond CMD XYMONDPORT=1984 xymonnet --report --ping --checkresponse LOGFILE $XYMONSERVERLOGS/xymon-network.log INTERVAL 5m
[xymonproxy] ENVFILE /etc/xymon/xymonserver.cfg CMD $XYMONHOME/bin/xymonproxy --server=10.1.9.17,127.0.0.1:1985 --listen=0.0.0.0:1984 --report=$MACHINE.xymonproxy --no-daemon --pidfile=$XYMONSERVERLOGS/xymonproxy.pid LOGFILE $XYMONSERVERLOGS/xymonproxy.log
In the xymonserver.cfg, XYMONDPORT is set to 1985. The proxy is on 1984 and the server is on 1985.
Turned on debugging on xymonnet and it says that it is sending to 1984 locally.
This works in 4.3.10 on CentOS 5. And has for a couple of years. And we see plenty of proxy traffic coming through.
From: Keith Dowell [mailto:snowolfex at yahoo.com] Sent: Saturday, January 02, 2016 3:41 PM To: Xymon Mailing List Subject: proxy issues
Ok - been trying my BEST to track down this issue, but simple of it is we are upgrading a proxy
Going from Centos 5.11 (or 7) and from xymon 4.3.10 to Centos 6.7 and xymon 4.3.21
Should be (you would think) as simple as making sure config files are same, or basically copy the /etx/xymon over, bring down old, bring up new on old ip. What is just absolutely weird, that I have YET to track down as to why or what, suddenly now conn, ntp, http, bbd are no longer updated. Everything else seems to be working and updating from proxy to main. What I need help with is why did THOSE just stop?
I've been going through the mailing list archives - I've setup a smaller "test system(s)" at the house (all on vm), can get everything working there, but NOT on this.Just any direction on what I could specifically debug to find this problem would be a help.
Thanks
Keith Dowell
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.
Hmm. The only thing that jumps out at me is that the version jump crosses the "extcombo" divide... A newer xymonnet sending to an older xymond might be sending messages the older one doesn't understand. xymonproxy (4.3.x at least) does not recombine into extcombo in any situation, so it wouldn't be causing it at that point.
Can you send xymonproxy a -USR1 signal to turn on verbosity? That should indicate what kind of / whether it's getting messages from xymonnet as expected.
Regards, -jc
On Sat, January 2, 2016 5:08 pm, Root, Paul T wrote:
A little more info. The proxy appears to be working. It does proxy some things, but it will not send xymonnet activity. As near as I can tell.
[xymonnet] ENVFILE /etc/xymon/xymonserver.cfg NEEDS xymond CMD XYMONDPORT=1984 xymonnet --report --ping --checkresponse LOGFILE $XYMONSERVERLOGS/xymon-network.log INTERVAL 5m
[xymonproxy] ENVFILE /etc/xymon/xymonserver.cfg CMD $XYMONHOME/bin/xymonproxy --server=10.1.9.17,127.0.0.1:1985 --listen=0.0.0.0:1984 --report=$MACHINE.xymonproxy --no-daemon --pidfile=$XYMONSERVERLOGS/xymonproxy.pid LOGFILE $XYMONSERVERLOGS/xymonproxy.log
In the xymonserver.cfg, XYMONDPORT is set to 1985. The proxy is on 1984 and the server is on 1985.
Turned on debugging on xymonnet and it says that it is sending to 1984 locally.
This works in 4.3.10 on CentOS 5. And has for a couple of years. And we see plenty of proxy traffic coming through.
From: Keith Dowell [mailto:snowolfex at yahoo.com] Sent: Saturday, January 02, 2016 3:41 PM To: Xymon Mailing List Subject: proxy issues
Ok - been trying my BEST to track down this issue, but simple of it is we are upgrading a proxy
Going from Centos 5.11 (or 7) and from xymon 4.3.10 to Centos 6.7 and xymon 4.3.21
Should be (you would think) as simple as making sure config files are same, or basically copy the /etx/xymon over, bring down old, bring up new on old ip. What is just absolutely weird, that I have YET to track down as to why or what, suddenly now conn, ntp, http, bbd are no longer updated. Everything else seems to be working and updating from proxy to main. What I need help with is why did THOSE just stop?
I've been going through the mailing list archives - I've setup a smaller "test system(s)" at the house (all on vm), can get everything working there, but NOT on this.Just any direction on what I could specifically debug to find this problem would be a help.
Thanks
Keith Dowell
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.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
On 03/01/16 12:50, J.C. Cleaver wrote:
Hmm. The only thing that jumps out at me is that the version jump crosses the "extcombo" divide... A newer xymonnet sending to an older xymond might be sending messages the older one doesn't understand. xymonproxy (4.3.x at least) does not recombine into extcombo in any situation, so it wouldn't be causing it at that point.
Can you send xymonproxy a -USR1 signal to turn on verbosity? That should indicate what kind of / whether it's getting messages from xymonnet as expected.
Hi,
This sounds like it could be one (of the many) issues I'm having (but haven't had time to look into for a while). Is there a simple method to tell xymonnet to avoid sending "extcombo" messages?
Thanks, Adam
-- Adam Goryachev Website Managers www.websitemanagers.com.au
On Sun, January 3, 2016 8:29 pm, Adam Goryachev wrote:
On 03/01/16 12:50, J.C. Cleaver wrote:
Hmm. The only thing that jumps out at me is that the version jump crosses the "extcombo" divide... A newer xymonnet sending to an older xymond might be sending messages the older one doesn't understand. xymonproxy (4.3.x at least) does not recombine into extcombo in any situation, so it wouldn't be causing it at that point.
Can you send xymonproxy a -USR1 signal to turn on verbosity? That should indicate what kind of / whether it's getting messages from xymonnet as expected.
Hi,
This sounds like it could be one (of the many) issues I'm having (but haven't had time to look into for a while). Is there a simple method to tell xymonnet to avoid sending "extcombo" messages?
Thanks, Adam
Unfortunately, no. And with combo generation being pretty low level within the code, so even setting MAXMSGSPERCOMBO to '1' will just result in an extcombo-wrapped single message.
It probably should have been called out better within the 4.3.13(?) Release Notes, but in a distributed infrastructure the central xymond needs to be updated first.
Regards, -jc
Ah, that might make sense.
The main server is still CentOS 5/Xymon 4.3.10.
We can do some testing to a development server by turning off it's xymonnet task.
I'll let Keith handle the request.
-----Original Message----- From: J.C. Cleaver [mailto:cleaver at terabithia.org] Sent: Saturday, January 02, 2016 7:50 PM To: Root, Paul T Cc: 'Keith Dowell'; Xymon Mailing List Subject: Re: [Xymon] proxy issues
Hmm. The only thing that jumps out at me is that the version jump crosses the "extcombo" divide... A newer xymonnet sending to an older xymond might be sending messages the older one doesn't understand. xymonproxy (4.3.x at least) does not recombine into extcombo in any situation, so it wouldn't be causing it at that point.
Can you send xymonproxy a -USR1 signal to turn on verbosity? That should indicate what kind of / whether it's getting messages from xymonnet as expected.
Regards, -jc
On Sat, January 2, 2016 5:08 pm, Root, Paul T wrote:
A little more info. The proxy appears to be working. It does proxy some things, but it will not send xymonnet activity. As near as I can tell.
[xymonnet] ENVFILE /etc/xymon/xymonserver.cfg NEEDS xymond CMD XYMONDPORT=1984 xymonnet --report --ping --checkresponse LOGFILE $XYMONSERVERLOGS/xymon-network.log INTERVAL 5m
[xymonproxy] ENVFILE /etc/xymon/xymonserver.cfg CMD $XYMONHOME/bin/xymonproxy --server=10.1.9.17,127.0.0.1:1985 --listen=0.0.0.0:1984 --report=$MACHINE.xymonproxy --no-daemon --pidfile=$XYMONSERVERLOGS/xymonproxy.pid LOGFILE $XYMONSERVERLOGS/xymonproxy.log
In the xymonserver.cfg, XYMONDPORT is set to 1985. The proxy is on 1984 and the server is on 1985.
Turned on debugging on xymonnet and it says that it is sending to 1984 locally.
This works in 4.3.10 on CentOS 5. And has for a couple of years. And we see plenty of proxy traffic coming through.
From: Keith Dowell [mailto:snowolfex at yahoo.com] Sent: Saturday, January 02, 2016 3:41 PM To: Xymon Mailing List Subject: proxy issues
Ok - been trying my BEST to track down this issue, but simple of it is we are upgrading a proxy
Going from Centos 5.11 (or 7) and from xymon 4.3.10 to Centos 6.7 and xymon 4.3.21
Should be (you would think) as simple as making sure config files are same, or basically copy the /etx/xymon over, bring down old, bring up new on old ip. What is just absolutely weird, that I have YET to track down as to why or what, suddenly now conn, ntp, http, bbd are no longer updated. Everything else seems to be working and updating from proxy to main. What I need help with is why did THOSE just stop?
I've been going through the mailing list archives - I've setup a smaller "test system(s)" at the house (all on vm), can get everything working there, but NOT on this.Just any direction on what I could specifically debug to find this problem would be a help.
Thanks
Keith Dowell
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.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
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.
participants (4)
-
cleaver＠terabithia.org
-
mailinglists＠websitemanagers.com.au
-
Paul.Root＠CenturyLink.com
-
snowolfex＠yahoo.com