- Xymon - Xymon mailman web

Restricting access to disable/acknowledge etc
by Neil.Simmonds＠studio.co.uk 27 Feb '23

27 Feb '23

Hi all, On my current prod Xymon (which was built by someone no longer with the company) we are required to supply a userid/passwd for disabling or acknowledging tests. As far as I can see this is done through the <Directory "/usr/share/xymon/cgi-secure"> part of the httpd.conf (or on my new server Xymon.conf in /etc/httpd/conf.d ) I've got the conf set like the below which is the same as the working system, the /etc/xymon/ xymonpasswd file exists, is owned by apache user and had 64- permissions as required yet I'm not getting prompted for the password when I disable a test? Am I missing something? <Directory "/usr/share/xymon/cgi-secure"> AllowOverride None Options ExecCGI Includes <IfModule mod_authz_core.c> # Apache 2.4+ Require all granted </IfModule> <IfModule !mod_authz_core.c> Order allow,deny Allow from all </IfModule> AuthUserFile /etc/xymon/xymonpasswd AuthGroupFile /etc/xymon/xymongroups AuthType Basic AuthName "Xymon Administration" <RequireAll> # "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 </RequireAll> </Directory> Studio is a trading name of Studio Retail Ltd which is authorised and regulated by the Financial Conduct Authority for consumer credit and general insurance. Studio Retail Ltd are members of the Finance and Leasing Association (FLA). Registered in England. No: 718151. Registered Office: Church Bridge House, Henry Street, Accrington, BB5 4EE NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Studio Retail Ltd and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Studio Retail Ltd. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Studio Retail Ltd reserves the right to monitor all e-mail communications through its internal and external networks. If you have received this email in error, please notify our careline on +44(0) 371 200 0378.

3 3

charting xymonnet Run Time for additional instances
by john.thurston＠alaska.gov 20 Jan '23

20 Jan '23

In our installation of Xymon, I've recently needed to spin up additional xymonnet "tasks". These are processes dedicated to specific "networks" (as specified with the NET:location tag). I am unable to figure out how to chart the runtime of these new processes. I have each reporting into the display servers under their own column. The pages those bubbles link to have all of the appropriate stats on them, but they are missing the nice RRD chart that is seen on the native xymonnet page. I've been thrashing about, but I can't hit on the magic recipe. Can someone help me out? What do I need to do to get Xymon to build an RRD, and display the resulting graph, for my specifically-named xymonnet processes? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska

1 0

How to test remote ports
by zechner＠vrvis.at 19 Jan '23

19 Jan '23

Hi, I've been trying to establish a remote port check, but cannot get it to work. After reading the man pages and the corresponding topics on the mailing list, I've configured a test like this: PORT REMOTE=1.2.3.4:80 but the remote port always comes back as down, even though it is up. Am I doing something wrong? Local port checks all work perfectly, only the remote ones do not. Am I doing something wrong here? Context: I am using local mode on all clients, so I'm putting all my checks in /etc/xymon/localclient.cfg, but this should not effect this check, right? Thanks in advance! Best regards Christoph Zechner

5 7

How to test remote ports
by henrik＠hswn.dk 19 Jan '23

19 Jan '23

Den 19.01.2023 kl. 08.13 skrev Christoph Zechner: >> why are you trying to do it with a client-side test? > > Because I thought this was the idea behind the remote port check, but > I now see my error here. > >> You should just add an http test to the configuration and run it as a >> network test. In hosts.cfg: >> >> 1.2.3.4 myhost? # http://1.2.3.4/ > > This does not test for the port though. The hosts.cfg entry above _does_ test port 80 by establishing a connection to the port, sending an http request and verifying the response. > Port 80 was just an example for a random port, if I wanted to check > port 3389 on a remote Windows machine, how would I do that? The protocols.cfg file lists the various network protocols that Xymon knows about (and you can add your own, if you need any). Port 3389 is the RDP port, which is one of the protocols Xymon knows. So to test for that, use 1.2.3.4 myhost # rdp Add as many network tests as you like, eg. if you want to test host 1.2.3.4 for both http and RDP: 1.2.3.4 myhost # http://1.2.3.4/ rdp Regards, Henrik

2 1

Issue with apt test & Ubuntu
by damien＠makelofine.org 18 Jan '23

18 Jan '23

Hi, If you are running Xymon client 'apt' test on an Ubuntu (maybe others) system, you may face unexpected issue related to phased packages updates. I've reported the issue to Ubuntu: https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/2003062 The fix is available in the bug report and is really easy to implement and validate. Regards, Damien

