- Xymon - Xymon mailman web

sslv3 error while testing https
by R.Schrittenlocher＠ub.uni-frankfurt.de 21 May '20

21 May '20

Dear all, we disabled for security reasons sslv3 in apache. Since then xymon complains about not being able to negotiate sslv3 and goes read with an ssl error. https://lists.xymon.com/archive/2014-December/040782.html shows that with bbtest-net could specificate which ssl version to use. This doesn't seem to be possible with xymon. Any hints how to test https correctly without sslv3? We are using xymon 4.3.17, Thanks Rolf

2 1

sysstemd startup
by neilsimmonds1808＠gmail.com 21 May '20

21 May '20

Hi, I'm having a strange issue with systemd startup. We run our Xymon as a user called hobbit. If I Start Xymon using the runclient.sh script as hobbit (i.e. /xymon/client/runclient.sh start) then all works perfectly. If I run it using systemctl start xymon a ps -eaf command clearly shows it running as hobbit but Iget the following in my /xymon/client/logs/xymonclient.log file 2020-05-19 14:28:13 Whoops ! Failed to send message (Connection failed) 2020-05-19 14:28:13 -> connect to Xymon daemon at xymonserver:1984 failed (Permission denied) 2020-05-19 14:28:13 -> Recipient 'xymonserver', timeout 15 2020-05-19 14:28:13 -> 1st line: 'client xymonclient.linux linux' If I test the connection all works OK root at xymonclient:/xymon/client # ./bin/xymon --debug "xymonserver" test 25296 2020-05-19 14:32:46 Transport setup is: 25296 2020-05-19 14:32:46 xymondportnumber = 1984 25296 2020-05-19 14:32:46 xymonproxyhost = NONE 25296 2020-05-19 14:32:46 xymonproxyport = 0 25296 2020-05-19 14:32:46 Recipient listed as ?xymonserver? 25296 2020-05-19 14:32:46 Standard protocol on port 1984 25296 2020-05-19 14:32:46 Will connect to address xymonserver port 1984 25296 2020-05-19 14:32:46 Connect status is 0 25296 2020-05-19 14:32:46 Sent 4 bytes 25296 2020-05-19 14:32:46 Closing connection My /usr/lib/sysemd/system/xymon.service file is [Unit] Description=Xymon systems and network monitor Documentation=man:xymon(7) man:xymonlaunch(8) man:xymon(1) After=network.target [Install] # Compatibility with "xymon" and "xymon-client" Alias=xymon.service Alias=xymon-client.service WantedBy=multi-user.target [Service] EnvironmentFile=/etc/sysconfig/xymonlaunch User=hobbit # We wrap in xymoncmd to eliminate the need for the bulk of the old init script ExecStart=/xymon/client/bin/xymonlaunch --config=/xymon/client/etc/clientlaunch.cfg --log=/xymon/client/logs/clientlaunch.log --pidfile=/xymon/client/ logs/clientlaunch.pid ExecStop=kill `cat /xymon/client/logs/clientlaunch.pid` PIDFile=/xymon/client/logs/clientlaunch.pid Type=simple User=hobbit # Kill xymonlaunch, but don't send kills to the underlying procs, since they # might be doing important things (like writing checkpoints and flushing caches) KillMode=process SendSIGHUP=yes SendSIGKILL=yes and my /etc/sysconfig/launch looks like this MACHINEDOTS=xymonclient SERVEROSTYPE=linux XYMONOSSCRIPT=xymonclient-linux.sh XYMONCLIENTHOME=/xymon/client/ I don't understand how it works perfectly when I start it as the user using the normal script yet get's permission denied when running under systemd but still as the same user

2 2

Displaying results when the DNS FQDN is different from uname -n
by scarville＠lereta.com 20 May '20

20 May '20

