- Xymon - Xymon mailman web

Xymon 4.3.29 scheduling and F30
by cleaver＠terabithia.org 03 May '19

03 May '19

Hi all, Just to give everyone an update, I have a few more patches I'm still looking at, but I mostly wanted to wait until I get a chance to test compile fixes on Fedora 30 final, which should drop today or tomorrow. There are still a number of compile warnings generally (mostly char mismatch warnings), but if you know of compile issues on other platforms specifically, it would be helpful if you could run a quick test on the latest 4.3.29 snapshot to see if it's resolved. The latest snap is available at https://sourceforge.net/p/xymon/code/HEAD/tree/branches/4.3.29/ in the upper right. Thanks, -jc

4 6

Patch - no-cpu-listing - cpu column
by john.horne＠plymouth.ac.uk 29 Apr '19

29 Apr '19

Hi, Using the Terabithia 4.3.28 RPMS, the 'cpu' column typically shows the output from the 'top' command received from the client. While we have no problem with users knowing if a server has a problem, we do not necessarily want them seeing the processes running on the server. (A bit of security by obscurity I suppose.) The attached patches implement a 'xymond_client' option named '--no-cpu- listing'. This is basically similar to the current '--no-ps-listing' and '--no- port-listing' options (both of which we already use). The default for the new option is to be disabled - that is, as before, the 'top' listing is shown. If the option is used (in the tasks.cfg file, under the 'clientdata' section), then no 'top' output is included in the 'cpu' column, and just the uptime output and CPU load graph are shown. Both patches are only a few lines long. We have used this patch for a long time without any problems. John. -- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

2 1

Graph titles and NAME: in hosts.cfg - bug?
by john.horne＠plymouth.ac.uk 29 Apr '19

29 Apr '19

Hello, (A bit long, sorry...) Using Xymon 4.3.28 from the Terabithia RPMs. I've been adding a few new client servers to our Xymon monitor. However, I have noticed today that for some graphs no graph title appears. The graph appears, the values appear (on the graph) and the graph lines appear. Just no title. It seems that this affects those client servers which are configured in the hosts.cfg file with a NAME: entry. For example: 10.11.12.13 server1 # NAME:"server1 (pre-prod web)" testip !ftp ssh... (I don't use FQDNs for the server names.) It seems that entries we have added to the 'graphs.cfg' file, and where the TITLE uses the 'exec:' function have the problem. (See the 'graphs.cfg' man page for info about using 'exec:'.) So, for example we have in graphs.cfg: ======= [memory] TITLE exec:/bin/sh -c 'echo Memory Utilisation - $2' YAXIS % Used ... ======= Debugging the graph output (by setting some variables) using 'xymoncmd showgraph.cgi --debug >/tmp/graph.out' shows: ======= # xymoncmd showgraph.cgi --debug >/tmp/graph.out sh: -c: line 0: syntax error near unexpected token `(' sh: -c: line 0: `/bin/sh -c 'echo Memory Utilisation - $2' server1 (pre-prod web) memory "14/Apr/2019 - 16/Apr/2019" "memory.rrd"' ======= As can be seen the parameters passed to 'showgraph.cgi' should include the hostname, but it includes the hostname and the NAME: entry. The shell barfs on the parentheses. If I run the above shell command directly but quoting the whole server name, then it works fine: ====== $ /bin/sh -c 'echo Memory Utilisation - $2' "server1 (pre- prod web)" memory "14/Apr/2019 - 16/Apr/2019" "memory.rrd" Memory Utilisation - 14/Apr/2019 - 16/Apr/2019 ====== This seems to be a bug. If the hostname parameter being sent to showgraph includes spaces (because the NAME: entry is included), then the whole parameter should be quoted. I suspect that if the NAME: entry itself has double-quotes in it, then the graph title could be a bit messed up. If in the above example I changed the parentheses to '=' signs, then no quoting is required but the title comes out as 'Memory Utilisation - web='. Perhaps in those instances, as the man page for graphs.cfg suggests, a local script is run instead to do the processing and dig out the correct graph title. It's late now, and I'm going to be busy leading up to the Easter break, but if I can I'll take a look and see if I can get a patch for the code. I'm suspecting it should be a one-line - if the total hostname parameter has a space then quote the whole thing. John. -- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

2 2

Goodbye and thanks for all the fish
by Phil.Crooker＠orix.com.au 29 Apr '19

29 Apr '19

Our company has decided to switch to a managed monitoring system, so goodbye, XYmon. I'm grateful to Henrik, Jeremy and everyone for all the work you've put in to XYmon over the years. I can't say I'll miss the regular expressions in analysis.cfg, but it certainly has saved my bacon many times. All the best, Phil

2 1

semaphore errors
by stef.coene＠docum.org 29 Apr '19

29 Apr '19

