- Xymon - Xymon mailman web

Renaming 4.x-master branch
by Bruno Manzoni 20 Jan '26

20 Jan '26

3 3

workflow beginnings and a few thoughts...
by Scot Kreienkamp 20 Jan '26

20 Jan '26

Gents, * I have a basic workflow together that triggers on creation of tags of pattern rel-*. When you create a tag following that pattern it will create a .tar.gz (ex: tag rel-4.3.31 will produce xymon-4.3.31.tar.gz, which will expand into directory xymon-4.3.31) of the repo contents and upload it to the tag. The change notes are created from the commits and are visible, and the SHA signature is visible as well. * The xymon mailing list archive seems to not have anything after 2024, and the link to it on the GitHub readme is broken. I don't know where the domain or xymon(a)xymon.com<mailto:xymon@xymon.com> mailing list resides, but should we consider updates to that and/or xymon.com? * We need the documentation somewhere more conducive to editing. Should we copy the documentation on xymon.com into the wiki on GitHub, or is there somewhere better? There's a lot of community knowledge that would be helpful to start gathering. Would anyone like to take on migrating/updating documentation? * I'll start trying to learn how to create the RPMs for the various versions of RedHat, and a docker image. If anyone from the Terabithia archive would be willing to share their RPM pipeline or directions I would certainly appreciate not having to recreate the wheel. It would also help ensure continuity with existing RPMs. Thanks! Scot Kreienkamp | Applications Infrastructure Architect | La-Z-Boy Corporate (734) 384-6403 | 1-734-915-1444 | Scot.Kreienkamp(a)la-z-boy.com One La-Z-Boy Drive | Monroe, Michigan 48162 | la-z-boy.com<http://www.la-z-boy.com/> facebook.com/lazboy<http://facebook.com/lazboy> | instagram.com/lazboy<https://instagram.com/lazboy> | youtube.com/lazboy<http://youtube.com/lazboy> [cid:lazboy_2024_inc_navy_4a4d68ec-613a-4141-a2aa-d73a2ae749f6.png] 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.

3 2

Additional technical context – divergence between main and 4.x-master
by Bruno Manzoni 16 Jan '26

16 Jan '26

