January 2016 - Xymon - Xymon mailman web

History not reporting correctly
by mpannucc＠ycp.edu 22 Jan '16

22 Jan '16

Hello! I was wondering if someone could help me out. When we click on "History" for our hosts, its always green. No matter what, the history is never accurate. I'm not sure where to look to fix this one. Thanks Matt -- This information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution or use of this e-mail communication by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender and delete all copies.

2 1

xymon msgs column
by Scott.Rebman＠hhsc.state.tx.us 20 Jan '16

20 Jan '16

Looking for help to set all msgs columns for windows hosts to green. The only entries in the client-local.cfg for win32 are: [win32] log:* ignore failure ignore error ignore warning This is my existing analysis.cfg file contents for CLASS=win32: ## System Level CLASSes and Defaults CLASS=win32 LOAD 80 90 # Load threholds are in % MEMPHYS 95 98 MEMSWAP 90 95 MEMACT 95 98 DISK C 90 95 # Can be harddrive or mount points DISK D 90 95 # Can be harddrive or mount points DISK E 90 95 # Can be harddrive or mount points PROC BBWin.exe 1 1 PORT STATE=LISTENING MIN=0 TRACK=Listen TEXT=Listen SVC BBWin startup=automatic status=started LOG %.system %error|warning|failure COLOR=green LOG %.security %error|warning|failure COLOR=green LOG %.* %^error|warning|failure COLOR=green Scott Allen Rebman Solaris System Administrator HHS/HHSC/Contractor TIERS Operations (512)873-6864 (CrossPark) (512) 549-0278 (Work Cell) Scott.Rebman at hhsc.state.tx.us

2 1

R: xymon 4.3.24 alerts.cfg Argument list too long
by Luca.CorsiniCSL＠esselunga.it 20 Jan '16

20 Jan '16

I solved the problem, it's the operating system stack A problem combination is an updated (linux >=2.6.23) kernel, but missing or suspect glibc support (glibc<=2.14) That applies exactly to RH6.7 My first solution is to put: * soft stack unlimited * hard stack unlimited In /etc/security/limits.conf Not the best, but works Luca -----Messaggio originale----- Da: J.C. Cleaver [mailto:cleaver at terabithia.org] Inviato: martedì 19 gennaio 2016 10:41 PM A: Corsini Luca CSL Oggetto: Re: [Xymon] xymon 4.3.24 alerts.cfg Argument list too long Hi Luca, That seems like a valid config. Can you run xymond_alert in --debug or --trace mode to see what it's sending? Although I'm not aware of a specific change around this area, what version were you coming from? Also, can you verify the whitespace on this and that the second line is indented from the first? Lastly, can you try without the 'FORMAT=SCRIPT' on the line itself? (It shouldn't make a difference in the parsing, but still.) Regards, -jc On Tue, January 19, 2016 6:17 am, Luca.CorsiniCSL at esselunga.it wrote: > Hello, > I've compiled xymon 4.3.24 from source on a redhat 6.7 64bit Now when > I setup a SCRIPT in alerts.cfg I get this error: > > 2016-01-19 15:14:49.091235 Could not launch paging script > /tmp/test_alert.sh: Argument list too long > > On another (older) installation the script works fine? What I got wrong? > Here is the entry in alerts.cfg > > HOST=firfs1.mil.esselunga.net SERVICE=ftp SCRIPT /tmp/test_alert.sh > test FORMAT=SCRIPT REPEAT=1 > > > MAIL works fine > > Thanks > > Luca > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

1 0

Create an Alert that Staggers Script Execution
by kylebassett＠gmail.com 19 Jan '16

19 Jan '16

Hi all, happy 2016 ;-) I'm trying to configure my alerts to trigger different scripts based on how long the host has been offline. I can write up something outside of xymon, but I figured someone might have a more elegant solution. If I do not specify a DURATION, xymon will trigger the multiple scripts. With a DURATION defined, xymon will only trigger the lowest specified DURATION (in the following example, the first "immediate" script). Does anyone have thoughts on how to trigger the scripts in a staggered fashion? Example hobbit-alerts.cfg HOST=apple SERVICE=conn SCRIPT alert_group1.sh 123456 REPEAT=8h RECOVERED #immediate SCRIPT alert_group2.sh 123456 REPEAT=1h DURATION>1 RECOVERED #1min SCRIPT alert_group3.sh 123456 REPEAT=1h DURATION>3 RECOVERED #3min Thanks in advance for the help, -Kyle

