November 2015 - Xymon - Xymon mailman web

Best Practice Maintenance for Xymon?
by fallenhootforum＠gmail.com 23 Nov '15

23 Nov '15

Hi, I just want to thank everyone for the forum post, and keeping Xymon alive. This is a really great monitoring product. Now to my question. How does one keep the log files, history files, RRD files, and anything else stored under check? I currently only need data for the last year. So I am looking to delete it or archive it. Does anyone have scripts that they would like to share to help maintain the growing Xymon data? Thanks.

2 1

enhancement request
by stef.coene＠docum.org 21 Nov '15

21 Nov '15

Hi, Is it possible to automatically include subdirectories? So for every config file "<file>.cfg", do an include of the files in "<file>.d" Stef

4 4

"acceptonly" behavior
by john.thurston＠alaska.gov 19 Nov '15

19 Nov '15

The "acceptonly" concept has been discussed briefly here, and was tried out in 4.3.22-RC3. It's behavior wasn't as expected and it was removed again. If this tag is going to make its way back in, I think we should have a little discussion of how we'd like it to behave. Since I originally brought the subject up, I figure it's polite if I started this conversation. What would be most useful to me is a per-host tag which was also accepted on the .default. host lines. The tag would carry one or more test names. Any messages for the host for a test not named on this tag would be discarded as if they had never been received. An event would not be logged for this message. A case-insensitive string match would meet my needs. The affected host will be able to send any messages they like, but only those named in the 'acceptonly' tag will be accepted. If test results for a newly-excluded host.test combination exist, it will eventually result in a purple for that host.test, just as if the host had stopped reporting that test. If test results for a newly-excluded host.test combination do not exist, there will never be a record of them in the history and they will not appear on any report or create any alarms. How might this tag interact with some other functions; like proxy, msgcache, or pulldata? Do messages from these sources enter the flow early enough that tags in hosts.cfg can have the desired effect? -- 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

2 3

It it possible to have a test that doesn't propagate status to the xymon page?
by glauber.ribeiro＠experian.com 19 Nov '15

19 Nov '15

Hello all, I have a test that routinely turns red, and I would like to keep that, but without making the whole xymon page go red. Is this possible? Thanks, glauber --- Glauber Ribeiro Experian Automotive, Schaumburg IL Infrastructure and Information Security e: glauber.ribeiro at experian.com p: 224-698-3108 f: 224-698-5032

2 5

Client IP address change
by everett.vernon＠gmail.com 19 Nov '15

19 Nov '15

Found it. It was a new host, which I built over the weekend. I hadn't been given all the info, so I assigned a PIDOOMA IP address from a range I knew were not in use, just to get the ball rolling. It had been added to DNS by an overeager colleague who logged in on the weekend and spotted my email notifying of the new build. When I was given the correct IP address info, it was quick and easy to fix, but the DNS guy wasn't told about the change, because we all thought it wasn't in DNS yet. So it's all good. No mystery. Just a bit of confusion. Thanks for your assistance. Regards Vernon On 19 November 2015 at 14:48, Jeremy Laidman <jlaidman at rebel-it.com.au> wrote: > Vernon > > I don't believe Xymon keeps the IP address cached. It (xymonnet) asks the > system resolver every time. If you don't have testip set (or a similar > command-line option), xymonnet will always try to resolve the name, and if > it resolves then the IP in hosts.cfg is ignored. > > Although you said the server isn't in the DNS, it might be in the > /etc/hosts file, or NIS or LDAP or any other host resolution database the > Xymon server's OS is configured to use (in /etc/nsswitch.conf). > > Try running "getent hosts <hostname>" and see if it shows the IP address. > > J > On 19 Nov 2015 13:42, "Vernon Everett" <everett.vernon at gmail.com> wrote: > >> Yep, that worked. >> So where is it keeping a record of the IP address or cache of the name/IP? >> As I mentioned, I changed hosts.cfg, and restarted Xymon server. >> I would have expected that to force a reread of hosts.cfg, and cleared >> any cache of the old IP address. >> >> Thanks for you help. >> >> Regards >> Vernon >> >> >> On 18 November 2015 at 10:04, Josh Luthman <josh at imaginenetworksllc.com> >> wrote: >> >>> The default conn test is to the hostname. If it can't get DNS for it, >>> then it will try the IP. >>> >>> To skip this behavior you can do (in hosts.cfg) >>> 1.1.1.1 foo.bar.com # testip >>> >>> If the hostname doesn't have DNS you'll need to do this and of course >>> correct the IP. >>> >>> >>> Josh Luthman >>> Office: 937-552-2340 >>> Direct: 937-552-2343 >>> 1100 Wayne St >>> Suite 1337 >>> Troy, OH 45373 >>> >>> On Tue, Nov 17, 2015 at 9:01 PM, Vernon Everett < >>> everett.vernon at gmail.com> wrote: >>> >>>> Hi all >>>> >>>> Is there a "trick" to changing the IP address of a monitored Unix >>>> client? >>>> We had to change the IP address of a client a few days ago, but not the >>>> host name. >>>> In hosts.cfg, I changed the IP, but since then, the host conn is still >>>> red, and lists the old IP address. >>>> I tried restarting the Xymon server, and when that didn't help, I >>>> restarted the cache daemon - not that I was expecting that to help. (The >>>> client isn't in DNS.) >>>> The only place it can get the IP (old or new) is from hosts.cfg, and I >>>> have removed all references to the old IP from hosts.cfg. >>>> All other (client side) tests work fine, except conn, and of course ssh >>>> and rpc, which are disabled automatically, believing the host is down. >>>> >>>> Any tips appreciated. >>>> >>>> Regards >>>> Vernon >>>> >>>> >>>> >>>> -- >>>> >>>> "Accept the challenges so that you can feel the exhilaration of victory" >>>> - General George Patton >>>> >>>> "Don't find fault. Find a remedy" >>>> - Henry Ford >>>> >>>> _______________________________________________ >>>> Xymon mailing list >>>> Xymon at xymon.com >>>> http://lists.xymon.com/mailman/listinfo/xymon >>>> >>>> >>> >> >> >> -- >> >> "Accept the challenges so that you can feel the exhilaration of victory" >> - General George Patton >> >> "Don't find fault. Find a remedy" >> - Henry Ford >> >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com >> http://lists.xymon.com/mailman/listinfo/xymon >> >> -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford

1 0

Client IP address change
by everett.vernon＠gmail.com 19 Nov '15

19 Nov '15

Hi all Is there a "trick" to changing the IP address of a monitored Unix client? We had to change the IP address of a client a few days ago, but not the host name. In hosts.cfg, I changed the IP, but since then, the host conn is still red, and lists the old IP address. I tried restarting the Xymon server, and when that didn't help, I restarted the cache daemon - not that I was expecting that to help. (The client isn't in DNS.) The only place it can get the IP (old or new) is from hosts.cfg, and I have removed all references to the old IP from hosts.cfg. All other (client side) tests work fine, except conn, and of course ssh and rpc, which are disabled automatically, believing the host is down. Any tips appreciated. Regards Vernon -- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton "Don't find fault. Find a remedy" - Henry Ford

