- Xymon - Xymon mailman web

Windows Powershell client v2.21
by zak.beck＠accenture.com 20 Oct '17

20 Oct '17

Hi v2.21 of XymonPSClient has been committed. This has a couple of new minor features and a minor fix, as follows: * Added reporting data to the server using UTF8 encoding. This is optional and the default remains to use ASCII. Use at your own risk - there's a possibility that not all server compiles will support receiving UTF8. (thanks Luboš Pavlíček) * Added the ability to include 'local' data in the core client message. This replicates functionality found in the Linux client - basically you can have external scripts write data to a file under the local folder (location specified by setting localdatalocation) and it will get written to a section in the client message like [local:<filename>]. You can then use a command like this to retrieve it: xymon 0 "clientlog <client host> section=local:<filename>" (thanks David Boyer for the inspiration!) * Fixed the Powershell provider appearing in file, log, dirsize and other tests - you would have only seen this if you were using UNC paths, it would have appeared like this: [file:Microsoft.PowerShell.Core\FileSystem::\\server\share\filename.txt], it should now appear like this: [file:\\server\share\filename.txt] I have also updated the documentation to include the new features. I have also updated nssm.exe in the repository. If you are running the client on Windows 10 Creator's Edition, you will need to use this new updated nssm.exe. Thanks Zak ________________________________ 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. ______________________________________________________________________________________ www.accenture.com

2 5

no client results arrive, lot of TIME_WAIT at server - SOLVED
by norbert.kriegenburg＠de.ibm.com 20 Oct '17

20 Oct '17