2 1

remote msgcache
by Paul.Root＠CenturyLink.com 19 Jan '16

19 Jan '16

Hi, My network guys are building a couple new networks that for security reasons won't be directly connected to our xymon servers. There are two machines that are just 1 network away, and the firewall allows them through. And then there are 2 networks that connects to the customers that has 1 server on it each. They talk to the first 2 servers. So my question is, do I have to put a xymon proxy on the first two machines, or could I do something weird like bring up msgcache on it, and then have the far remote machines send to the message cache? Paul Root Lead Engineer CenturyLink Network Reliability Operations Center 390 Commerce Dr Woodbury, MN 55125 Direct: (651)312-5207 Paul.Root at centurylink.com This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

2 2

xymon 4.3.24 alerts.cfg Argument list too long
by Luca.CorsiniCSL＠esselunga.it 19 Jan '16

19 Jan '16

Hello, I've compiled xymon 4.3.24 from source on a redhat 6.7 64bit Now when I setup a SCRIPT in alerts.cfg I get this error: 2016-01-19 15:14:49.091235 Could not launch paging script /tmp/test_alert.sh: Argument list too long On another (older) installation the script works fine? What I got wrong? Here is the entry in alerts.cfg HOST=firfs1.mil.esselunga.net SERVICE=ftp SCRIPT /tmp/test_alert.sh test FORMAT=SCRIPT REPEAT=1 MAIL works fine Thanks Luca

1 0

log monitoring hostname matching trouble
by EDSchminke＠Hormel.com 18 Jan '16

18 Jan '16

I think I've got this figured out. It's now behaving as expected. The root of my problem seemed to be the fact that the xymon client on the monitored system was running in "local mode". I removed the "--local" from the CMD line of the [client] block in $XYMONCLIENTHOME/etc/clientlaunch.cfg The existence of this line in my msg file was what clued me to that; this line no longer exists now that the client message. @@client#1|1|127.0.0.1|lpcobwas2p.hfc.ad|linux Once I cleared that up, I determined that when trying to match hostname in client-local.cfg, it matches based on what you have defined in hosts.cfg Server: [root at lxcobxymonp etc]# grep lpcobwas2p hosts.cfg 0.0.0.0 lpcobwas2p # CLIENT:lpcobwas2p.hfc.ad [root at lxcobxymonp etc]# sed -n '70,71 p' client-local.cfg [lpcobwas2p] log:/var/log/messages:9997 [root at lxcobxymonp etc]# Thanks everyone for your help! Erik D. Schminke | Associate Systems Programmer Hormel Foods Corporation | One Hormel Way | Austin, MN 55912 Phone: (507) 434-6817 edschminke at hormel.com | www.hormelfoods.com From: Jeremy Laidman <jlaidman at rebel-it.com.au> To: EDSchminke at hormel.com Date: 01/12/2016 08:03 PM Subject: Re: [Xymon] log monitoring hostname matching trouble Erik Hmm. It's hard to know what might be wrong. First, note that it can take some time (10 minutes maybe) for the cfg file to appear. Check your ~xymon/client/tmp/ directory and ensure that the xymon user can write there (probably should have owner and group both as "xymon"). Then, see if you have a client message temp file there with something like ls -l ~xymon/client/tmp/msg.*.txt This should show the hostname that the Xymon client is using, as part of the filename. It will also show the permissions, which should make the file writeable by the xymon user. Also, check the first line of the file (eg: head -1 ~xymon/client/tmp/msg.*.txt) and see if the hostname listed there is what you're expecting. Try sending the msg.*.txt file via the xymon client message, and see if you get the cfg file as output: $ ~xymon/client/bin/xymoncmd $ $XYMON $XYMSRV @ < $XYMONTMP/msg.*.txt $ exit Or even just: $ ~xymon/client/bin/xymoncmd $ echo "client $MACHINE.linux linux" | $XYMON $XYMSRV @ (Substitute "linux" for your OS.) Cheers Jeremy On Sat, Jan 9, 2016 at 3:10 AM <EDSchminke at hormel.com> wrote: Hello, I'm trying to get log monitoring to work on a new implementation of Xymon (v4.3.24) For whatever reason, my client doesn't seem to be receiving a logfetch.cfg file from the server after it checks in. I've tried a number of combinations of hostname and none of them seem to work: [lpcobwas2p] (hostname only) [lpcobwas2p.hfc.ad] (FQDN, periods) [lpcobwas2p,hfc,ad] (FQDN, commas) None of them seem to work. Any ideas? Server side: [root at lxcobxymonp server]# pwd /home/xymon/server [root at lxcobxymonp server]# hostname lxcobxymonp.hfc.ad [root at lxcobxymonp server]# [root at lxcobxymonp server]# tail -2 etc/client-local.cfg [lpcobwas2p] log:/var/log/messages:20480 [root at lxcobxymonp server]# [root at lxcobxymonp server]# grep lpcobwas2p etc/hosts.cfg 0.0.0.0 lpcobwas2p # CLIENT:lpcobwas2p.hfc.ad [root at lxcobxymonp server]# Client side: [root at lpcobwas2p client]# pwd /home/xymon/client [root at lpcobwas2p client]# hostname lpcobwas2p.hfc.ad [root at lpcobwas2p client]# [root at lpcobwas2p client]# head -2 tmp/msg.lpcobwas2p.hfc.ad.txt @@client#1|1|127.0.0.1|lpcobwas2p.hfc.ad|linux client lpcobwas2p,hfc,ad.linux linux [root at lpcobwas2p client]# Erik D. Schminke | Associate Systems Programmer Hormel Foods Corporation | One Hormel Way | Austin, MN 55912 Phone: (507) 434-6817 edschminke at hormel.com | www.hormelfoods.com _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

