A couple of migration questions
list Ryan Novosielski
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Going to upgrade from 4.2.3 to 4.3.10 next week and I want to answer just a quick couple of questions (I'll outline my setups briefly so you can warn me if you see a caveat). I have one server running two Solaris zones, one with a somewhat internal view of our network, one with a somewhat external view -- both have a xymonnet and xymonnetagain running. I also have another server running xymongen, clientdata, alert, etc. that hosts what I'd have formerly called the BBDISPLAY. What is going to be happening is I'm moving the latter pieces on the "display" server to a different server and upgrading to 4.3.10. At the same time, I'm going to upgrade the xymonnet machines to 4.3.10 and point them at the new server. I've really already done all of this, but on an alternate port for the two xymonnet machines. I plan to change back to the standard port when I go live with it, and to copy any data to the new live machine that has changed in the interim. My questions are: 1) Do the xymonnet machines listen on the Xymon port? They seem to, but I can't see any reason why they should. If they didn't, I'd configure the xymonnet machines to use the standard port 1984 to give me less to do when going live. 2) When I am ready to switch over to the new "display" server which is the one that has all of the history data and RRD files and all of that, do I just need to sync the hostdata directory to be sure that the historical information is not lost, or are there other things as well (as well as are there things in hostdata I should NOT copy over)? The RRD files from the old host work on the new host, and I currently have a running copy of 4.3.10 that was created from upgrading a copy of the 4.2.3 software on the original machine. 3) I see that xymonproxy cannot share a machine with xymond as they both use the same port. I assume depending on the answer to question 1, it can share a machine with xymonnet, right? 4) A couple of events (including the recent hurricane we had over here) have raised the need for a second Xymon server in cases where a campus will be unavailable for some time. Is using xymonproxy to distribute this information the way to go in a master/slave situation? Defining multiple XYMSRV's? Something else? Thanks for any insights anyone is willing to give. - -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDA+LcACgkQmb+gadEcsb4A+QCeLAANykvfRHvM3SaQUtSGveKR 6iAAn22wknww/9f00y2D51vjhBmXfPbR =Xiu3 -----END PGP SIGNATURE-----
list Jeremy Laidman
▸
On 7 December 2012 06:57, Novosielski, Ryan <user-ae4522577e16@xymon.invalid> wrote:
1) Do the xymonnet machines listen on the Xymon port? They seem to, but I can't see any reason why they should. If they didn't, I'd configure the xymonnet machines to use the standard port 1984 to give me less to do when going live.
I agree, the xymonnet process should not be listening on any port. Only the xymond process listens on port 1984.
▸
3) I see that xymonproxy cannot share a machine with xymond as theyboth use the same port. I assume depending on the answer to question 1, it can share a machine with xymonnet, right?
I would think so.
▸
4) A couple of events (including the recent hurricane we had over here) have raised the need for a second Xymon server in cases where a campus will be unavailable for some time. Is using xymonproxy to distribute this information the way to go in a master/slave situation?
It might work just fine for some things. But things like enable/disable on the web GUI will need to be performed on both servers, to keep them in sync.
Defining multiple XYMSRV's? Something else?
I have two independent Xymon servers in different locations, each configured identically (using subversion over ssh for replicating the configuration). The clients are configured with $XYMSRV=0.0.0.0 and $XYMSERVERS set to contain both server IP addresses. There are two gotchyas with this system, both of which are easily solved. One is that the "display" servers must not list each other in $XYMSERVERS, and should only list their own IP address (so as to avoid Xymon message loops, if I remember correctly). The other problem is that as a consequence of each display server only listing itself, a enable/disable message doesn't get sent to both servers, and have to be performed on both. My fix for this is: 1) create a modifed "xymonserver.cfg" file that includes the original "xymonserver.cfg" and then re-defines XYMSERVERS to list both servers 2) define XYMONENV_ENADIS=/path/to/xymonserver-enadis.cfg so that the modified config file can be specified 3) define CGI_ENADIS_OPTS="--env=$XYMONENV_ENADIS" so that the CGI script uses the modified file with both servers listed. J
list Ryan Novosielski
▸
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/09/2012 06:53 PM, Jeremy Laidman wrote:
On 7 December 2012 06:57, Novosielski, Ryan <user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid>> wrote: 1) Do the xymonnet machines listen on the Xymon port? They seem to, but I can't see any reason why they should. If they didn't, I'd configure the xymonnet machines to use the standard port 1984 to give me less to do when going live. I agree, the xymonnet process should not be listening on any port. Only the xymond process listens on port 1984.
Well, tracked this one down! Most things have "NEEDS xymond" and at one point I thought that mattered and didn't disable xymond. It's been running for no reason on my setup apparently since the beginning.
▸
- -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlDGLVkACgkQmb+gadEcsb4BIQCfYZ4lWq1yG4etMFXBxfDK5691
NgAAoJMEadfhhPkIqy09xsdbmKHRp4JG
=9IdP
-----END PGP SIGNATURE-----
list Larry Barber
There's no problem with having xymonproxy and xymond running on the same machine, you just need to change the port that one of them listens on. It's usually easier to change xymond's port. I have run several servers with xymonproxy running "on top" of xymond, where the xymonproxy instance would forward to both another port on the machine it was running on (usually 1985) and to another machine that was running a backup instance of xymon or a test instance. Thanks, Larry Barber
▸
On Mon, Dec 10, 2012 at 12:43 PM, Novosielski, Ryan <user-ae4522577e16@xymon.invalid>wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/09/2012 06:53 PM, Jeremy Laidman wrote:On 7 December 2012 06:57, Novosielski, Ryan <user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid>> wrote: 1) Do the xymonnet machines listen on the Xymon port? They seem to, but I can't see any reason why they should. If they didn't, I'd configure the xymonnet machines to use the standard port 1984 to give me less to do when going live. I agree, the xymonnet process should not be listening on any port. Only the xymond process listens on port 1984.Well, tracked this one down! Most things have "NEEDS xymond" and at one point I thought that mattered and didn't disable xymond. It's been running for no reason on my setup apparently since the beginning. - -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDGLVkACgkQmb+gadEcsb4BIQCfYZ4lWq1yG4etMFXBxfDK5691 NgAAoJMEadfhhPkIqy09xsdbmKHRp4JG =9IdP -----END PGP SIGNATURE-----
list Ryan Novosielski
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So I guess the result is that I could change the 1984 port to be a proxy instead, changing xymond to say 1985, and the only thing that I'd have to change to 1985 would be where the proxy forwards the messages instead of all of the clients, right?
▸
On 12/10/2012 03:10 PM, Larry Barber wrote:There's no problem with having xymonproxy and xymond running on the same machine, you just need to change the port that one of them listens on. It's usually easier to change xymond's port. I have run several servers with xymonproxy running "on top" of xymond, where the xymonproxy instance would forward to both another port on the machine it was running on (usually 1985) and to another machine that was running a backup instance of xymon or a test instance. Thanks, Larry Barber On Mon, Dec 10, 2012 at 12:43 PM, Novosielski, Ryan <user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid>> wrote: On 12/09/2012 06:53 PM, Jeremy Laidman wrote:On 7 December 2012 06:57, Novosielski, Ryan <user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid>>> wrote:1) Do the xymonnet machines listen on the Xymon port? They seem to, but I can't see any reason why they should. If they didn't, I'd configure the xymonnet machines to use the standard port 1984 to give me less to do when going live.I agree, the xymonnet process should not be listening on any port. Only the xymond process listens on port 1984.Well, tracked this one down! Most things have "NEEDS xymond" and at one point I thought that mattered and didn't disable xymond. It's been running for no reason on my setup apparently since the beginning.
- -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEUEARECAAYFAlDGQ3IACgkQmb+gadEcsb4h+QCXXTQEsWvpC+62MqwQ+m0oz90t
twCaA5nvatAYzuLpYy2YYNXmKfAnl24=
=Zr5V
-----END PGP SIGNATURE-----
list Larry Barber
Pretty much. Keep in mind that admin messages will only be sent to the _last_ entry in the --servers argument. Doing it this way ensures that inter-machine communication can be kept on port 1984, which simplifies things a little.
▸
Thanks,
Larry Barber
On Mon, Dec 10, 2012 at 2:17 PM, Novosielski, Ryan <user-ae4522577e16@xymon.invalid>wrote:
I'd have to change to 1985 would be where the proxy forwards the
list Paul Root
I do that to. Works pretty slick. One thing we just ran into though was with bluesync. We'd get a feedback loop and the disabled tests wouldn't stay disabled. We decided to upgrade to 4.3.10 and use the built in xymond_distribute. Unfortunately, that didn't help. The same problem persisted. Then I figured out that we should send to xymond not the proxy. That solved the problem.
▸
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Larry Barber
Sent: Monday, December 10, 2012 2:10 PM
To: Novosielski, Ryan
Cc: xymon >> xymon at xymon.com
Subject: Re: [Xymon] A couple of migration questions
There's no problem with having xymonproxy and xymond running on the same machine, you just need to change the port that one of them listens on. It's usually easier to change xymond's port. I have run several servers with xymonproxy running "on top" of xymond, where the xymonproxy instance would forward to both another port on the machine it was running on (usually 1985) and to another machine that was running a backup instance of xymon or a test instance.
Thanks,
Larry Barber
On Mon, Dec 10, 2012 at 12:43 PM, Novosielski, Ryan <user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/09/2012 06:53 PM, Jeremy Laidman wrote:On 7 December 2012 06:57, Novosielski, Ryan <user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>
▸
<mailto:user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid>>> wrote:
1) Do the xymonnet machines listen on the Xymon port? They seem
to, but I can't see any reason why they should. If they didn't,
I'd configure the xymonnet machines to use the standard port 1984
to give me less to do when going live.
I agree, the xymonnet process should not be listening on any port.
Only the xymond process listens on port 1984.Well, tracked this one down! Most things have "NEEDS xymond" and at one point I thought that mattered and didn't disable xymond. It's been running for no reason on my setup apparently since the beginning. - -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid> - 973/972.0922<tel:973%2F972.0922> (2-0922)
▸
\__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDGLVkACgkQmb+gadEcsb4BIQCfYZ4lWq1yG4etMFXBxfDK5691 NgAAoJMEadfhhPkIqy09xsdbmKHRp4JG =9IdP -----END PGP SIGNATURE-----
list Paul Root
Set XYMONPORT to 1984 in tasks.cfg on the xymonnet and xymonnetagain command lines CMD XYMONDPORT=1984 xymonnet --report --ping --checkresponse
▸
-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Novosielski, Ryan
Sent: Monday, December 10, 2012 2:18 PM
To: Larry Barber
Cc: xymon >> xymon at xymon.com
Subject: Re: [Xymon] A couple of migration questions
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So I guess the result is that I could change the 1984 port to be a proxy instead, changing xymond to say 1985, and the only thing that I'd have to change to 1985 would be where the proxy forwards the messages instead of all of the clients, right?
On 12/10/2012 03:10 PM, Larry Barber wrote:There's no problem with having xymonproxy and xymond running on the same machine, you just need to change the port that one of them listens on. It's usually easier to change xymond's port. I have run several servers with xymonproxy running "on top" of xymond, where the xymonproxy instance would forward to both another port on the machine it was running on (usually 1985) and to another machine that was running a backup instance of xymon or a test instance. Thanks, Larry Barber On Mon, Dec 10, 2012 at 12:43 PM, Novosielski, Ryan <user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid>> wrote: On 12/09/2012 06:53 PM, Jeremy Laidman wrote:On 7 December 2012 06:57, Novosielski, Ryan <user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid>>> wrote:1) Do the xymonnet machines listen on the Xymon port? They seem to, but I can't see any reason why they should. If they didn't, I'd configure the xymonnet machines to use the standard port 1984 to give me less to do when going live.I agree, the xymonnet process should not be listening on any port. Only the xymond process listens on port 1984.Well, tracked this one down! Most things have "NEEDS xymond" and at one point I thought that mattered and didn't disable xymond. It's been running for no reason on my setup apparently since the beginning.
- -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEUEARECAAYFAlDGQ3IACgkQmb+gadEcsb4h+QCXXTQEsWvpC+62MqwQ+m0oz90t twCaA5nvatAYzuLpYy2YYNXmKfAnl24= =Zr5V -----END PGP SIGNATURE-----
list Ryan Novosielski
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks. This is all helpful. I did the upgrade today and things are pretty much back to working the way I want them to. Going forward I should be able to take advantage of some of the new stuff and make some of it more robust than my old setup.
▸
On 12/10/2012 05:29 PM, Root, Paul wrote:I do that to. Works pretty slick. One thing we just ran into though was with bluesync. We’d get a feedback loop and the disabled tests wouldn’t stay disabled. We decided to upgrade to 4.3.10 and use the built in xymond_distribute. Unfortunately, that didn’t help. The same problem persisted. Then I figured out that we should send to xymond not the proxy. That solved the problem.
*From:*xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com]
▸
*On Behalf Of *Larry Barber *Sent:* Monday, December 10, 2012 2:10 PM *To:* Novosielski, Ryan *Cc:* xymon >> xymon at xymon.com *Subject:* Re: [Xymon] A couple of migration questions There's no problem with having xymonproxy and xymond running on the same machine, you just need to change the port that one of them listens on. It's usually easier to change xymond's port. I have run several servers with xymonproxy running "on top" of xymond, where the xymonproxy instance would forward to both another port on the machine it was running on (usually 1985) and to another machine that was running a backup instance of xymon or a test instance. Thanks, Larry Barber On Mon, Dec 10, 2012 at 12:43 PM, Novosielski, Ryan <user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid>> wrote: On 12/09/2012 06:53 PM, Jeremy Laidman wrote:On 7 December 2012 06:57, Novosielski, Ryan <user-ae4522577e16@xymon.invalid<mailto:user-ae4522577e16@xymon.invalid <mailto:user-ae4522577e16@xymon.invalid>>> wrote:1) Do the xymonnet machines listen on the Xymon port? They seem to, but I can't see any reason why they should. If they didn't, I'd configure the xymonnet machines to use the standard port 1984 to give me less to do when going live.I agree, the xymonnet process should not be listening on any port. Only the xymond process listens on port 1984.Well, tracked this one down! Most things have "NEEDS xymond" and at one point I thought that mattered and didn't disable xymond. It's been running for no reason on my setup apparently since the beginning.
- -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlDGYyIACgkQmb+gadEcsb5LOgCfTT/4Qd1c8zUEnK2idbCLyxiC
BSwAoIz5uczxJ02w0eTqwx941xcs/mNR
=ePZX
-----END PGP SIGNATURE-----