Hm, this was a tricky one, but Thomas pointed me to the environment check which then leads to the solution. Thanks! I double checked the env for the xymon: $ xymoncmd /usr/bin/env | egrep -i home PATH=/home/xymon/client/bin:/bin:/usr/bin:/sbin:/usr/sbin:/etc PWD=/home/xymon HOME=/home/xymon _=/home/xymon/server/bin/xymoncmd XYMONHOME=/home/xymon/client XYMONCLIENTHOME=/home/xymon/client XYMON=/home/xymon/client/bin/xymon XYMONTMP=/home/xymon/client/tmp XYMONCLIENTLOGS=/home/xymon/client/logs XYMONRUNDIR=/home/xymon/client/logs LOCAL_CLIENTCONFIG=/home/xymon/client/etc/localclient.cfg LOCAL_LOGFETCHCFG=/home/xymon/client/etc/logfetch.cfg HOBBITCLIENTHOME=/home/xymon/client BBHOME=/home/xymon/client BB=/home/xymon/client/bin/xymon BBTMP=/home/xymon/client/tmp BBCLIENTLOGS=/home/xymon/client/logs XYMONHOME points to the client dir, even if in xymonserver.cfg is defined: XYMONHOME="/home/xymon/server" # The Xymon server directory, where programs and configurations So the serverprogs use the binaries from the client? This also explains why some commands were not found or only worked with relative path, because they do not exist in a usual client bin dir. It was a fresh compiled xymon, so i checked the binaries. I then found out that the XYMONHOME is compiled into the binaries. During manual copy of the different progs into the client and server bin dirs (it is a hardened environment were i don't have root access even for xymon install) obviously i mixed up some client binaries into server bindir. This then leads to those strange effects. Now i replaced the server bins with the ones from the common dir in source tree, and all is good. $ xymoncmd /usr/bin/env | egrep -i home PATH=/home/xymon/server/bin:/usr/local/bin:/usr/sbin:/usr/bin:/bin PWD=/home/xymon/server/logs HOME=/home/xymon _=/home/xymon/server/bin/xymoncmd OLDPWD=/home/xymon XYMONHOME=/home/xymon/server XYMONCLIENTHOME=/home/xymon/client XYMONSERVERROOT=/home/xymon/server XYMONSERVERLOGS=/home/xymon/server/logs XYMONRUNDIR=/home/xymon/server/run XYMONTMP=/home/xymon/server/tmp HOSTSCFG=/home/xymon/server/etc/hosts.cfg XYMON=/home/xymon/server/bin/xymon I wonder if it is necessary to have those path hardcoded, or if this can be replaced by generally using the environment vars? Then we don't need to deal with different binaries for client and server with the same name. But as always, thx for the great tool and the help of the community! Norbert From: Norbert Kriegenburg/Germany/IBM To: Thomas Eckert <thomas.eckert at it-eckert.de> Cc: xymon <xymon at xymon.com> Date: 19/10/2017 18:19 Subject: Re: [Xymon] no client results arrive, lot of TIME_WAIT at server Hi Thomas, thank you for your hints. Lets go through your suggestions: - you were right with the INTERVAL. This was added by accident, but doesn't harm (no more channels are started), removed, no effect - yes, server process was restartet at 5:13am UTC 1. - environment looks as expected: $ xymoncmd /usr/bin/env | egrep -i 'xymsrv|xymonservers|bbdisp' XYMONSERVERS=10.137.56.43 XYMSRV=10.137.56.43 BBDISP=10.137.56.43 BBDISPLAYS=10.137.56.43 2. - unfortunately i don't have root access here for a tcpdump 3. - now it gets strange: if i try your suggestion i get this (doublechecked at other server and the syntax works ok): $ xymoncmd xymond_channel --channel=client cat 2017-10-19 15:58:58.843500 execvp() failed: No such file or directory (but of curse xymoncmd is in the path) if i try with relative path i get this (run from bin path): $ ./xymoncmd ./xymond_channel --channel=client cat 2017-10-19 16:01:02.173601 Could not get shm of size 524288: No such file or directory 2017-10-19 16:01:02.173943 Channel not available some of these messages i can find in some logs: $ grep "Could not get shm" * alert.log:2017-10-19 10:38:00.733526 Could not get shm of size 1048576: No such file or directory history.log:2017-10-19 10:38:00.730686 Could not get shm of size 1048576: No such file or directory hostdata.log:2017-10-19 10:38:00.730538 Could not get shm of size 524288: No such file or directory rrd-data.log:2017-10-19 10:38:00.734198 Could not get shm of size 524288: No such file or directory I searched the web for those messages, and found some in hobbit/xymon mailing list, but no details or solution. http://lists.xymon.com/oldarchive/2008/06/msg00183.html But: the client messages from server still arrive and the tests are all visible... very strange Norbert From: Thomas Eckert <thomas.eckert at it-eckert.de> To: xymon <xymon at xymon.com> Date: 19/10/2017 16:42 Subject: Re: [Xymon] no client results arrive, lot of TIME_WAIT at server Sent by: "Xymon" <xymon-bounces at xymon.com> On 19 Oct 2017, at 14:49, Norbert Kriegenburg < norbert.kriegenburg at de.ibm.com> wrote: Yes, that's what i checked at first. But i assume that also the info from the servers own client data are captured by the same client channel listener, and that obviously works. valid point Nothing in the clientdata.log, even if i activate the DEBUG mode with a kill -USR2 PID My clientdata section: # The client back-end module. You need this if you are running the Xymon client on any system. [clientdata] ENVFILE $XYMONSERVERHOME/etc/xymonserver.cfg NEEDS xymond CMD /home/xymon/server/bin/xymond_channel --channel=client \ --log=$XYMONSERVERLOGS/clientdata.log xymond_client \ --no-clear-files \ --no-clear-ports \ --no-port-listing \ --uptime-status INTERVAL 2m The `INTERVAL` here is not im my and xymon.com’s-version of tasks.cfg— not sure if it does harm (it _may_ try to start a new channel every 2 minutes). ps listing: $ ps -ef|grep "xymond_channel --channel=client"|grep -v grep xymon 18865 18705 0 05:13 ? 00:00:00 /home/xymon/server/bin/xymond_channel --channel=client --log=/home/xymon/server/logs/clientdata.log xymond_client --no-clear-files --no-clear-ports --no-port-listing --uptime-status If this process does not change it should be fine; your xymon server was restarted 5:13 this morning? I have a lot of TIME_WAITS from time to time, no idea why this goes up and down: $ netstat -atn|grep 1984 tcp 0 0 0.0.0.0:1984 0.0.0.0:* LISTEN tcp 0 0 10.137.56.43:37752 10.137.56.43:1984 TIME_WAIT tcp 0 0 10.137.56.43:37822 10.137.56.43:1984 TIME_WAIT ... 10.137.56.43 is the Xymon server IP. $ netstat -atn|grep 1984|wc -l 165 (sometimes much much more) (But goes down to 7 after some mins) Looks like internal xymon-communication. As long as the TIME_WAIT-count does not go >20k that should not be the cause. Thing’s I’d try from here: 1. double-check the XYMSRV / XYMONSERVERS setting on the client(s), e.g. with: xymoncmd /usr/bin/env | egrep -i 'xymsrv|xymonservers|bbdisp’ 2. just to double-check: tcpdump on xymon server and a client to check for tcp/1984 communication 3. run a channel-listener an the server to see if the client messages (other than the ones from the local client) make it xymoncmd xymond_channel --channel=client cat | grep ‘^client ' xymoncmd xymond_channel --channel=client cat The latter might be very noisy — the former just prints the “header”/1st line of each connection. There should be one message for each client sending data every 5 minutes. HTH Thomas <graycol.gif>Thomas Eckert ---19/10/2017 11:14:56---Norbert, I assume your manual (BB way) is something like `xymon 1.2.3.4 “status example.com.test …”` From: Thomas Eckert <thomas.eckert at it-eckert.de> To: xymon <xymon at xymon.com> Date: 19/10/2017 11:14 Subject: Re: [Xymon] no client results arrive, lot of TIME_WAIT at server Sent by: "Xymon" <xymon-bounces at xymon.com> Norbert, I assume your manual (BB way) is something like `xymon 1.2.3.4 “status example.com.test …”`. The xymon-client send `clientdata` that is processed by a “channel listener” and _that_ sends status-messages similar to above (a bit simplified). That channel-listener may not be running/crashing: Check our `tasks.cfg` for the section `[clientdata]` and verify, if the `xymond_channel`-process is running (I suspect it’s not). Maybe the `clientdata.log` helps with debugging. You may also run the task manually to get further information. What’s your problem with the "lot of TIME_WAIT”? Are these just for tcp/1984-connections? Cheers Thomas On 19 Oct 2017, at 07:30, Norbert Kriegenburg < norbert.kriegenburg at de.ibm.com> wrote: experts, i have a new (not my first) Xymon installation (4.3.28 on RH 7.4, self compiled). All looks good, but the clients only show the network tests (conn, ssh). Only the Xymon server itself shows everything (disk, cpu,...). - all clients are RH 7.4, same install image used (i just copied over the client part with client config, create a cronjob for automatic start, so no root access nor extra install needed) - nothing suspicious in server or client logs (even in debug mode) - no ghosts - if i send a test manually (the old BB way) this shows at Xymon immediately (so the client settings are ok) - if i shutdown the xymond at server, the client logs complains: 2017-10-19 05:09:18.051994 Whoops ! Failed to send message (Connection failed) 2017-10-19 05:09:18.052104 -> Could not connect to Xymon daemon at 10.137.56.43:1984 (Connection refused) (so obviously they communicate) Querying the xymond shows: xymon 127.0.0.1 "query clientname.ssh" green  Thu Oct 19 05:21:29 2017 ssh ok is ok, but xymon 127.0.0.1 "query clientname.disk" shows nothing Any ideas? Norbert _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

