October 2015 - Xymon - Xymon mailman web

HOWTO: Upgrading MAGServer Xymon installation
by steuer＠hotmail.com 30 Oct '15

30 Oct '15

Hi All - I wanted to offer my upgrade notes on how to upgrade the Xymon installation contained within the MAGServer from Squidworks (http://www.squidworks.net/software-projects/mag/) I couldn't find documentation anywhere on how to go about this, so if others are wondering how to upgrade from the 4.3.4 install of Xymon to the latest (4.3.21 as of this email) these are the steps I used: 1. Good idea to backup the VM in case anything goes wrong 2. Download Xymon package from SourceForge and use tar to extract the files 3. Review the Makefile for the 4.3.4 install that came with MAGServer. The original install of xymon version 4.3.4 files can be located at /root/xymon 4. Run the "./configure" but don't run make yet. The MAGServer package does not use many of the defaults. Make sure to use the same variables where appropriate from the old Makefile, example: XYMONTOPDIR, SECURECGIDIR, XYMONHOSTURL, etc. 5. Compare again the new Makefile to the old Makefile, making sure that variables for location paths, etc. match so that the new install will place files in the correct place. 6. Run "make" but don't run "make install" yet. 7. At this point check the directory /var/www/xymon/server. In my install there was a broken symbolic link here named "xymon" (the file had red reverse background). If it's there, remove it because it prevents the make install from working, it complains about the directory path being too deep. 8. Run make install. 9. Upgrade is complete and should be OK now. Maybe for good measure restart xymon to make sure all comes up OK after a restart. These steps worked for me, hopefully it works for others who use the MAGServer VM appliance. Rob

1 0

Upgrading Question 4.3.8 to 4.3.21
by fallenhootforum＠gmail.com 30 Oct '15

30 Oct '15

Hi everyone, I have been testing out monitoring tools, and I have really liked what Xymon can do. I have been using a the VM demo (Debian 6) Version 4.3.8. I have upgraded that to the Debian 8. I have reconfigured everything to reflect what I am looking for, but for the life of me when I try to upgrade it to 4.3.21. It never reflects on the webpage. Everything runs smooth, but would like to newest version. I am not sure if I am doing something wrong during the installation or what. I have restarted xymon, appache, server, and have reinstalled it. I guess my question is.. How do you upgrade? Do I need to turn of 4.3.8? Is it pointing to the wrong files? Is the install different? Thanks for the help.

2 1

Xymon 4.3.22-beta Release Download
by cleaver＠terabithia.org 30 Oct '15

30 Oct '15

Hello all! Xymon-4.3.22-beta has been posted to Sourceforge, containing bug fixes and a smattering of new features and improvements since 4.3.21. It's reachable at http://sourceforge.net/projects/xymon/files/Xymon/4.3.22/xymon-4.3.22-beta.… Some notable changes are at https://sourceforge.net/projects/xymon/files/Xymon/4.3.22/, while the full Changelog is at https://sourceforge.net/p/xymon/code/7707/tree/branches/4.x-master/Changes I know there are a few pending bug fixes already that I'd like to get in before the next release (multigraphs, if I can track down the source), however the number of features warrants some testing. Please let me know if you notice any issues (especially on non-Linux systems, as I don't have as much direct access to those). In particular, the changes in how xymonnet interprets 301/401/403 HTTP status codes could cause some confusion. Those who've customized their NTPDATE or TRACEROUTE command lines should check out the new Options variables. And finally, it would be helpful to have high volume environments (>60000 hosts) testing the "noflap" option for any notable performance impact. (It should be very slight.) If all goes okay, I'd like to release the final 4.3.22 some time next week. Regards, -jc

3 4

Alert repeat time not interrupted when going yellow->red
by john.r.rothlisberger＠accenture.com 30 Oct '15

30 Oct '15

I am wondering if anyone has seen this before and to be honest it doesn't happen all the time. Xymon 4.3.21 running on either Ubuntu or RHEL (happens on both). If I have a rule for a warning that has a set REPEAT interval, and that warning (yellow) goes to alert (red), the time has to expire for the yellow before the rules are applied for the red. Example: Notification.log: Tue Oct 20 00:31:09 2015 clientbox.disk (x.x.x.x) disk_warn 1445315463 100 <8 hours pass> Tue Oct 20 08:31:11 2015 clientbox.disk (x.x.x.x) disk_alert 1445344265 100 Alerts.cfg: PAGE=CLIENTPAGE COLOR=red,yellow,purple SCRIPT /home/xymon/server/ext/pg/my_alert_script disk_alert DURATION>20 REPEAT=15m COLOR=red SERVICE=disk FORMAT=TEXT UNMATCHED SCRIPT /home/xymon/server/ext/pg/my_warn_script disk_warn DURATION>30 REPEAT=8h COLOR=yellow SERVICE=disk FORMAT=TEXT UNMATCHED STOP The disk went to red at 03:10:00 but instead of sending out an immediate alert as the status changed, it waited out the full time length of the REPEAT value (8hours) and then sent the alert. I have seen this before and it drives me nuts but it doesn't happen all the time. Ideas? Thanks, John Upcoming PTO: _____________________________________________________________________ John Rothlisberger IT Strategy, Infrastructure & Security - Technology Growth Platform TGP for Business Process Outsourcing Accenture 312.693.3136 office _____________________________________________________________________ ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com

2 3

Linux client 'timediff'
by colin.coe＠gmail.com 30 Oct '15

30 Oct '15

Hi all Apologies if I'm missing the obvious but is there a Linux client equivalent to the 'timediff' test for Windows clients? I'm using the client and server RPMs from terabithia. Thanks CC

2 2

HELP
by benmchich.leila＠gmail.com 29 Oct '15

29 Oct '15

Hey, I'm a new user of Xymon,and i've faced a problem while monitoring a website that contains a frameset in the coding,and it also it redirect us to a pop up page.how can i monitor this website? Thanks for answering as soon as possible. -- Networking and telecom engineer Intern at EURAFRIC-INFORMATION.

2 1

alert using global variable instead of command configured in xymonserver.cfg
by jesse＠techknowcs.com 29 Oct '15

29 Oct '15

After upgrade to 4.3.21 the global mail variable is being used instead of the custom command configured inside of xymonserver.cfg from xymoneserver.cfg: # For the xymond_alert module MAIL="sendmail -f XYMON -s" # Command used to send an e-mail with a subject MAILC="sendmail -f XYMON " # Command used to send an e-mail with no subject from xymond_alert: xymon at zeus:/usr/local/xymon/server/bin$ ./xymond_alert --test 111-KMC454E conn 00003362 2015-10-29 08:54:14 send_alert 111-KMC454E:conn state Paging 00003362 2015-10-29 08:54:14 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 120 00003362 2015-10-29 08:54:14 Failed 'HOST=050-CannonMFP TIME=*:0600:2200' (hostname not in include list) 00003362 2015-10-29 08:54:14 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 123 00003362 2015-10-29 08:54:14 *** Match with 'HOST=* TIME=*:0600:2200' *** 00003362 2015-10-29 08:54:14 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 124 00003362 2015-10-29 08:54:14 Failed 'IGNORE HOST=Zeus' (hostname not in include list) 00003362 2015-10-29 08:54:14 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 125 00003362 2015-10-29 08:54:14 Failed 'IGNORE HOST=050-CannonMFP' (hostname not in include list) 00003362 2015-10-29 08:54:14 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 126 00003362 2015-10-29 08:54:14 *** Match with 'MAIL jesse.johnson at chl.cc REPEAT=480M RECOVERED' *** 00003362 2015-10-29 08:54:14 Mail alert with command '/var/mail/xymon "Xymon [12345] 111-KMC454E:conn CRITICAL (RED)" jesse.johnson at chl.cc' 00003362 2015-10-29 08:54:14 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 127 00003362 2015-10-29 08:54:14 *** Match with 'MAIL peter.becker at chl.cc REPEAT=480M RECOVERED' *** 00003362 2015-10-29 08:54:14 Mail alert with command '/var/mail/xymon "Xymon [12345] 111-KMC454E:conn CRITICAL (RED)" peter.becker at chl.cc' xymon at zeus:/usr/local/xymon/server/bin$ After setting Global MAIL variable manually: xymon at zeus:/usr/local/xymon/server/bin$ MAIL="sendmail -f XYMON" xymon at zeus:/usr/local/xymon/server/bin$ ./xymond_alert --test 111-KMC454E conn 00003489 2015-10-29 08:56:51 send_alert 111-KMC454E:conn state Paging 00003489 2015-10-29 08:56:51 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 120 00003489 2015-10-29 08:56:51 Failed 'HOST=050-CannonMFP TIME=*:0600:2200' (hostname not in include list) 00003489 2015-10-29 08:56:51 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 123 00003489 2015-10-29 08:56:51 *** Match with 'HOST=* TIME=*:0600:2200' *** 00003489 2015-10-29 08:56:51 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 124 00003489 2015-10-29 08:56:51 Failed 'IGNORE HOST=Zeus' (hostname not in include list) 00003489 2015-10-29 08:56:51 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 125 00003489 2015-10-29 08:56:51 Failed 'IGNORE HOST=050-CannonMFP' (hostname not in include list) 00003489 2015-10-29 08:56:51 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 126 00003489 2015-10-29 08:56:51 *** Match with 'MAIL jesse.johnson at chl.cc REPEAT=480M RECOVERED' *** 00003489 2015-10-29 08:56:51 Mail alert with command 'sendmail -f XYMON "Xymon [12345] 111-KMC454E:conn CRITICAL (RED)" jesse.johnson at chl.cc' 00003489 2015-10-29 08:56:51 Matching host:service:dgroup:page '111-KMC454E:conn:printers:111LV' against rule line 127 00003489 2015-10-29 08:56:51 *** Match with 'MAIL peter.becker at chl.cc REPEAT=480M RECOVERED' *** 00003489 2015-10-29 08:56:51 Mail alert with command 'sendmail -f XYMON "Xymon [12345] 111-KMC454E:conn CRITICAL (RED)" peter.becker at chl.cc' xymon at zeus:/usr/local/xymon/server/bin$

2 2

Xymon URL Monitor
by bjoseph＠enstage.com 28 Oct '15

28 Oct '15

From: Benedicta Joseph [mailto:benedicta.joseph at wibmo.com] Sent: 27 October 2015 11:48 To: 'xymon at xymon.com' <xymon at xymon.com> Subject: Xymon URL Monitor Hi, I have configured Xymon Server. Can anyone tell me , how to Monitor URL through Xymon? Xymon must send alert, if I'm able to open that URL. Thanks, Benedicta This message contains confidential information and is intended only for the individual named or entity to whom they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

3 2

3 issues on new build of 4.3.21 on CentOS 6
by Paul.Root＠CenturyLink.com 28 Oct '15

28 Oct '15

Hi all, I'm building the latest xymon into my own RPM, and on CentOS 6. The client works fine, but I have some issues with the server. There are a lot of variables, that may be influencing my issues. My current environment is RHEL 5 and CentOS 5. But I want to get more up to date. Building an RPM for 4.3.21 on CentOS 5 proved impossible too much work for too little benefit because of rrdtools newer versions not compiling on CentOS5 and such. Thus the move to newer OS. I'm also trying to use selinux. I'd always had it off or in permissive before, because I didn't want to deal with it. I'm making the effort now. We'll see how that goes. So sorry for the roll up. Here are the issues: 1) Disabled tests do not have the blue icon. The non-green page is showing the tests that are red or yellow. But if you click on the test, the page displays properly, blue background and the disable message is there. Also on the main pages, the icon remains red or yellow. 2) Some pages, notably on the new server, I get "Status not available" on a number of tests. They range from my own scripts to xymonnet. Other tests do work, like the client built in ones. 3) Cleared tests aren't clearing. This may well be the same issue as disable tests. I have a couple of tests that were red, but came green. But the page icon remains red. Any ideas? I've fixed the selinux messages that come up in /var/log/messages. Thanks, Paul. 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 Yellow alerts not working
by bruno＠redix.com.br 28 Oct '15

