Xymon Mailing List Archive search

Xymon status does not get updated

17 messages in this thread

list Yanni · Thu, 11 Oct 2012 10:08:51 +0100 ·
Hi everyone

2 days ago I updated xymon to the latest version:4.3.10 and for some reason unknown to me xymond stopped updating the hosts.cfg file.

Please see xymongen.log below:

2012-10-10 16:53:58 ->  Recipient '193.61.54.144', timeout 15
2012-10-10 16:53:58 ->  1st line: 'xymondboard fields=hostname,testname,color,flags,lastchange,logtime,validtime,acktime,disabletime,sender,cookie,line1,acklist'
2012-10-10 16:53:58 xymond status-board not available, code 7
2012-10-10 16:53:58 Failed to load current Xymon status, aborting page-update

Could somebody please help me?

Many thanks
Yanni
list Jeremy Laidman · Fri, 12 Oct 2012 16:48:19 +1100 ·
quoted from Yanni
On 11 October 2012 20:08, Yanni <user-04b379562e0f@xymon.invalid> wrote:
2 days ago I updated xymon to the latest version:4.3.10 and for some
reason unknown to me xymond stopped updating the hosts.cfg file.

Please see xymongen.log below:

2012-10-10 16:53:58 ->  Recipient '193.61.54.144', timeout 15
What is this server?  If this is your Xymon server, then what we have here
is a failure to communicate.  Given that there was a timeout (rather than a
rejected connection) I suspect a firewall or packet filter is dropping the
packets, or perhaps a routing problem.  Try to telnet to this IP address
from your Xymon server, and if that doesn't work, you know it's unlikely to
be a Xymon problem.

Aside from that, I'm confused.  Why would Xymon modify the hosts.cfg file?
Isn't that supposed to be edited by a human?

J
list Yanni · Fri, 12 Oct 2012 11:17:56 +0100 ·
Hi

Sorry for the confusion. I was trying to say that xymond does not load the hosts.cfg file instead of it doesn't update hosts.cfg.

Yes this IP is my xymon server. I can telnet and ssh to the server from terminal with no problems.
For some strange reason the xymon main page does not get updated anymore. I have manually added a few more hosts in 'hosts.cfg' but they don't show up.

Also I have checked that
1) xymon.sh is running
2) SELINUX was disabled but iptables was not, so I have now turned iptables off as well but the problem persists. :(

I really don't know what is happening. If you have anymore suggestions please  let me know.

Many thanks
Yanni
quoted from Jeremy Laidman


On 10/12/2012 06:48 AM, Jeremy Laidman wrote:
On 11 October 2012 20:08, Yanni <user-04b379562e0f@xymon.invalid <mailto:user-04b379562e0f@xymon.invalid>> wrote:

    2 days ago I updated xymon to the latest version:4.3.10 and for
    some reason unknown to me xymond stopped updating the hosts.cfg file.

    Please see xymongen.log below:

    2012-10-10 16:53:58 ->  Recipient '193.61.54.144', timeout 15


What is this server?  If this is your Xymon server, then what we have here is a failure to communicate.  Given that there was a timeout (rather than a rejected connection) I suspect a firewall or packet filter is dropping the packets, or perhaps a routing problem.  Try to telnet to this IP address from your Xymon server, and if that doesn't work, you know it's unlikely to be a Xymon problem.

Aside from that, I'm confused.  Why would Xymon modify the hosts.cfg file? Isn't that supposed to be edited by a human?

J
list Jeremy Laidman · Mon, 15 Oct 2012 11:04:08 +1100 ·
quoted from Yanni
On 12 October 2012 21:17, Yanni <user-04b379562e0f@xymon.invalid> wrote:
 Yes this IP is my xymon server. I can telnet and ssh to the server from
terminal with no problems.
Sorry, I meant to ask if you can  telnet to it on port 1984, rather than
the default telnet port.  So:

telnet 193.61.54.144 1984
quoted from Yanni

For some strange reason the xymon main page does not get updated anymore. I
have manually added a few more hosts in 'hosts.cfg' but they don't show up.
The Xymon page generator probably needs to query the xymond process using
port 1984 (using the xymon command).

Also I have checked that
1) xymon.sh is running
Is xymond running?