1 0

no client results arrive, lot of TIME_WAIT at server
by norbert.kriegenburg＠de.ibm.com 20 Oct '17

20 Oct '17

Hi Thomas, thank you for your hints. Lets go through your suggestions: - you were right with the INTERVAL. This was added by accident, but doesn't harm (no more channels are started), removed, no effect - yes, server process was restartet at 5:13am UTC 1. - environment looks as expected: $ xymoncmd /usr/bin/env | egrep -i 'xymsrv|xymonservers|bbdisp' XYMONSERVERS=10.137.56.43 XYMSRV=10.137.56.43 BBDISP=10.137.56.43 BBDISPLAYS=10.137.56.43 2. - unfortunately i don't have root access here for a tcpdump 3. - now it gets strange: if i try your suggestion i get this (doublechecked at other server and the syntax works ok): $ xymoncmd xymond_channel --channel=client cat 2017-10-19 15:58:58.843500 execvp() failed: No such file or directory (but of curse xymoncmd is in the path) if i try with relative path i get this (run from bin path): $ ./xymoncmd ./xymond_channel --channel=client cat 2017-10-19 16:01:02.173601 Could not get shm of size 524288: No such file or directory 2017-10-19 16:01:02.173943 Channel not available some of these messages i can find in some logs: $ grep "Could not get shm" * alert.log:2017-10-19 10:38:00.733526 Could not get shm of size 1048576: No such file or directory history.log:2017-10-19 10:38:00.730686 Could not get shm of size 1048576: No such file or directory hostdata.log:2017-10-19 10:38:00.730538 Could not get shm of size 524288: No such file or directory rrd-data.log:2017-10-19 10:38:00.734198 Could not get shm of size 524288: No such file or directory I searched the web for those messages, and found some in hobbit/xymon mailing list, but no details or solution. http://lists.xymon.com/oldarchive/2008/06/msg00183.html But: the client messages from server still arrive and the tests are all visible... very strange Norbert From: Thomas Eckert <thomas.eckert at it-eckert.de> To: xymon <xymon at xymon.com> Date: 19/10/2017 16:42 Subject: Re: [Xymon] no client results arrive, lot of TIME_WAIT at server Sent by: "Xymon" <xymon-bounces at xymon.com> On 19 Oct 2017, at 14:49, Norbert Kriegenburg < norbert.kriegenburg at de.ibm.com> wrote: Yes, that's what i checked at first. But i assume that also the info from the servers own client data are captured by the same client channel listener, and that obviously works. valid point Nothing in the clientdata.log, even if i activate the DEBUG mode with a kill -USR2 PID My clientdata section: # The client back-end module. You need this if you are running the Xymon client on any system. [clientdata] ENVFILE $XYMONSERVERHOME/etc/xymonserver.cfg NEEDS xymond CMD /home/xymon/server/bin/xymond_channel --channel=client \ --log=$XYMONSERVERLOGS/clientdata.log xymond_client \ --no-clear-files \ --no-clear-ports \ --no-port-listing \ --uptime-status INTERVAL 2m The `INTERVAL` here is not im my and xymon.com’s-version of tasks.cfg— not sure if it does harm (it _may_ try to start a new channel every 2 minutes). ps listing: $ ps -ef|grep "xymond_channel --channel=client"|grep -v grep xymon 18865 18705 0 05:13 ? 00:00:00 /home/xymon/server/bin/xymond_channel --channel=client --log=/home/xymon/server/logs/clientdata.log xymond_client --no-clear-files --no-clear-ports --no-port-listing --uptime-status If this process does not change it should be fine; your xymon server was restarted 5:13 this morning? I have a lot of TIME_WAITS from time to time, no idea why this goes up and down: $ netstat -atn|grep 1984 tcp 0 0 0.0.0.0:1984 0.0.0.0:* LISTEN tcp 0 0 10.137.56.43:37752 10.137.56.43:1984 TIME_WAIT tcp 0 0 10.137.56.43:37822 10.137.56.43:1984 TIME_WAIT ... 10.137.56.43 is the Xymon server IP. $ netstat -atn|grep 1984|wc -l 165 (sometimes much much more) (But goes down to 7 after some mins) Looks like internal xymon-communication. As long as the TIME_WAIT-count does not go >20k that should not be the cause. Thing’s I’d try from here: 1. double-check the XYMSRV / XYMONSERVERS setting on the client(s), e.g. with: xymoncmd /usr/bin/env | egrep -i 'xymsrv|xymonservers|bbdisp’ 2. just to double-check: tcpdump on xymon server and a client to check for tcp/1984 communication 3. run a channel-listener an the server to see if the client messages (other than the ones from the local client) make it xymoncmd xymond_channel --channel=client cat | grep ‘^client ' xymoncmd xymond_channel --channel=client cat The latter might be very noisy — the former just prints the “header”/1st line of each connection. There should be one message for each client sending data every 5 minutes. HTH Thomas <graycol.gif>Thomas Eckert ---19/10/2017 11:14:56---Norbert, I assume your manual (BB way) is something like `xymon 1.2.3.4 “status example.com.test …”` From: Thomas Eckert <thomas.eckert at it-eckert.de> To: xymon <xymon at xymon.com> Date: 19/10/2017 11:14 Subject: Re: [Xymon] no client results arrive, lot of TIME_WAIT at server Sent by: "Xymon" <xymon-bounces at xymon.com> Norbert, I assume your manual (BB way) is something like `xymon 1.2.3.4 “status example.com.test …”`. The xymon-client send `clientdata` that is processed by a “channel listener” and _that_ sends status-messages similar to above (a bit simplified). That channel-listener may not be running/crashing: Check our `tasks.cfg` for the section `[clientdata]` and verify, if the `xymond_channel`-process is running (I suspect it’s not). Maybe the `clientdata.log` helps with debugging. You may also run the task manually to get further information. What’s your problem with the "lot of TIME_WAIT”? Are these just for tcp/1984-connections? Cheers Thomas On 19 Oct 2017, at 07:30, Norbert Kriegenburg < norbert.kriegenburg at de.ibm.com> wrote: experts, i have a new (not my first) Xymon installation (4.3.28 on RH 7.4, self compiled). All looks good, but the clients only show the network tests (conn, ssh). Only the Xymon server itself shows everything (disk, cpu,...). - all clients are RH 7.4, same install image used (i just copied over the client part with client config, create a cronjob for automatic start, so no root access nor extra install needed) - nothing suspicious in server or client logs (even in debug mode) - no ghosts - if i send a test manually (the old BB way) this shows at Xymon immediately (so the client settings are ok) - if i shutdown the xymond at server, the client logs complains: 2017-10-19 05:09:18.051994 Whoops ! Failed to send message (Connection failed) 2017-10-19 05:09:18.052104 -> Could not connect to Xymon daemon at 10.137.56.43:1984 (Connection refused) (so obviously they communicate) Querying the xymond shows: xymon 127.0.0.1 "query clientname.ssh" green  Thu Oct 19 05:21:29 2017 ssh ok is ok, but xymon 127.0.0.1 "query clientname.disk" shows nothing Any ideas? Norbert _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