28 Oct '15

Hi, I have many alerts on my xymon working fine with the color red. I have configured some yellow color alerts, but they are not working. I check the notifications.log file and it does not show anything for yellow alerts. Im using xymon 4.3.11 Here ir my alerts.cfg file: HOST=%.* COLOR=yellow SCRIPT $ANALISADOR_BIN xxx at xxx DURATION>1m SERVICE=uptime,cpu,disk SCRIPT $ANALISADOR_BIN xxx at xxx REPEAT=1d TIME=$HORARIO_COMERCIAL DURATION>1h SERVICE=ssh,conn,disk,procs,svcs,sonicwall,zextras,zimbra,vmio,tomcat,rhds,raid,mysql,conni,bacula,apache,wb,sqlbkp,mssql,hvrepl,dhcp,dfsr,whois HOST=%.* COLOR=red SCRIPT $ANALISADOR_BIN xxx at xxx REPEAT=1d TIME=$HORARIO_COMERCIAL DURATION>6m SERVICE=bkp,fbbkp,fwcluster,netstat,ntbkp,orabkp,orastb,ssh,standby,uptime,conn,conni,disk,drbd,eth,procs,svcs,vm,kvm,mysql,raid,rdp,rhds,tomcat,bnu,sbkp,snet,mssql,hvrepl,dhcp,dfsr There is something wrong in my cfg file? Anyone has the same problem? Thanks

2 5