October 2018 - Xymon - Xymon mailman web

Capture and send data To Elasticsearch and Kibana
by francois.outteryck＠soprasteria.com 27 Sep '22

27 Sep '22

Hi Peter, Examples of task.cfg configuration with status and stachg events : [capture_status] ENVFILE /home/xymon/server/etc/xymonserver.cfg NEED xymond CMD xymond_channel --channel=status /home/xymon/server/ext/capture.sh --log=$XYMONSERVERLOGS/xymond_task_capture.log LOGFILE /var/log/xymon/lunch_capture.log [capture_stachg] ENVFILE /home/xymon/server/etc/xymonserver.cfg NEED xymond CMD xymond_channel --channel=stachg /home/xymon/server/ext/capture.sh --log=$XYMONSERVERLOGS/xymond_task_capture_stachg.log LOGFILE /var/log/xymon/lunch_capture_stachg.log Capture.sh script simple made to call a php script : #!/bin/sh /usr/bin/php /var/www/kibana/capture.php $@ </dev/stdin >>/var/log/xymon/xymond_capture_php.log 2>&1 And capture.php make all job : <?php date_default_timezone_set('Europe/Paris'); $TODO=FALSE; $ARRAY_COLLECTOR=array(); $COLLECTOR=null; while (FALSE !== ($line = fgets(STDIN))) if ($line!='') { $tab=reduce_array($line); if (sizeof($tab)==0) continue; if ($line=="@@\n") { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } } else if (substr($tab[0],0,8)=='@@stachg') { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } /* 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 /* @@stachg#seq|timestamp|sender|origin|hostname|testname|expiretime|color|prevcolor|changetime|disabletime|disablemsg|downtimeactive|clienttstamp|modifiers */ $COLLECTOR='stachg'; $metadata=explode('|',$tab[0]); $sender=$metadata[2]; $hostname=$metadata[3]; $metadata=array( 'Collector'=>$COLLECTOR, 'Sender'=>$metadata[2], 'ServerName'=>$metadata[4], 'Type'=>$metadata[5], 'Status'=>$metadata[7], 'PrevStatus'=>$metadata[8], 'LogTime'=>$metadata[1], 'ValidTime'=>$metadata[6], 'LastChange'=>$metadata[9], 'DisableTime'=>$metadata[10], 'DisableMSg'=>$metadata[11], 'Message'=>'' ); $id=$metadata['ServerName'].'_'.$metadata['Type'].'_'.$meta['LastChange']; $ARRAY_COLLECTOR=null; $ARRAY_COLLECTOR=array(); $TODO=TRUE; } else if (substr($tab[0],0,8)=='@@status') { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } /* 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 /* @@status|timestamp|sender|origin|hostname|testname|expiretime|color|testflags|prevcolor|changetime|ackexpiretime|ackmessage|disableexpiretime|disablemessage|clientmsgtstamp|flapping */ $COLLECTOR='status'; $metadata=explode('|',$tab[0]); $sender=$metadata[2]; $hostname=$metadata[3]; $metadata=array( 'Collector'=>$COLLECTOR, 'Sender'=>$metadata[2], 'ServerName'=>$metadata[4], 'Type'=>$metadata[5], 'Status'=>$metadata[7], 'LogTime'=>$metadata[1], 'ValidTime'=>$metadata[6], 'LastChange'=>$metadata[10], 'DisableTime'=>$metadata[13], 'AckTime'=>$metadata[11], 'DisableMSg'=>$metadata[14], 'Message'=>'' ); $id=$metadata['ServerName'].'.'.$metadata['Type']; $ARRAY_COLLECTOR=null; $ARRAY_COLLECTOR=array(); $TODO=TRUE; } else { if (substr($tab[0],0,2)=='@@') { if ($TODO) { $metadata['Message']=implode('',$ARRAY_COLLECTOR); SendData($id,$metadata,$COLLECTOR); $TODO=FALSE; $COLLECTOR=null; } } if ($TODO) $ARRAY_COLLECTOR[]=$line; } } function CallAPI($method, $url, $data = false) { $curl = curl_init(); switch ($method) { case "POST": curl_setopt($curl, CURLOPT_POST, 1); if ($data) curl_setopt($curl, CURLOPT_POSTFIELDS, $data); break; case "PUT": curl_setopt($curl, CURLOPT_PUT, 1); break; default: if ($data) $url = sprintf("%s?%s", $url, http_build_query($data)); } curl_setopt($curl, CURLOPT_URL, $url); curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1); $result = curl_exec($curl); curl_close($curl); return $result; } function reduce_array($line) { $tab=explode(' ',$line); $nr=array(); for ($i=0;$i<sizeof($tab);$i++) if (trim($tab[$i])!='') $nr[]=trim($tab[$i]); return $nr; } function SendData($id,$cc,$COLLECTOR=null) { if ($COLLECTOR==null) return; $d=new DateTime(); if ($cc['LastChange']!='') {$d->setTimestamp($cc['LastChange']);$cc['LastChange']=$d->format('c');} else {$cc['LastChange']='NaN';} if ($cc['LogTime']!='') {$d->setTimestamp($cc['LogTime']);$cc['LogTime']=$d->format('c');} else {$cc['LogTime']='NaN';} if ($cc['ValidTime']!='') {$d->setTimestamp($cc['ValidTime']);$cc['ValidTime']=$d->format('c');} else {$cc['ValidTime']='NaN';} if (isset($cc['AckTime'])) { if ($cc['AckTime']!='') {$d->setTimestamp($cc['AckTime']);$cc['AckTime']=$d->format('c');} else {$cc['AckTime']='NaN';} } if ($cc['DisableTime']!='') {$d->setTimestamp($cc['DisableTime']);$cc['DisableTime']=$d->format('c'); } else {$cc['DisableTime']='NaN';} $data = json_encode($cc); $data=str_replace('"NaN"','null',$data); echo $id.'=>'.$data."\n"; $url="http://127.0.0.1:9200/xymon/".$COLLECTOR."/".$id; $res=CallAPI("POST",$url,$data); } ?> De : Peter Welter [mailto:peter.welter at gmail.com] Envoyé : vendredi 23 décembre 2016 14:45 À : OUTTERYCK Francois Cc : xymon at xymon.com Objet : Re: [Xymon] Capture and send data To Elasticsearch and Kibana Hi Francois, Looks good, your sample. I am very interested in your integration efforts. How do you select what is going to be inserted in the ELK stack? All status messages that Xymon receives? And could you provide an example of the xymond_channel block in you task.cfg and the capture.sh? Tasks.cfg probably is something like: [es] ... CMD xymond_channel --channel=status /home/xymon/server/ext/capture.sh ... And the capture.sh contains some curl script to the ELK stack? Regards, Peter 2016-12-14 18:15 GMT+01:00 OUTTERYCK Francois <francois.outteryck at soprasteria.com<mailto:francois.outteryck at soprasteria.com>>: Hello, I just do a small work with Xymon in order to send status data to Elasticsearch. And with Kibana reporting is easy. How it work ? Simple : With capture of status message (xymond_channel --channel=status /home/xymon/server/ext/capture.sh ) script encode status message in json and send as document in elasticSearch. Example of Mapping document status in elasticsearch : "status"=> array( "properties"=>array( "ServerName"=> array("type"=> "string"), "Type"=> array("type"=> "string"), "Status"=> array("type"=> "string"), "LastChange"=> array("type"=> "date","format"=> "strict_date_optional_time"), "LogTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "ValidTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "AckTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "DisableTime"=> array("type"=> "date","format"=> "strict_date_optional_time"), "Sender"=> array("type"=> "string"), "DisableMSg"=> array("type"=> "string"), "Message"=> array("type"=> "string") ) ) All is done with a 130 lines script. So simple to integrate in existing environment and so powerfull usage of Xymon/elasticsearch/Kibana For those who don’t know kibana : https://www.elastic.co/products/kibana [cid:image001.png at 01D25EA3.F74489F0] _______________________________________________ Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon

2 1

Xymon and apache 2.4.35 security problem
by dl1025＠att.com 09 Oct '19

09 Oct '19

I recently upgraded to apache 2.4.35 and was having some issues with password file to secure xymon-seccgi. I got not get apache to read the password file. To get it to work I had to change from Require all granted to Require all denied. Now, it works. I get prompted to enter username and password. Here is the section from my httpd.conf file for your reference if you will run into similar problems. ScriptAlias /xymon-seccgi/ "/opt/app/workload/bbapp/bb/cgi-secure/" <Directory "/opt/app/workload/bbapp/bb/cgi-secure"> AllowOverride None Options ExecCGI Includes <IfModule mod_authz_core.c> # Apache 2.4+ Require all denied </IfModule> <IfModule !mod_authz_core.c> Order deny,allow Allow from all </IfModule> # Password file where users with access to these scripts are kept. # Although expected in $XYMONHOME/etc/ by the useradm and chpasswd # scripts, files here can be read with the "config" message type, # which allows status-privileged clients to read arbitrary regular files # from the directory. # # This file should be owned and readable only by the apache server user, # and ideally merely a symlink to a location outside of $XYMONHOME/etc/ # # Create it with: # htpasswd -c /opt/app/workload/bbapp/bb/server/etc/xymonpasswd USERNAME # chown apache:apache /opt/app/workload/bbapp/bb/server/etc/xymonpasswd # chmod 640 /opt/app/workload/bbapp/bb/server/etc/xymonpasswd # Add more users / change passwords with: "htpasswd /opt/app/workload/bbapp/bb/server/etc/xymonpasswd USERNAME" # # You can also use a group file to restrict admin access to members of a # group, instead of anyone who is logged in. In that case you must setup # the "xymongroups" file, and change the "Require" settings to require # a specific group membership. See the Apache docs for more details. AuthUserFile /opt/app/workload/bbapp/bb/server/etc/xymonpasswd AuthGroupFile /opt/app/workload/bbapp/bb/server/etc/xymongroups AuthType Basic AuthName "Xymon Administration" # "valid-user" restricts access to anyone who is logged in. Require valid-user # "group admins" restricts access to users who have logged in, AND # are members of the "admins" group in xymongroups. # Require group admins </Directory> I also enabled the following modules. LoadModule authn_file_module modules/mod_authn_file.so LoadModule authn_dbm_module modules/mod_authn_dbm.so LoadModule authn_anon_module modules/mod_authn_anon.so LoadModule authn_core_module modules/mod_authn_core.so LoadModule authz_host_module modules/mod_authz_host.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule authz_core_module modules/mod_authz_core.so LoadModule access_compat_module modules/mod_access_compat.so LoadModule auth_basic_module modules/mod_auth_basic.so LoadModule reqtimeout_module modules/mod_reqtimeout.so LoadModule filter_module modules/mod_filter.so LoadModule mime_module modules/mod_mime.so LoadModule log_config_module modules/mod_log_config.so LoadModule env_module modules/mod_env.so LoadModule headers_module modules/mod_headers.so LoadModule setenvif_module modules/mod_setenvif.so LoadModule version_module modules/mod_version.so LoadModule unixd_module modules/mod_unixd.so LoadModule status_module modules/mod_status.so LoadModule autoindex_module modules/mod_autoindex.so LoadModule cgid_module modules/mod_cgid.so LoadModule dir_module modules/mod_dir.so LoadModule alias_module modules/mod_alias.so LoadModule rewrite_module modules/mod_rewrite.so

