October 2015 - Xymon - Xymon mailman web

Need help with upgrade from 4.3.17 to 4.3.20
by cleaver＠terabithia.org 17 Jul '18

17 Jul '18

Hmm. So far, the only way I've been able to reproduce this is by replacing the ScriptAlias directives with mere Alias's in the xymon.conf apache config. Has there been any change in the path you've used for the CGI directory since the previous version, or is there any chance that another Alias line is taking precedence over the ScriptAlias? Do you see anything in the apache access/error logs that indicates an error? -jc On Tue, May 19, 2015 10:37 am, Cortes, Manny wrote: > Having the same problem after installing 4.3.20 on both Ubuntu server > 14.04 and 15.04. > > Thanks, > > > Manuel A Cortes > > Systems Programmer III > > [IBM_Cert] > > IBM Certified System Administrator AIX 7 > > Information Services > > 321-841-6534 > > Orlandohealth.com > > Facebook.com/orlandohealth > > Youtube.com/orlandohealth > > @orlandohealth on twitter > > > > 1414 Kuhl Avenue.,MP136 > > Orlando, Florida 32806 > > From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Asif Iqbal > Sent: Tuesday, May 19, 2015 12:59 PM > To: J.C. Cleaver > Cc: xymon at xymon.com > Subject: Re: [Xymon] Need help with upgrade from 4.3.17 to 4.3.20 > > > > On Tue, May 19, 2015 at 12:40 PM, J.C. Cleaver > <cleaver at terabithia.org<mailto:cleaver at terabithia.org>> wrote: > Hmm. It seems like it's trying to pass along the binary rather than > actually execute it. Can you > > a) validate the permissions on the various .sh files inside the > /xymon-cgi/ directory. (Wondering if there's a case where make install > doesn't set permissions properly), and > > > /var/lib/xymon/cgi-bin$ ls -al > total 6560 > drwxr-xr-x 2 root root 4096 May 19 10:19 . > drwxr-xr-x 16 xymon xymon 4096 May 19 10:19 .. > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 acknowledgements.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 appfeed-critical.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 appfeed.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 certreport.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 columndoc.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 confreport-critical.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 confreport.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 criticalview.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 csvinfo.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 datepage.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 eventlog.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 findhost.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 ghostlist.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 historylog.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 history.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 hostgraphs.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 hostlist.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 nongreen.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 notifications.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 perfdata.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 reportlog.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 report.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 showgraph.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 snapshot.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 svcstatus.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 topchanges.sh > > > b) verify that the ScriptAlias or ExecCGI options are still present in > apache.conf. > > > grep xymon-cgi /etc/apache2/sites-enabled/xymon-apache.conf > # "/xymon" and "/xymon-cgi" URLs. > ScriptAlias /xymon-cgi/ "/var/lib/xymon/cgi-bin/" > RewriteRule ^/xymon-cgi/bb-hist.sh /xymon-cgi/history.sh [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-eventlog.sh /xymon-cgi/eventlog.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-rep.sh /xymon-cgi/report.sh [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-replog.sh /xymon-cgi/reportlog.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-snapshot.sh /xymon-cgi/snapshot.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-findhost.sh /xymon-cgi/findhost.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-csvinfo.sh /xymon-cgi/csvinfo.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbitcolumn.sh /xymon-cgi/columndoc.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-datepage.sh /xymon-cgi/datepage.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbitgraph.sh /xymon-cgi/showgraph.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-hostsvc.sh /xymon-cgi/svcstatus.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-histlog.sh /xymon-cgi/historylog.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-confreport.sh /xymon-cgi/confreport.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-confreport-critical.sh > /xymon-cgi/confreport-critical.sh [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-nkview.sh /xymon-cgi/criticalview.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-certreport.sh /xymon-cgi/certreport.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-nongreen.sh /xymon-cgi/nongreen.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-hostgraphs.sh /xymon-cgi/hostgraphs.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-ghosts.sh /xymon-cgi/ghostlist.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-notifylog.sh /xymon-cgi/notifications.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-hostlist.sh /xymon-cgi/hostlist.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-perfdata.sh /xymon-cgi/perfdata.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-topchanges.sh /xymon-cgi/topchanges.sh > [R=permanent,L] > > > HTH, > > -jc > > > On Tue, May 19, 2015 7:56 am, Asif Iqbal wrote: >> I am not sure what I need to after the upgrade for the columns to show >> data >> instead of >> something like this >> >> >> ELF ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½>ï¿½ ï¿½ï¿½ï¿½ >> @ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ Ã >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½8ï¿½ ï¿½@ï¿½%ï¿½"ï¿½ ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½Ã¸ >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½Ã¸ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½8 ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½8 >> @ï¿½ï¿½ï¿½ï¿½ï¿½8 @ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½Ã¤Ã¤ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½Ã¤Ã¤ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ >> >> I removed FollowSymLinks from xymon-apache.conf file under /xymon-cgi/ >> and /xymon-seccgi/ and restarted. >> >> I am using ubuntu >> >> -- >> Asif Iqbal >> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu<http://pgp.mit.edu> >> A: Because it messes up the order in which people normally read text. >> Q: Why is top-posting such a bad thing? >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com<mailto:Xymon at xymon.com> >> http://lists.xymon.com/mailman/listinfo/xymon >> > > > > > -- > Asif Iqbal > PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu<http://pgp.mit.edu> > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > > ________________________________ > > This e-mail message and any attached files are confidential and are > intended solely for the use of the addressee(s) named above. If you are > not the intended recipient, any review, use, or distribution of this > e-mail message and any attached files is strictly prohibited. > > This communication may contain material protected by Federal privacy > regulations, attorney-client work product, or other privileges. If you > have received this confidential communication in error, please notify the > sender immediately by reply e-mail message and permanently delete the > original message. To reply to our email administrator directly, send an > email to: postmaster at orlandohealth.com . > > If this e-mail message concerns a contract matter, be advised that no > employee or agent is authorized to conclude any binding agreement on > behalf of Orlando Health by e-mail without express written confirmation by > an officer of the corporation. Any views or opinions presented in this > e-mail are solely those of the author and do not necessarily represent > those of Orlando Health. >

