[Xymon] A couple of migration questions

Root, Paul Paul.Root at CenturyLink.com
Mon Dec 10 23:15:19 CET 2012


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 <novosirj at umdnj.edu<mailto:novosirj at umdnj.edu>> 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 <novosirj at umdnj.edu<mailto:novosirj at umdnj.edu>
> <mailto:novosirj at umdnj.edu<mailto:novosirj at umdnj.edu>>> 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
|$&| |__| |  | |__/ | \| _| |novosirj at umdnj.edu<mailto:novosirj at umdnj.edu> - 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-----

_______________________________________________
Xymon mailing list
Xymon at xymon.com<mailto:Xymon at xymon.com>
http://lists.xymon.com/mailman/listinfo/xymon

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20121210/1b8c0e05/attachment.html>


More information about the Xymon mailing list