April 2019 - Xymon - Xymon mailman web

Roadmap/GitHub?/IPv6
by herzog＠phys.ethz.ch 17 Apr '19

17 Apr '19

hey JC, thanks for the status update. I've done some pretty extensive IPv6 xymon testing 6 years ago ([1] and later private emails with Henrik) and found IPv6 support to be in pretty good shape in then 4.3.99.tgz. However, none of this seems to be in 4.3.28. Since we're now once again (and for reals this time!) on the verge of introducing IPv6 into our networks, I'll have to come back to working on xymon IPv6. I'd be happy to do all sorts of testing, but where to start? I can't even find any 4.4 (alpha) tree out there. Can you advise? thanks and best regards, -Christian [1] https://xymon.xymon.narkive.com/BbXHR8kH/status-of-ipv6-support On Fri, Mar 08, 2019 at 06:46:52AM -0800, Japheth Cleaver wrote: > I think a larger discussion on Xymon's roadmap in terms of Docker and > container analysis is definitely something warranted. A host-based approach > tends to invite individualized responses to coordination among varying > levels of architecture (including both host -> hypervisor, baremetal (eg, > DRAC) -> host, and hypervisor "status" reporting), but containers' typically > ephemeral nature could merit a distinct reference point -- or not, if it's > desired to have them persistently reportable. Host-Svc may or may not make > sense there. > > I tend to agree that a move to Github may be helpful here at this point - > athough with the various community issues people have had with GH since MS's > purchase, it seems there has been a bit of an outcry, I'm not sure there's > much SF will end up being able to capitalize on. It would certainly make > PR's easier to coordinate and invite more interaction. > > The largest stalling point on the roadmap here was indeed the IPv6 > transition. I think things are releasable in an Alpha state, and that was > the intent at the last release, but it's been difficult to find any site > using IPv6 at sufficient scale who could help with the testing process. > That's a bit of a Catch-22 though, and perhaps it would be best to release > an easy reference point for future testing and go from there - along with > the various other patches that I've received. (And this does raise the > question of what the next highest priorities out there will be.) > > Regards, > -jc > > -- 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/

6 20

Xymon EXTIME configuration
by mtpins＠nndev.org 17 Apr '19

17 Apr '19

[ resending to the list, the original only went to the original poster ] >One of our clients wanted suspend process monitoring during a specific time >period. For their production server, they >requested EXTIME=0123456:1750:2110. That seems to be working as expected. >However, for their test server, they wanted an additional EXTIME for the >entire weekend. They want this to start at 5:50 PM on Friday and end at >7:00 AM on Monday. We've tried to set this up in three different ways, but >can't seem to get it to work. So far, our configuration has resulted in >them getting 5 emails per alert. The latest settings are listed below. We >would appreciate any assistance you can provide. >EXTIME=1234:1750:2110 >EXTIME=5:1750:2359 >EXTIME=6:0000:2359 >EXTIME=0:0000:2359 >EXTIME=1:0000:0700 You want them all on one line. For the production box: EXTIME=*:1750:2110 And for test: EXTIME=1234:1750:2110,5:1750:2359,60:0000:2359,1:0000:0700

2 1

Xymon EXTIME configuration
by rstyson＠vcu.edu 16 Apr '19

16 Apr '19

One of our clients wanted suspend process monitoring during a specific time period. For their production server, they requested EXTIME=0123456:1750:2110. That seems to be working as expected. However, for their test server, they wanted an additional EXTIME for the entire weekend. They want this to start at 5:50 PM on Friday and end at 7:00 AM on Monday. We've tried to set this up in three different ways, but can't seem to get it to work. So far, our configuration has resulted in them getting 5 emails per alert. The latest settings are listed below. We would appreciate any assistance you can provide. EXTIME=1234:1750:2110 EXTIME=5:1750:2359 EXTIME=6:0000:2359 EXTIME=0:0000:2359 EXTIME=1:0000:0700 Many thanks, Bob

1 0

WinPSClient msgs
by tolomelli.luca＠gmail.com 14 Apr '19