2 1

Custom RRD definition help
by Scot.Kreienkamp＠la-z-boy.com 19 Oct '17

19 Oct '17

Hi everyone, I have a test that only executes once per hour, so I am trying to setup a custom RRD definition with a 60 minute step to capture the data. The test is working and is sending its data back as a data message and the RRD file is being created, so all that is setup properly. If I dump the RRD file I can find the most recent value within the last_ds field in the RRD file, but none of the values are ever stored. I'm stumped as to why, hopefully someone can help clue me in. Thanks! [dwrite] -s3600 #1 hour for 48 hours +1 RRA:AVERAGE:0.5:1:49 #2 hour average for 12 days +1 RRA:AVERAGE:0.5:2:156 #4 hour average for 48 days +1 RRA:AVERAGE:0.5:4:294 #8 hour average for 576 days +1 RRA:AVERAGE:0.5:8:1731 Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | * 734-384-6403 | | * 7349151444 | * Scot.Kreienkamp at la-z-boy.com<mailto:%7BE-mail%7D> www<http://www.la-z-boy.com/>.la-z-boy.com<http://www.la-z-boy.com/> | facebook.<https://www.facebook.com/lazboy>com<https://www.facebook.com/lazboy>/<https://www.facebook.com/lazboy>lazboy<http://facebook.com/lazboy> | twitter.com/lazboy<https://twitter.com/lazboy> | youtube.com/<https://www.youtube.com/user/lazboy>lazboy<https://www.youtube.com/user/lazboy> [cid:lzbVertical_hres.jpg] This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.

