June 2016 - Xymon - Xymon mailman web

Creating a custom nongreeen.html
by Gary.McKenner＠rac.com.au 27 Jun '16

27 Jun '16

Hi, A few months ago I managed to get xymongen to create a custom non-green.html that only has red status , this file red.html is created every minute along with non-green.html , critical.html & xymon.html I cannot remember where I added the extra config to run this extra non-green.sh filtering out only the red status and has no eventlog or acklog. I seem to recall adding an extra stanza to a file to create this custom file but I cannot remember where the file is. I ran a strace of the scheduled xymongen command exactly as it is run by Xymon and you can see the red.html file being created after the normal non-green.html # strace -f ./xymongen --recentgifs --subpagecolumns=2 --report > /tmp/xymongen.txt3 2>&1 ... open("nongreen.html.tmp", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 3 open("/usr/share/xymon/web/stdnongreen_header", O_RDONLY) = 4 fstat(4, {st_mode=S_IFREG|0644, st_size=1221, ...}) = 0 read(4, "<!DOCTYPE HTML PUBLIC \"-//W3C//D"..., 1221) = 1221 close(4) = 0 fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ff815a4a000 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=453, ...}) = 0 write(3, "<!DOCTYPE HTML PUBLIC \"-//W3C//D"..., 4096) = 4096 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=453, ...}) = 0 open("/usr/share/xymon/web/bulletin_header", O_RDONLY) = -1 ENOENT (No such file or directory) write(3, "</a><span class=\"invis\"> | </spa"..., 4096) = 4096 open("/usr/share/xymon/data/hist/allevents", O_RDONLY) = -1 ENOENT (No such file or directory) open("/var/log/xymon/acknowledge.log", O_RDONLY) = 4 stat("/var/log/xymon/acknowledge.log", {st_mode=S_IFREG|0644, st_size=244, ...}) = 0 fstat(4, {st_mode=S_IFREG|0644, st_size=244, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ff815a49000 read(4, "1465774929\t1877328492\t2880\t18773"..., 4096) = 244 read(4, "", 4096) = 0 close(4) = 0 munmap(0x7ff815a49000, 4096) = 0 open("/usr/share/xymon/web/stdnongreen_footer", O_RDONLY) = 4 fstat(4, {st_mode=S_IFREG|0644, st_size=332, ...}) = 0 read(4, "<BR><BR>\n\n<TABLE SUMMARY=\"Bottom"..., 332) = 332 close(4) = 0 open("/usr/share/xymon/web/bulletin_footer", O_RDONLY) = -1 ENOENT (No such file or directory) write(3, "ends\"><IMG SRC=\"/xymon/gifs/gree"..., 2422) = 2422 close(3) = 0 munmap(0x7ff815a4a000, 4096) = 0 rename("nongreen.html.tmp", "nongreen.html") = 0 open("red.html.tmp", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 3 open("/usr/share/xymon/web/stdnongreen_header", O_RDONLY) = 4 fstat(4, {st_mode=S_IFREG|0644, st_size=1221, ...}) = 0 read(4, "<!DOCTYPE HTML PUBLIC \"-//W3C//D"..., 1221) = 1221 close(4) = 0 fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ff815a4a000 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=453, ...}) = 0 write(3, "<!DOCTYPE HTML PUBLIC \"-//W3C//D"..., 4096) = 4096 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=453, ...}) = 0 open("/usr/share/xymon/web/bulletin_header", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/xymon/web/stdnongreen_footer", O_RDONLY) = 4 fstat(4, {st_mode=S_IFREG|0644, st_size=332, ...}) = 0 read(4, "<BR><BR>\n\n<TABLE SUMMARY=\"Bottom"..., 332) = 332 close(4) = 0 open("/usr/share/xymon/web/bulletin_footer", O_RDONLY) = -1 ENOENT (No such file or directory) write(3, "</a><span class=\"invis\"> | </spa"..., 3570) = 3570 close(3) = 0 munmap(0x7ff815a4a000, 4096) = 0 rename("red.html.tmp", "red.html") = 0 Any ideas of where and what I edited to get this custom html file created Cheers, [cid:image001.png at 01D1C6EC.9D2898C0] Gary McKenner Unix Systems Administrator Group IT Operations I’m for a better WA. Royal Automobile Club of WA (Inc.) 832 Wellington Street, West Perth, WA 6005 T 08 9436 4310 M 0417972910 E gary.mckenner at rac.com.au ________________________________ DISCLAIMER: Disclaimer. This e-mail is private and confidential. If you are not the intended recipient, please advise us by return e-mail immediately, and delete the e-mail and any attachments without using or disclosing the contents in any way. The views expressed in this e-mail are those of the author, and do not represent those of this company unless this is clearly indicated. You should scan this e-mail and any attachments for viruses. This company accepts no liability for any direct or indirect damage or loss resulting from the use of any attachments to this e-mail. ________________________________

