Proxy Priority?
list Sean Clark
I have a setup like this:
+------------------------+ +----------------------+
| xymon:1985 | | |
|------------------------| | Downstream client |
| xymonproxy:1984 | <-----+| |
+------------------------+ +----------------------+
• |
|
|
+-----> proxy sends to localhost:1985, and upstream host1 1984, upstream host2 1984
[this is repeated across several sites]
The issue is, when downstream client looks to get it's config – in some sites, it gets the local-client from xymon:1985 host, but in others, it gets it from upstream hostX:1984
The xymondproxy in the tasks.cfg is identical in each place (--server localhost:1985, host1:1984, host2:1984) -- so I am confused as to why some get localhost, and some do not — the local-client is different in each place – and I'D prefer some setting I am missing (?) so that it always gets the local-client from the xymon:1985 instance.
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
list David Baldwin
Sean, You can sync client-local.cfg if you designate one of the servers as master. If all the servers are the same, it won't matter which one responds. xymon master "config client-local.cfg" Will retrieve the master client-local.cfg. David.
▸
I have a setup like this:
+------------------------+ +----------------------+
| xymon:1985 | | |
|------------------------| | Downstream client |
| xymonproxy:1984 | <-----+| |
+------------------------+ +----------------------+
• |
|
|
+-----> proxy sends to localhost:1985, and upstream host1 1984,
upstream host2 1984
[this is repeated across several sites]
The issue is, when downstream client looks to get it's config – in
some sites, it gets the local-client from xymon:1985 host, but in
others, it gets it from upstream hostX:1984
The xymondproxy in the tasks.cfg is identical in each place (--server
localhost:1985, host1:1984, host2:1984) -- so I am confused as to
why some get localhost, and some do not — the local-client is
different in each place – and I'D prefer some setting I am missing (?)
so that it always gets the local-client from the xymon:1985 instance.
This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject
to copyright belonging to Time Warner Cable. This E-mail is intended
solely for the use of the individual or entity to which it is
addressed. If you are not the intended recipient of this E-mail, you
are hereby notified that any dissemination, distribution, copying, or
action taken in relation to the contents of and attachments to this
E-mail is strictly prohibited and may be unlawful. If you have
received this E-mail in error, please notify the sender immediately
and permanently delete the original and any copy of this E-mail and
any printout.
--
David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 user-cbbf693f2c89@xymon.invalid Leverrier Street Bruce ACT 2617 Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
list Sean Clark
Yeah, I know if the files are all the same, I wouldn't have issues However, some of those displays, want no test of "files" The other displays, I do want tests of files… that's why they were different I didn't notice it was working like this right away – a majority go to 1985 local… but not all
▸
From: David Baldwin <user-cbbf693f2c89@xymon.invalid<mailto:user-cbbf693f2c89@xymon.invalid>> Date: Wednesday, February 6, 2013 5:57 PM To: Sean Clark <user-2db5fbcae9a7@xymon.invalid<mailto:user-2db5fbcae9a7@xymon.invalid>> Cc: "xymon at xymon.com<mailto:xymon at xymon.com>" <xymon at xymon.com<mailto:xymon at xymon.com>> Subject: Re: [Xymon] Proxy Priority? Sean, You can sync client-local.cfg if you designate one of the servers as master. If all the servers are the same, it won't matter which one responds. xymon master "config client-local.cfg" Will retrieve the master client-local.cfg. David. I have a setup like this: +------------------------+ +----------------------+ | xymon:1985 | | | |------------------------| | Downstream client | | xymonproxy:1984 | <-----+| | +------------------------+ +----------------------+ • | | | +-----> proxy sends to localhost:1985, and upstream host1 1984, upstream host2 1984 [this is repeated across several sites] The issue is, when downstream client looks to get it's config – in some sites, it gets the local-client from xymon:1985 host, but in others, it gets it from upstream hostX:1984 The xymondproxy in the tasks.cfg is identical in each place (--server localhost:1985, host1:1984, host2:1984) -- so I am confused as to why some get localhost, and some do not — the local-client is different in each place – and I'D prefer some setting I am missing (?) so that it always gets the local-client from the xymon:1985 instance. This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. -- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616
user-cbbf693f2c89@xymon.invalid<mailto:user-cbbf693f2c89@xymon.invalid> Leverrier Street Bruce ACT 2617 Keep up to date with what's happening in Australian sport visit www.ausport.gov.au<http://www.ausport.gov.au>;
▸
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
list David Baldwin
Sean, The client report is generated only once and sent to all reporting servers. If you want to do the files test on only 1 of those, so be it, but the data needs to be there in the first place. The servers not doing the files test will just ignore that section of the client data. The cached copy of client-local.cfg which is used to configure the log files to include is delivered from one of the servers reported to (it actually gets returned to the client after the TCP socket is shutdown when the client report has been sent to a server). If this process gives different results for different servers, then no guarantees on anything. Best to keep them all in sync, then you'll get the same thing each time. David.
▸
Yeah, I know if the files are all the same, I wouldn't have issues However, some of those displays, want no test of "files" The other displays, I do want tests of files… that's why they were different I didn't notice it was working like this right away – a majority go to 1985 local… but not all From: David Baldwin <user-cbbf693f2c89@xymon.invalid Date: Wednesday, February 6, 2013 5:57 PM To: Sean Clark <user-2db5fbcae9a7@xymon.invalid <mailto:user-2db5fbcae9a7@xymon.invalid>> Cc: "xymon at xymon.com <mailto:xymon at xymon.com>" <xymon at xymon.com
<mailto:xymon at xymon.com>>
▸
Subject: Re: [Xymon] Proxy Priority? Sean, You can sync client-local.cfg if you designate one of the servers as master. If all the servers are the same, it won't matter which one responds. xymon master "config client-local.cfg" Will retrieve the master client-local.cfg. David.I have a setup like this: +------------------------+ +----------------------+ | xymon:1985 | | | |------------------------| | Downstream client | | xymonproxy:1984 | <-----+| | +------------------------+ +----------------------+ • | | | +-----> proxy sends to localhost:1985, and upstream host1 1984, upstream host2 1984 [this is repeated across several sites] The issue is, when downstream client looks to get it's config – in some sites, it gets the local-client from xymon:1985 host, but in others, it gets it from upstream hostX:1984 The xymondproxy in the tasks.cfg is identical in each place (--server localhost:1985, host1:1984, host2:1984) -- so I am confused as to why some get localhost, and some do not — the local-client is different in each place – and I'D prefer some setting I am missing (?) so that it always gets the local-client from the xymon:1985 instance. This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 user-cbbf693f2c89@xymon.invalid Leverrier Street Bruce ACT 2617 Keep up to date with what's happening in Australian sport visit
www.ausport.gov.au <http://www.ausport.gov.au>;
▸
This message is intended for the addressee named and may contain
confidential and privileged information. If you are not the intended
recipient please note that any form of distribution, copying or use of
this communication or the information in it is strictly prohibited and
may be unlawful. If you receive this message in error, please delete
it and notify the sender.-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 user-cbbf693f2c89@xymon.invalid Leverrier Street Bruce ACT 2617