2 2

Notification Issues
by kc.kuhns＠executech.com 19 Oct '17

19 Oct '17

Good morning, We're using Xymon 4.3.25 and are running into a strange issue. We use Armor to monitor servers and various things at all of our clients. Our host file is setup something like this: Page User1 User One Subpage Client1 Client One 8.8.8.8 DC.Google # NOCONN Page User2 User Two Subpage Client2 Client Two 75.75.75.75 DC.Comcast # NOCONN Each technician that we have has a page, and each client has its own subpage under the related technician. We often move clients around to different technicians so in the above example, we may decide to move Client2 to User1. When we do that, it seems that User2 still receives email alerts for DC.Comcast even though it has been moved under User1. When looking at the info tab for DC2, it would show only User1 and nothing tied to User2. There's also nothing relating to that client in the alerts file. Is there some type of cache that we need to clear when we move clients around to different technicians to prevent this? Appreciate the help.

3 7

no client results arrive, lot of TIME_WAIT at server
by norbert.kriegenburg＠de.ibm.com 19 Oct '17

19 Oct '17

Yes, that's what i checked at first. But i assume that also the info from the servers own client data are captured by the same client channel listener, and that obviously works. Nothing in the clientdata.log, even if i activate the DEBUG mode with a kill -USR2 PID My clientdata section: # The client back-end module. You need this if you are running the Xymon client on any system. [clientdata] ENVFILE $XYMONSERVERHOME/etc/xymonserver.cfg NEEDS xymond CMD /home/xymon/server/bin/xymond_channel --channel=client \ --log=$XYMONSERVERLOGS/clientdata.log xymond_client \ --no-clear-files \ --no-clear-ports \ --no-port-listing \ --uptime-status INTERVAL 2m ps listing: $ ps -ef|grep "xymond_channel --channel=client"|grep -v grep xymon 18865 18705 0 05:13 ? 00:00:00 /home/xymon/server/bin/xymond_channel --channel=client --log=/home/xymon/server/logs/clientdata.log xymond_client --no-clear-files --no-clear-ports --no-port-listing --uptime-status I have a lot of TIME_WAITS from time to time, no idea why this goes up and down: $ netstat -atn|grep 1984 tcp 0 0 0.0.0.0:1984 0.0.0.0:* LISTEN tcp 0 0 10.137.56.43:37752 10.137.56.43:1984 TIME_WAIT tcp 0 0 10.137.56.43:37822 10.137.56.43:1984 TIME_WAIT ... 10.137.56.43 is the Xymon server IP. $ netstat -atn|grep 1984|wc -l 165 (sometimes much much more) (But goes down to 7 after some mins) From: Thomas Eckert <thomas.eckert at it-eckert.de> To: xymon <xymon at xymon.com> Date: 19/10/2017 11:14 Subject: Re: [Xymon] no client results arrive, lot of TIME_WAIT at server Sent by: "Xymon" <xymon-bounces at xymon.com> Norbert, I assume your manual (BB way) is something like `xymon 1.2.3.4 “status example.com.test …”`. The xymon-client send `clientdata` that is processed by a “channel listener” and _that_ sends status-messages similar to above (a bit simplified). That channel-listener may not be running/crashing: Check our `tasks.cfg` for the section `[clientdata]` and verify, if the `xymond_channel`-process is running (I suspect it’s not). Maybe the `clientdata.log` helps with debugging. You may also run the task manually to get further information. What’s your problem with the "lot of TIME_WAIT”? Are these just for tcp/1984-connections? Cheers Thomas On 19 Oct 2017, at 07:30, Norbert Kriegenburg < norbert.kriegenburg at de.ibm.com> wrote: experts, i have a new (not my first) Xymon installation (4.3.28 on RH 7.4, self compiled). All looks good, but the clients only show the network tests (conn, ssh). Only the Xymon server itself shows everything (disk, cpu,...). - all clients are RH 7.4, same install image used (i just copied over the client part with client config, create a cronjob for automatic start, so no root access nor extra install needed) - nothing suspicious in server or client logs (even in debug mode) - no ghosts - if i send a test manually (the old BB way) this shows at Xymon immediately (so the client settings are ok) - if i shutdown the xymond at server, the client logs complains: 2017-10-19 05:09:18.051994 Whoops ! Failed to send message (Connection failed) 2017-10-19 05:09:18.052104 -> Could not connect to Xymon daemon at 10.137.56.43:1984 (Connection refused) (so obviously they communicate) Querying the xymond shows: xymon 127.0.0.1 "query clientname.ssh" green  Thu Oct 19 05:21:29 2017 ssh ok is ok, but xymon 127.0.0.1 "query clientname.disk" shows nothing Any ideas? Norbert _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