2 1

Questions about supplemental client messages
by jlaidman＠rebel-it.com.au 27 Jun '16

27 Jun '16

Hi y'all I have some questions about the use of supplemental client messages (by specifying a collector ID in the "client" message). The man page has very little to say on the matter. I want to have a client-side script that collects the latest BIND DNS statistics and feeds them to the Xymon server via a supplemental client message. This is achieved using the following type of command (simplified for the exercise): { echo "client/named_stats $MACHINE.$SERVEROSTYPE $CONFIGCLASS" echo "[named_stats]" cat /path/to/latest/named.stats } | $XYMON $XYMSRV "@" This generates the following in the client data webpage: <begin example> [collector:named_stats] client/named_stats dns.example.com.freakos freakos [named_stats] +++ Statistics Dump ++ (1234567890) ... ++ Outgoing Queries ++ [View: default] 12345 A 345 NS ... ++ Resolver Statistics ++ [Common] 9693 mismatch responses received [View: default] ... <end example> My questions regarding this are: 1. Should I be including the $CONFIGCLASS in the report, like other client messages? Xymon puts the class onto a newline when I do this. The man page says the class is optional for a client message, but if I wanted to change the class, I don't think I would be able to. Or maybe it only makes sense to specify the class for the main client message, and not supplemental ones. 2. When I write the server-side processor, I'll need to collect the output by specifying the client section name of [named_stats]. But there's also a "[collector:named_stats] section heading that gets created automatically. Should I be adding the "[named_stats]" section at all, or instead making use of the [collector:named_stats] that gets created regardless? It probably doesn't matter if I have both, but I don't want to break anything, including some future intended use of these extra client messages. 3. The content of the client data section I'm sending happens to have square bracketed terms like "[Common]" and "[View: default]". This makes it impossible for me to fetch the whole [named-stats] section. My instinct is to escape these somehow, but I don't know of any standard "Xymon" way of doing this beyond a simple backslash. Cheers Jeremy

1 0

question
by jlaidman＠rebel-it.com.au 27 Jun '16

27 Jun '16

On Sun, Jun 12, 2016 at 2:10 AM <m.pingel at ndr.de> wrote: > Hi, > Thanks. But my client are all windows-pc. > Firstly, I have created a new xymon-procmem script: http://tools.rebel-it.com.au/xymon-procmem/ It's also listed in the xymonton.org monitors. Secondly, if the Windows client you're using sends some kind of process list, it might be possible to extract memory usage. If you can give me the output of the [ps] section of the client data, I can take a look at merging support into xymon-procmem. J

2 2

Remove xymond
by NMaharaj＠tcta.co.za 27 Jun '16

27 Jun '16

2 1

bad processing of client data on the server
by Scot.Kreienkamp＠la-z-boy.com 24 Jun '16

24 Jun '16