Let's try to reproduce the conditions that would have led to the error
message.  Try running this to see what it gives you:

xymoncmd xymon 193.61.54.144 'xymondboard fields=hostname,testname,**color
,flags,lastchange,**logtime,validtime,acktime,**disabletime,sender,cookie,**
line1,acklist'

Cheers
Jeremy
list Yanni · Mon, 15 Oct 2012 10:25:31 +0100 ·
It seems that telnet works because it returns "connected to 
193.61.54.144", however it looks like it hangs after the:
(Escape character is '^]') line. I can type things but nothing is 
returned when I hit "Enter", only the cursor just goes to the next line.
I only use ssh so I can't tell if my telnet works properly.

This is what I get:

telnet 193.61.54.144 1984
Trying 193.61.54.144...
Connected to 193.61.54.144.
Escape character is '^]'.

Yes xymond is running. It's first on my "top" list:

(23182 xymon 25   0  7992 1984 1380 R   100.0    0.1   8286:29 xymond)


The command you asked me to run returns the following:

2012-10-15 10:00:10 Using default environment file 
/home/xymon/server/etc/xymonserver.cfg
2012-10-15 10:00:25 Whoops ! Failed to send message (timeout)
2012-10-15 10:00:25 ->
2012-10-15 10:00:25 ->  Recipient '193.61.54.144', timeout 15
2012-10-15 10:00:25 ->  1st line: 'xymondboard 
fields=hostname,testname,color,flags,lastchange,logtime,validtime,acktime,disabletime,sender,cookie,line1,acklist'


A few more log files.

xymonlaunch.log:
2012-10-15 09:56:06 Loading hostnames
2012-10-15 09:56:06 Loading saved state
2012-10-15 09:56:06 Setting up network listener on 0.0.0.0:1984
2012-10-15 09:56:06 Cannot bind to listen socket (Address already in use)
2012-10-15 09:56:06 Task xymond terminated, status 1

hostdata.log:
2012-09-18 15:02:19 Tried to down BOARDBUSY: Invalid argument
2012-09-18 15:02:19 Peer not up, flushing message queue
2012-09-18 15:07:29 Peer not up, flushing message queue

clientdata.log:
2012-09-18 15:02:19 Tried to down BOARDBUSY: Invalid argument
2012-09-18 15:02:40 Peer not up, flushing message queue
2012-10-09 15:46:38 Whoops ! Failed to send message (timeout)
2012-10-09 15:46:38 ->
2012-10-09 15:46:38 ->  Recipient '193.61.54.144', timeout 15
2012-10-09 15:46:38 ->  1st line: 'config hosts.cfg'
2012-10-09 15:46:38 Cannot load hosts.cfg from xymond, code 7
2012-10-09 15:46:38 Failed to load from xymond, reverting to file-load


Thanks Jeremy
quoted from Jeremy Laidman


On 10/15/2012 01:04 AM, Jeremy Laidman wrote:
On 12 October 2012 21:17, Yanni <user-04b379562e0f@xymon.invalid 
<mailto:user-04b379562e0f@xymon.invalid>> wrote:

    Yes this IP is my xymon server. I can telnet and ssh to the server
    from terminal with no problems.


Sorry, I meant to ask if you can  telnet to it on port 1984, rather 
than the default telnet port.  So:

telnet 193.61.54.144 1984

    For some strange reason the xymon main page does not get updated
    anymore. I have manually added a few more hosts in 'hosts.cfg' but
    they don't show up.


The Xymon page generator probably needs to query the xymond process 
using port 1984 (using the xymon command).

    Also I have checked that
    1) xymon.sh is running


Is xymond running?

Let's try to reproduce the conditions that would have led to the error 
message.  Try running this to see what it gives you:

xymoncmd xymon 193.61.54.144 'xymondboard 

fields=hostname,testname,color,flags,lastchange,logtime,validtime,acktime,disabletime,sender,cookie,line1,acklist'

