April 2015 - Xymon - Xymon mailman web

SPLITNCV and graphs
by solitaryr＠gmail.com 22 Apr '15

22 Apr '15

I'm trying to add a new graph to a test using NCV (SPLITNCV actually). I read through the graphing tips, I read several emails that provided hints (not my exact problem but nudged me the right way)... long story short. I finally got he graph to show up on my test page...but the rrd file doesn't seem to be populating the fields as expected when I run "rrdtool dump". The only thing I can figure is that the test I'm performing doesn't run every 5 minutes but every 15 minutes. Does that matter? I would have expected in the worst case that only every 3rd row would have a value. What am I missing here? Note, I dropped my test to run every 5 minutes to see if this theory is true. As a side note, it would be extremely helpful if the NCV component didn't look at the entire status but required a comment block (for example) to contain it. That way you could keep your data stream isolated from your message. For example:  My test kept creating an rrd file for a date string that was part of the status message. That's a bit annoying. =G=

9 12

*nix servers are not emailing alerts
by mpannucc＠ycp.edu 22 Apr '15

22 Apr '15

Hello I currently took over xymon administration in our institution. We currently receive alerts for all of our Windows servers for just about any condition. However, *nix servers seem to be very reserved in what they sound out...if they send anything at all. I have tried to locate where I should be specifying that I would like the *nix servers to send alerts like the Windows serves do but have no had much luck. One thing In particular I would like to receive emails about is when the disk is reaching its threshold. If I log into the web interface I can see the live status...just no emails every go out, and everything looks to be setup correctly. If there are some things I should be looking at, any help would be great. Thank you 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

logstash output for xymon
by wbeauchaine＠katei.net 18 Apr '15

18 Apr '15

Hi sorry for the delay, the logstash team never answered me when i sent this email i using this output in my production. Currently unfortunately i doesn't use xymon but i think this output works fine. Regards, Wilfrid Le 2015-03-31 17:24, Peter Welter a écrit : > It has been some time, I know, but since I do not see any follow up with either http://logstash.net [1]of the xymon list I ask this question. > > Has there been any progress in adopting your xymon/logstash-script part into the repository by the community? > Does your adaptation still work just fine? > We are in the midst of deploying the ELK-stack and we are using Xymon, so I am very curious. > > Thanks Peter > > http://peterwelterplatz.blogspot.com/ [2] > > 2012-06-03 20:48 GMT+02:00 wbeauchaine <wbeauchaine at katei.net>: > Hello, > > i have sent email to logstash team but no response ... > > Regards, > Wilfrid > > Le 2012-06-01 20:57, Michael Baydoun a écrit : > Would love to see this added as an output to logstash > > On Wed, May 30, 2012 at 9:18 AM, Wilfrid Beauchaine > <wbeauchaine at katei.net [5]> wrote: > > Hello > > i use http://www.logstash.net [3] [1] and xymon so i adapted the > logstash output zabbix for xymon: > > http://pastebin.com/UQBJF7m7 [4] [2] > > Actually i have not contacted logstash team to add this output. > So if you want use this you need to copy this code to > logstash/outputs/xymon.rb. > Execute jar -uf logstash-1.1.0.1-monolithic.jar > logstash/outputs/xymon.rb to add this on jar file > > i have only test this on linux > > if you have any question please contact me by email > > Regards, > Wilfrid > > _______________________________________________ > Xymon mailing list > Xymon at xymon.com [3] > http://lists.xymon.com/mailman/listinfo/xymon [5] [4] > > Links: > ------ > [1] http://www.logstash.net [3] > [2] http://pastebin.com/UQBJF7m7 [4] > [3] mailto:Xymon at xymon.com > [4] http://lists.xymon.com/mailman/listinfo/xymon [5] > [5] mailto:wbeauchaine at katei.net _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon [5] Links: ------ [1] http://logstash.net [2] http://peterwelterplatz.blogspot.com/ [3] http://www.logstash.net [4] http://pastebin.com/UQBJF7m7 [5] http://lists.xymon.com/mailman/listinfo/xymon

2 1

Any way to do http tests with HEAD request?
by landrew＠pnnl.gov 17 Apr '15

17 Apr '15

I've been converting from running an installation of BigBrother professional to Xymon (4.3.18), and I've had some complaints that the HTTP test is impacting a few of our servers (lots of back-end database requests and calculations for a generated page that is being tested for availability.) I didn't understand why nobody was complaining previously, until I saw that BigBro was set up to use the "curl" command with the "-I" option (aka the "--head" option) to send a "HEAD" request to the server. The BigBro web test used this setting: .... hawkeye{root}169: grep curl etc/bbdef-server.sh # OR USE curl, WHICH IS BETTER... LYNX="/usr/bin/curl -g -s -S -m 45 -I -k --connect-timeout 15 --user-agent 'Mozilla/5.0' " hawkeye{root}170: .... Is there some equivalent ability in Xymon to just issue a "HEAD" request when testing http and https services? I expected I'd find an equivalent option for use in the hosts.cfg file in Xymon, but haven't been able to find it if it's there. Any ideas on how to -Andrew