2 1

no client results arrive, lot of TIME_WAIT at server
by norbert.kriegenburg＠de.ibm.com 19 Oct '17

19 Oct '17

experts, i have a new (not my first) Xymon installation (4.3.28 on RH 7.4, self compiled). All looks good, but the clients only show the network tests (conn, ssh). Only the Xymon server itself shows everything (disk, cpu,...). - all clients are RH 7.4, same install image used (i just copied over the client part with client config, create a cronjob for automatic start, so no root access nor extra install needed) - nothing suspicious in server or client logs (even in debug mode) - no ghosts - if i send a test manually (the old BB way) this shows at Xymon immediately (so the client settings are ok) - if i shutdown the xymond at server, the client logs complains: 2017-10-19 05:09:18.051994 Whoops ! Failed to send message (Connection failed) 2017-10-19 05:09:18.052104 -> Could not connect to Xymon daemon at 10.137.56.43:1984 (Connection refused) (so obviously they communicate) Querying the xymond shows: xymon 127.0.0.1 "query clientname.ssh" green  Thu Oct 19 05:21:29 2017 ssh ok is ok, but xymon 127.0.0.1 "query clientname.disk" shows nothing Any ideas? Norbert

2 1

how to monitor SharePoint Online with Xymon
by kspringer＠innovateteam.com 16 Oct '17