Cheers
Jeremy
list John Horne · Mon, 15 Oct 2012 11:23:14 +0100 ·
quoted from Yanni
On Mon, 2012-10-15 at 10:25 +0100, Yanni wrote:
2012-10-15 10:00:10 Using default environment
file /home/xymon/server/etc/xymonserver.cfg
2012-10-15 10:00:25 Whoops ! Failed to send message (timeout)
2012-10-15 10:00:25 ->  
2012-10-15 10:00:25 ->  Recipient '193.61.54.144', timeout 15
Do you have anything like '--status-senders' set for xymond in your
tasks.cfg file? If so, is this IP address listed?
quoted from Yanni
xymonlaunch.log:
2012-10-15 09:56:06 Loading hostnames
2012-10-15 09:56:06 Loading saved state
2012-10-15 09:56:06 Setting up network listener on 0.0.0.0:1984
Are you using multiple Xymon servers or should this ('0.0.0.0') be
whatever XYMONSERVERIP is set to in xymonserver.cfg?
quoted from Yanni

2012-10-09 15:46:38 Whoops ! Failed to send message (timeout)
2012-10-09 15:46:38 ->  
2012-10-09 15:46:38 ->  Recipient '193.61.54.144', timeout 15
2012-10-09 15:46:38 ->  1st line: 'config hosts.cfg'
2012-10-09 15:46:38 Cannot load hosts.cfg from xymond, code 7
2012-10-09 15:46:38 Failed to load from xymond, reverting to file-load
When I had accidentally restricted access to our Xymon server, I
received errors such as 'connection refused'. In your case you get a
timeout, which tends to imply it is not connecting. If iptables and
selinux have been stopped, then I would check the settings in the
'server/etc' files to ensure that your Xymon server is configured
correctly.


John.

-- 
John Horne, Plymouth University, UK
Tel: +XX (X)XXXX XXXXXX    Fax: +XX (X)XXXX XXXXXX
list Jeremy Laidman · Tue, 16 Oct 2012 11:39:19 +1100 ·
quoted from Yanni
On 15 October 2012 20:25, Yanni <user-04b379562e0f@xymon.invalid> wrote:
 It seems that telnet works because it returns "connected to
193.61.54.144", however it looks like it hangs after the:
(Escape character is '^]') line.
That's to be expected.  When doing a telnet test like this, you can get one
of three things:
* connection refused (nothing listening on that port)
* time-out (firewall dropping packets)
* connected (works)

You got the last one, so all good.

If you have netcat, try doing this:

$ echo xymondboard | netcat 193.61.54.144 1984

This should get you a list of hosts and their status.  The command might be
"nc" rather than "netcat".

xymonlaunch.log:
quoted from Yanni
2012-10-15 09:56:06 Setting up network listener on 0.0.0.0:1984
2012-10-15 09:56:06 Cannot bind to listen socket (Address already in use)
Perhaps you have xymond running twice?  Stop xymond, and kill all remaining
xymond  processes before attempting to start it again.  Before starting,
you should see no output from this:

$ netstat -na|grep 1984.*LISTEN

Cheers
Jeremy
list Yanni · Tue, 16 Oct 2012 15:04:33 +0100 ·
OK, I downloaded and installed netcat and run the command: $ echo xymondboard | netcat 193.61.54.144 1984
waited for a couple of seconds but nothing was returned. I tried both 'netcat' and 'nc'.

I then killed all xymond jobs: $ killall -9 xymond

then run your netstat command: $ netstat -na|grep 1984.*LISTEN
and it returned:
$ tcp        0      0 0.0.0.0:1984 0.0.0.0:*                   LISTEN

xymond is not anymore in my 'top' list.

$ps auf | grep xymond
returns:
$ xymon     1465  0.0  0.0   4012   664 pts/1    S+   14:35 0:00          \_ grep xymond

also xymon.sh is running

I am getting confused and the reason is that although I think I killed xymond now xymon seems to be working and the hosts.cfg file gets loaded. I removed and added a few hosts and the main xymon page gets updated now.
However my xymond is not happy because it's posting a yellow dizzy face.

Please see a few lines from xymonlaunch.log:

