- Xymon - Xymon mailman web

xymonnet testip And host.cfg Entry
by tom＠it-eckert.de 23 Aug '14

23 Aug '14

Great it works now :) cc'ed list.... On Aug 22, 2014 11:00 PM, "Rebman,Scott (HHSC Contractor)" <Scott.Rebman at hhsc.state.tx.us> wrote: > > Thomas, > > Thanks for the extra set of eyes. It does work once corrected. > > It's all about the syntax. > > Thanks again. > > Scott Allen Rebman > Solaris System Administrator > HHS/HHSC/Contractor > TIERS Operations > (512)873-6864 (CrossPark) > (512)275-6122 (cell) > Scott.Rebman at hhsc.state.tx.us > > > > > -----Original Message----- > From: Thomas Eckert [mailto:tom at it-eckert.de] > Sent: Friday, August 22, 2014 12:00 PM > To: Rebman,Scott (HHSC Contractor) > Cc: xymon at xymon.com > Subject: Re: [Xymon] xymonnet testip And host.cfg Entry > > On both lines mentioning your glabal zone the hash (#) after the hostname is missing. Probably just a cut and paste error. > > Having used conn checks for multihomed machines rarely but from the manpage the syntax seems to be: > > 10.###.###.12 # conn=best,10.###.###.12,172.###.###.78 > > Cheers > Thomas > > On Aug 22, 2014 6:17 PM, "Rebman,Scott (HHSC Contractor)" wrote: > > > > Looking for assistance in recognizing (pinging) admin networks on > > Solaris 10/11 global zones and ldoms but keep using public IP’s for > > containers (zones) > > > > Found the following on the xymonnet man page: > > > > --dns=[ip|only|standard] > > Determines how xymonnet finds the IP adresses of the hosts to test. By default (the "standard"), xymonnet does a DNS lookup of the hostname to determine the IP address, unless the host has the "testip" tag, or the DNS lookup fails. > > With "--dns=only" xymonnet will ONLY do the DNS lookup; if it fails, then all services on that host will be reported as being down. > > With "--dns=ip" xymonnet will never do a DNS lookup; it will use the > > IP adresse specified in hosts.cfg for the tests. Thus, this setting is > > equivalent to having the "testip" tag on all hosts. Note that http > > tests will ignore this setting and still perform a DNS lookup for the > > hostname given in the URL; see the "xymonnet tags for HTTP tests" > > section in hosts.cfg(5) > > > > But on the host.cfg man page: > > > > testip > > By default, Xymon will perform a name lookup of the hostname to get the IP address it will use for network tests. This tag causes Xymon to use the IP listed in the hosts.cfg file. > > > > But then it goes on to say later in the hosts.cfg page: > > > > Testing sites by IP-address > > xymonnet ignores the "testip" tag normally used to force a test to use the IP-address from the hosts.cfg file instead of the hostname, when it performs http and https tests. > > The reason for this is that it interacts badly with virtual hosts, especially if these are IP-based as is common with https-websites. > > The xymon info page does list the admin network IP but the conn page continues to check the public IP address: > > > > > > - Information > > Fri Aug 22 09:38:43 2014 > > > > 08/21/14 What happened to the iostat2 column on the Solaris boxes? > > > > > > > > Hostname: > > > > OS: > > SunOS 5.11 11.1 sun4v sparc sun4v Client S/W: > > IP: > > 172.###.###.78 > > > > > > - conn > > Fri Aug 22 09:40:14 2014 > > > > 08/21/14 What happened to the iostat2 column on the Solaris boxes? > > > > > > > > Top of Form > > Bottom of Form > > Fri Aug 22 09:38:41 2014 conn NOT ok > > > > Service conn on is not OK : Host does not respond to > > ping > > > > > > System unreachable for 1424 poll periods (258838 seconds) > > > > 10.###.###.12 is unreachable > > > > > > > > > > > > host.cfg file entry: > > > > group > > 172.###.###.78 testip > > 10.###.###.41 #COMMENT:"" > > 10.###.###.42 #COMMENT:"" > > 10.###.###.43 #COMMENT:"" > > 10.###.###.44 #COMMENT:"" > > 10.###.###.45 #COMMENT:"" > > 10.###.###.46 #COMMENT:"" > > 10.###.###.47 #COMMENT:"" > > 10.###.###.48 #COMMENT:"" > > 10.###.###.49 #COMMENT:"" > > 10.###.###.79 #COMMENT:"" > > 10.###.###.81 #COMMENT:"" > > 10.###.###.166 #COMMENT:"" > > 10.###.###.53 #COMMENT:"" > > 10.###.###.170 #COMMENT:"" > > 10.###.###.55 #COMMENT:"" > > 10.###.###.56 #COMMENT:"" > > 10.###.###.57 #COMMENT:"" > > 10.###.###.58 #COMMENT:"" > > 10.###.###.73 #COMMENT:"" > > 10.###.###.168 #COMMENT:"" > > > > I have also added the following entry to the hosts.cfg file with no luck getting the conn to go green: > > > > 10.###.###.12 conn={best}10.###.###.12,172.###.###.78 > > > > How do I correct this to have the conn also ping the admin IP address but yet allow the continued checks of DNS for the containers (zones)? > > > > Scott Allen Rebman > > Solaris System Administrator > > Northrop Grumman > > > > > > > > > >

1 0

Administratrivia: Problems for yahoo.com mailing list subscribers
by henrik＠hswn.dk 23 Aug '14

23 Aug '14

Hi, Yahoo has an annoying habit of making life difficult for mail admins, and they have recently done so again by enabling a DMARC 'reject' policy for all of their subscribers. DMARC is one of the newer tools to combat spam, but it has the unfortunate side effect of being completely incompatible with most mailing list software. This came to my attention this morning, when most of the yahoo subscribers to the mailing list were disabled. http://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-what… http://wiki.list.org/display/DEV/DMARC I have this morning upgraded the Mailman software used on the Xymon mailing list. The effect of this is that mails from Yahoo adresses (and others, who has set DMARC policy to 'reject' or 'quarantine') will be wrapped in an "outer message" when forwarded to the list. Most of you won't notice, but it depends on how your e-mail client handles such messages. Regards, Henrik

1 0

bb2.html
by usaims＠yahoo.com 22 Aug '14

22 Aug '14

Greetings, How do I clear out the "100 events received in the past xxx" in the bb2.html? TIA, Rod

2 1

DOWNTIME for http content checks
by mburger＠bubbanfriends.org 22 Aug '14

22 Aug '14

I've looked at the hosts.cfg man page, I've done some searching of the list archives, and I've done some experimentation of my own, but I seem to be unable to achieve the following: I have some hosts for which I'd like to perform web content checks. I've got the cont= lines setup like so: cont=ptlcls2;http://some.host.here:20039/wps/portal/fhmc;"regex[[:space:]]text" And the alarm works just fine. I've tried adding: DOWNTIME=content:*:1435:1445:"some description" or DOWNTIME=ptlcls2:*:1435:1445:"some description" But the new column "ptlcls2" still goes red, rather than blue, during the DOWNTIME period. The only thing I can think of is that DOWNTIME isn't available for content checks, or that I'm incorrectly specifiying the test/status/column for the DOWNTIME specification. If anyone has any insight as to what I might be doing wrong, I'd greatly appreciate it. -- Mike Burger http://www.bubbanfriends.org "It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1

2 2

xymonnet testip And host.cfg Entry
by tom＠it-eckert.de 22 Aug '14

22 Aug '14

On both lines mentioning your glabal zone the hash (#) after the hostname is missing. Probably just a cut and paste error. Having used conn checks for multihomed machines rarely but from the manpage the syntax seems to be: 10.###.###.12 <global zone> # conn=best,10.###.###.12,172.###.###.78 Cheers Thomas On Aug 22, 2014 6:17 PM, "Rebman,Scott (HHSC Contractor)" <Scott.Rebman at hhsc.state.tx.us> wrote: > > Looking for assistance in recognizing (pinging) admin networks on Solaris 10/11 global zones and ldoms but keep using public IP’s for containers (zones) > > Found the following on the xymonnet man page: > > --dns=[ip|only|standard] > Determines how xymonnet finds the IP adresses of the hosts to test. By default (the "standard"), xymonnet does a DNS lookup of the hostname to determine the IP address, unless the host has the "testip" tag, or the DNS lookup fails. > With "--dns=only" xymonnet will ONLY do the DNS lookup; if it fails, then all services on that host will be reported as being down. > With "--dns=ip" xymonnet will never do a DNS lookup; it will use the IP adresse specified in hosts.cfg for the tests. Thus, this setting is equivalent to having the "testip" tag on all hosts. Note that http tests will ignore this setting and still perform a DNS lookup for the hostname given in the URL; see the "xymonnet tags for HTTP tests" section in hosts.cfg(5) > > But on the host.cfg man page: > > testip > By default, Xymon will perform a name lookup of the hostname to get the IP address it will use for network tests. This tag causes Xymon to use the IP listed in the hosts.cfg file. > > But then it goes on to say later in the hosts.cfg page: > > Testing sites by IP-address > xymonnet ignores the "testip" tag normally used to force a test to use the IP-address from the hosts.cfg file instead of the hostname, when it performs http and https tests. > The reason for this is that it interacts badly with virtual hosts, especially if these are IP-based as is common with https-websites. > The xymon info page does list the admin network IP but the conn page continues to check the public IP address: > > <Organization Name> > <Global Zone> - Information > Fri Aug 22 09:38:43 2014 > > 08/21/14 What happened to the iostat2 column on the Solaris boxes? > > > > Hostname: > <Global Zone> > OS: > SunOS <Global Zone> 5.11 11.1 sun4v sparc sun4v > Client S/W: > IP: > 172.###.###.78 > > <Organization Name> > <Global Zone> - conn > Fri Aug 22 09:40:14 2014 > > 08/21/14 What happened to the iostat2 column on the Solaris boxes? > > > > Top of Form > Bottom of Form > Fri Aug 22 09:38:41 2014 conn NOT ok > > Service conn on <Global Zone> is not OK : Host does not respond to ping > > > System unreachable for 1424 poll periods (258838 seconds) > > 10.###.###.12 is unreachable > > > > > > host.cfg file entry: > > group > 172.###.###.78 <global hostname> testip > 10.###.###.41 <container hostname> #COMMENT:"<comment>" > 10.###.###.42 <container hostname> #COMMENT:"<comment>" > 10.###.###.43 <container hostname> #COMMENT:"<comment>" > 10.###.###.44 <container hostname> #COMMENT:"<comment>" > 10.###.###.45 <container hostname> #COMMENT:"<comment>" > 10.###.###.46 <container hostname> #COMMENT:"<comment>" > 10.###.###.47 <container hostname> #COMMENT:"<comment>" > 10.###.###.48 <container hostname> #COMMENT:"<comment>" > 10.###.###.49 <container hostname> #COMMENT:"<comment>" > 10.###.###.79 <container hostname> #COMMENT:"<comment>" > 10.###.###.81 <container hostname> #COMMENT:"<comment>" > 10.###.###.166 <container hostname> #COMMENT:"<comment>" > 10.###.###.53 <container hostname> #COMMENT:"<comment>" > 10.###.###.170 <container hostname> #COMMENT:"<comment>" > 10.###.###.55 <container hostname> #COMMENT:"<comment>" > 10.###.###.56 <container hostname> #COMMENT:"<comment>" > 10.###.###.57 <container hostname> #COMMENT:"<comment>" > 10.###.###.58 <container hostname> #COMMENT:"<comment>" > 10.###.###.73 <container hostname> #COMMENT:"<comment>" > 10.###.###.168 <container hostname> #COMMENT:"<comment>" > > I have also added the following entry to the hosts.cfg file with no luck getting the conn to go green: > > 10.###.###.12 <global zone> conn={best}10.###.###.12,172.###.###.78 > > How do I correct this to have the conn also ping the admin IP address but yet allow the continued checks of DNS for the containers (zones)? > > Scott Allen Rebman > Solaris System Administrator > Northrop Grumman > > > > >

1 0

xymonnet testip And host.cfg Entry
by Scott.Rebman＠hhsc.state.tx.us 22 Aug '14

22 Aug '14

Looking for assistance in recognizing (pinging) admin networks on Solaris 10/11 global zones and ldoms but keep using public IP's for containers (zones) Found the following on the xymonnet man page: --dns=[ip|only|standard] Determines how xymonnet finds the IP adresses of the hosts to test. By default (the "standard"), xymonnet does a DNS lookup of the hostname to determine the IP address, unless the host has the "testip" tag, or the DNS lookup fails. With "--dns=only" xymonnet will ONLY do the DNS lookup; if it fails, then all services on that host will be reported as being down. With "--dns=ip" xymonnet will never do a DNS lookup; it will use the IP adresse specified in hosts.cfg for the tests. Thus, this setting is equivalent to having the "testip" tag on all hosts. Note that http tests will ignore this setting and still perform a DNS lookup for the hostname given in the URL; see the "xymonnet tags for HTTP tests" section in hosts.cfg<http://xymon.sourceforge.net/xymon/help/manpages/man5/hosts.cfg.5.html>(5) But on the host.cfg man page: testip By default, Xymon will perform a name lookup of the hostname to get the IP address it will use for network tests. This tag causes Xymon to use the IP listed in the hosts.cfg file. But then it goes on to say later in the hosts.cfg page: Testing sites by IP-address xymonnet ignores the "testip" tag normally used to force a test to use the IP-address from the hosts.cfg file instead of the hostname, when it performs http and https tests. The reason for this is that it interacts badly with virtual hosts, especially if these are IP-based as is common with https-websites. The xymon info page does list the admin network IP but the conn page continues to check the public IP address: <Organization Name> <Global Zone> - Information Fri Aug 22 09:38:43 2014 [X] 08/21/14 What happened to the iostat2<http://dwru002.hhscie.txaccess.net/hobbit/help/doc/removed-iostat2.html> column on the Solaris boxes? Hostname: <Global Zone> OS: SunOS <Global Zone> 5.11 11.1 sun4v sparc sun4v Client S/W: IP: 172.###.###.78 [X] <Organization Name> <Global Zone> - conn Fri Aug 22 09:40:14 2014 [X] 08/21/14 What happened to the iostat2<http://dwru002.hhscie.txaccess.net/hobbit/help/doc/removed-iostat2.html> column on the Solaris boxes? Top of Form Bottom of Form [X]

1 0

Xymon client under older SUSE Server
by hj.beckers＠kreis-steinfurt.de 22 Aug '14

22 Aug '14

I'va compiled Xymon 4.3.16 on a openSUSE 12.2 server with a kernel 3.4.6.-2.10. Everything works. Now I would like to put the client part on a SUSE Linux Enterprise Server 10 SP1 with a kernel 2.6.16.46-0.12. "runclient.sh start" refuses to start: /lib64/libc.so.6: version 'GLIBC_2.7' not found (required by ... /xymonlauch). The message is repeated with 'GLIBC_2.14' as missing. As I can't compile xymon on this server, is there a way to make xymon believe everything is OK: "ldpeload" or a symbolic link? Hermann-Josef Beckers

3 3

central clients port check suppressed
by didds3＠yahoo.co.uk 22 Aug '14

22 Aug '14

xymon 4.3.17 clients in local mode have the ports and netstat "parts" of hobbitclient-linux.sh commented out so that nothing wrt ports is returned. but for clients using central mode end up with a white sad face showing on the monitor - because I have no interest in any port monitoring currently. how do i STOP port monitoring for these central mode clients?

2 1

Xymon Newbie - Installation Issues
by sam.robert＠outlook.com 21 Aug '14

21 Aug '14

Xymon Community & All those who responded & helped, Thank you a ton for all the help and replies. I finally got it going with all of the valuable help provided here and I doubt I would have been able to make it work without the help I got. So Thank you, once again. It's really appreciated. I would also like to thank the author of Xymon for such a great Open-Source product. From what I have seen so far, nothing comes close. Keep it up! It's a really great community here and love to be part of it. Hopefully will be able to help once I get up to speed with Xymon. Sam. From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Sam Robert Sent: 21 August 2014 08:29 To: xymon at xymon.com Subject: [Xymon] Xymon Newbie - Installation Issues Hello All, I am a Linux and Xymon newbie to begin with so please go easy on me. Found Xymon in my search for a simple yet powerful network monitor and love what I have seen so far. However I cant seem to get it installed properly no matter what. So far I have tried all instances of Linux over at AWS and so far the best with the least amount of errors is Red Hat Enterprise Linux 7.0 - Even on that, the RRDTOOL-DEVEL is nowhere to be found and after spending half a day found the rpm at REPOFORGE and installed from there and the ./configure seemed happy with it. However no matter what I do, I could not find C-ARES-DEVEL to install and the RPM I found gave constant errors. Anyhow, my question is what to do with the C-ARES error or the ARES.H errors on configure. Let them be or how can I install them properly? Also after the installation how do I configure APACHE as on other distros I could never get the XYMON page to come up because of a different www folder and each distro has its own issues. Does anybody know of a complete guide or tutorial for newbies using which I can get Xymon to work? I have followed almost 8 to 10 different Xymon articles for different distros and could not get any to work because of the versions difference and other issues. Please Help! Sam.

1 0

Graphs on dailup hosts
by r.oliver＠web.de 21 Aug '14

21 Aug '14

Dear All, if a dailup host is not online, the graphs for the downtime are white. Is it possible to clear out that white portion so that an ongoing line is shown? Monitored client systems with a low uptime just show some small dots, for example on the disk usage graph. The ongoing line in that graph should show the tracked data for the amount of uptime. E.g. the 48h disk usage graph shows the usage for the last 48h uptime and not for the real time. How can I easily accomplish this? Thanks! Regards

1 0