February 2013 - Xymon - Xymon mailman web

how integrate xymonpdf into new xymon-menue
by martin.flemming＠desy.de 14 Jul '13

14 Jul '13

Hi ! I need an hint how to integrate the xymonpdf http://www.trantor.org/xymonton/doku.php/reports:xymonpdf or other entries into the new xymon-menue .. ... > * Edit '$BBHOME/server/www/menu/menu_items.js' and add two lines in > 'Reports' section like those ones (I put my scripts into $BBHOME/server/www/pdf) : > > ['Analysis PDF', '/xymon/pdf/analysis.php'], > ['Reports PDF', '/xymon/pdf/pdf.php'] didn't work ... because the menue_items.js is missing :-) i've added an entry in xymonmenu.cfg <a class="inner" href="$BBSERVERWWWURL/pdf/pdf.php">PDF Report</a> but without success :-( thanks & cheers Martin

5 9

Problem with NOTICE rule in alerts.cfg
by waa-hobbitml＠revpol.com 24 May '13

24 May '13

I noticed that the xymon_alerts docs show there is a NOTICE keyword which is described as: NOTICE Rule matches if the message is a "notify" message. This type of message is sent when a host or test is disabled or enabled. I wanted to be alerted via a custom SMS script of any test as soon as it is enabled or disabled. So in the alerts.cfg file I had initially set up a line that I thought would trigger whenever a test was enabled or disabled like so: HOST=* SCRIPT $xymon-sms-alert $waaphone TIME=$smsalerthours FORMAT=SMS NOTICE As I was testing enabling and disabling, it appeared that I had gotten the syntax correct and I was off to the next thing. However, when a normal test went yellow, I received two SMS alerts for it. My logs shows that the CFID environment variable was showing that my new alert listed above was triggering the SMS as well as the PAGE=%firewalls/* alert that was supposed to trigger it. I then tried NOTICE SCRIPT $xymon-sms-alert $waaphone TIME=$smsalerthours FORMAT=SMS as well as NOTICE=* SCRIPT $xymon-sms-alert $waaphone TIME=$smsalerthours FORMAT=SMS and finally HOST=* NOTICE SCRIPT $xymon-sms-alert $waaphone TIME=$smsalerthours FORMAT=SMS But it seems that ANY status change including normal green, yellow, red, purple triggers this alert as well as any other correctly matching alert. I did some additional testing with all three above configurations using: xymond_alert --test fw.example.com testname And each of them showed (in order): *** Match with 'HOST=*' *** *** Match with 'SCRIPT $xymon-sms-alert $waaphone TIME=$smsalerthours FORMAT=SMS NOTICE' *** *** Match with 'NOTICE' *** *** Match with 'SCRIPT $xymon-sms-alert $waaphone TIME=$smsalerthours FORMAT=SMS' *** *** Match with 'NOTICE=*' *** *** Match with 'SCRIPT $xymon-sms-alert $waaphone TIME=$smsalerthours FORMAT=SMS' *** *** Match with 'HOST=* NOTICE' *** *** Match with 'SCRIPT $xymon-sms-alert $waaphone TIME=$smsalerthours FORMAT=SMS' *** Would love to get this working correctly and appreciate any help! -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/

2 2

Duplicate email Recipients in Info page
by Don.Kuhlman＠schawk.com 10 May '13

10 May '13

Does that mean it will stay green for a half hour before going red if the service has stopped ? Thanks! On 6/6/12 12:35 PM, "Betsy Schwartz" <betsy.schwartz at gmail.com> wrote: >On Wed, Jun 6, 2012 at 1:28 PM, Don Kuhlman <Don.Kuhlman at schawk.com> >wrote: > >> I've been working on the email issue and now seem to have another >>issue. I >> shut down the bbwin service on two windows computers that xymon was >> monitoring and it's not alerting that the service and/or process has >> stopped. > >Default purple interval , aka "status lifetime" is half an hour... I >think it's hardcoded on the server side. > >Individual alerts can also set their lifetimes. We do that with some >of our custom tests, run them every half hour with a lifetime of a >couple of hours. >

5 7

xymon e-mail alerts show up as attachments instead of e-mail
by icepickjazz＠gmail.com 29 Mar '13

29 Mar '13

Not a wild thought. Yes you are correct. I was getting ready to post my findings. We recently moved our xymon server from fedora core 3 to SLES 11. Fedora used mail and SLES 11 mail is linked to mailx. The windows clients are sending carriage returns in the status ^M (carriage return). The problem occured on SuSe server but not on redhat server, because mailx expects input text to be in Unix format, with lines separated by *newline*(^J, \n) characters only. Non-Unix text files that use *carriage return* (^M, \r) characters in addition will be treated as binary data. Hence the reason we get notifications that show up as attachments. Also explains why AIX servers don't have the problem and the windows servers do. Thanks On Mon, Sep 19, 2011 at 9:36 PM, Scott Pfister <icepickjazz at gmail.com>wrote: > Not a wild thought. Yes you are correct. I was getting ready to post my > findings. We recently moved our xymon server from fedora core 3 to SLES > 11. Fedora used mail and SLES 11 mail is linked to mailx. The windows > clients are sending carriage returns in the status ^M (carriage return). > The problem occured on SuSe server but not on redhat server, because mailx > expects input text to be in Unix format, with lines separated by *newline*(^J, \n) characters only. Non-Unix text files that use > *carriage return* (^M, \r) characters in addition will be treated as > binary data. Hence the reason we get notifications that show up as > attachments. Also explains why AIX servers don't have the problem and the > windows servers do. > > Thanks > > > On Mon, Sep 19, 2011 at 8:08 PM, Ralph Mitchell <ralphmitchell at gmail.com>wrote: > >> Wild thought - could the Windows reports be turned into attachments in >> your email server and/or client because the line-ends are <cr><lf> instead >> of just <lf> ?? >> >> Ralph Mitchell >> >> >> On Mon, Sep 19, 2011 at 6:06 PM, Scott Pfister <icepickjazz at gmail.com>wrote: >> >>> Good day, >>> >>> We are running xymon 4.2.3 and are experiencing some particularities with >>> e-mail alerts showing up as attachments like att00001.bin instead of the >>> normal message. The problem is sporadic. For example windows server throws >>> CPU alter. E-mail sent shows up as an attachment in the recipient e-mail. >>> AIX servers throw cpu alerts don't experience this problem. Client >>> shouldn't matter. Any tips for troubleshooting this issue? If we open the >>> attachment in the editor it shows what should be in the body of the email. >>> Hobbit server is running postfix. >>> >>> red Mon Sep 19 15:07:50 EDT 2011 [indyctx8.companyname.com] up: 10:12, 1 >>> users, 224 procs, load=100%, PhysicalMem: 3072MB(74%) >>> >>> >>> >>> Memory Statistics >>> Total Physical memory: 3220598784 bytes (3.00GB) >>> Available Physical memory: 850558976 bytes (812.00MB) >>> Total PageFile size: 4294967295 bytes (4.00GB) >>> Available PageFile size: 4294967295 bytes (4.00GB) >>> Total Virtual memory size: 2147352576 bytes (2.00GB) >>> Available Virtual memory size: 2106589184 bytes (1.96GB) >>> >>> Most active processes >>> 96.23% oexplore (0x26a4 [9892]) >>> 00.60% svchost (0xbf0 [3056]) >>> 00.32% lsass (0x23c [572]) >>> 00.26% oexplore (0x29c8 [10696]) >>> 00.25% oexplore (0x255c [9564]) >>> 00.21% Smc (0x3c4 [964]) >>> 00.20% SmcGui (0x3230 [12848]) >>> 00.19% oexplore (0x20dc [8412]) >>> 00.16% oexplore (0x14d0 [5328]) >>> 00.13% XTE (0xfc4 [4036]) >>> >>> See >>> http://hobbit.companyname.docm/hobbit-cgi/bb-hostsvc.sh?HOST=indyctx8&SERVI… >>> >>> >>> thanks, >>> >>> Scott >>> >>> >>> >>> _______________________________________________ >>> Xymon mailing list >>> Xymon at xymon.com >>> http://lists.xymon.com/mailman/listinfo/xymon >>> >>> >> >

3 2

XyMon client binaries default security is bad
by a.chervonets＠cominder.eu 08 Mar '13

08 Mar '13

upgraded XyMon (clinet) to 4.3.10 (the same was at least in 4.3.5) and notices all files in bin can read and execute privileges to everyone: ls -l client/bin/ total 1840 -rwxr-xr-x 1 xymon monitor 161079 Feb 28 21:08 clientupdate -rwxr-xr-x 1 xymon monitor 200250 Feb 28 21:08 logfetch -rwxr-xr-x 1 xymon monitor 151256 Feb 28 21:08 msgcache -rwxr-xr-x 1 xymon monitor 153905 Feb 28 21:08 orcaxymon -rwxr-xr-x 1 xymon monitor 156173 Feb 28 21:08 xymon -rwxr-xr-x 1 xymon monitor 133445 Feb 28 21:08 xymoncfg .... I suppose it depends on umask setting during installation, but I would be more happy if installation process setup more secured configuration regardless of default settings. At least: -rwxr-x---

10 19

Problem with netapp.pl
by linuxmasterjedi＠free.fr 08 Mar '13

08 Mar '13

Hi, I've just contacted "Francesco Duranti" who maintain some plugins for BEA/Netapp and DB [1] At the same time, I would to know if someone could be interested by implementing a new feature in this perl code ? On the netapp.ini file, we can add exception for Disk (D) warning/panic level, Inode (I) warning/panic level, Snapshot (S) warning/panic level but we can add exceptions to Quota. I'm looking for someone who could duplicate/tweak a couple of perl code lines to add this Quota exception feature. Contact me for extra information, thanks ! [1] : http://sourceforge.net/projects/hobbit-perl-cl/

1 1

Feature Request ~ logfetch
by Michael.Beatty＠sherwin.com 06 Mar '13

06 Mar '13

I see the comments made in logfetch.c /* Is it ok for these to be hardcoded ? */ #define MAXCHECK 102400 /* When starting, dont look at more than 100 KB of data */ #define MAXMINUTES 30 #define POSCOUNT ((MAXMINUTES / 5) + 1) #define LINES_AROUND_TRIGGER 5 My answer to this would be, "no". Due to various reasons, it is not desirable to run my client more than once every hour. Therefore, the msgs check for log files is almost useless unless I change these values (and honestly, I'm not even sure that would work as I haven't seen if this would impact anything else). If I ran my client every hour, I would lose 50% of my log data. I would like to see where the log check would be dependent on how long of an interval your client is run as opposed to a hard coded 30 minutes. -- Michael Beatty