2 3

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

[Patch] xymond_rrd crash when parsing Linux ifconfig data
by steve＠opendium.com 22 Feb '19

22 Feb '19

This patch addresses two problems: 1. For Linux clients, do_ifstat_rrd parses the ifconfig output using the regex: ([a-z0-9]+(_[0-9]+)?:*|lo:?)\s pickdata() is called like this: pickdata(bol, ifstat_linux_pcres[0], 1, &ifname) With a network interface name such as "foo1", the regex produces 2 results: 0: "foo1 " 1: "foo1" pickdata() discards result 0 and assigns result 1 ("foo1") to the ifname parameter as expected. With a network interface name such as "foo_1", the regex produces 3 results: 0: "foo_1 " 1: "foo_1" 2: "_1" pickdata() discards result 0, assigns result 1 ("foo_1") to the ifname parameter and then tries to assign result 2 ("_1") to the next parameter in the variable argument list. Since there it no such parameter, this results in a segmentation fault and xymond_rrd crashes. The attached patch adds a "num_args" parameter to pickdata() to tell it how many arguments are in the variable argument list and ensure it never rolls off the end of that list. 2. I have some clients with network interface names in the form "foo.5", "foo_bar" and "foo-bar" ("eth0.5" is especially common when eth0 is carrying an 802.1q trunk, for example). Xymon does not collect statistics on those network interfaces because they don't match the regex. This patch relaxes the regex a bit so that it matches these network interfaces. -- - Steve Hill Technical Director Opendium Online Safety / Web Filtering http://www.opendium.com Enquiries: sales at opendium.com +44-1792-824568 Support: support at opendium.com +44-1792-825748 Opendium Limited is a company registered in England and Wales. Company No. 5465437 Highfield House, 1 Brue Close, Bruton, Somerset, BA10 0HY, England.

