February 2017 - Xymon - Xymon mailman web

Limiting repeated messages
by erik＠schminke.us 16 Feb '17

16 Feb '17

Using what you'd provided, here's what I'd put in your alerts.cfg HOST=NMSRep SERVICE=LogMasterErr,NMSRepScheduler,NMSRepTask,RepDisc_Issues COLOR=red,yellow,purple RECOVERED SCRIPT /usr/local/scripts/html_mail.pl $NG-NMSRep-DEV DURATION>7d DURATION<14d REPEAT=1d I moved the duration rules down to the "SCRIPT" line. I also added a 2nd duration rule to demonstrate you could time box this. The script will fire once per day for 7 days, after 7 days.

3 2

java heap plugin
by velpulavenkat6＠gmail.com 16 Feb '17

16 Feb '17

Hi, Hope you are doing well Can some one help me how to add java heap memory plugin in xymon server. Regards Venkat Yadav 9704871816

1 0

critical systems page-- a couple feature requests
by erik＠schminke.us 16 Feb '17

16 Feb '17

1) Would it be possible change the critical systems page to allow the /colors displayed/ on the page to be more of a checkbox style selection? one with each color available to select? i would really like to present just red+purple on my critical systems page to my NOC operators. i see purple as being a greater severity than yellow, and (depending on) possibly more severe than red. Reason: I've seen a number of times in AIX, where an application has managed to over consume system resources, so the OS kills off processes to protect itself. The xymon client often gets caught up in that and stops reporting in. Meanwhile, we're running without, e.g., the procs test to determine whether our core processes are still running. A purple alert on that page would prompt them to call us, but if only red is displayed, the test will probably remain silent and unnoticed. We also don't want them contacting us for yellow alerts, as those are not necessarily fatal to business operations. 2) An increase in granularity would be helpful as well. By that I mean, allow xymon admins to add more than one config for a hostname.testname. I would find it useful to be able to configure for hostname.testname.status.timespec. Also, allow for multiple configurations, each with their own priority, resolver group, and instructions. Reason: As an admin, I would want to monitor PRIO 1+2+3 and only have my NOC monitor for PRIO 1 during the day. But then at night, have them monitor for PRIO 1+2+3 at night, but would also like change what a test's priority becomes. I might have them follow different instructions or contact a different group based on time. Thanks, Erik

1 0

Monitoring nginx
by chrisp＠lightstoneauto.co.za 16 Feb '17

16 Feb '17

Good day All a could find on the interwebs that could help me to monitor nginx was https://github.com/ZeWaren/xymon-nginx and http://lists.xymon.com/archive/2011-March/031188.html I followed the xymon-nginx.pl guide to the tee, but the graphs do not display, the rrd data is generated and I can view the rrd data with the rrdtool. What is the suggested method to monitor nginx and track performance data. Kind regards [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/AUTOlogoW.png] Chris Pretorius [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/phone.png] 0872367740 [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/email.png] chrisp at lightstone.co.za<mailto:chrisp at lightstone.co.za> [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/web.png] www.signio.co.za<http://www.signio.co.za> [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/address.png] Centurion Square, 3rd Floor, cnr Heuwel and Gordon Hood rd, Centurion This communication is subject to Lightstone's email disclaimer<http://www.lightstone.co.za/portal/content/email-disclaimer.aspx>

1 1

another xymonnet error that maybe shouldn't be an error?
by rlhamil2＠gmail.com 16 Feb '17

16 Feb '17

Error output: xymonnet: Cannot resolve IP for host lapple.local with a hosts.cfg entry of 0.0.0.0 lapple.local # NAME:lapple CLIENT:lapple.pri dialup noflap=location ssh ntp rpc=mountd,nlockmgr,nfs,rpcbind,rquotad,status,ypbind NOCOLUMNS:files multihomed NOPROPPURPLE:+location NOPROPYELLOW:+location "lapple" - the laptop - may report as "lapple.pri" at home, but either at home or connected in via VPN*, may be known as "lapple.local". The .local domain is multicast DNS (aka Bonjour), which is dynamic - the name itself is advertised by the host in question, and only resolves when the host is on the local network (even the VPN case took some interesting trickery, since the VPN is layer 3, and a VPN client doesn't have its own MAC address). In other words, in the case of 0.0.0.0 together with dialup, should it really be an error if the name can't be looked up? There's cases it could happen without anything untoward being involved...and I don't see any better way to configure an intermittent mobile client with potentially varying IP address, than how I did it.

1 0

xymondxboard xml error
by andrew.bezold＠siemens.com 15 Feb '17

15 Feb '17