I have several new machines that do not display local information in XYMon. Part of that is the FQDN differs from the name returned by uname -n. For example apg-rdtx-nde-01.lereta.net thinks it is just plain apg-rdtx-nde-01. I verified this by capturing the clientlog sent to the server. I tried the obvious trick of putting a CLIENT: entry into host.cfg but to no avail. That works for a couple of other nodes where the name returned by uname -n is different than the DNS name we know them by so I am mystified as to why it won't work here Example hosts.cfg entry: 10.1.224.187 apg-rdtx-nde-01.lereta.net # ssh CLIENT:apg-rdtx-nde-01 As I said above, I captured the traffic from one of the clients and I can see that it is sending the information to XYMon. However, I cannot find where it is being stored if at all. Normally, I look in /var/xymon/data/hostdata/<servername> but it doesn't appear to be there. Is there a way to make this work? -- Stephen

3 3

Version Control
by malcolm.r.hunter＠gmail.com 19 May '20

19 May '20

Hi, Please forgive my ignorance if I've missed something. I'm trying to track changes to files in SourceForge, but trunk hasn't been updated since 2014 - only the branches. When I was working on FOSS projects, I was used to working on trunk as it always had the latest changes to the software. Branches were kept for releases and only updated when major bugfixes were needed to be back-ported. With Xymon as it is, I have to jump around the branches to track changes to files. Am I missing something? Malcolm

1 1

Should Blue State Stop Notifications?
by scarville＠lereta.com 18 May '20

18 May '20

Recently we moved all of our oracle databases to an Oracle Database Appliance (ODA). Unfortunately, on one database, some java bugs prevented a stored procedure from running correctly. The decision was made to point all the processes back to the "old" server and now the database on the ODA goes up and down as they DBAs test. I dutifully put it in a blue state but I still get emails telling me when it goes down. Is this correct behavior? I run a shell script on the ODA that checks the status of each database and sends it to XYMon. -- Stephen Carville Master of Turning Crappy Tools into Crappy Miracles ?\_(?)_/? ------------------------------------------------- A consilia hominis et Deus cachinnus.

1 1

[External] FW: alerts
by scott.birl＠temple.edu 18 May '20

18 May '20

> From: Hyppolite, Jean <Jean.Hyppolite at umm.edu> > Sent: Monday, May 18, 2020 10:52 AM > To: Scott Birl <scott.birl at temple.edu> > Subject: RE: [External] [Xymon] FW: alerts > > Hi > > Do you mean this rule below > > HOST=* > ??????? MAIL mailto:myemail at mymail.com FORMAT=TEXT SERVICE=conn,disk,files,memory,svcs REPEAT=20M COLOR=red RECOVERED > Yes, that's a good start. Any other rules that apply to that server? There's a few things missing that you may want to explicitly set: DURATION, REPEAT, and TIME, all of which are explained in alerts.cfg. That should help curb the excess alerts, and possibly prevent emails from being sent from flapping. Another suggestion is to break down that rule into multiple rules, ie: HOST=* MAIL mailto:myemail at mymail.com FORMAT=TEXT SERVICE=conn REPEAT=20M COLOR=red RECOVERED MAIL mailto:myemail at mymail.com FORMAT=TEXT SERVICE=disk REPEAT=20M COLOR=red RECOVERED MAIL mailto:myemail at mymail.com FORMAT=TEXT SERVICE=files REPEAT=20M COLOR=red RECOVERED MAIL mailto:myemail at mymail.com FORMAT=TEXT SERVICE=memory REPEAT=20M COLOR=red RECOVERED MAIL mailto:myemail at mymail.com FORMAT=TEXT SERVICE=svcs REPEAT=20M COLOR=red RECOVERED That would allow you tweak the settings for individual services. > > > From: Xymon <mailto:xymon-bounces at xymon.com> On Behalf Of Hyppolite, Jean > > > Sent: Monday, May 18, 2020 10:39 AM > > > To: mailto:xymon at xymon.com > > > Subject: [External] [Xymon] FW: alerts > > > > > > > > > Also To clarify, A lot of alerts we are getting are delayed alerts, alerts that are being sent out hours later > > > > > > From: Hyppolite, Jean > > > Sent: Monday, May 18, 2020 10:09 AM > > > To: mailto:xymon at xymon.com > > > Subject: alerts > > > > > > Hello, > > > > > > Our Xymon server is sending out a lot of excess and some false alerts. It seems that when a server is not reachable it sends the alerts out, but when the server recovers it never sends the > > > recovery message, but keeps sending the down critical messages. And idea what may be causing this? Is there? a way to look at exactly what alerts are being sent out from the xymon server from xymon? Also is there a way to configure xymon not to send out email alerts on flapping statuses? > > > Our Xymon server version is:? Xymon 4.3.30-1.el7.terabithia > > > > > > > > > Thanks > > > Jean > > > > > > > From: Scott Birl <mailto:scott.birl at temple.edu> > > Sent: Monday, May 18, 2020 10:43 AM > > To: mailto:xymon at xymon.com > > Subject: RE: [External] [Xymon] FW: alerts > > > > Please post the rules from alerts.cfg for that particular server. > >