2 1

DISPLAYGROUP fails in analysis.cfg
by doughnut＠doughnut.net 01 Feb '19

01 Feb '19

I have a xymon server running "Debian GNU/Linux 9 (stretch)" with xymon 4.3.28-2. I'm having bad luck getting DISPLAYGROUP to work in analysis.cfg. It seems to only match on the first 7 characters. I also see this problem on "Debian GNU/Linux 8 (jessie)" with xymon 4.3.17-6+deb8u1. Below, I've shown that the display group is set, and that the analysis.cfg file is being parsed correctly by xymon, yet the the svcstatus page only shows the shortest of the DISPLAYGROUP enabled lines. root at misc-ten105-test:/etc/xymon# egrep -H Testnet.Database.Servers hosts.cfg hosts.cfg:group Testnet Database Servers root at misc-ten105-test:/etc/xymon# cat analysis.d/davetest.cfg HOST=* EXCLASS=linux PROC davetest-nonlinux 1 150 yellow PROC davetest-Testnet.Database.Servers 1 150 yellow DISPLAYGROUP=%(Testnet.Database.Servers) PROC davetest-Database 1 150 yellow DISPLAYGROUP=%(Database) PROC davetest-Databas 1 150 yellow DISPLAYGROUP=%(Databas) PROC davetest-Testnet.Database 1 150 yellow DISPLAYGROUP=%(Testnet.Database) PROC davetest-Testnet.Data 1 150 yellow DISPLAYGROUP=%(Testnet.Data) PROC davetest-Testnet.D 1 150 yellow DISPLAYGROUP=%(Testnet.D) PROC davetest-Testnet. 1 150 yellow DISPLAYGROUP=%(Testnet.) PROC davetest-Testnet 1 150 yellow DISPLAYGROUP=%(Testnet) PROC davetest-Testne 1 150 yellow DISPLAYGROUP=%(Testne) root at misc-ten105-test:/etc/xymon# sudo -u xymon xymoncmd xymond_client --dump-config | grep davetest [...] PROC davetest-nonlinux 1 150 yellow HOST=* EXCLASS=linux (line: 375) PROC davetest-Testnet.Database.Servers 1 150 yellow HOST=* DISPLAYGROUP=%(Testnet.Database.Servers) EXCLASS=linux (line: 377) PROC davetest-Database 1 150 yellow HOST=* DISPLAYGROUP=%(Database) EXCLASS=linux (line: 378) PROC davetest-Databas 1 150 yellow HOST=* DISPLAYGROUP=%(Databas) EXCLASS=linux (line: 379) PROC davetest-Testnet.Database 1 150 yellow HOST=* DISPLAYGROUP=%(Testnet.Database) EXCLASS=linux (line: 380) PROC davetest-Testnet.Data 1 150 yellow HOST=* DISPLAYGROUP=%(Testnet.Data) EXCLASS=linux (line: 381) PROC davetest-Testnet.D 1 150 yellow HOST=* DISPLAYGROUP=%(Testnet.D) EXCLASS=linux (line: 382) PROC davetest-Testnet. 1 150 yellow HOST=* DISPLAYGROUP=%(Testnet.) EXCLASS=linux (line: 383) PROC davetest-Testnet 1 150 yellow HOST=* DISPLAYGROUP=%(Testnet) EXCLASS=linux (line: 384) PROC davetest-Testne 1 150 yellow HOST=* DISPLAYGROUP=%(Testne) EXCLASS=linux (line: 385) root at misc-ten105-test:/etc/xymon# lynx -dump -nolist 'http://localhost/xymon-cgi/svcstatus.sh?HOST=balin2012.collegenet.testnet&S…' [...] Xymon balin2012.mydomain.testnet - procs Wed Jul 11 13:29:40 2018 _______________________________________________________________________ HISTORY Wed Jul 11 13:29:40 2018 - Processes NOT ok yellow davetest-nonlinux (found 0, req. between 1 and 150) yellow davetest-Testnet (found 0, req. between 1 and 150) yellow davetest-Testne (found 0, req. between 1 and 150) Status unchanged in 8 days, 21 hours, 22 minutes Status message received from 10.101.1.35 Client data available