I think I've found a bug. When using the "xymondxboard" command, I get an xml of everything I'm tracking. However, some of those alerts are disabled indefinitely. When the xml of those alerts is created, some of the tags are missing or incomplete. Specifically, the DisableTime tag is missing an end tag, the Sender tag is missing altogether, and the newline that should come before the Cookie tag is not there. These errors make the entire xml unparseable. I'm currently using Xymon Version 4.3.17, but looking at the readme the issue doesn't appear to be fixed in the updated versions. Someone correct me if I'm wrong, because if I just have to update I can do that. Bad XML Part: <ServerStatus> <ServerName>hostname</ServerName> <Type>testtype</Type> <Status>blue</Status> <TestFlags> </TestFlags> <LastChange>Wed Jan 25 09:12:39 2017</LastChange> <LogTime>Wed Feb 15 19:40:50 2017</LogTime> <ValidTime>Tue Jan 19 03:14:07 2038</ValidTime> <AckTime>N/A</AckTime> <DisableTime> <Cookie>N/A</Cookie> <MessageSummary><!deleted for privacy></MessageSummary> </ServerStatus> Good XML Part: <ServerStatus> <ServerName>hostname</ServerName> <Type>testtype</Type> <Status>blue</Status> <TestFlags> </TestFlags> <LastChange>Fri Mar 25 12:02:39 2016</LastChange> <LogTime>Wed Feb 15 19:40:50 2017</LogTime> <ValidTime>Thu Feb 10 17:53:00 2022</ValidTime> <AckTime>N/A</AckTime> <DisableTime>Thu Feb 10 17:53:00 2022</DisableTime> <Sender>127.0.0.1</Sender> <Cookie>N/A</Cookie> <MessageSummary><!deleted for privacy></MessageSummary> </ServerStatus> This message and any attachments are solely for the use of intended recipients. The information contained herein may include trade secrets, protected health or personal information, privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you are not an intended recipient, you are hereby notified that you received this email in error, and that any review, dissemination, distribution or copying of this email and any attachment is strictly prohibited. If you have received this email in error, please contact the sender and delete the message and any attachment from your system. Thank you for your cooperation

1 0

xymonnet column missing
by kspringer＠innovateteam.com 15 Feb '17

15 Feb '17

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20170215/c5ce6f94/attach…>

2 1

OpenBSD Compile Issue with logfetch
by matt1299＠gmail.com 15 Feb '17

15 Feb '17

Hello all, Not sure if anyone else has come across this or not, but I'm running into an issue compiling the latest Xymon client (4.3.28) on OpenBSD 6.0. I'm just compiling the client, since that's all I need for OpenBSD. So, I am first running: MAKE=gmake ./configure.client I just selected all the defaults for the prompts for this example. Then, when running 'gmake', I am getting a compile error when it gets to the logfetch part: ... gcc -g -O2 -Wall -Wno-unused -Wno-pointer-sign -D_REENTRANT -I/usr/local/include -L/usr/local/lib -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DBSD -I/root/xymon-4.3.28/include -DCLIENTONLY=1 -o logfetch logfetch.c ../lib/libxymonclient.a logfetch.c: In function 'logdata': logfetch.c:210: error: 'intmax_t' undeclared (first use in this function) logfetch.c:210: error: (Each undeclared identifier is reported only once logfetch.c:210: error: for each function it appears in.) logfetch.c:210: error: expected ')' before 'bufsz' gmake[1]: *** [Makefile:41: logfetch] Error 1 gmake[1]: Leaving directory '/root/xymon-4.3.28/client' gmake: *** [build/Makefile.rules:77: client] Error 2 (If anyone wants the full 'gmake' output, let me know!) If I go and comment out all the lines with logfetch in them in client/Makefile, then everything compiles successfully and I can even do a 'gmake install' and everything works just fine (but only after commenting out the logfetch lines in $XYMONHOME/bin/xymonclient.sh). Honestly, this works fine for my case since I don't really need any logfetch functionality working for this particular client anyways. But it'd be nice if I didn't have to do all this commenting every time I want to compile a new version of the Xymon client on OpenBSD. Has anyone run into this issue and/or know what needs to be done to resolve it? Thanks in advance for any assistance!! -- Matt Vander Werf

2 3

TCP Connection Issues?
by skadz＠skadz.com 15 Feb '17

15 Feb '17

So, we were able to figure this out on our own. The fix was to add "--concurrency=25" to the xymonnet test and everything got much much better. Skadz On Mon, Jan 30, 2017 at 5:06 PM, Ryan Skadberg <skadz at skadz.com> wrote: > Anyone ever seen this? > > I have a few hundred servers in my xymon setup and have about 200 http > checks, as well as some other server side scripts that check things via > tcp. Recently all of my http and telnet connections will start to flap for > 5-10 mins and cause all/most of my http and telnet checks to go red. I > added a delayred to stop the paging, but I am still getting a wonderful > Christmas tree a few times a day, just yellow now. > > It feels like an issue with the number of file handles or maybe the number > of tcp connections, but I can't seem to get the right formula to fix it > up. Anyone have any suggestions? > > Skadz > > PS - Running 4.3.17. Haven't had a time to upgrade in a while (and had > some issues with some of the web changes last time I tried) > >

1 0

MacBook client
by kspringer＠innovateteam.com 15 Feb '17

15 Feb '17

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20170210/757235a8/attach…>

3 3