March 2017 - Xymon - Xymon mailman web

Extra lines for non-existent data
by jlaidman＠rebel-it.com.au 23 Mar '17

23 Mar '17

Hi I'm sure this has been discussed previously, but I don't know if there was a fix or a work-around. I have a few graphs that Xymon wants to show over multiple graphs. In the example below, this is happening for two different graph definitions.The second of each graph has no data, and so the graphs are broken. [image: Inline images 1] In the first of the two graphs (in each case) the URL for the graph image contains "first=1&count=5". The second, broken, graph image URL contains "first=6&count=5". Each of these graph definitions, in graphs.cfg, uses one RRD file per DEF, where each RRD file has only one data series (named "lambda"). I seem to recall that when xymongen is constructing the URLs for the images, it has to make a guess about how many to include, based on how many lines it things there might be, and that guess is not always accurate. Is there a way to provide hints to xymongen about the number of lines in a graph? I also seem to recall that Devmon managed to work around this problem, but I don't know how, or if the same technique can be applied outside of Devmon. J

1 1

Alerts via twitter
by Wim.Nelis＠nlr.nl 23 Mar '17

23 Mar '17

Hello, I would like to send some of the Xymon alerts via twitter. Has someone a script to do so? Regards, Wim Nelis.

2 1

False positives on RAM and DISK F19
by jdottdot＠hotmail.com 22 Mar '17

22 Mar '17

I can't seem to find a solution for a problem I'm having: I'm running xymon-client on several Fedora 19 servers. The client version is 4.3.28 release 1.fc19. There isn't an option to upgrade the servers right now from F19. Memory report showing over 100%: server:memory red [758975] red Wed Mar 22 08:56:44 MDT 2017 - Memory CRITICAL Memory Used Total Percentage &red Physical 1236M 123M 1004% &red Actual 9293M 123M 7555% &green Swap 2266M 2867M 79% Disk showing 0 units free even though that isn't the case: server:disk red [208517] red Wed Mar 22 07:42:39 MDT 2017 - Filesystems NOT ok &red 11933080 4623272 73% / (0 units free) has reached the PANIC level (512 units) &red 636 6149980 1% /dev/shm (0 units free) has reached the PANIC level (512 units) &red 1016 6149600 1% /run (0 units free) has reached the PANIC level (512 units) &red 0 6150616 0% /sys/fs/cgroup (0 units free) has reached the PANIC level (512 units) &red 264948 5885668 5% /tmp (0 units free) has reached the PANIC level (512 units) &red 117488 62417 66% /boot (0 units free) has reached the PANIC level (512 units) Filesystem 1024-blocks Used A ail]ble Capacity Mounted on /dev/mapper/fedora_pvapp05-root 17411420 11933080 4623272 73% / tmpfs 6150616 636 6149980 1% /dev/shm tmpfs 6150616 1016 6149600 1% /run tmpfs 6150616 0 6150616 0% /sys/fs/cgroup tmpfs 6150616 264948 5885668 5% /tmp /dev/xvda1 194241 117488 62417 66% /boot Does anyone know if there is a patch for this or has anyone successfully run a newer version of the client on an older OS? Thanks, John

3 2

best aproach for KpyM Telnet/SSH Server
by rbadilla＠grupocesa.com 21 Mar '17

21 Mar '17