2 3

Project: Xymon dashboard
by dominique.frise＠unil.ch 08 Nov '18

08 Nov '18

Hi, My colleagues found this addon awesome but have a small feature request. Would it be possible to integrate the current date/time (like on all Xymon pages) on the same line as the title ? Thanks, Dominique ________________________________ De : Xymon <xymon-bounces at xymon.com> de la part de Christian Herzog <herzog at phys.ethz.ch> Envoyé : jeudi, 28 juin 2018 15:36 À : xymon at xymon.com Objet : Re: [Xymon] Project: Xymon dashboard Hi all, I just fixed a major issue that prevented Xymondash from properly working for some of you. If it didn't work yesterday, you might want to give the current commit another go. best, -Christian On Tue, Jun 26, 2018 at 06:15:11PM +0200, Dirk Kastens wrote: > Hi, > > I just got it to work on my system. > > - I had to install python 3.6. > - I had to copy the cgi scripts to /usr/share/xymon/cgi-bin, changing > main.js: > > const XYMONURL = '/xymon-cgi/svcstatus.sh'; > const XYMONACKURL = '/xymon-cgi/xymon-ack'; > const XYMONJSONURL = '/xymon-cgi/xymon2json'; > > - I had to change the path to xymon in xymon2json on line 77: > > return ['/usr/bin/xymon 0 ' + cmd] > > I didn't make any further testing for the moment. > > -- > Viele Gruesse, > > Dirk Kastens > Universitaet Osnabrueck, Rechenzentrum (Computer Center) > Albrechtstr. 28, 49069 Osnabrueck, Germany > Tel.: +49-541-969-2347, FAX: -2470 > > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon -- Dr. Christian Herzog <herzog at phys.ethz.ch> support: +41 44 633 26 68 IT Services Group, HPT H 8 voice: +41 44 633 39 50 Department of Physics, ETH Zurich 8093 Zurich, Switzerland http://nic.phys.ethz.ch/ _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

2 1

Xymon client configuration for Ubuntu
by Andy.Farrior＠victoriacollege.edu 31 Oct '18

31 Oct '18

How are Ubuntu users configuring Xymon to monitor any log files? I just installed 18.04.1 LTS. Are you modifying Xymon's client-local.cfg file to match whatever OS Ubuntu is sending to Xymon or are you modifying the rsyslog config files to generate a /var/log/messages file? Aside - Wish this was configured ahead of time as a part of the Ubuntu Xymon packages. After installing the Ubuntu Xymon packages, Xymon is matching an OS configured to monitor /var/log/messages in the client-local.cfg file. However, the stock Ubuntu distribution does not generate a /var/log/messages file. According to the /etc/rsyslog.d/50-default.conf file, Ubuntu by default generates these log files: # Default rules for rsyslog. # # For more information see rsyslog.conf(5) and /etc/rsyslog.conf # # First some standard log files. Log by facility. # auth,authpriv.* /var/log/auth.log *.*;auth,authpriv.none -/var/log/syslog #cron.* /var/log/cron.log #daemon.* -/var/log/daemon.log kern.* -/var/log/kern.log #lpr.* -/var/log/lpr.log mail.* -/var/log/mail.log #user.* -/var/log/user.log # # Logging for the mail system. Split it up so that # it is easy to write scripts to parse these files. # #mail.info -/var/log/mail.info #mail.warn -/var/log/mail.warn mail.err /var/log/mail.err # # Some "catch-all" log files. # #*.=debug;\ # auth,authpriv.none;\ # news.none;mail.none -/var/log/debug #*.=info;*.=notice;*.=warn;\ # auth,authpriv.none;\ # cron,daemon.none;\ # mail,news.none -/var/log/messages # # Emergencies are sent to everybody logged in. # *.emerg :omusrmsg:* # # I like to have messages displayed on the console, but only on a virtual # console I usually leave idle. # #daemon,mail.*;\ # news.=crit;news.=err;news.=notice;\ # *.=debug;*.=info;\ # *.=notice;*.=warn /dev/tty8 Another option would be to create a file like /etc/rsyslog.d/xymon.conf # # consolidate logs into single file for Xymon to monitor *.=info;*.=notice;*.=warn;\ auth,authpriv.none;\ cron,daemon.none;\ mail,news.none -/var/log/messages If that would be agreeable, it could conceivably be included in the Ubuntu Xymon packages. Thx, Andy Andy Farrior Director of Technology Services Victoria College 2200 E Red River Victoria, TX 77901 Andy.Farrior at VictoriaCollege.edu Office: 361.582.2547 Fax: 361.572.6492

