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-----