1 0

Xymon 4.4
by magdi.mahmoud＠easynet.com 16 Jan '16

16 Jan '16

Please when the 4.4 ver. Will be released Regards Magdi M. UK Hosting Systems Engineer [Description: cid:image003.png at 01D117C1.8700AB30]<http://www.easynet.com/> A. Chancellor House, 5 Thomas More Square, London, E1W 1YW T. +44 (0) 20 7032 5173 M. +44 (0) 77500814000 This email and any attachments may be confidential and/or legally privileged. If you have received this e-mail and you are not a named addressee, please inform the sender of this email by sending a return email to the address above and then delete the e-mail and your response from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this e-mail. Any views or opinions presented are solely those of the author. Any statements made, or intentions expressed in this communication may not necessarily reflect the view of Easynet. No content herein will bind Easynet or any associated company unless confirmed by the execution of a formal contract by Easynet. Any figures or amounts given in this email are quotations only and are subject to change. Although Easynet routinely screen for viruses, addressees should scan this e-mail and any attachments for viruses. Easynet make no representation or warranty as to the absence of viruses in this e-mail or any attachments. Please note that to ensure regulatory compliance and for the protection of our customers and business, we may monitor and read e-mails sent to and from our server(s). Easynet Limited (registered number 02954343) and Easynet Global Services Limited (registered number 08458875) are incorporated in England and Wales and share the same registered office at St. James House, Oldbury, Bracknell, Berkshire, RG12 8TH

2 1

"Valid Until" column for the "Acknowledgements" report
by Dominique.Frise＠unil.ch 16 Jan '16

16 Jan '16

Hi, First of all thanks to Andy Smith for providing the very useful "Acknowledgements" report ! Our sysadmins are often mistyping the "Duration" (e.g. mins instead of days) when using the "Acknowledge Alert" page. The host/service is then shown unacked sooner than expected. The only way to show what was entered for "Duration" is to look into the acknowledge.log file. The attached patch for ./lib/acknowledgementslog.c adds a "Valid Until" column to the "Acknowledgements" report. This was tested on Xymon 4.3.24 Dominique Frise? - UNIL

2 1

Temperature plugin for xymon
by Foster.Patch＠accuweather.com 14 Jan '16

14 Jan '16

Hello, I’ve been browsing the internet for a plugin/extension that will monitor server temperature and alarm if it gets too high. I have been unsuccessful, mostly because the links I find lead to dead pages. I was wondering if there was anyone here who has used on of these and can recommend a reliable download. Thank you! -Foster Patch

3 2