3 4

Monitored router shown as flapping
by colin.coe＠gmail.com 19 Nov '15

19 Nov '15

Hi all I have a Cisco router at a remote location which we connect to via its HSPA+ (3G/mobile data) network interface. Xymon shows this router (and the kit behind it) as flapping. I've set a ping going from the Xymon server to this router and left it going for approx 20 minutes. In this time Xymon showed it being "unreachable" however no pings were lost from the CLI. We have many routers with this setup and these other routers are not experiencing this problem. The server is running RHEL 6 + Xymon 4.3.23 RPM from Terabithia. Any ideas on this? Thanks CC

2 2

Modifying Page Titles
by Foster.Patch＠accuweather.com 18 Nov '15

18 Nov '15

Hello, I'm not sure how to go about overriding specific title pages. I am referring to the browser title at the top that is usually in the format: "green: Xymon - Status ...". I would like that to continue displaying the icon to display its status, but want to change the name to "Web Servers". Is there any way to do this? I was looking into the options for hosts.cfg and xymongen, but after testing, have been unable to make any changes to it. Thanks, Foster

2 1

Add url link to ext script
by rltexas1＠gmail.com 17 Nov '15

17 Nov '15

Good morning I created a single service report page using an ext script. It is a one page report based on another ext script that reports per host. But the requirement is to be able to click on a red icon and it link to the actual issue. Is there a way to source xymon to give me the host for the service ? Then how do I link it to an icon using the xymon&red tag. Thanks

2 1

client-local.cfg an powershell client
by lukas.kohl＠ergodirekt.de 17 Nov '15

17 Nov '15

Hello, I am a little bit confused right now, maybe you guys can help me. Right now, I have a bunch of windows Servers, which report their status via Zacks Powershell client to my Xymon Server [4.3.17]. Since the netstat Graphs are not working properly, I tweaked the code a little bit, and changed the collector OS from powershell to bbwin: was (HOST.OS CLASS): [collector:] client myserver.powershell powershell XymonPS is (HOST.OS CLASS): [collector:] client myserver.bbwin powershell XymonPS This worked, and now I can see the netstat trends. In order to get all the client logfiles, I added a new section in the client.local.cfg: [os=bbwin] eventlogswanted:*:10240:Warning,Critical,Error clientversion:2.05:http://xymonserver/psclient/ eventlog:system:10240 Unfortunately the rules won't get applied. I also tried it without the OS= prefix, which doesn't work either. Regarding the manpage it should work: https://www.xymon.com/help/manpages/man5/client-local.cfg.5.html Do you have any Idea, whats wrong here ? P.s.: If anyone is interested in the netstat Code, I can post it here. Kind regards, Lukas Kohl ERGO Direkt Versicherungen Systembetrieb 2 Karl-Martell-Straße 60 90344 Nürnberg Deutschland Tel.: +49-911-148-2857 www.ergodirekt.de Blog: http://blog.ergodirekt.de Facebook: www.facebook.com/ERGODirekt Google+: www.google.com/+ergodirekt Twitter: www.twitter.com/ERGODirekt YouTube: www.youtube.com/ERGODirekt _______________________ ERGO Direkt Lebensversicherung AG · Amtsgericht Fürth HRB 2787 · UST-ID-Nr. DE159593454 ERGO Direkt Versicherung AG · Amtsgericht Fürth HRB 2934 · UST-ID-Nr. DE159593438 ERGO Direkt Krankenversicherung AG · Amtsgericht Fürth HRB 4694 · UST-ID-Nr. DE159593446 Vorsitzender der Aufsichtsräte der ERGO Direkt Lebensversicherung AG und der ERGO Direkt Krankenversicherung AG: Dr. Clemens Muth Vorsitzender des Aufsichtsrats der ERGO Direkt Versicherung AG: Christian Diedrich Vorstände: Dr. Daniel von Borries (Vorsitzender), Ralf Hartmann, Dr. Jörg Stoffels · Sitz: Fürth Karl-Martell-Straße 60 · 90344 Nürnberg · Internet: ergodirekt.de UniCredit Bank AG - HypoVereinsbank Kto.-Nr.: 66 071 430 · BLZ 700 202 70 IBAN: DE63 7002 0270 0066 0714 30 · BIC: HYVEDEMM

2 4