hi people: I have several windows machines with KpyM Telnet/SSH Server (http://www.kpym.com/2/kpym/index.htm) But the standard xymon ssh test always alarm since the expect return string of KpyM SSH server isn't the same. So I wondering if better make an isolated test for this process like WINSSH on protocols.cfg or is safe to modify the ssh protocols.cfg entry ??? Thanks in advanced!

2 1

Multiple NET: tags?
by jlaidman＠rebel-it.com.au 21 Mar '17

21 Mar '17

Does anyone know if it's valid to use multiple NET: tags for a host, or will it break stuff? I don't actually use NET: tags for its real purpose (for xymonnet to match with $XYMONNETWORK) and instead I have some server-side scripts that are only meant for hosts on some networks. If I wanted to define a host so that it is included in multiple server-side script processing, can I do something like this: 10.1.1.1 host1.example.com # NET:net1 NET:net2 Eventually, someone might want to use NET: tags as intended, and I don't want to make that not work, or behave unexpectedly.

2 1

host and test names with dots
by rodrigoborgespereira＠gmail.com 20 Mar '17

20 Mar '17

Hello, Is it possible to have test names and host names with dots, and use them with xymon client? For example: xymon localhost "status+60 GREEN <hostname>.<testname> message" How could this work, if at all? Thanks,

5 5

HP Ilo's
by kc6ovd＠gmail.com 17 Mar '17

17 Mar '17

Fellow xymoners, anyone monitoring HP Ilo’s? just wondering if you are using Devmon or some other script. Looking for samples and comments. Thanks. -Kevin Sent from Mail for Windows 10

3 4

basic protocol test goes clear not red
by bakgat8＠hotmail.com 17 Mar '17

17 Mar '17

in the protocol.cfg file I have [autosysa] port 7520 [autosysb] port 7500 in hosts.cfg 10.65.4.76 USPHL0SQLF6 #DESCR:autosys-prod-jobs autosysa autosysb now I find this in my history Wed Mar 8 05:23:32 2017 autosysa ok : Ping failed, or dialup host/service Service autosysa on USPHL0SQLF6 is OK Dialup host/service, or test depends on another failed test Host appears to be down Seconds: 0.000000000 I never said this was a dialup host or service - I expect it to go red when it fails .. not go clear. Can anyone tell me why Xymon thinks this is a dialup host? from the eventlog [clear]<http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…>[green]<http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…> Sat Mar 04 16:32:40 2017 [clear] <http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…> 0:01:37 Fri Mar 03 16:12:35 2017 [green] <http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…> 1 days 0:20:05 Fri Mar 03 16:10:11 2017 [clear] <http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…> 0:02:24 Fri Feb 17 13:15:37 2017 [green] <http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…> 14 days 2:54:34 Fri Feb 17 13:12:43 2017 [clear] <http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…> 0:02:54 seems it will eventually go red Wed Mar 08 05:25:31 2017 [red] <http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…> 0:01:00 Wed Mar 08 05:23:44 2017 [clear] <http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…> 0:01:47 Sat Mar 04 16:34:17 2017 [green] <http://usphl0pxymam00.starfss.com/xymondev1-cgi/historylog.sh?HOST=USPHL0SQ…> 3 days 12:49:27

1 0

Strange error in alerts.log
by jlaidman＠rebel-it.com.au 17 Mar '17

17 Mar '17

David Is xymond_alert running on the same server as xymond? If so, perhaps try setting XYMSRV or XYMSERVERS to 127.0.0.1 and see if that helps. I'm wondering if the problem has something to do with your VM. Does the xymond.log flap messages mention what test was flapping? Cheers Jeremy On 17 March 2017 at 05:01, David Boyer <davieb at gmail.com> wrote: > Jeremy, > Yes, it returns hosts.cfg and the contents of the hosts.d > directory. A little more background, as the VM is nat'd and the > route-able address is what is being queried and configured in the > xymonserver.cfg config file. The error surfaced 9 times over night.. > > The xymond.log has a dozen or so msgs about flapping, xymonnet.log is > empty. The history log just has msgs from the restarting on the server > yesterday about not updating a ext test and color unchanged. > > Thanks, > Dave > > On Wed, Mar 15, 2017 at 3:41 PM, Jeremy Laidman <jlaidman at rebel-it.com.au> > wrote: > >> On 16 March 2017 at 06:24, David Boyer <davieb at gmail.com> wrote: >> >>> >>> Anybody have any info on this error in ~xymon/server/logs/alert.log? >>> >>> Whoops ! Failed to send message (select(2) failed) >>> -> Select failure while sending to Xymon daemon at 192.168.11.100:1984 >>> -> Recipent '192.168.11.100', timeout 15 >>> -> 1st line: 'config hosts.cfg' >>> Cannot load hosts.cfg from xymond, code 6 >>> Failed to load from xymond, reverting to file-load >>> >> >> I'm guessing this is displayed when xymond_alert asks xymond to give it >> the "hosts.cfg" file contents, but the xymond process is not responding at >> that time. The fact that you get a timeout after 15 seconds, rather than >> being refused, suggests that either the xymond daemon was running but >> wedged, or that a firewall was dropping packets so the socket could not be >> established in the first place. I'm not a coder, but my guess is that >> select(2) is called after the socket is up, and so a wedged xymond is more >> likely. >> >> Why would xymond not respond? Perhaps high CPU load, or memory thrashing? >> >> Do you see these log messages often? If it's only occasionally, are they >> all about the same time of day? >> >> Can you run this command and see if it gives the hosts.cfg file: >> >> $ /path/to/xymon 192.168.11.100 'config hosts.cfg' >> >> J >> >> >

1 0

Strange error in alerts.log
by davieb＠gmail.com 15 Mar '17

15 Mar '17

Anybody have any info on this error in ~xymon/server/logs/alert.log? Whoops ! Failed to send message (select(2) failed) -> Select failure while sending to Xymon daemon at 192.168.11.100:1984 -> Recipent '192.168.11.100', timeout 15 -> 1st line: 'config hosts.cfg' Cannot load hosts.cfg from xymond, code 6 Failed to load from xymond, reverting to file-load Thanks, Dave

2 1