- Xymon - Xymon mailman web

Multiple Issues with 4.3.17 install
by jlaidman＠rebel-it.com.au 17 Oct '14

17 Oct '14

Neal I have to say, apart from the mention of xymon_rrd crashing, much of what I see appears normal. The "network listener on 0.0.0.0:1984" indicates that xymond is listening to connections any IP addresses. xymond will go yellow when when it's restarted. The messages under "Latest error messages" all appear to be normal start-up messages for xymond. Cheers Jeremy On 17 October 2014 09:40, Neal, Jonathan W via Xymon <xymon at xymon.com> wrote: > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > > > ---------- Forwarded message ---------- > From: "Neal, Jonathan W" <wes.neal at verizon.com> > To: "xymon at xymon.com" <xymon at xymon.com> > Cc: > Date: Thu, 16 Oct 2014 18:40:46 -0400 > Subject: Multiple Issues with 4.3.17 install > > I am coming from an early 4.2 install. I merged my bb-hosts, > hobbit-alerts.cfg and hobbit-clients.cfg files into the proper files in the > new 4.3.17 install. I also copied over the entire histlogs directory from > data. Currently xymon_rrd keeps dying and going purple with a Fatal > signal error. > > > > rrd-status log has this in it going back most of the day: > > > > 2014-10-16 19:23:00 Peer at 0.0.0.0:0 failed: Broken pipe > > 2014-10-16 19:23:00 Peer not up, flushing message queue > > 2014-10-16 19:24:43 Shutting down, flushing cached updates to disk > > 2014-10-16 19:28:39 Peer not up, flushing message queue > > 2014-10-16 20:00:35 Shutting down, flushing cached updates to disk > > 2014-10-16 20:00:36 Cache flush completed > > 2014-10-16 21:58:19 Peer not up, flushing message queue > > 2014-10-16 22:30:58 Shutting down, flushing cached updates to disk > > 2014-10-16 22:30:59 Cache flush completed > > 2014-10-16 22:31:14 Peer not up, flushing message queue > > > > Xymond is also constantly going yellow and I again see that 0.0.0.0:1984 > that is mentioned above: > > > > Statistics for Xymon daemon > > Version: 4.3.17 > > Up since 16-Oct-2014 22:31:09 (0 days, 00:04:59) > > > > Incoming messages : 937 > > - status : 885 > > - combo : 1 > > - extcombo : 22 > > - page : 0 > > - summary : 0 > > - data : 6 > > - client : 2 > > - notes : 0 > > - enable : 0 > > - disable : 0 > > - ack : 0 > > - config : 4 > > - query : 0 > > - xymondboard : 6 > > - xymondlog : 5 > > - drop : 0 > > - rename : 0 > > - dummy : 1 > > - ping : 0 > > - notify : 0 > > - schedule : 0 > > - download : 0 > > - Bogus/Timeouts : 5 > > Incoming messages/sec : 3 (average last 300 seconds) > > > > status channel messages: 885 (1 readers) > > stachg channel messages: 877 (1 readers) > > page channel messages: 37 (1 readers) > > data channel messages: 6 (1 readers) > > notes channel messages: 0 (0 readers) > > enadis channel messages: 0 (0 readers) > > client channel messages: 2 (1 readers) > > clichg channel messages: 0 (1 readers) > > user channel messages: 0 (0 readers) > > backfeed messages : 0 > > > > > > Latest error messages: > > Loading hostnames > > Loading saved state > > Setting up network listener on 0.0.0.0:1984 > > Setting up signal handlers > > Setting up xymond channels > > Setting up logfiles > > Setup complete > > > > Can anyone tell me what might be going on? > > Thanks in advance! > > > >

2 1

function run_command in ../lib/run.c assumes sh but uses any $SHELL
by gendalia＠iastate.edu 17 Oct '14

17 Oct '14