Hi all, Below is *a summary of the divergence* between "*main" (4.3.30) *and "*4.x-master"(4.4 dev). *Repo: github.com/xymon-monitoring/*xymon* *INTRODUCTION* *Goal: identify what exists in "main" and is missing in "4.x-master".* Focus on bug fixes and security. *MISSING COMMITS (GIT commands)* Functional commits present only in main (excluding releases): 28 Scope of unmatched commits: - 6,489 insertions - 4,333 deletions - Net +2,156 LOC (Line of Code) (See Git commands below.) *MISSING COMMITS without semantic equivalent (AI powered analysis)* Security / CVE - 484edeb2 – CVE-2019-* buffer overflow / XSS - 6dbcd04e – CVE-2016-2056 / 2058 command + JS injection - 1a4511a7 – CVE-2016-2057 IPC permissions - df404398 – CVE-2016-2055 config file exposure Crash / memory safety - ba47d2f9 – xymongen availability segfault - 81656c6a – crash on missing allevents - c3a8a2c9 – RPC buffer size miscalculation - 4f444be0 – netapp RRD memory leak - bee6eee8 – double-free in xymond - 1ab01960 – NULL checks to prevent segfault Correctness / parsing - 8ab6c328 – RRD DS comma parsing - eda84777 – SNMPv3 config parsing - a123a029 – do_temperature parentheses parsing - 3f266c08 – do_temperature parsing fixes - 3227f657 – logfetch off-by-one with triggers - 95092119 – history logs with dash/underscore names - 9f62e942 – NONETPAGE parsing tightening Build / portability - 4e846f16 – GCC diagnostics guards - b1414cd8 – stdint.h include tightening - 3eed090e – Fedora/GCC compile fixes - 0a546cc1 – avoid unnecessary mod_authz_groupfile loading Total: 21 commits *GIT COMMANDS USED * - Identify unmatched commits: git log --oneline --cherry-pick --left-right main...4.x-master | grep '^<' - Per-commit size: git show --shortstat - LOC aggregation: git log --cherry-pick --left-right --numstat main...4.x-master - Rewrite-aware comparison: git range-diff --stat 4.3.22-root..main 4.3.22-root..4.x-master - Security commit isolation: git log 4.3.22-root..main --oneline | grep -Ei 'CVE|security|XSS|overflow' I can make mistakes. Bruno

2 2

Project direction and next steps - feedback requested
by Bruno Manzoni 16 Jan '26

16 Jan '26

Hi all, Quick follow-up. So far, there seems to be agreement that: * 4.3 is the current production version. * 4.4 is unfinished and experimental. * The main blocker is the lack of a shared Git workflow. To move forward, feedback is needed, and input from everyone is welcome. Feedback from long-time maintainers and contributors would be especially appreciated (JC Cleaver in particular; Henrik Storner is already involved). In short: * Who is willing to help? * Is https://github.com/xymon-monitoring/xymon-svn-mirror a good place to move forward? * If not, is there a better proposal (for example under https://github.com/xymon-monitoring)? * What should be the next concrete step? Short replies are perfectly fine. Thanks, runo

10 15

Xymon development inquiry
by Mark Felder 15 Jan '26

15 Jan '26

Hi all, Is Henrik or JC Cleaver still working on Xymon? I am still the maintainer of the packages on FreeBSD and have been crawling through the mailing list archives, Debian packages, etc and have accumulated a lot of patches that have never made it into a Xymon release. I'm aware there's an Alpha of 4.4 with IPv6 support and a lot of changes too, but it's very much unfinished last I saw (IPv6 for client-server but Xymonnet not refactored to be able to execute IPv6 tests IIRC...) I'd like to light the fire again. Xymon is something special and I keep coming back to it. It's just the perfect amount of simplicity and power to make monitoring things easy. I have privately converted the Xymon source repo to Git much like has been done at https://github.com/xymon-monitoring/ but I've preserved all the tags and backdated them properly. My own list of changes is growing: - Fixed buffer overflow in trends which causes it to stop showing graphs if you have too many - Fix FreeBSD graphing of vmstat/CPU utilization (has been broken for many years) - Custom graphs docs do not match reality -- you can't submit NCV or trends data to be processed into RRD files and then display them on any status page you want. I've fixed this; you can put custom graphs on any status page now, not just ones that already have graphs - added ALPN support to xymmonnet so you can create custom protocols to do things like test IMAP through Nginx HTTPS/443 port - WIP -- debugging DS rule processing in analysis.cfg which doesn't obey "first match" like everything else, hope to have this nailed down soon Please reach out... Mark

7 13

Job: Xymon Integration Engineer (?!)
by Mark Felder 15 Jan '26

15 Jan '26

I don't know if this is real but I found it when searching for something else Xymon related: "The Xymon Integration Engineer will develop, deploy, and administer Java applications, configure the Xymon monitoring system, and integrate it with existing platforms." https://builtin.com/job/xymon-integration-engineer/8146321 Mark

1 0

Re: Xymon development inquiry
by Bruno Manzoni 14 Jan '26

14 Jan '26

Hi Nicola, Thanks a lot for your message and for your long experience with Hobbit and Xymon. It’s great to hear you’d like to help and have ideas. For now, I’m focusing on getting the Git migration settled and agreed on by everyone. Broader topics like 4.4, Docker, or integrations probably make more sense to discuss once that’s clear. By the way, I’ve invited you to collaborate on the repository. Thanks again for the feedback. Bruno Le 14.01.2026 à 06:11, Nicola a écrit : > Hi. > I have neen using Hobbit and then Xymon since about 22 years, I know > shell and I know Python very well. > I jave ideas on what could be added or improved, and I would love to > see Xymon thrive o please count me in if I can help. > > If Xymon 4.4 can be used as a replacement of 4.3, why not start from > there? > Can we include a docker version? > I see an attempt by Dewey Sasser 10 years ago. > Home assistant integration? > Multi tenancy? > > > Nicola > https://xymon.nicolacanepa.net > > Bruno Manzoni via Xymon wrote: > > >> Thanks Mark for checking and for the feedback. >> >> Good to know everything looks fine on your side and that the tags and >> history came through correctly. >> >> About switching the default branch to `main`: that’s a future step. For >> now, I’m avoiding making decisions on my own. >> >> I fully agree that reaching consensus on the git forge is the next step. >> Once that’s clear, starting to collect issues and get things moving >> again would be awesome. >> >> By the way, I’ve invited you to collaborate on the repo. Thanks very >> much for your feedback. >> >> Bruno >> >> Le 14.01.2026 à 00:10, Mark Felder via Xymon a écrit : >> >>> On 1/13/26 14:12, Bruno Manzoni via Xymon wrote: >>> >>>> Hi All, >>>> >>>> I redid a test of an initial import of the Xymon SVN repository into >>>> Git: >>>> >>>> https://github.com/xymon-monitoring/xymon-svn-mirror >>>> >>>> The goal was a faithful copy, not a cleanup: >>>> >>>> - full SVN history imported >>>> - no commits rewritten or dropped >>>> - no branches renamed >>>> - no tags modified >>>> >>>> Two helper scripts used for the migration (SVN mirroring and >>>> SVN-to-Git conversion) are included in the repository for >>>> transparency and reproducibility. A short document (GIT-MIGRATION.md) >>>> explains the methodology and the current status. >>>> >>>> Current state: >>>> >>>> - 4.x-master is still the default branch, matching the historical SVN >>>> layout >>>> - a main branch was added to document the migration and related >>>> scripts; it will probably be removed later >>>> - no decisions have been made yet (branch naming, cleanup, or future >>>> governance) >>>> >>>> I would really appreciate if experienced contributors could take a >>>> look at this work, as I don’t feel qualified to fully assess it myself. >>>> Henrik, if you’re available to validate it, you’ve been invited to >>>> the repository with full access, as have JC, TOM, and others. Please >>>> let me know if access doesn’t work. >>>> >>> >>> >>> >>> This looks similar to what my own effort produced. The tags are >>> correctly backdated, all looks well. I think the only change that >>> needs to happen is to alter the default branch to "main". >>> >>> If we can find consensus on moving development to this or another git >>> forge hosted somewhere/anywhere, I'd love to begin creating issues and >>> MRs with the patches I've collected and created so we can get the ball >>> rolling on a 4.3.31 release. >>> >>> >>> Mark >>> _______________________________________________ >>> Xymon mailing list -- xymon(a)xymon.com >>> >> To unsubscribe send an email to xymon-leave(a)xymon.com >> _______________________________________________ >> Xymon mailing list -- xymon(a)xymon.com >> To unsubscribe send an email to xymon-leave(a)xymon.com

1 0

SMTP+STARTTLS
by Grant Taylor 08 Jan '26

08 Jan '26

Hi, Is there a way to have Xymon monitor the TLS certificate on SMTP while using SMTP's STARTTLS verb? I'm already monitoring the certificate on SMTPS (SMTP with implicit TLS on port 465) but I'd like to also monitor the certificate on SMTP+STARTTLS (SMTP with explicit TLS via STARTTLS verb on port 25). I've got some weird systems where the ports aren't using the same daemon / config, as such I can't rely on both being the same. -- Grant. . . .

4 9

ALPN support for network tests
by Mark Felder 26 Nov '25

26 Nov '25

Hello, I had a need to monitor some services that are being multiplexed/proxied by Nginx with the stream module like so: stream { map $ssl_preread_alpn_protocols $proxy { default 127.0.0.1:8443; ~\bsmtp\b 127.0.0.1:465; ~\bimap\b 127.0.0.1:993; } server { listen 443; listen [::]:443; proxy_pass $proxy; ssl_preread on; } } This detects the ALPN handshake and passes the traffic through to the real IMAP or SMTP backend. Monitoring this was not possible with Xymon, but I have a working implementation attached. This will allow you to define a new protocol like [imaps443] options ssl,alpn=imap port 443 Now I can successfully monitor these services. I considered trying to extend the http monitoring tests to allow this as well so you can force HTTP/2 or HTTP/3 even but I don't think that's possible. Perhaps in another life the HTTP testing should be refactored around libcurl so a giant featureset becomes automatically available... :) Disclaimer: this patch was only made possible with the help of Qwen as I'm not super experienced in C. I didn't bother cleaning up its obnoxious inline comments, but after a cursory review it doesn't seem like bad code... Mark

1 0

RPMS for EL10
by Dirk Kastens 21 Nov '25

21 Nov '25

Hi, will there be xymon RMPs for Enterprise Linux 10? The latest RPMs on Therabitia are for el9. The directory "el10" is empty. https://terabithia.org/rpms/xymon/el10/x86_64/ -- Regards, Dirk Kastens

1 0