14 Apr '19

Using WinPSClient can I set the analysis.cfg based upon some events ID? If so, how?

1 0

Call for 4.3.29 Patches
by abs＠shadymint.com 12 Apr '19

12 Apr '19

Hi JC, On Tue, Mar 26, 2019 at 01:37:32PM -0700, Japheth Cleaver wrote: > I'm pushing for a release of 4.3.29 relatively soon. These 2 changes allow you to run the client from a shared directory. *** ./client/runclient.sh.FCS Wed Jan 27 21:12:32 2016 --- ./client/runclient.sh Fri Apr 12 07:14:38 2019 *************** *** 86,92 **** rm -f $XYMONCLIENTHOME/logs/clientlaunch.$MACHINEDOTS.pid fi ! $XYMONCLIENTHOME/bin/xymonlaunch --config=$XYMONCLIENTHOME/etc/clientlaunch.cfg --log=$XYMONCLIENTHOME/logs/clientlaunch.log --pidfile=$XYMONCLIENTHOME/logs/clientlaunch.$MACHINEDOTS.pid if test $? -eq 0; then echo "Xymon client for $SERVEROSTYPE started on $MACHINEDOTS" else --- 86,92 ---- rm -f $XYMONCLIENTHOME/logs/clientlaunch.$MACHINEDOTS.pid fi ! $XYMONCLIENTHOME/bin/xymonlaunch --config=$XYMONCLIENTHOME/etc/clientlaunch.cfg --log=$XYMONCLIENTHOME/logs/clientlaunch.$MACHINEDOTS.log --pidfile=$XYMONCLIENTHOME/logs/clientlaunch.$MACHINEDOTS.pid if test $? -eq 0; then echo "Xymon client for $SERVEROSTYPE started on $MACHINEDOTS" else *** ./client/clientlaunch.cfg.FCS Wed Apr 10 09:40:32 2019 --- ./client/clientlaunch.cfg Fri Apr 12 07:14:55 2019 *************** *** 17,28 **** DISABLED ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg CMD $XYMONCLIENTHOME/bin/msgcache --no-daemon --pidfile=$XYMONCLIENTLOGS/msgcache.pid ! LOGFILE $XYMONCLIENTLOGS/msgcache.log # The main client task [client] ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg CMD $XYMONCLIENTHOME/bin/xymonclient.sh ! LOGFILE $XYMONCLIENTLOGS/xymonclient.log INTERVAL 5m --- 17,28 ---- DISABLED ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg CMD $XYMONCLIENTHOME/bin/msgcache --no-daemon --pidfile=$XYMONCLIENTLOGS/msgcache.pid ! LOGFILE $XYMONCLIENTLOGS/msgcache.$MACHINEDOTS.log # The main client task [client] ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg CMD $XYMONCLIENTHOME/bin/xymonclient.sh ! LOGFILE $XYMONCLIENTLOGS/xymonclient.$MACHINEDOTS.log INTERVAL 5m -- Andy

2 1

clientconfig.cfg - local configuration check definitions
by storerr＠nibco.com 12 Apr '19

12 Apr '19

Zak (or anyone else who knows), If I want to configure a Windows server running the XymonPSClient using the clientconfig.cfg file, where can I find documentation on how to configure each of the checks? In particular, I'd like to run checks on services (SVCS), processes (PROCS) and files (FILES). If you have examples, I would appreciate seeing them. I understand I have to configure alerting on the Xymon server. If you feel strongly about client configuration belonging on the Xymon server, feel free to point me at documentation for that too. Thanks. Ray Storer ________________________________ 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.

3 4

Call for 4.3.29 Patches
by abe＠deuxchevaux.org 12 Apr '19

12 Apr '19