If I restart xymon while using tcsh, for example, suddenly my ntp test breaks, because: === red Thu Oct 16 22:39:47 2014 ntp NOT ok Service ntp on <elided> is not OK : Service unavailable Command: ntpdate -u -q -p 2 <elided> 2>&1 1: Permission denied. === /var/log/xymon/1, of course, is confused about the value of 2, because it can write there sometimes, which is also interesting. For the moment, I've hard coded 'export SHELL=/bin/sh' in the startup script for xymon, but the assumption shouldn't be made that $SHELL is a /bin/sh derivative. -Tracy

3 4

SSLv3 vs TLS, not working for !https
by gjs＠sonnit.dk 17 Oct '14

17 Oct '14

Hi all So looking at the recent POODLE SSL v3 attack, I started reconfiguring servers and hosts. I same across a problem, not with https sites - as Xymon supports TLS on those, but pop3, imaps and probably more. Services are reported down, but they are up, just not supporting SSLv3 Error output: Unspecified SSL error in SSL_connect to pop3s (58115/tcp) on host 192.168.201.xx: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure Unspecified SSL error in SSL_connect to imaps (57603/tcp) on host 192.168.201.xx: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure I'm not sure what to patch here, to make xymonnet use TLS instead of SSL on all protocols. Any suggestions would be most appreciated, as many of our hosts are now reported as down. -- Best regards Gorm J. Siiger

1 0

Multiple Issues with 4.3.17 install additional
by wes.neal＠verizon.com 16 Oct '14

16 Oct '14

The other things that seems to be happening is that all alerts are going to all possible recipients. The info panel for most all of the systems I checked look like this: conn wes.neal at one.verizon.com (R) - - 1h - purple,red page-ems-team1 at one.verizon.com 10m 1s - 2d - purple,red wes.neal at one.verizon.com(R) - - 1h - purple,red page-ems-team1 at one.verizon.com 10m 1s - 2d - purple,red page_ems_team3 at lists.verizonbusiness.com 10m 1s - 2d - purple,red page_ems_team3 at lists.verizonbusiness.com 10m 1s - 2d - purple,red page_ems_team3 at lists.verizonbusiness.com 10m 1s - 2d - purple,red page_ems_team3 at lists.verizonbusiness.com The rules which I copied over from my old system look like this though for this system in particular. HOST=$aspmdpbulk MAIL $ems1 REPEAT=60m RECOVERED MAIL page-ems-team1 at one.verizon.com SERVICE=conn DURATION>10 REPEAT=2d All of my rules in alerts.cfg pretty much look like the above. An email for everything and a page for connectivity. I have checked the file for white space, typos etc. I do not see any. Is there script or something out there that will parse the *.cfg files for errors?

1 0

Multiple Issues with 4.3.17 install
by wes.neal＠verizon.com 16 Oct '14

16 Oct '14