5 8

Bug in msgs test in 4.3.19
by johan.sjoberg＠deltait.se 16 Apr '15

16 Apr '15

Hi. I upgraded our Xymon server to 4.3.19. Unfortunately, I experienced problems with the msgs test for the Xymon server itself. The most serious bug is that I am getting log rows associated with the wrong log file, and triggering alerts for that file. If I look in the client data, I can see that a few lines are from the correct file, but then it switches over to another log file's content: [msgs:/var/log/server01.log] <...SKIPPED...> Apr 16 15:53:32 server01 AppMailImporter[INFO]: KTRO2155 Successfully made deed avaliable to registrator group propID = 10029300 Apr 16 15:54:38 server01 AppMailImporter[INFO]: KESK2216 Email did not have a body or contains crap from scanners only. Not creating deed, but for attachments! Apr 16 15:54:38 server01 AppMailImporter[INFO]: KESK2216 PostList item created with propID = 10101563 Apr 16 15:54:38 server01 AppMailImporter[INFO]: KESK2216 Attachment written to disk with GUID = 6fc966f7-796b-427f-b114-173f927ae451.pdf Apr 16 15:54:39 server01 AppMailImporter[INFO]: KESK2216 Created document with propID = 10101564 and ObjectID = 15612 <...CURRENT...> Apr 16 15:54:39 server01 AppMailImporter[INFO]: KESK2216 Successfully connected document with deed propID = 10101563 and ObjectID = 15612 cal proxy 192.168.105.10/255.255.255.255/0/0 on interface outside Apr 16 15:51:02 fw2-v10 %ASA-3-713902: Group = 192.168.206.250, IP = 192.168.206.250, QM FSM error (P2 struct &0x00007fff4a020c40, mess id 0x5ac031d1)! Apr 16 15:51:02 fw2-v10 %ASA-3-713902: Group = 192.168.206.250, IP = 192.168.206.250, Removing peer from correlator table failed, no match! The logs for "server01" are from the correct file, but the ones from "fw2-v10" are from a different log file which has different alert match rules. The log file for fw2-v10 is also included in the client data, as a separate section Also, if I alert on all log entries, I now get alerts for <...CURRENT...>, which I guess is some tag that is added internally by Xymon. This I can avoid by adding ignore for this string, so it's not a big problem. Regards, Johan

2 1

Xymon 4.3.19 Released
by abs＠shadymint.com 16 Apr '15

16 Apr '15

J.C. Cleaver wrote: > Hello, > > Xymon 4.3.19 has been released to SF and should be available on a mirror > near you! It can be downloaded from > https://sourceforge.net/projects/xymon/ > > > 4.3.19 contains a number of bug fixes and improvements, along with a > several new features. > > - a report on all recent acknowledgements is now available > - a specific time range can now be excluded for analysis or alerting > purposes with the EXTIME= directive > - additional filters are available with the "xymondboard" command, > including searching the full body text of a status report > - the last position read in a log file is now indicated on the 'msgs' > status report > - a new 'deltacount' option for counting recent matching lines in a log file > - improved Windows PowerShell client support > > For a full list of changes, see the Changes file inside the tarball. > > > All users of 4.3.x or earlier versions of Xymon are encouraged to upgrade. > > > > Regards, > > -jc Someone has pointed out here that columndoc.sh is not working. It must have been like this since the cgiwrap shellshock workaround went in. I would have had a go at a fix, but not sure where the preferred place would be, either add the QUERY_STRING into cgiwrap or deal with it directly in csvinfo? -- Andy

2 1

xymon-snmpcollect - state ? xymond_channel worker needed for trending ?
by steve＠nerdynomads.net 16 Apr '15

16 Apr '15