1 0

Edges of the DNS test
by john.thurston＠alaska.gov 18 Jan '23

18 Jan '23

The basic "dns" test in Xymon (currently running 4.3.30-1.el7.terabithia) is frustrating me. As far as I can tell, there is no way to: + change the test-name (i.e. it is always "dns") + force tcp or udp connections Has anyone found a way around these limitations? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska

2 2

https://xymon.com/
by stef.coene＠docum.org 17 Jan '23

17 Jan '23

Hi, I just noticed that the Xymon website can use some cleanup in the menu's. There is a link to the old BBWin client but not to the new Powershell client. And the 'Where is Hobbit' points to a non existing link and redirets https://lists.xymon.com/oldarchive/ which does not exist. Stef

1 0

Decommissioned systems showing in ghosts
by colin.coe＠gmail.com 03 Jan '23

03 Jan '23

Hi all I decommissioned (i.e. physically removed) a bunch of Cisco switches some time ago but I see that they are still showing in the ghost report. I've checked hosts.cfg and devmon's hosts db but can't find them. Any ideas on how to track down why they're still showing up? Thanks

2 2

Stale alerts not being purged
by john.thurston＠alaska.gov 27 Dec '22

27 Dec '22

My Xymon (Xymon 4.3.30-1.el7.terabithia) is no longer noticing it is time to stop sending email alerts. A customer will ping me, saying "I'm still getting emails for a problem I fixed 10 days ago!" I find the messages in question in the /notifications.log/ Yep, there are a lot of them. I can see the test recovered ages ago, and there should no longer be notifications. If I go look in /alert.chk/, I can see the host:test in question If I restart xymon, the /alert.log/ will get a bunch of lines "Stale alert found", but the lines remain in the /alert.chk/ The only way I have figured out to clean this up is to grep the 'Stale' host:test pairs out of the /alert.log/, stop xymon, feed the host:test pairs through sed to delete the offending lines from /alert.chk/, and restart xymon. Anyone have any ideas what's wrong here? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska

1 1

journalctl support for RHEL/Alma Linux 9
by lists＠benjamindsmith.com 11 Dec '22

11 Dec '22

Hi everyone, I've been introducing a few AlmaLinux 9 hosts into my monitored network. I'm happy to share my build notes, so far, but specifically am wondering about "msgs" monitoring - it does not seem that journalctl is supported? Ben EL9 install notes below COMPILING: EL9 (CLIENT ONLY) 1) yum -y groupinstall "Development Tools" yum install pcre-devel useradd xymon 2) cd /usr/src 3) ./configure --client DON'T FORGET TO PUT IN THE RIGHT SERVER IP!! 4) ./make 5) tar -zcf xymon.client.not.installed.el9.tgz 6) scp xymon.client.not.installed.el9.tgz root at monitor:/var/www/html/. INSTALLING CREATED CLIENT 1) Verify the hostname matches xymon server config hostname # set as necessary: hostnamectl set-hostname $HOSTNAME 2) Run the following cd /usr/src # NOTE THE VERSION!! wget http://monitor.effortlessis.com/xymon.client.not.installed.elVERSION.tgz tar -zxvf xymon.client.not.installed.tgz useradd xymon yum install libtirpc libtirpc-devel yum groupinstall "Development Tools" (if needed) cd xymon-4.3.30 make install 3) Verify it works su - xymon xymon --debug # make sure it runs ok - WHAT DOES THIS DO? 4) yum groupremove "Development Tools" (if installed just for this) ./runclient.sh start # wait a few minutes # see it on the server: http://monitor.effortlessis.com/xymon/ run xymon directly to see it works. As user xymon on client Useful https://xymon.sourceforge.io/xymon/help/manpages/man1/xymon.1.html 4) Make it work via init. cp -av /root/repo/xymon/xymond /etc/rc.d/init.d/xymond4) ln -s /etc/rc.d/init.d/xymond /etc/rc.d/rc3.d/S99xymond; cd /etc/rc.d/init.d; chcon --reference=functions xymond systemctl enable xymond; systemctl start xymond; 4a) Make it work via systemctl ## not done yet 5) Common issues: A) /var/log/messages chown root.xymon /var/log/messages; chmod g+r /var/log/messages B) on xymon server, edit procs C) SELinux error on start xymond via systemctl ( ??? WTF IS THIS? )

2 1