A few weeks ago there was a thread on this list about xymon confusing the client reports by reporting results from one client on another client entirely. I had been watching strange things happen to my Xymon instance occasionally and just now caught the first irrefutable proof that was indeed happening in my environment. The ports test page for retv6034 contains the results from another server entirely, which can be proven by comparing the text of the ports page with the client data report. Xymon server has obviously gotten this wrong in processing somewhere as the client data brought back through the client data link at the bottom of the ports test page contains the correct data. The two servers are multiple hops away from both each other and the Xymon server, and the Xymon server load at the time was .1 and 96% idle CPU usage. Here's a snippet from the ports test page from retv6034 at the time, which was reporting red due to missing ports that were being monitored on retv6034: TCP 10.103.1.63:135 10.1.1.34:40773 ESTABLISHED TCP 10.103.1.63:135 10.1.2.23:57996 ESTABLISHED TCP 10.103.1.63:135 10.1.7.55:12679 ESTABLISHED TCP 10.103.1.63:135 10.1.7.55:12722 ESTABLISHED TCP 10.103.1.63:135 10.1.7.56:20008 ESTABLISHED TCP 10.103.1.63:135 10.112.1.62:52119 ESTABLISHED TCP 10.103.1.63:135 10.125.1.63:23527 ESTABLISHED TCP 10.103.1.63:139 0.0.0.0:0 LISTENING And here's the entire ports section from the client data report for retv6034. This is the correct data for what should have been on the page: [ports] Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 127.0.0.1:8005 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:199 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8009 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:60111 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:35060 0.0.0.0:* LISTEN tcp 0 0 10.170.1.114:53 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN tcp 0 0 10.170.1.114:33972 10.1.1.200:1984 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.242:15971 FIN_WAIT2 tcp 0 0 10.170.1.114:8080 10.170.1.240:7519 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.240:63015 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.242:64431 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.240:32815 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.240:10363 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.241:54788 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.242:54629 ESTABLISHED tcp 0 0 10.170.1.114:8080 10.170.1.242:25603 FIN_WAIT2 tcp 0 0 10.170.1.114:8080 10.170.1.240:52365 TIME_WAIT tcp 0 0 10.170.1.114:44018 10.1.2.50:514 ESTABLISHED tcp 0 0 10.170.1.114:8080 10.170.1.241:15201 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.242:10447 FIN_WAIT2 tcp 0 0 10.170.1.114:8080 10.170.1.241:1043 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.240:17144 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.241:13427 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.241:4912 TIME_WAIT tcp 0 0 10.170.1.114:33974 10.1.1.200:1984 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.240:52295 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.241:18884 TIME_WAIT tcp 0 0 10.170.1.114:913 10.170.1.220:2049 ESTABLISHED tcp 0 0 10.170.1.114:58396 10.1.2.54:2003 ESTABLISHED tcp 0 0 10.170.1.114:8080 10.1.1.200:50195 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.240:3119 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.241:54730 TIME_WAIT tcp 0 0 10.170.1.114:33976 10.1.1.200:1984 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.242:10171 ESTABLISHED tcp 0 0 10.170.1.114:8080 10.170.1.240:42249 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.241:6831 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.241:51631 TIME_WAIT tcp 0 0 10.170.1.114:58394 10.1.2.54:2003 ESTABLISHED tcp 0 0 10.170.1.114:8080 10.170.1.242:63087 TIME_WAIT tcp 0 0 10.170.1.114:33978 10.1.1.200:1984 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.242:20554 FIN_WAIT2 tcp 0 0 10.170.1.114:49506 10.1.7.75:389 ESTABLISHED tcp 0 0 10.170.1.114:8080 10.170.1.240:47234 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.242:47185 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.241:50056 TIME_WAIT tcp 0 0 10.170.1.114:8080 10.170.1.240:26500 TIME_WAIT tcp 0 0 :::111 :::* LISTEN tcp 0 0 :::44688 :::* LISTEN tcp 0 0 :::36886 :::* LISTEN udp 0 0 0.0.0.0:993 0.0.0.0:* udp 0 0 0.0.0.0:995 0.0.0.0:* udp 0 0 0.0.0.0:878 0.0.0.0:* udp 0 0 0.0.0.0:110 0.0.0.0:* udp 0 0 0.0.0.0:111 0.0.0.0:* udp 0 0 0.0.0.0:631 0.0.0.0:* udp 0 0 10.170.1.114:123 0.0.0.0:* udp 0 0 127.0.0.1:123 0.0.0.0:* udp 0 0 0.0.0.0:123 0.0.0.0:* udp 0 0 0.0.0.0:647 0.0.0.0:* udp 0 0 0.0.0.0:143 0.0.0.0:* udp 0 0 0.0.0.0:783 0.0.0.0:* udp 0 0 127.0.0.1:921 0.0.0.0:* udp 0 0 0.0.0.0:161 0.0.0.0:* udp 0 0 10.170.1.114:53 0.0.0.0:* udp 0 0 127.0.0.1:53 0.0.0.0:* udp 0 0 0.0.0.0:40131 0.0.0.0:* udp 0 0 0.0.0.0:52420 0.0.0.0:* udp 0 0 0.0.0.0:847 0.0.0.0:* udp 0 0 :::878 :::* udp 0 0 :::111 :::* udp 0 0 :::123 :::* udp 0 0 :::35899 :::* udp 0 0 :::35906 :::* Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | * 734-384-6403 | | * 7349151444 | * Scot.Kreienkamp at la-z-boy.com<mailto:%7BE-mail%7D> www<http://www.la-z-boy.com/>.la-z-boy.com<http://www.la-z-boy.com/> | facebook.<https://www.facebook.com/lazboy>com<https://www.facebook.com/lazboy>/<https://www.facebook.com/lazboy>lazboy<http://facebook.com/lazboy> | twitter.com/lazboy<https://twitter.com/lazboy> | youtube.com/<https://www.youtube.com/user/lazboy>lazboy<https://www.youtube.com/user/lazboy> [cid:lzbVertical_hres.jpg] This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.