2012-10-16 11:07:41 FATAL: xymond sees clientcount 1, should be 0. Check for hanging xymond_channel processes or stale semaphores
2012-10-16 11:07:41 Cannot setup page channel
2012-10-16 11:07:41 Task xymond terminated, by signal 9
2012-10-16 11:07:46 Loading hostnames
2012-10-16 11:07:47 Loading saved state
2012-10-16 11:07:47 Setting up network listener on 0.0.0.0:1984
2012-10-16 11:07:47 Setting up signal handlers
2012-10-16 11:07:47 Setting up xymond channels
2012-10-16 11:07:47 Setting up logfiles

So why everything works after I killed all xymond???

I am super-confused.
quoted from Jeremy Laidman

On 10/16/2012 01:39 AM, Jeremy Laidman wrote:
On 15 October 2012 20:25, Yanni <user-04b379562e0f@xymon.invalid <mailto:user-04b379562e0f@xymon.invalid>> wrote:

    It seems that telnet works because it returns "connected to
    193.61.54.144", however it looks like it hangs after the:
    (Escape character is '^]') line.


That's to be expected.  When doing a telnet test like this, you can get one of three things:
* connection refused (nothing listening on that port)
* time-out (firewall dropping packets)
* connected (works)

You got the last one, so all good.

If you have netcat, try doing this:

$ echo xymondboard | netcat 193.61.54.144 1984

This should get you a list of hosts and their status.  The command might be "nc" rather than "netcat".

    xymonlaunch.log:

    2012-10-15 09:56:06 Setting up network listener on *MailScanner
    warning: numerical links are often malicious:* 0.0.0.0:1984
    <http://0.0.0.0:1984>;
quoted from Jeremy Laidman
    2012-10-15 09:56:06 Cannot bind to listen socket (Address already
    in use)


Perhaps you have xymond running twice?  Stop xymond, and kill all remaining xymond  processes before attempting to start it again.  Before starting, you should see no output from this:

$ netstat -na|grep 1984.*LISTEN

Cheers
Jeremy
list Yanni · Tue, 16 Oct 2012 15:42:27 +0100 ·
Hi John
quoted from John Horne

| Do you have anything like '--status-senders' set for xymond in your
| tasks.cfg file? If so, is this IP address listed?

No, I do not have anything like that in tasks.cfg. I haven't touched this file.
quoted from John Horne

| Are you using multiple Xymon servers or should this ('0.0.0.0') be
| whatever XYMONSERVERIP is set to in xymonserver.cfg?

There is no secondary xymon server but there is a big brother running.
My task at the moment is to gradually retire big brother and move everything to Xymon but I still have a LONG way to go.
quoted from John Horne


| When I had accidentally restricted access to our Xymon server, I
| received errors such as 'connection refused'. In your case you get a
| timeout, which tends to imply it is not connecting. If iptables and
| selinux have been stopped, then I would check the settings in the
| 'server/etc' files to ensure that your Xymon server is configured
| correctly.


I haven't done anything like that in my case.

After running:
$killall -9 xymond

The main xymon page gets updated but the xymond column is yellow.
(???????) I am full of questionmarks.
list Ryan Novosielski · Tue, 16 Oct 2012 11:03:47 -0400 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
quoted from Yanni

On 10/16/2012 10:44 AM, Yanni wrote:
| Are you using multiple Xymon servers or should this ('0.0.0.0')
be | whatever XYMONSERVERIP is set to in xymonserver.cfg?

There is no secondary xymon server but there is a big brother
running. My task at the moment is to gradually retire big brother
and move everything to Xymon but I still have a LONG way to go.
That's not going to work. They both listen on the same port, which is
impossible. If you want to, you can use an alternate port for Xymon
and go that route.

- -- 
- ---- _  _ _  _ ___  _  _  _
|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 Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB9d1IACgkQmb+gadEcsb6e/QCeJyoTOHJhahMREQYQySr2xdfA
X/EAn2Hrkso72Yt6rV36fHoXfeW9MWE0
=SJOo
-----END PGP SIGNATURE-----
list Paul Root · Tue, 16 Oct 2012 15:32:39 +0000 ·
Change the primary port, 1984 to a proxy. And move Big Brother to another port, and the new xymon to a separate port. Then the proxy forwards to those ports.