Hi, We are getting these errors on 2 xymon servers running 4.3.21 and 4.3.28. Any steps I can do to debug and/or prevent this error? The only solution is a restart of the xymon daemons. 2018-10-24 12:06:21.110407 semop failed, Invalid argument 2018-10-24 12:06:21.110456 Dropping message due to semaphore error ipcs ------ Message Queues -------- key msqid owner perms used-bytes messages ------ Shared Memory Segments -------- key shmid owner perms bytes nattch status 0x00000000 0 root 644 80 2 0x00000000 32769 root 644 16384 2 0x00000000 65538 root 644 280 2 0x01013343 2818051 xymon 600 10485760 2 0x02013343 2850820 xymon 600 10485760 2 0x03013343 2883589 xymon 600 10485760 2 0x04013343 2916358 xymon 600 10485760 2 0x05013343 2949127 xymon 600 262144 1 0x06013343 2981896 xymon 600 32768 1 0x07013343 3014665 xymon 600 10485760 2 0x08013343 3047434 xymon 600 10485760 2 0x09013343 3080203 xymon 600 131072 3 0xfa0101b9 1277964 root 666 30435368 2 0xfa0101bd 1310733 root 666 30435368 1 ------ Semaphore Arrays -------- key semid owner perms nsems 0x000000a7 98304 root 600 1 0x00000000 7995393 www-data 600 1 0x00000000 8028162 www-data 600 1 0x00000000 1769475 www-data 600 1 Stef

3 5

WordPress Monitoring
by matthew＠adultliteracy.ac.nz 28 Apr '19

28 Apr '19

I know this question may not be answered, but I am wondering if Xymon can monitor a WordPress website or 2 on DreamHost. I have a shared service account. Matthew Gregory IT Manager Rural Youth & Adult Literacy Trust www.adultliteracy.ac.nz m: 022 644 9544 t: 0800 891 339 e: matthew at adultliteracy.ac.nz

3 2

how to tune memory threshold for Windows PS client?
by rlhamil2＠gmail.com 28 Apr '19

28 Apr '19

For a wimpy laptop (latest Windows 10 Pro, 6 GB RAM), it goes orange pretty quick (three days or so), even though its mostly sitting idle. Is this MEMSWAP in analysis.cfg on the server that I want to tweak, or something else? What's reasonable for a Windows system like that? And does Windows grow swap automatically if needed (in which case the threshold could probably safely be higher)? Sun 28 Apr 08:13:01 2019 - Memory low Memory Used Total Percentage Real/Physical 3350M 5717M 58% Actual/Virtual 163M 960M 16% Swap/Page 4459M 6677M 66%

1 0

Yet another flap
by rcohen55＠gmail.com 26 Apr '19

26 Apr '19

Hi have one server which keeps flapping on msgs. Spent hours to look for the obvious culprit (another feeder) until it dawn on me that it must be the logfetch, since there are no issues with other columns. And indeed, after running logfetch with --debug=stderr, I discovered that it is not always running - I mean not triggered at all - which triggered the flapping status. I dug here and there, to no avail. Any bright ideas are welcome.. Cheers Ron

2 2

MRTG graphs are in bytes instead of bits
by scarville＠lereta.com 25 Apr '19

25 Apr '19

I started using mrtg to graph traffic over a 1 Gbps point-to-point link to a DR site. It is currently being monitored using cricket. When comparing the mrtg graph to the cricket graphs, the mrtg graph seems to be in bytes/second instead of bits/second. The y-axis label says bits/second but the values are way to small. This is the configuration for the switch port. ## CA to AZ P2P Directory[mrtg.ca-coresw.gi_1_1_1]: ca2az-p2p.lereta.net Target[mrtg.ca-coresw.gi_1_1_1]: 1:ROcommunity at ca-coresw.lereta.net Options[mrtg.ca-coresw.gi_1_1_1]: bits Title[mrtg.ca-coresw.gi_1_1_1]: P2P to AZ MaxBytes[mrtg.ca-coresw.gi_1_1_1]: 125000000 I haven't used mrtg in years so I may be just screwing up the configuration. Any help is appreciated. -- Stephen Carville

2 3

strange behavior of xymon client in openSUSE
by metron6＠gmail.com 25 Apr '19

25 Apr '19

>From an opensuse linux, i'm trying to connect to my xymon servers... take a look at this.. in /etc/default/xymon-client This works XYMONSERVERS="10.129.13.2" This works XYMONSERVERS="10.10.100.100" This doesn't XYMONSERVERS="10.10.100.100 10.129.13.2" This works XYMONSERVERS="10.10.100.100" XYMONSERVERS="10.129.13.2" linux:~ # cat /etc/os-release NAME="openSUSE Leap" VERSION="42.3" ID=opensuse ID_LIKE="suse" VERSION_ID="42.3" PRETTY_NAME="openSUSE Leap 42.3" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:42.3" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" -- regards, George Michalopoulos born & raise @ Metron 6 (six) Metron6 at gmail.com

2 1