November 2018 - Xymon - Xymon mailman web

xymon startup on macs
by rlhamil2＠gmail.com 03 Nov '18

03 Nov '18

One of my Macs (older OS, 10.6 aka Snow Leopard) comes up purple after reboot, requiring killing the client's xymonlaunch process (which launchd restarts, and then comes up ok). This is because the hostname isn't properly set yet. I had a workaround that worked on other systems, but not that one, in the form of a modified runclient.sh script that took an additional option to wait until it could e.g. ping the xymon server by name before proceeding with the rest of what the script does, at which point the network would be up and the hostname set. Looking at the Mac man page for hostname, I saw mention of a way to set the hostname that would persist across reboots: scutil --set HostName name-of-host Did that, rebooted, and it came up fine. That should probably avoid the need to hack up runclient.sh (and bring changes forward when updating). There might be undesirable implications for doing that on a laptop that was used on different networks, though.

1 0

TIME syntax question
by scott.birl＠temple.edu 02 Nov '18

02 Nov '18

TIME=12345:1200:2100 -----Original Message----- From: Xymon <xymon-bounces at xymon.com> On Behalf Of Neal, Jonathan W via Xymon Sent: Friday, November 2, 2018 12:30 PM To: xymon at xymon.com Subject: [Xymon] TIME syntax question Trying to find the actual syntax for the TIME specification in alerts.cfg So something like TIME=*:1200:2100 only sends that alerts during that time, 7 days a week. I assume the * is for day of the week. So if you only wanted to send it Monday - Friday, what is the syntax for it? Is it like cron where I can put 1-5 in there like TIME=1-5:1200:2100 or am I totally off base? Thanks in advance. _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

1 0

TIME syntax question
by jeremy.ruffer＠gmail.com 02 Nov '18

02 Nov '18

You csn use W for weekdays. Jeremy On Fri, 2 Nov 2018 16:35 Neal, Jonathan W via Xymon <xymon at xymon.com wrote: > > > > ---------- Forwarded message ---------- > From: "Neal, Jonathan W" <wes.neal at verizon.com> > To: xymon at xymon.com > Cc: > Bcc: > Date: Fri, 2 Nov 2018 12:30:09 -0400 > Subject: TIME syntax question > Trying to find the actual syntax for the TIME specification in alerts.cfg > > So something like TIME=*:1200:2100 only sends that alerts during that > time, 7 days a week. I assume the * is for day of the week. So if you > only wanted to send it Monday - Friday, what is the syntax for it? Is it > like cron where I can put 1-5 in there like TIME=1-5:1200:2100 or am I > totally off base? > > Thanks in advance. > > > > > ---------- Forwarded message ---------- > From: "Neal, Jonathan W via Xymon" <xymon at xymon.com> > To: xymon at xymon.com > Cc: > Bcc: > Date: Fri, 2 Nov 2018 12:30:09 -0400 > Subject: [Xymon] TIME syntax question > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

1 0

TIME syntax question
by wes.neal＠verizon.com 02 Nov '18

02 Nov '18

Trying to find the actual syntax for the TIME specification in alerts.cfg So something like TIME=*:1200:2100 only sends that alerts during that time, 7 days a week. I assume the * is for day of the week. So if you only wanted to send it Monday - Friday, what is the syntax for it? Is it like cron where I can put 1-5 in there like TIME=1-5:1200:2100 or am I totally off base? Thanks in advance.

1 0

acknowledgements does not survive xymon restart
by norbert.kriegenburg＠de.ibm.com 02 Nov '18

02 Nov '18

Experts: I have a new fairly large xymon environment (4.3.28 with >10k servers), and of course there are always a lot of alerts acknowledged. Unfortunately all these acks are resetted if i restart the xymon daemon (xymon.sh restart) to activate config changes f.e. This is the same if i use the "Acknowledge alert" from the menu or the (undocumented) "xymondack" feature of xymon. This leads to a lot of extra effort and confusion... Any ideas how i can save the ack situation and restore it after a restart? Norbert

2 3

acknowledgements does not survive xymon restart
by norbert.kriegenburg＠de.ibm.com 02 Nov '18

