November 2018 - Xymon - Xymon mailman web

Christmas icons
by wlrutherford＠alaska.edu 28 Nov '18

28 Nov '18

Thank you. I knew somebody would have a set of them squirreled away! :-) On Wed, Nov 28, 2018 at 12:39 AM Dirk Kastens < dirk.kastens at uni-osnabrueck.de> wrote: > Hi Walter, > > I'm using these every year :-) > > Am 28.11.2018 um 02:24 schrieb Walter Rutherford: > > Hello, > > > > I remember years ago at a different job I found a set of Christmasy > > replacement icons to use with Big Brother, (yes, that long ago). That > > computer is long gone so I searched online but I haven't been able > > to find a copy of those holiday icons anywhere. > > > > Does anybody happen to have a copy of those icons handy? > > Dirk >

1 0

Xymon network tests alerts
by chrisp＠lightstoneauto.co.za 28 Nov '18

28 Nov '18

Good day. I built a new xymon monitor on centos7, using the Terabithia repo. All is working great except for some network tests. I receive a couple alerts during the evening mostly for server conn test and http tests failing. When looking at the history the failed test were red for 10 to maybe 30 seconds, the http tests up to 2 minutes. I have been running continues pings from the xymon server in screen sessions and so far did not drop a packet. What other tests can I do to verify the xymon tests, or is there a known solution for this problem. Kind regards [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/AUTOlogoW.png] Chris Pretorius [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/phone.png] 0872367740 [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/email.png] chrisp at lightstone.co.za<mailto:chrisp at lightstone.co.za> [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/web.png] www.signio.co.za<http://www.signio.co.za> [https://lsc-assets.scdn1.secure.raxcdn.com/lssig/address.png] Centurion Square, 3rd Floor, cnr Heuwel and Gordon Hood rd, Centurion This communication is subject to Lightstone's email disclaimer<http://www.lightstone.co.za/portal/content/email-disclaimer.aspx>

1 0

Can the ps client notify when windows updates are available.
by me＠tdiehl.org 27 Nov '18

27 Nov '18

Hi, I am wondering if anyone has a way to monitor a windows server using the powershell client so that it will notify xymon when a machine needs to have windows updates installed and or rebooted? I currently have xymon triggering a yellow uptime dot if the machine(s) are up more than 30 days but I am looking for something more accurate. Is there some kind of external script available? If this does not exist, does anyone know how to detect that updates are needed or the machine needs a reboot. My Google foo seems to lacking in this area. Regards, -- Tom me at tdiehl.org

2 1

Xymon Complete Features List
by William.Gregoire＠ca.ebarrette.com 27 Nov '18

27 Nov '18

Hello, I have made some research on the internet to understand everything that xymon can monitor. I have come up with this list: 1- Hosts Activities. 2- Network Services. 3- http, FTP, Smtp, pop3, imap, webmail, request monitor. 4- Local Disk Utilisation. 5- Logfiles. 6- Processes . 7- Memory. 8- Domain name expiration date & websites url & SSL certificate status. 9- Testing a specific URL of a webpage. Is this list complete ? or there are other things that Xymon can monitor ? Thanks in advance.

2 1

Get username on disabled alerts
by yyyadvendra＠gmail.com 27 Nov '18

27 Nov '18

Hi Guys New to xymon I am looking around to capture the username somewhere in a webpage if a test was disabled, Any help would be appreciated. Thanks Yadvendra

4 5

Alerts not recognizing DURATION flag
by danyiem＠vcu.edu 21 Nov '18

21 Nov '18

Hi all, We had an incident this morning where a server's http check went red for 2m 35s starting at 04:15, recovering at 04:17 and sent out an alert at 04:21 with a subject 'servername:keepalive CRITICAL (RED)' and the body of the message 'green Wed Nov 21 04:18:46 2018: Content OK'. The strange thing is that in alerts.cfg the MAIL is set up with 'DURATION >5m' and should not be sending out alerts at all if the problem does not persist for more than 5 minutes. In the info tab for this server it does show '1st Delay' as '5m 1s', so it appears to be seeing the setting, just not respecting it. We are using Xymon 4.3.28-1.el7.terabithia running on CentOS 7.5. Does anyone know why this might be happening? Thanks, *Eliza Danyi* Operating Systems Analyst VCU Computer Center E-mail: danyiem at vcu.edu *Don't be a phishing victim -- VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details, visit **https://ts.vcu.edu/about-us/information-security/common-questions/what-is-phishing/ <https://ts.vcu.edu/about-us/information-security/common-questions/what-is-p…> *

