December 2022 - Xymon - Xymon mailman web

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

27 Dec '22

I've been forced to implement the following on a daily christmas tree timer :/ TODAY=$( date +%Y-%m-%d ) logfile=/var/log/xymon/alert.log checkpointfile=/var/lib/xymon/tmp/alert.chk z=$( mktemp -p /tmp $0.XXXX ) trap "rm -rf $z" exit # Restarting the daemon is the only way I have found # to generate the 'Stale' lines in the log file systemctl restart xymon sleep 120 # find the stale hosts reported today in the log file # build a file containing 'delete' commands for sed egrep "^$TODAY ............... Stale alert " ${logfile} |cut -d " " -f 6 \ ? | tr ':' '|' | sed 's#^#/^# ; s#$#/d#' > ${z} # Delete the stale hosts from the checkpoint file while xymond is stopped systemctl stop xymon && sed -i -f ${z} ${checkpointfile} && systemctl start xymon If anyone can offer any ideas into /why/ my xymon isn't purging dead alerts, I'd love to hear them. -- 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 On 11/17/2022 9:04 AM, John Thurston wrote: > > 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 0

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

Differences between vrsion 4.3.4 and 4.3.30
by Neil.Simmonds＠studio.co.uk 07 Dec '22

07 Dec '22

Hi all, I have some http tests on Xymon. They give a return code of 403 Forbidden and on my current Prod server (running Xymon 4.3.4) they are green. On my new server I'm setting up they are red with exactly the same hosts.cfg As far as I can see at the moment I need to add httpstatus="2..|403" to the tests on the new server but I'm wondering of there's some other place it can be set globally or if this is a genuine difference between 4.3.4 and 4.3.30 ? Kind Regards, Neil. Neil Simmonds Senior Platform & Middleware Engineer (Unix). 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.

2 1