[Xymon] A couple of migration questions

[Root, Paul]

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 
> <novosirj at umdnj.edu <mailto:novosirj at umdnj.edu>> wrote:
> 
> 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.
> 
> 
> _______________________________________________ Xymon mailing list 
> Xymon at xymon.com <mailto:Xymon at xymon.com> 
> http://lists.xymon.com/mailman/listinfo/xymon
> 
> 

- --
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Sr. Systems Programmer 
|$&| |__| |  | |__/ | \| _| |novosirj at umdnj.edu - 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-----

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