16 Oct '17

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20171016/521194a7/attach…>

1 0

xymon ntp check issue
by satish.txt＠gmail.com 16 Oct '17

16 Oct '17

Damn!! you got damn! right :) +1 On Mon, Oct 16, 2017 at 4:50 AM, Christian Hettler <christian.hettler at asknet.de> wrote: > Hello Satish, > > if you configure more than one xymon server on the client and > the first one isn't reachable, the second xymon server reports > such a clock offset. It is related to the timeout for the first > xymon server. > > regards, > > Christian > > On Sun, Oct 15, 2017 at 09:20:26PM -0400, Satish Patel wrote: >> We have two remove machine running on UTC timezone and our xymon >> server located in EST timezone, now i am seeing very strange issue, in >> those two remote server one of server has 47s time difference, even it >> has right time all other servers in remote location showing correct >> time in xymon except single machine which is showing 47s off i have >> checked everything and nothing wrong in server, even configuration of >> ntpclient is identical, not sure how to troubleshoot this issue, >> something is wrong with xymon server but not sure where? >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com >> http://lists.xymon.com/mailman/listinfo/xymon

1 0

xymon ntp check issue
by satish.txt＠gmail.com 16 Oct '17

16 Oct '17

We have two remove machine running on UTC timezone and our xymon server located in EST timezone, now i am seeing very strange issue, in those two remote server one of server has 47s time difference, even it has right time all other servers in remote location showing correct time in xymon except single machine which is showing 47s off i have checked everything and nothing wrong in server, even configuration of ntpclient is identical, not sure how to troubleshoot this issue, something is wrong with xymon server but not sure where?

1 0