I am coming from an early 4.2 install. I merged my bb-hosts, hobbit-alerts.cfg and hobbit-clients.cfg files into the proper files in the new 4.3.17 install. I also copied over the entire histlogs directory from data. Currently xymon_rrd keeps dying and going purple with a Fatal signal error. rrd-status log has this in it going back most of the day: 2014-10-16 19:23:00 Peer at 0.0.0.0:0 failed: Broken pipe 2014-10-16 19:23:00 Peer not up, flushing message queue 2014-10-16 19:24:43 Shutting down, flushing cached updates to disk 2014-10-16 19:28:39 Peer not up, flushing message queue 2014-10-16 20:00:35 Shutting down, flushing cached updates to disk 2014-10-16 20:00:36 Cache flush completed 2014-10-16 21:58:19 Peer not up, flushing message queue 2014-10-16 22:30:58 Shutting down, flushing cached updates to disk 2014-10-16 22:30:59 Cache flush completed 2014-10-16 22:31:14 Peer not up, flushing message queue Xymond is also constantly going yellow and I again see that 0.0.0.0:1984 that is mentioned above: Statistics for Xymon daemon Version: 4.3.17 Up since 16-Oct-2014 22:31:09 (0 days, 00:04:59) Incoming messages : 937 - status : 885 - combo : 1 - extcombo : 22 - page : 0 - summary : 0 - data : 6 - client : 2 - notes : 0 - enable : 0 - disable : 0 - ack : 0 - config : 4 - query : 0 - xymondboard : 6 - xymondlog : 5 - drop : 0 - rename : 0 - dummy : 1 - ping : 0 - notify : 0 - schedule : 0 - download : 0 - Bogus/Timeouts : 5 Incoming messages/sec : 3 (average last 300 seconds) status channel messages: 885 (1 readers) stachg channel messages: 877 (1 readers) page channel messages: 37 (1 readers) data channel messages: 6 (1 readers) notes channel messages: 0 (0 readers) enadis channel messages: 0 (0 readers) client channel messages: 2 (1 readers) clichg channel messages: 0 (1 readers) user channel messages: 0 (0 readers) backfeed messages : 0 Latest error messages: Loading hostnames Loading saved state Setting up network listener on 0.0.0.0:1984 Setting up signal handlers Setting up xymond channels Setting up logfiles Setup complete Can anyone tell me what might be going on? Thanks in advance!

1 0

PROC change needed
by dewelker＠gmail.com 16 Oct '14

16 Oct '14

I have this java command-line that shows up in a PROC status (ps listing) on multiple lines. I'd like to be able to have this text replaced with some one-liner. I thought the way to do that was using a PROC line in the analysis.cfg file with the TEXT option, but that doesn't do anything to either the client data OR the PROC status page. Can this somehow be done in a xymond_worker? Can it ONLY be done in a xymond_worker? Sample analysis.cfg file: HOST=* PROC="java" 1 100 green TEXT="java - with a lot of parameters" Any ideas or thoughts would be appreciated. Thanks, David

3 3

MEMACT > 100%
by stef.coene＠docum.org 16 Oct '14

16 Oct '14

Hi, I have an AIX servers that uses more memory then there is available in the server. After upgrading the server to 4.3.17, I noticed that the check is changed and that the percentage of Actual memory is not calculated: Memory Used Total Percentage green Physical 5997M 6144M 97% clear Actual 8697M 6144M 0% - invalid data green Swap 3112M 8192M 37% This is the output before the upgrade: Memory Used Total Percentage green Physical 6099M 6144M 99% green Actual 9065M 6144M 147% green Swap 3358M 8192M 40% Stef

1 1

Flapping Status? What does it mean?
by maik＠vegasystems.com 16 Oct '14

16 Oct '14

We recently migrated our Hobbit 4.2 server to Xymon 4.3.18. For some some clients, I noticed a warning "Xymon WARNING: Flapping status". What is flapping status? how to avoid, but not disable it? Maik

3 2

The 'bad' syntax has been deprecated.....
by maik＠vegasystems.com 15 Oct '14

15 Oct '14

After migrating our old hobbit server to latest version 4.3.18, another error message appeared. Error output: WARNING: The 'bad' syntax has been deprecated, please convert to 'delayred' and/or 'delayyellow' tags What I noticed on other pages online, the warning usually includes a <TESTNAME> value, but not at our installation. Seems to be very difficult to debug it. Maybe someone has a hint? Thanks Maik

2 1

4.3.17 Issue after the install
by john.thurston＠alaska.gov 15 Oct '14

15 Oct '14

On 10/15/2014 11:43 AM, Neal, Jonathan W via Xymon wrote: > On the webpage Under Administration though the last three things in the drop down won't work for me. They all point to xymons/xymon-seccgi which is a script alias in the apache.conf file for the cgi-secure directory. Check the owner and group on the files. Look in the Apache error_log for more information. Check the httpd.conf and confirm xymon-seccgi is listed as a valid source for CGI. -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska

1 0