Sorry for the replying to an old message, but seems there hasn't been any recent discussion of snmp polling. I believe I have everything working perfectly with 4.3.18, I see clientdata coming in on my test switch and I am collecting data on the [ifmib] definition in "server/etc/snmpmibs.cfg". What I don't have is trending on that data. I am assuming that is because the data is coming in under to xymon via "client" message versus a "data" message. To get trends, I assume I could write a xymond_channel worker listening on the client channel and using a filter option to target only "snmpcollect" messages. This would process the raw data, and submit the data I want to trend on via "data" messages ? Or am I just to bogged in the details and missing something obvious ? Thanks, -Steve -----Original Message----- To: hobbit (at) hswn.dk *Subject: Re: [hobbit] snmp *From: Henrik Stoerner <henrik (at) hswn.dk> *Date: Fri, 7 Mar 2008 07:34:31 +0100 *References: <001001c88014$695664f0$0500a8c0 (at) noip.org> *User-agent: Mutt/1.5.15+20070412 (2007-04-11) On Fri, Mar 07, 2008 at 06:30:53AM +0100, Lars Ebeling wrote: > I would like to have an examle of the snmp configuration file: > hobbit-snmphosts.cfg-- Here's one: [osiris.hswn.dk] version=2c community=public ip=172.16.10.100 ifmib={172.16.10.100} # ifmib={*} hrsystem hrstorage=(Real Memory) hrstorage=(Swap Space) hrstorage=(/) hrstorage=(/work) hrtask=<*> To understand how it works, you need to look at the hobbit-snmpmibs.cfg file also. In this file you'll find an [ifmib] section that begins with [ifmib] keyidx (IF-MIB::ifDescr) keyidx [IF-MIB::ifPhysAddress] keyidx <IF-MIB::ifName> validx {IP-MIB::ipAdEntIfIndex} ifDescr = IF-MIB::ifDescr Note the different kind of parentheses / brackets ? What these do is they act like an index into the list of network interfaces. So the line "ifmib={172.16.10.100}" means "grab the ifmib data for the network interface whose {IP-MIB::ipAdEntIfIndex} (IP-address) is 172.16.10.100. If you wanted the statistics from the "eth0" net-interface, you would use "ifmib=(eth0)". The line that just read "hrsystem" has no index, because this data - part of the Host Ressources MIB - only has one entry globally (e.g. there is only one count of how many users are logged on). The "hrtask=<*>" of course means to fetch information about all of the tasks running on the system. Regards, Henrik

2 2

Xymon prominently displayed in "Weather Channel" TV commercials in CT, USA
by waa-hobbitml＠revpol.com 16 Apr '15

16 Apr '15

Saw a Weather Channel commercial the other and when they display their NOC and pan around, there is a screen in the middle of the room clearly displaying what appears to be a Xymon "nongreen.html" page, and another much larger one on the NOC's main video wall. Wondering if anyone else has noticed this, or if it is not even Xymon. :) Cheers! -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/ -- Not responsible for anything below this line --

7 8

xymon client message STATUSLIFETIME?
by jlaidman＠rebel-it.com.au 15 Apr '15

15 Apr '15

I'll assume you've looked at the "dialup" keyword, which will make client (eg cpu and disk) statuses clear instead of purple. The default lifetime (30 minutes) is defined by the STATUSLIFETIME variable defined in xymonserver.cfg on the server. To override this value for network checks, you can specify "--validity=N" on the command-line used to run xymonnet. Neither of these are likely to help you. The client messages are turned into status messages by xymond_client. All instances of code in xymond_client that sends a status message do so without a validity specified. One thing you could do is to write a script that reads and refreshes the status for all relevant entries for the server in question, run every 25 minutes. For example: $XYMON $XYMSRV 'xymondboard host=host.example.com test=^(disk|memory|cpu)$ fields=hostname,testname,color,clntstamp' This gives you the client timestamp (in epoch seconds) - when the client message was received. You can subtract this from the current time (eg from "date +%s") to get the age of the client message. If it's less than 25 minutes, you have a status message that needs to be "refreshed". What you then would do is to query (with: $XYMON $XYMSRV "xymondlog host.example.com.cpu") and replay the status message (including whatever colour it had) with "+LIFETIME" added. Also, you could label all such hosts with a special keyword like how xymonnet uses "dialup", perhaps "daily". Then use "xymongrep daily" to get the hostnames you want to refresh. Cheers Jeremy On 14 April 2015 at 01:09, Werner Maier <werner at maiers.de> wrote: > Hi, > > I have the following problem: > > I want to monitor the client data of a machine that is only up > once a day. > > the machine gets waked up w/ wakeonlan, takes an rsnapshost of other > servers, and shuts down again. (no need to be up 24/7 with 8 2 TB HDDs, > raidcontroller)... > > I know about the normal xymon status+LIFETIME protocol. > but I don't see where or how to configure that client to send > a LIFETIME with the "xymonclient.sh" - it uses the > "client" protocol. > > how do I set the validity for these tests to 24h+ ? > (1600 minutes should be ok). > > thanks in advance. > > Werner > -- > Dipl.-Ing. Univ. Werner Maier > http://www.maiers.de/ > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

1 0

New XymonPSClient running in central mode
by colin.coe＠gmail.com 15 Apr '15

15 Apr '15

Hi all I've googled but not found an answer to this. Anyone know if the new PowerShell client supports central mode? Thanks CC

2 2