1 0

Question from a Xymon newbie on scheduling Xymon please
by kern_doe＠yahoo.com 24 Oct '18

24 Oct '18

Hello gurus,How do I program in this file clientlaunch.cfg to run a a specific time instead of by interval (for example: INTERVAL 5m)?Thank you in advance.Kern -- Let's go GreenThis email contains 100% recycled electrons.

2 1

[External] PS client enhancement of ServiceCheck
by storerr＠nibco.com 22 Oct '18

22 Oct '18

Tim, does starting powershell.exe with the command line parameter of "-Version 2.0" help at all? -----Original Message----- Date: Thu, 18 Oct 2018 12:24:10 -0400 From: Timothy Williams <tlwilliams4 at vcu.edu> To: zak.beck at accenture.com Cc: xymon at xymon.com Subject: Re: [Xymon] [External] PS client enhancement of ServiceCheck Message-ID: <CAMVnr4NC7B7oEMYcOd5bU_JN5b58R9pmgZpZ1mLGfb+NoJY_hw at mail.gmail.com> Content-Type: text/plain; charset="utf-8" Zak, all I pushed my revised script out to a few servers. Most all have upgraded powershell, but a few 2008 & 2008R2 still have PS v2. Script will not start, but no clear error about why. It runs fine on the '08 servers with PS v3, v4, or v5. The ones with v2 seem to be running the script in a v1 instance. Error: Program C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe for service XymonPSClient exited with return code 4294770688. Any way to force it to run in v2? Or do you see anything in the new function that would choke v1? On Tue, Oct 9, 2018 at 9:28 AM Timothy Williams <tlwilliams4 at vcu.edu> wrote: > Sounds good to me. I've only been powershell coding a year, so I'm > sure there are more elegant and efficient ways than what I've devised. > Tim > ________________________________ CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.

2 1

PS client enhancement of ServiceCheck
by tlwilliams4＠vcu.edu 18 Oct '18

18 Oct '18