Hi, On Tue, Mar 26, 2019 at 01:37:32PM -0700, Japheth Cleaver wrote: > I'm pushing for a release of 4.3.29 relatively soon. I've been > trying to go through the backlog to identify un-applied patches, but > I know there are some that I'm missing. If you have build fixes or > runtime changes that have not yet been put in in 4.3.29 already > (see: https://sourceforge.net/p/xymon/code/HEAD/tree/branches/4.3.29/Changes) > I'd appreciate if you could point them out. One thing I noticed very recently which might be worth considering for 4.3.29: xymond/etcfiles/xymonserver.cfg.DIST contains: NTPDATEOPTS="-u -q -p 1" If on the host running xymond, ntpdate from the ntpsec project is installed, then I just get the warning: $ ntpdate -u -q -p 1 127.0.0.1 ntpdate: -p is no longer supported. 2019-04-11 19:22:28.524619 (-0200) +0.000002 +/- 0.000053 127.0.0.1 s4 no-leap $ So it might be an idea to drop the "-p 1" completely. Kind regards, Axel -- PGP: 2FF9CD59612616B5 /~\ Plain Text Ribbon Campaign, http://arc.pasp.de/ Mail: abe at deuxchevaux.org \ / Say No to HTML in E-Mail and Usenet Mail+Jabber: abe at noone.org X https://axel.beckert.ch/ / \ I love long mails: https://email.is-not-s.ms/

4 5

conn-check too slow?
by christian.becker＠rhein-zeitung.net 11 Apr '19

11 Apr '19

Hello out there, we have a huge number of Windows virtual machines that run on HyperV. All of them are using bbwin to report their health to our Xymon server. If such a Windows virtual machine reboots, either planned or unplanned, it reboots that fast in HyperV, that Xymon doesn't recognize this in the conn or cpu test, but only in the uptime test which goes yellow for the time as defined in analysis.cfg. How do you guys handle this, when you want to know if a Windows virtual machine has rebooted? Is alerting on uptime the only way for a reboot? Here's our xymonnet section from xymonserver.cfg: [xymonnet] ENVFILE /opt/xymon/server/etc/xymonserver.cfg NEEDS xymond CMD xymonnet --report --ping --checkresponse --no-ares --bb-proxy-syntax --shuffle LOGFILE $XYMONSERVERLOGS/xymonnet.log INTERVAL 2m Anything worth to change here?? Regards and tanks in advance Christian

1 0

xymonproxy setup
by john.r.rothlisberger＠accenture.com 09 Apr '19

09 Apr '19

Can anyone help clue me in to how to get xymonproxy to work? In my environment I have multiple Xymon servers that I would like to have them report to a single server. (xymonserver[1-5] -> xymonserverA) In tasks.cfg (on one of them for testing) I setup xymonproxy as such: [xymonproxy] ENABLED ENVFILE /home/xymon/server/etc/xymonserver.cfg CMD $XYMONHOME/bin/xymonproxy --server=xymonserverA-IP --report=xymonserverA-IP.xymonproxy - -no-daemon --pidfile=$XYMONSERVERLOGS/xymonproxy.pid LOGFILE $XYMONSERVERLOGS/xymonproxy.log For xymond, history, alert, clientdata, rrdstatus, rrddata, hostdata, xymonfetch - were all set to DISABLED. For xymongen, xymonnet, xymonnetagain - were all active with NEEDS xymond. I left xymonserver1 listening on port 1984 for data from its clients. Xymonserver1 also reports to xymonserverA as a client (no issues here). Xymonserver1 continued to work normally with nothing being sent to xymonserverA. Either I am trying to use xymonproxy incorrectly or I have something misconfigured. Ideas? Thanks, John Upcoming PTO: May 10th-17th _____________________________________________________________________ John Rothlisberger IT Strategy, Infrastructure & Security - Technology Growth Platform TGP for Business Process Outsourcing Accenture 312.693.3136 office _____________________________________________________________________ ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com

2 1

Xymon-Client in Solaris
by jgsuareza1984＠gmail.com 05 Apr '19

05 Apr '19

HI I already have the server, now I need to install the client xymon on Solaris Sparc Do you need any special configuration in Solaris Sparc as a client? Atentamente, *Gabriel Suárez*

2 1