1 0

Increase size of BBALPHAMSG size
by dl1025＠att.com 21 Nov '18

21 Nov '18

My email alerts are getting large. I need to be able to increase the BBALPHAMSG size to larger to 4096. Is there an environmental variable I can use? I am running xymon 4.3.28 on Red Hat Linux. Thanks

1 1

client not sending to both servers
by malcolm.r.hunter＠gmail.com 20 Nov '18

20 Nov '18

What happens if you swap the servers around in BBDISPLAYS? That's a pretty old client. Have you considered upgrading? Malc On Tue, 20 Nov 2018 at 17:10, Ian Diddams via Xymon <xymon at xymon.com> wrote: > > > > ---------- Forwarded message ---------- > From: Ian Diddams <didds3 at yahoo.co.uk> > To: Xymon Mailing List <xymon at xymon.com> > Cc: > Bcc: > Date: Tue, 20 Nov 2018 17:00:08 +0000 (UTC) > Subject: client not sending to both servers > client config in ~xymon/client/etc/hobbitclient.cfg > > .. > BBDISP="0.0.0.0" # IP address of the Hobbit server > BBDISPLAYS="192.168.55.243 192.168.52.64" # IP of > multiple Hobbit servers. BBDISP must be "0.0.0.0". > ... > > the server on 192.168.55.243 received all the epxted disk, cpu etc info > and displays it fine. > > But the server in 192.168.52.64 - doesn;t. > > Ive sniffed the 1984 port on the server (..52.64) and nothing comes in. > Ive done the same on the client but I can see it going out... > > > > basic monitoring works (conn) fine > > Ive tested a quick script that "writes" a status message to a TEST alert > on ...52.64 and that appears. > > I can telnet from the client to ...52.64 on port 1984 fine. > > ghost client report has nothing in it that could be the client. > > Its as if the client isn;t even sending it to the swerver anyway (tcpdump > etc) > > ass I see in the logs is > > hobbitclient.log: > 2018-11-20 16:38:57 Whoops ! bb failed to send message - timeout > 2018-11-20 16:38:57 Failed to get a message, terminating > > > > repeated over and over and over. > > > > anyone any ideas? > > or how to increase the logging level to "see" more stuff? > > or... ? > > > > ---------- Forwarded message ---------- > From: Ian Diddams via Xymon <xymon at xymon.com> > To: Xymon Mailing List <xymon at xymon.com> > Cc: > Bcc: > Date: Tue, 20 Nov 2018 17:00:08 +0000 (UTC) > Subject: [Xymon] client not sending to both servers > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

1 0

client not sending to both servers
by didds3＠yahoo.co.uk 20 Nov '18

20 Nov '18

client config in ~xymon/client/etc/hobbitclient.cfg ..BBDISP="0.0.0.0" # IP address of the Hobbit serverBBDISPLAYS="192.168.55.243 192.168.52.64" # IP of multiple Hobbit servers. BBDISP must be "0.0.0.0".... the server on 192.168.55.243 received all the epxted disk, cpu etc info and displays it fine. But the server in 192.168.52.64 - doesn;t. Ive sniffed the 1984 port on the server (..52.64) and nothing comes in. Ive done the same on the client but I can see it going out... basic monitoring works (conn) fine Ive tested a quick script that "writes" a status message to a TEST alert on ...52.64 and that appears. I can telnet from the client to ...52.64 on port 1984 fine. ghost client report has nothing in it that could be the client. Its as if the client isn;t even sending it to the swerver anyway (tcpdump etc) ass I see in the logs is hobbitclient.log: 2018-11-20 16:38:57 Whoops ! bb failed to send message - timeout2018-11-20 16:38:57 Failed to get a message, terminating repeated over and over and over. anyone any ideas? or how to increase the logging level to "see" more stuff? or... ?

1 0

Ignoring snap mounts
by josh＠imaginenetworksllc.com 18 Nov '18

18 Nov '18

I am trying to ignore /snap/*. I've got my host as such: HOST=foo.bar.com DISK %^/snap.*/ IGNORE INODE %^/snap* IGNORE Neither of these are matching (notice the .*/ versus *). The man page says "%^/oracle.*/" will match any filesystem whose mountpoint begins with "/oracle". Replicating this, though, doesn't seem to be working for me - I'm expecting the DISK to be working at this point as I matched the example. I'm getting a red status that the file system is 100% used. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

3 3