Paul Root    - Senior Engineer
Managed Services Systems - CenturyLink

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On
Behalf Of Novosielski, Ryan
Sent: Tuesday, October 16, 2012 10:04 AM
To: Yanni
Cc: xymon at xymon.com
Subject: Re: [Xymon] Xymon status does not get updated
quoted from Ryan Novosielski

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/16/2012 10:44 AM, Yanni wrote:
| Are you using multiple Xymon servers or should this ('0.0.0.0')
be | whatever XYMONSERVERIP is set to in xymonserver.cfg?

There is no secondary xymon server but there is a big brother
running. My task at the moment is to gradually retire big brother
and move everything to Xymon but I still have a LONG way to go.
That's not going to work. They both listen on the same port, which is
impossible. If you want to, you can use an alternate port for Xymon
and go that route.

- --
- ---- _  _ _  _ ___  _  _  _
|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 Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB9d1IACgkQmb+gadEcsb6e/QCeJyoTOHJhahMREQYQySr2xdfA
X/EAn2Hrkso72Yt6rV36fHoXfeW9MWE0
=SJOo
-----END PGP SIGNATURE-----

list Ryan Novosielski · Tue, 16 Oct 2012 11:38:22 -0400 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Any recommendations on such software? I've not got a need for this
anymore, but I can see it coming in handy in the future.
quoted from Paul Root

On 10/16/2012 11:36 AM, Root, Paul wrote:
Change the primary port, 1984 to a proxy. And move Big Brother to
another port, and the new xymon to a separate port. Then the proxy
forwards to those ports.

Paul Root    - Senior Engineer Managed Services Systems -
CenturyLink

-----Original Message----- From: xymon-bounces at xymon.com
[mailto:xymon-bounces at xymon.com] On Behalf Of Novosielski, Ryan 
Sent: Tuesday, October 16, 2012 10:04 AM To: Yanni Cc:
xymon at xymon.com Subject: Re: [Xymon] Xymon status does not get
updated
On 10/16/2012 10:44 AM, Yanni wrote:
| Are you using multiple Xymon servers or should this
('0.0.0.0') be | whatever XYMONSERVERIP is set to in
xymonserver.cfg?

There is no secondary xymon server but there is a big
brother running. My task at the moment is to gradually retire
big brother and move everything to Xymon but I still have a
LONG way to go.
That's not going to work. They both listen on the same port, which
is impossible. If you want to, you can use an alternate port for
Xymon and go that route.
_______________________________________________ Xymon mailing
list Xymon at xymon.com
quoted from Paul Root
- -- 
- ---- _  _ _  _ ___  _  _  _
|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 Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB9f20ACgkQmb+gadEcsb439ACgsrnNDDk5QLE8wrR8rIbONznZ
Tl8AoNs/0sKJaGPFnaj3ubFfO2gwFC3d
=YMHO
-----END PGP SIGNATURE-----
list Yanni · Tue, 16 Oct 2012 16:51:58 +0100 ·
Hi

Yes our BB does listen to 1984 and most likely that was causing the 
problems I've been having lately.
Is it is easy to change xymon's port to something else?
Could you please let me know which config file I have to change?

Thank you
quoted from Ryan Novosielski

On 10/16/2012 04:03 PM, Novosielski, Ryan wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/16/2012 10:44 AM, Yanni wrote:
| Are you using multiple Xymon servers or should this ('0.0.0.0')
be | whatever XYMONSERVERIP is set to in xymonserver.cfg?

There is no secondary xymon server but there is a big brother
running. My task at the moment is to gradually retire big brother
and move everything to Xymon but I still have a LONG way to go.
That's not going to work. They both listen on the same port, which is
impossible. If you want to, you can use an alternate port for Xymon
and go that route.

- -- 
- ---- _  _ _  _ ___  _  _  _
|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 Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB9d1IACgkQmb+gadEcsb6e/QCeJyoTOHJhahMREQYQySr2xdfA
X/EAn2Hrkso72Yt6rV36fHoXfeW9MWE0
=SJOo
-----END PGP SIGNATURE-----
list Paul Root · Tue, 16 Oct 2012 16:00:34 +0000 ·
Xymon comes with a proxy.