2 3

POC Demo
by kspringer＠innovateteam.com 18 May '20

18 May '20

What exactly do you want to monitor? Just saying Active Directory is pretty vague. Thanks, Kris Springer -----Original Message----- From: Jose Jorge Garcia via Xymon <xymon at xymon.com> To: "xymon at xymon.com" <xymon at xymon.com> Cc: Jean Carlo Barboza <Jean.Barboza at wu.com> Sent: Tue, 12 May 2020 3:48 PM Subject: [Xymon] POC Demo

2 2

4.3.30 Proxy server updating to 4.3.21 main server
by Paul.Root＠CenturyLink.com 18 May '20

18 May '20

Yesterday, I tried to swap in a new xymon proxy server running 4.3.30-1 from Terabithia on CentOS 7. It is a hybrid, with the proxy on 1984 and the server on 1985. The URL displayed as expected - with issues aligning with what the temporary IP address could and could not get to. When I swapped in, the primary went purple on the things it can't get to but the proxy can - mostly conn and ntp (i.e. noconn in the hosts.cfg file and ntp not in it, but that is reversed in the proxy). Is there a compatibility issue with 4.3.30 updating 4.3.21? My primary server is CentOS 6 and the xymon is custom built by me. I've moved just about every server to use Terabithia, but not that one. Layout is slightly different, so I'm hesitant to upgrade it right now. Paul Root Lead Operations Engineer - IT Managed Services 390 Commerce Dr Woodbury, Mn 55125 651-312-5207 paul.root at centurylink.com This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

1 0

FW: alerts
by Jean.Hyppolite＠umm.edu 18 May '20

18 May '20

Also To clarify, A lot of alerts we are getting are delayed alerts, alerts that are being sent out hours later From: Hyppolite, Jean Sent: Monday, May 18, 2020 10:09 AM To: xymon at xymon.com Subject: alerts Hello, Our Xymon server is sending out a lot of excess and some false alerts. It seems that when a server is not reachable it sends the alerts out, but when the server recovers it never sends the recovery message, but keeps sending the down critical messages. And idea what may be causing this? Is there a way to look at exactly what alerts are being sent out from the xymon server from xymon? Also is there a way to configure xymon not to send out email alerts on flapping statuses? Our Xymon server version is: Xymon 4.3.30-1.el7.terabithia Thanks Jean This e-mail and any accompanying attachments may be privileged, confidential, contain protected health information about an identified patient or be otherwise protected from disclosure. State and federal law protect the confidentiality of this information. If the reader of this message is not the intended recipient; you are prohibited from using, disclosing, reproducing or distributing this information; you should immediately notify the sender by telephone or e-mail and delete this e-mail.

2 1

alerts
by Jean.Hyppolite＠umm.edu 18 May '20

18 May '20

Hello, Our Xymon server is sending out a lot of excess and some false alerts. It seems that when a server is not reachable it sends the alerts out, but when the server recovers it never sends the recovery message, but keeps sending the down critical messages. And idea what may be causing this? Is there a way to look at exactly what alerts are being sent out from the xymon server from xymon? Also is there a way to configure xymon not to send out email alerts on flapping statuses? Our Xymon server version is: Xymon 4.3.30-1.el7.terabithia Thanks Jean This e-mail and any accompanying attachments may be privileged, confidential, contain protected health information about an identified patient or be otherwise protected from disclosure. State and federal law protect the confidentiality of this information. If the reader of this message is not the intended recipient; you are prohibited from using, disclosing, reproducing or distributing this information; you should immediately notify the sender by telephone or e-mail and delete this e-mail.

1 0