All, I've started using the servicecheck function to restart services more extensively lately. However, I encountered a department which needs to shut down a monitored service during a maintenance window, and the servicecheck would restart it. Thus, I created a 'noservicecheck' item in the client-local.cfg process. Hope you find it useful enough to add to next PS version. Tim Williams Virginia Commonwealth University Computing Center Here is a section to add to the XymonPSClient.doc help file: noservicecheck noservicecheck:SERVICENAME:DAYOFWEEK:STARTHOUR:DURATION Checks if a specified Windows Service servicecheck exists and suppresses it during the specified Maintenance Window. Window can span multiple days, as specified by Duration, but would terminate if script is restarted after initiation day/hour. SERVICENAME – name of the service to check for a ‘servicecheck’ statement. DAYOFWEEK – numeric day of the week, where Sunday = 0, Monday = 1, etc. STARTHOUR – military hour to start the Maintenance Window, 0 for midnight up to 23 DURATION – how long in hours a servicecheck should not institute a restart Examples: servicecheck:Sophos Message Router:10 noservicecheck:Sophos Message Router:0:5:1 (no restart starting first scan after Sunday 5AM to first scan after 6AM) *Here are the revisions in XymonClient.PS1:* *Add* following to declared variables about line 48: $MaintChecks = @{} *Add* line to function XymonClientConfig($cfglines) for new item to be recognized: -or $l -match '^noservicecheck:' ` *Replace* 'servicecheck' function: function XymonServiceCheck { WriteLog "Executing XymonServiceCheck" if ($script:clientlocalcfg_entries -ne $null) { $servicecfgs = @($script:clientlocalcfg_entries.keys | where { $_ -match '^servicecheck' }) foreach ($service in $servicecfgs) { # parameter should be 'servicecheck:<servicename>:<duration>' $checkparams = $service -split ':' # validation if ($checkparams.length -ne 3) { WriteLog "ERROR: not enough parameters (should be servicecheck:<servicename>:<duration>) - $checkparams[1]" continue } else { $duration = $checkparams[2] -as [int] if ($checkparams[1] -eq '' -or $duration -eq $null) { WriteLog "ERROR: config error (should be servicecheck:<servicename>:<duration>) - $checkparams[1]" continue } } # check for maintenance window $serviceexclds = @($script:clientlocalcfg_entries.keys | where { $_ -match '^noservicecheck' }) foreach ($maintservice in $serviceexclds) { # parameter should be 'noservicecheck:<servicename>:<numeric day of week Sun=0>:<military start hour>:<duration in Hours>' $checkMparams = $maintservice -split ':' if ($checkparams[1] -eq $checkMparams[1]){ # validation of number of parameters if ($checkMparams.length -ne 5) { WriteLog ("ERROR: not enough parameters (noservicecheck:<servicename>:<numeric day of week Sun=0>:<military start hour>:<duration Hrs> {0}" -f $checkMparams[1]) continue } else { # get values $MaintDay = $checkMparams[2] -as [int] if($MaintDay -eq 0){$MaintWeekDay = "Sunday"} if($MaintDay -eq 1){$MaintWeekDay = "Monday"} if($MaintDay -eq 2){$MaintWeekDay = "Tuesday"} if($MaintDay -eq 3){$MaintWeekDay = "Wednesday"} if($MaintDay -eq 4){$MaintWeekDay = "Thursday"} if($MaintDay -eq 5){$MaintWeekDay = "Friday"} if($MaintDay -eq 6){$MaintWeekDay = "Saturday"} $MaintStartHour = $checkMparams[3] -as [int] $MaintDuration = $checkMparams[4] -as [int] # validation of basic values if ($checkMparams[1] -eq '' -or $MaintDuration -eq $null -or ($MaintDay -inotin 0..6) -or ($MaintStartHour -inotin 0..23)) { WriteLog ("ERROR: config error (noservicecheck:<servicename>:<numeric day of week Sun=0>:<military start hour>:<duration Hrs>) {0}" -f $checkMparams[1]) continue } } if (((get-date).DayofWeek -eq $MaintWeekDay) -and ((get-date).Hour -eq $MaintStartHour) ) { if ($script:MaintChecks.ContainsKey($checkMparams[1])) { $MaintWindowEnd = $script:MaintChecks[$checkMparams[1]].AddHours($MaintDuration) if ((get-date) -lt $MaintWindowEnd){ WriteLog (" Maintenance: Skipping Service Check until after $($MaintWindowEnd) for {0}" -f $checkMparams[1]) continue }Else{ clear.variable $script:MaintChecks } } else{ WriteLog ("Not seen this NoServiceCheck before, starting Maintenance Window now for {0}" -f $checkMparams[1]) $hourTop = (get-date).Minute $script:MaintChecks[$checkMparams[1]] = (get-date).AddMinutes(-($hourTop)) continue } } # end of maintenance hold } WriteLog ("Checking service {0}" -f $checkparams[1]) $winsrv = Get-Service -Name $checkparams[1] if ($winsrv.Status -eq 'Stopped') { writeLog ("!! Service {0} is stopped" -f $checkparams[1]) if ($script:ServiceChecks.ContainsKey($checkparams[1])) { $restarttime = $script:ServiceChecks[$checkparams[1]].AddSeconds($duration) writeLog "Seen this service before; restart time is $restarttime" if ($restarttime -lt (get-date)) { writeLog (" -> Starting service {0}" -f $checkparams[1]) $winsrv.Start() } } else { writeLog "Not seen this service before, setting restart time -1 hour" $script:ServiceChecks[$checkparams[1]] = (get-date).AddHours(-1) } } elseif ('StartPending', 'Running' -contains $winsrv.Status) { writeLog " -Service is running, updating last seen time" $script:ServiceChecks[$checkparams[1]] = get-date } } } } }

2 3