8 25

Recovery notifications not generated when test goes red->yellow->green?
by hobbit＠elyograg.org 13 Dec '17

13 Dec '17

It appears that if a test goes from the red state, to the yellow state, and then to the green state, no recovery notification is sent. If it goes directly from red to green, then we get a notification. Initial notifications are only sent on RED and PURPLE. We have recovery notifications configured for most tests. Xymon server is 4.3.21, built using makerpm.sh and installed with yum on CentOS 6. I do not know whether our previous version (4.3.14) behaved similarly. It was almost an accident that I discovered the problem at all. Is this expected behavior? If it is, can I change it? Thanks, Shawn

4 3

DNS failures causing "runtime longer than time limit"
by jlaidman＠rebel-it.com.au 11 Sep '17

11 Sep '17

Hi I'm running Xymon v4.3.10 on Linux, and I'm quite sure it's compiled with c-ares support. I have 12 new DNS servers that were added to Xymon about one month ago. All of my server entries in hosts.cfg have "testip". The tasks.cfg runs xymonet with "--dns-timeout=3". The hosts entries look like so: 10.10.10.1 dnshost1.example.com # testip dns=NS:example.com,SOA: example.com About a week ago, connectivity to all of these servers failed, and at the same time, the xymonnet run time jumped from less than 15 seconds to about 330 seconds, so about 315 seconds extra. The xymonnet page says 295 seconds is taken up by DNS tests. If the increase in time taken is about 315 and is entirely due to the 12 servers failing, then each failed server is adding about 26 seconds to the total run time. I don't think this should be happening like this. With two DNS checks per server, the DNS checks should be taking 6 seconds each to time-out, not 26. If I run xymonnet with "--timing --no-update" and specify only one hostname, I can view the results and the timing. This shows that the ping check gets reported after about 3 seconds, and then the DNS tests are executed and take 26 seconds total. My naiive assumption was that when a server failed a ping (and didn't have "noclear" defined in hosts.cfg) then the network checks would be skipped. On re-reading the man page for hosts.cfg, it dawned on me that a failed ping simply suppresses failed test /results/, but doesn't stop the tests from being run. So the real problem is that the "--dns-timeout=3" is not being taken into consideration by xymonnet. If I run xymonnet with "--debug" it tells me: 1900 2015-06-03 12:02:20 ares_search: tlookup='example.com', class=1, type=2 1900 2015-06-03 12:02:20 ares_search: tlookup='example.com', class=1, type=6 1900 2015-06-03 12:02:20 Processing 0 DNS lookups with ARES 1900 2015-06-03 12:02:46 Finished ARES queue after loop 423 This is peculiar. Why would it say "processing 0 DNS lookups" when there are two lookups to test? Could this be because xymonnet hasn't actually been built with ARES support and I didn't know it? Is there a good way to tell? If I add "--no-ares" I get the same results perhaps suggesting a lack of ARES support. On the other hand, if I add "timeout:3" and "attempts:1" into resolv.conf, I also get the same results. If I run "nm /path/to/xymonnet | grep gethostby" it returns "ares_gethostbyname". Just for fun, I compiled Xymon v4.3.21 and ran the xymonnet binary from there, with no change in behaviour. I also tried removing the "--dns-timeout" option so that it defaults to 30 seconds, but still no change - 26 seconds for two DNS tests. So, I'm not really sure what the problem is, but xymonnet certainly isn't behaving as I would expect. Cheers Jeremy

2 3

EXTIME still valid ?
by rltexas1＠gmail.com 22 Jun '16

22 Jun '16

Is the EXTIME option still valid in the alerts.cfg I am having problems testing the following EXTIME=1:1140:1240 Should be exclude Monday's 11:40 to 12:40. Will test EXTIME=M:1140:1240 But if it's M for Monday what would Sunday be ? Thanks

4 4

MAGMA XYMon Web GUI Admin Now Available!
by sanderson＠CORNETSER.com 07 Jan '16

07 Jan '16

Henrik and Fellow Xymoners, Just for you I have pushed off any real work for today just to get you all a first release of MAGMA the XYMon Web GUI Admin. MAGMA is an add-on web GUI for managing Host, Groups and Alarms on a XYmon 4.3 or newer system. You can find MAGMA at http://www.squidworks.net/magma/ There you will find the description, screen shots and features of MAGMA along with the link to download the source package. It requires MySQL and PHP5 and is very simple to install. All supporting information is included in the tarball. How does it work? --------------------------- It stores all alarm and host/group configs in the SQL database and rewrites the Host.cfg, Analysis.cfg and Alarms.cfg files causing the XYmon system to update its tests and pages based on the changes in these files. It will overwrite the files each time a host is added or edited making the process of updating automatic. To get the full benefit of MAGMA you should place all hosts in "central" mode, although this is not required, without it your management is somewhat restrictive (external test management only). In Central mode you get full management features for all tests. If you have any questions or need some help just send me a email @ sanderson @ squidworks.net Cubert 8-) Aka Shannon Anderson

6 5

Xymon and Oracle ASM?
by betsy.schwartz＠gmail.com 30 Dec '15

30 Dec '15

Anyone got any good scripts for xymon and Oracle ASM?

5 4

downtime globally
by jlaidman＠rebel-it.com.au 09 Nov '15

09 Nov '15

On 26 June 2015 at 06:01, Dito <dito74 at gmail.com> wrote: > The test that I need NOT reporting on weekends are NOT network tests, they > are custom ALC that written on the agent folder and forwarded to the xymon > server. Can I only use Downtime for Network tests? > I don't believe it's only for network tests; should work for all tests. > Right now now I have this line, but I am still getting alerts on weekends > > 10.51.0.203 bosutil.domainname.com # smtp > DOWNTIME=ALC1:5:2300:2359:check_op_con,ALC2:5:2300:2359:check_op_con,ALC1:0:0000:1200:check_op_con,ALC1:6:0000:2359:check_op_con,ALC2:0:0000:1200:check_op_con,ALC2:6:0000:2359:check_op_con,mq:0:0300:1000:snapshots > This all looks OK to me. It says to me that you want the server to be in "downtime" state from Friday 11pm to Sunday midday. What day/time are you getting alerts? Just a hint, you can specify multiple tests in one DOWNTIME specification. So for example: DOWNTIME=ACL1,ACL2:5:2300:2359:check_op_con,... I doubt this would help though, but might shorten your config a bit. Interestingly, an example in the Changes file uses a semicolon instead of a comma to separate the different DOWNTIME specifications, so perhaps see if that helps. Have you looked at the "info" page for the server? It should show what Xymon thinks are the down-times for that server. Can you confirm that this page matches your expectations? J

2 3

Xymon version 5
by jglouisjr＠gmail.com 31 Oct '15

31 Oct '15

Hi all, Maybe I'm out of the loop on this but is there going to be a version 5 of Xymon? Is there a roadmap page? Thanks, Jim -- *----------------------------------------[image: http://action.lung.org/site/TR/Climb?px=5751753&pg=personal&fr_id=12850&s_s…] <http://action.lung.org/site/TR/Climb?px=5751753&pg=personal&fr_id=12850&s_s…> Jim Louis \\\\||//// \ ~ ~ / | @ @ |* *--oOo---(_)---oOo--* "The software isn't finished until the last user is dead." ~ Anonymous

2 1

Status, NCV and time stamps
by mvanderw＠nd.edu 31 Oct '15

31 Oct '15

(Sending this again to the list, as I sent it using the wrong e-mail previously (non-subscriber e-mail)) I second this request for enhancement. It would be nice to be able to send more data from the client to be displayed on the column/test page, but not get parsed to be included in the RRD graph. Only parsing certain lines that are in the NCV format would be a nice feature. Something like what J.C. mentioned ("a data parser that looks for a hidden HTML comment marker for lines to process (and ignores the rest)") would work well for this, IMO. Or is there a way to do this already? (even through a hack?) Nothing urgent, just something that would be nice to be included in some future Xymon release. Thanks. -- Matt Vander Werf On Tue, Oct 6, 2015 at 10:39 AM, Matt Vander Werf <matt1299 at gmail.com> wrote: > I second this request for enhancement. It would be nice to be able to send > more data from the client to be displayed on the column/test page, but not > get parsed to be included in the RRD graph. Only parsing certain lines that > are in the NCV format would be a nice feature. Something like what J.C. > mentioned ("a data parser that looks for a hidden HTML comment marker for > lines to process (and ignores the rest)") would work well for this, IMO. > > Or is there a way to do this already? (even through a hack?) > > Nothing urgent, just something that would be nice to be included in some > future Xymon release. > > Thanks. > > -- > Matt Vander Werf > > On Mon, Oct 5, 2015 at 7:48 PM, Boldt, David <dboldt at usgs.gov> wrote: > >> Thanks for these leads. Will looks at both the filter and "trends" >> message options. >> >> As a request for enhancement, I think it would be useful to have an >> option to use a regexp to extract data from the status, one for each >> variable. >> >> >> >> On Mon, Oct 5, 2015 at 7:36 PM, J.C. Cleaver <cleaver at terabithia.org> >> wrote: >> >>> On Mon, October 5, 2015 3:52 pm, Boldt, David wrote: >>> > I'm in the process of converting Big Brother tests to XYMon and would >>> like >>> > to enable RRD/graphics for these tests. >>> > >>> > Several of these tests present date/time information which is >>> important. >>> > >>> > As a workaround for one test I have replaced the colon on a HH:MM:DD >>> > formatted date with a dot, but it doesn't really look like a time >>> anymore. >>> > >>> > * Is there a way to have NCV ignore colons (and only use "=")? >>> > >>> > * Is there a way to have NCV ignore a line (which might contain >>> colons)? >>> >>> >>> Unfortunately, there isn't a way to do either of these at the moment. I'd >>> considered a data parser that looks for a hidden HTML comment marker for >>> lines to process (and ignores the rest), but it's not quite present yet. >>> >>> >>> > >>> > * Can I use Data messages in such a way that the corresponding Status >>> > message is not parsed? >>> >>> The easiest way to do this would be to add a --filter= option to the >>> xymond_channel command line for the xymond_rrd process that's handling >>> the >>> *status* channel, but not the data channel. >>> >>> There's a CPU load hit for doing so (since now you're doing a PCRE on >>> each >>> message), however it may not have much of an impact depending on your >>> message volume. >>> >>> >>> > * Might there be some other mechanism entirely? >>> >>> Generally, speaking for more advanced RRD submission, the 'trends' >>> message >>> can be a useful data payload which is read directly by xymond_rrd. The >>> advantage there (aside from more direct control) is the ability to send >>> data points for multiple graphs at once, which could outweigh the expense >>> of another message transmission. >>> >>> >>> HTH, >>> >>> -jc >>> >>> >>> >> >> >> -- >> -- David Boldt >> <dboldt at usgs.gov> >> >> >> "Ah, this is obviously some strange usage of the word 'safe' that I >> wasn't previously aware of." >> --Douglas Adams (1952 - 2001), Arthur Dent in "The Hitchhikers Guide >> to the Galaxy" >> >> >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com >> http://lists.xymon.com/mailman/listinfo/xymon >> >> >

3 2

Combo status question
by colin.coe＠gmail.com 31 Oct '15

31 Oct '15

Hi all Is it possible to have a combo status for switch ports on non-stacked switches? For example, gi1/0/24 on either switch sw01 or sw02 must be up. Thanks CC

1 0