1 0

bbmrtg.pl
by mailinglist＠tikklik.nl 24 Jun '16

24 Jun '16

Hello, I have used xymon / BB for many years. I had to do a reinstall (server crash) I had a collum traffic But I cant get this to work again. If I manualy run the script bbmrtg.pl I see localhost status mx2.mx2....com green Thu Jun 23 17:08:02 2016 but that has to be mx2..com the configfile looks like this bb*host[mx2..com]: mx2..com bb*svc[mx2..com]: mx2..com bb*unit[mx2..com]: bytes/sec bb*althost[mx2..com]: mx2..com bb*altsvc[mx2..com]: traffic I see a ghost report reported host mx2...com.mx2... any idees how to fixc this?

2 1

Custom Tests
by joshuasocrates＠gmail.com 23 Jun '16

23 Jun '16

Hello again Xymon members, I'm very new to both Unix systems and Xymon, and I have to say learning Xymon on a Unix system is currently leaving me pretty stumped for a lot of things. Right now I am attempting to create a script that will read the past 20 minutes of a log file, and report an array of values back to Xymon. I am looking for the end result to have a "green face" if less than five zeroes are detected, a yellow from 5 - 10, and a red from 10 and up. I have the script written, but I am unsure how to implement it into Xymon and have the results printed out when I click on the face beneath the test column. Results to be viewed after clicking the test column are in the format as followed: TIMESTAMP DATANAME DATATYPE FREQUENCY TIMEFRAME With respective info included. So how would I go around formatting the end result of a test to look like this when you clicked for more information? Cheers all! Joshua H

2 1

EXTIME still valid ?
by rltexas1＠gmail.com 22 Jun '16

22 Jun '16

Is the EXTIME option still valid in the alerts.cfg I am having problems testing the following EXTIME=1:1140:1240 Should be exclude Monday's 11:40 to 12:40. Will test EXTIME=M:1140:1240 But if it's M for Monday what would Sunday be ? Thanks

4 4

Reload error
by joshuasocrates＠gmail.com 22 Jun '16

22 Jun '16

I've been getting an error with Xymon since I edited the host page last, and for the life of me I cannot figure out why. Error is as follows: -> Recipient 'xxx.xxx.xxx.xx', timeout 15 -> 1st line: 'config hosts.cfg' Cannot load hosts.cfg from xymond, code 7 Failed to load from xymond, reverting to file-load Whoops! Failed to send a message (timeout) And this repeats for a while in /alert.log. As a result, my xymon page is currently saying it is still... Fri Jun 17 07:35:35 2016. I would like to avoid posting my actual hosts.cfg page, but if it comes to that I will do so. Does anyone have any suggestions? I've compared my hosts.cfg file to others I can find, and I don't see any reason why there should be errors. Thanks, Joshua

2 1

Intelligent CPU Load Settings
by howe.bill＠gmail.com 21 Jun '16

21 Jun '16

Xymon'ers, Is there any planned functionality to be able to dynamically set a xymon client's LOAD alert settings based upon how many processors it has? The current static defaults are not too helpful, and hand editing an entry in /etc/xymon/analysis/*.cfg for every server just shouldn't have to be done. _*Ideally*_ It would be best if along with the "top" view that is reported by clients, they also reported their CPU count (either with "nproc" or "grep -c proc /proc/cpuinfo") Then the CPU count could be shown on client's "cpu" service page. <= Critical information when determining if load is a problem or not. Since the count would then be reported to and available on the xymon server, it could then be possible to set warnings and criticals based off of CPU count. (IE Warn at a load number equal to CPU count, Critical at a number equal to CPU count x 1.5) Regards, -- Bill Howe howe.bill at gmail.com

2 4