4 3

[Newbie] Understanding client-server configuration (terabithia's rpm 4.3.10-1.fc17)
by a_s_y＠sama.ru 06 Mar '13

06 Mar '13

Hello. I attempt to setup xymon from terabithia's packages (rebuilded 4.3.10-1.fc17.src.rpm with small changes for ALT Linux) Xymon's server works and ready for receive data from clients I think: tcp 0 0 0.0.0.0:1984 0.0.0.0:* LISTEN 3557/xymond Web pages generated correctly. All server's tests works. Now I attempt to setup client. So, 3 questions. 1. I need to make some network's tests on client and transfer results to server. Should I setup client installation or server installation in this case ? 2. I found a bug in packages. xymon and xymon-client packages contains /usr/libexec/xymon-client/xymonclient.sh with code: Is this script need always ? if test "$LOCALMODE" = "yes"; then echo "@@" >> $MSGTMPFILE /usr/libexec/xymon-client/xymond_client --local <$MSGTMPFILE else xymond_client exist in xymon package only and by another path: /usr/libexec/xymon/xymond_client Is this script need always ? Could this be the cause of problems in the client ? 3. About package. xymon package contains xymonclient-*.sh for non linux. All this removed from xymon-client. Are they forgotten in xymon package or they needed ? -- Regards, Sergey

3 9

filesystem check with multiple disk monitors
by bakgat8＠hotmail.com 01 Mar '13

01 Mar '13

Howdy I am a user from bigbrother days. In bigbrother I cloned/customized the filesystem check script to allow me to have more than one disk column. I usually had columns for disk_sys (OS) , disk_dba (dbase) and disk_app (application). This allowed me to wake the other people (app/dba) when it was their disk problem, a problem I was not going to touch anyway. In BB the script ran on the remote/client machine. Now here in xymon I see disk is part of the data pulled for each client and parsed on the server. I can (and have) written a test to run on the client and send the status back up to xymon - the old BB way. I was wondering if there was enough interest in above functionality for me to make the effort to include it in the server side parse code. I have already looked into this and got a not-pretty-code version working with this expended config in analysis the FST (three chars) is appended to disk so below config will give extra columns disk_dba disk_ard in addition to just disk. You can make as many extras as you want. Just disk got everything not put anywhere else ... being paranoid about losing newly added filesystems, there must be a 'everything else' column. HOST=dbasserverone DISK %^/ip|du|vd|hq|sp|st|hd|iq|dc|id|ht|dt|hp|dd|dq... FST=dba 100 101 DISK %^/[a-z][a-z][0-9][0-9][0-9] FST=dba 100 101 DISK %^/dp... FST=dba 93 95 DISK %^/redo..|arc.. FST=ard 90 95 In the screenshot the entries with disk_sys is actually the clients running the old BB way. "Everything else" is in disk_sys. For these I could hide the disk column, which is the column/monitor that the server is generating. I just did not do the hide step. This is a test setup, we are evaluating moving to Xymon. I found no commercial product that can do multiple filesystem checks the way I want, but I could make Xymon do it. Yeah open source! -- Bakkies

2 3

Fw: negative values for HeapMemoryUsage (jmxstat.sh)
by marco.avvisano＠regione.toscana.it 27 Feb '13

27 Feb '13

Try to send to the list.. Someone have similar problems using this script ? regards Marco Il 21/02/2013 10.56, Marco Avvisano ha scritto: > Hi Andy, > > i have a problem using your script after i increase memory for one > jboss istance. > I add another 1.5g of memory (3g total). The problem is the negative > number for HeapMemoryUsage. > The script get right values from bean. The problem is when it > trasform these value in kb. > There some debug:on committed value: > > the code : > regexp > {^.*committed=([0-9]*),.*init=([0-9]*),.*max=([0-9]*),.*used=([0-9]*)} > $d -> committed init max used > > > ^HeapMemoryUsage$ { > regexp > {^.*committed=([0-9]*),.*init=([0-9]*),.*max=([0-9]*),.*used=([0-9]*)} > $d -> committed init max used > debug_print "$d" > debug_print "VALORE COMMITTED1 $committed" > append composite $a "Committed" > debug_print "VALORE COMMITTED3 $committed" > set committed [expr $committed/1024] > debug_print "VALORE COMMITTED3 $committed" > debug_print "got $composite=$committed" > > > The output: > > DBG: VALORE COMMITTED1 2438594560 > DBG: VALORE COMMITTED3 2438594560 > DBG: VALORE COMMITTED3 -1812864 > > Seems that tcl could have some problems working on "big" values. > You have the similar problems ? > > best regards, > > Marco > >

1 0