You turn it on in tasks.cfg

First, set Big Brother to 1986, or something. Sorry, I don't know how to do that.

Second, set the xymon server to another port:

[xymond]
        ENVFILE /etc/xymon/xymonserver.cfg
        CMD xymond --listen=0.0.0.0:1985 --pidfile=$XYMONSERVERLOGS/xymond.pid --restart=$XYMONTMP/xymond.chk --checkpoint-file=$XYMONTMP/xymond.chk --checkpoint-interval=600 --log=$XYMONSERVERLOGS/xymond.log --admin-senders=127.0.0.1,$XYMONSERVERIP --store-clientlogs=!msgs

You'll also need to have xymonnet go to the right place.

[xymonnet]
        ENVFILE /etc/xymon/xymonserver.cfg
        NEEDS xymond
        CMD XYMONDPORT=1984 xymonnet --report --ping --checkresponse
        LOGFILE $XYMONSERVERLOGS/xymon-network.log
        INTERVAL 5m

And of course, the repeat process:

[xymonnetagain]
        ENVFILE /etc/xymon/xymonserver.cfg
        NEEDS xymond
        CMD XYMONDPORT=1984 $XYMONHOME/ext/xymonnet-again.sh
        LOGFILE $XYMONSERVERLOGS/xymonnet-again.log
        INTERVAL 1m

I would guess that Big Brother has the same sort of deal.

Then set the proxy on port 1984:

[xymonproxy]
        ENVFILE /etc/xymon/xymonserver.cfg
        CMD $XYMONHOME/bin/xymonproxy --server=127.0.0.1:1985,127.0.0.1:1986 --listen=0.0.0.0:1984 --report=$MACHINE.xymonproxy --no-daemon --pidfile=$XYMONSERVERLOGS/xymonproxy.pid
        LOGFILE $XYMONSERVERLOGS/xymonproxy.log
quoted from Ryan Novosielski

Paul Root    - Senior Engineer
Managed Services Systems - CenturyLink

-----Original Message-----
From: Novosielski, Ryan [mailto:user-ae4522577e16@xymon.invalid]
Sent: Tuesday, October 16, 2012 10:38 AM
To: Root, Paul
Cc: Yanni; xymon at xymon.com
Subject: Re: [Xymon] Xymon status does not get updated

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Any recommendations on such software? I've not got a need for this
anymore, but I can see it coming in handy in the future.

On 10/16/2012 11:36 AM, Root, Paul wrote:
Change the primary port, 1984 to a proxy. And move Big Brother to
another port, and the new xymon to a separate port. Then the proxy
forwards to those ports.

Paul Root    - Senior Engineer Managed Services Systems -
CenturyLink

-----Original Message----- From: xymon-bounces at xymon.com
[mailto:xymon-bounces at xymon.com] On Behalf Of Novosielski, Ryan
Sent: Tuesday, October 16, 2012 10:04 AM To: Yanni Cc:
xymon at xymon.com Subject: Re: [Xymon] Xymon status does not get
updated
On 10/16/2012 10:44 AM, Yanni wrote:
| Are you using multiple Xymon servers or should this
('0.0.0.0') be | whatever XYMONSERVERIP is set to in
xymonserver.cfg?

There is no secondary xymon server but there is a big
brother running. My task at the moment is to gradually retire
big brother and move everything to Xymon but I still have a
LONG way to go.
That's not going to work. They both listen on the same port, which
is impossible. If you want to, you can use an alternate port for
Xymon and go that route.
_______________________________________________ Xymon mailing
list Xymon at xymon.com
- --
- ---- _  _ _  _ ___  _  _  _
|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 Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB9f20ACgkQmb+gadEcsb439ACgsrnNDDk5QLE8wrR8rIbONznZ
Tl8AoNs/0sKJaGPFnaj3ubFfO2gwFC3d
=YMHO
-----END PGP SIGNATURE-----
list Yanni · Tue, 16 Oct 2012 17:00:34 +0100 ·
Thanks Paul but that's a bit too advanced for me.
I'd rather use a different port for xymon for now at least.
quoted from Paul Root