02 Nov '18

Don't get me wrong: i don't do frequent restarts usually, but from time to time i need a restart, or the whole server must be restarted bc. of patches. And as i constantly have to add new checks with new NCV definitions the TEST2RRD and SPLITNCV settings in xymonserver.cfg changes, this needs also a restart. Because we have such a huge numer of servers a lot of departments use Xymon regularly (luckily), and use the ack mechanism to organize their work (add ticket number to an alert, do some evaluation reports and so on). To have >100 alerts ack'ed is normal situation. And it creates a lot of extra work to restore this. In old BB times the acks always survived downtimes and restarts, but now there are no more ack files stored in the acks dir, so i thought it would be restored from the info in the alert.chk file, what is not the case. Norbert From: EDSchminke at Hormel.com To: xymon at xymon.com Cc: norbert.kriegenburg at de.ibm.com Date: 11/01/2018 12:58 PM Subject: Re: [Xymon] acknowledgements does not survive xymon restart What config changes are you making that requires such frequent restarts? Changes to hosts.cfg, alerts.cfg, analysis.cfg, client-local.cfg; these are files that get changed most frequently in my environment. None of which require a restart to pick up the changes. I think the only one that *does* need a restart, would be xymonserver.cfg, and the only component that would need to be restarted would be xymond, not the full stack. Erik D. Schminke | Associate Systems Programmer Hormel Foods Corporation | One Hormel Place | Austin, MN 55912 Phone: (507) 434-6817 edschminke at hormel.com | www.hormelfoods.com

2 2

xymon@xymon.com
by mailinglist＠tikklik.nl 01 Nov '18

01 Nov '18

Hello Damien, There is a little bug in the script /usr/sbin/hpacucli ctrl all show config | grep drive logicaldrive 1 (273.4 GB, RAID 1+0, OK) physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 146.8 GB, OK) physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 146.8 GB, OK) physicaldrive 2I:1:3 (port 2I:box 1:bay 3, SAS, 146.8 GB, OK) physicaldrive 2I:1:4 (port 2I:box 1:bay 4, SAS, 146.8 GB, OK) physicaldrive 2I:1:5 (port 2I:box 1:bay 5, SAS, 146.8 GB, OK, spare) /usr/sbin/hpacucli ctrl all show config | grep drive | awk '{print $NF}' | sed s/\)// OK OK OK OK OK Spare So the sparedisk is reported as bad 😊 My change below: STATUS=$(echo $OUTPUT | awk '{print $NF}' | sed s/\)//) if [ "$STATUS" == "spare" ] ; then STATUS=$(echo $OUTPUT | cut -d',' -f4 | sed 's/ //g') fi -----Oorspronkelijk bericht----- Van: Steffan <mailinglist at tikklik.nl> Verzonden: donderdag 11 oktober 2018 16:22 Aan: 'xymon at xymon.com' <xymon at xymon.com> Onderwerp: xymon at xymon.com Hello Damien, I treid your script. When running in testmode it works fine. It is creating /var/lib/xymon/tmp/xymon-hardware.msg But when running as a deamon i am getting /bin/cat: /var/lib/xymon/tmp/xymon-hardware.msg: No such file or directory Any idees? Steffan -----Oorspronkelijk bericht----- Hi Théo, With all due modesty, I wrote something that could match with your expectations : https://wiki.xymonton.org/doku.php/monitors:hardware_sensors Regards, Damien Martins

2 1

acknowledgements does not survive xymon restart
by EDSchminke＠Hormel.com 01 Nov '18

01 Nov '18

What config changes are you making that requires such frequent restarts? Changes to hosts.cfg, alerts.cfg, analysis.cfg, client-local.cfg; these are files that get changed most frequently in my environment. None of which require a restart to pick up the changes. I think the only one that *does* need a restart, would be xymonserver.cfg, and the only component that would need to be restarted would be xymond, not the full stack. Erik D. Schminke | Associate Systems Programmer Hormel Foods Corporation | One Hormel Place | Austin, MN 55912 Phone: (507) 434-6817 edschminke at hormel.com | www.hormelfoods.com

1 0