On 10/16/2012 04:32 PM, Root, Paul wrote:
Change the primary port, 1984 to a proxy. And move Big Brother to another port, and the new xymon to a separate port. Then the proxy forwards to those ports.

Paul Root    - Senior Engineer
Managed Services Systems - CenturyLink

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On
Behalf Of Novosielski, Ryan
Sent: Tuesday, October 16, 2012 10:04 AM
To: Yanni
Cc: xymon at xymon.com
Subject: Re: [Xymon] Xymon status does not get updated

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/16/2012 10:44 AM, Yanni wrote:
| Are you using multiple Xymon servers or should this ('0.0.0.0')
be | whatever XYMONSERVERIP is set to in xymonserver.cfg?

There is no secondary xymon server but there is a big brother
running. My task at the moment is to gradually retire big brother
and move everything to Xymon but I still have a LONG way to go.
That's not going to work. They both listen on the same port, which is
impossible. If you want to, you can use an alternate port for Xymon
and go that route.

- --
- ---- _  _ _  _ ___  _  _  _
|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 Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB9d1IACgkQmb+gadEcsb6e/QCeJyoTOHJhahMREQYQySr2xdfA
X/EAn2Hrkso72Yt6rV36fHoXfeW9MWE0
=SJOo
-----END PGP SIGNATURE-----

list Ryan Novosielski · Tue, 16 Oct 2012 12:07:58 -0400 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't recall, but grepping the files for "1984" should turn it up
pretty quickly.
quoted from Yanni

On 10/16/2012 11:52 AM, Yanni wrote:
Hi

Yes our BB does listen to 1984 and most likely that was causing the
 problems I've been having lately. Is it is easy to change xymon's
port to something else? Could you please let me know which config
file I have to change?

Thank you

On 10/16/2012 04:03 PM, Novosielski, Ryan wrote: On 10/16/2012
10:44 AM, Yanni wrote:
| Are you using multiple Xymon servers or should this
('0.0.0.0') be | whatever XYMONSERVERIP is set to in
xymonserver.cfg?

There is no secondary xymon server but there is a big
brother running. My task at the moment is to gradually retire
big brother and move everything to Xymon but I still have a
LONG way to go.
That's not going to work. They both listen on the same port, which
is impossible. If you want to, you can use an alternate port for
Xymon and go that route.
- -- 
- ---- _  _ _  _ ___  _  _  _
|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 Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB9hl4ACgkQmb+gadEcsb6ecgCfZOeM8IpLYo8C9reRzEqYDwDX
+NkAnRTpbZ2HeAByhsADqIv17CuUNfgI
=ly9l
-----END PGP SIGNATURE-----
list Yanni · Tue, 16 Oct 2012 17:34:23 +0100 ·
Thanks a lot Ryan.

I found it. It's in xymonserver.cfg
quoted from Ryan Novosielski

On 10/16/2012 05:07 PM, Novosielski, Ryan wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't recall, but grepping the files for "1984" should turn it up
pretty quickly.

On 10/16/2012 11:52 AM, Yanni wrote:
Hi

Yes our BB does listen to 1984 and most likely that was causing the
  problems I've been having lately. Is it is easy to change xymon's
port to something else? Could you please let me know which config
file I have to change?

Thank you

On 10/16/2012 04:03 PM, Novosielski, Ryan wrote: On 10/16/2012
10:44 AM, Yanni wrote:
| Are you using multiple Xymon servers or should this
('0.0.0.0') be | whatever XYMONSERVERIP is set to in
xymonserver.cfg?

There is no secondary xymon server but there is a big
brother running. My task at the moment is to gradually retire
big brother and move everything to Xymon but I still have a
LONG way to go.
That's not going to work. They both listen on the same port, which
is impossible. If you want to, you can use an alternate port for
Xymon and go that route.
- -- 
- ---- _  _ _  _ ___  _  _  _
|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 Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB9hl4ACgkQmb+gadEcsb6ecgCfZOeM8IpLYo8C9reRzEqYDwDX
+NkAnRTpbZ2HeAByhsADqIv17CuUNfgI
=ly9l
-----END PGP SIGNATURE-----