Hi Bruno,

 

oh boy, I can confirm that you’re right and I forgot to mention, that -during my previous attempts- I’ve installed the repo ol10_u1_developer_EPEL (to be able to install fping)

and the GetPageSpeed-Repos using dnf -y install https://extras.getpagespeed.com/release-latest.rpm to be able to install pcre1.

 

For any reason I’ve then disabled those GetPageSpeed-Repos, that’s the reason why they didn’t show up in my earlier posts.

 

Hope that doesn’t throw you back too much, not knowing that I was using this – sorry for that!

 

Remembering this now, I’ve installed another fresh Oracle Linux 10.1, this time using ol10_u1_developer_EPEL as “extra add on repo” to be able to install fping.

 

To confirm things about pcre:

 

[root@cb-ol10 xymon-rrd-abi-compat-cleanup-1.9]# rpm -qa | grep pcre

pcre2-syntax-10.44-1.0.1.el10.3.noarch

pcre2-10.44-1.0.1.el10.3.x86_64

[root@cb-ol10 xymon-rrd-abi-compat-cleanup-1.9]#

 

 

[root@cb-ol10 xymon-rrd-abi-compat-cleanup-1.9]# dnf search pcre

Last metadata expiration check: 0:10:28 ago on Thu 05 Mar 2026 05:53:31 PM CET.

================================================================= Name & Summary Matched: pcre ==================================================================

pcre2-devel.x86_64 : Development files for pcre2

pcre2-syntax.noarch : Documentation for PCRE2 regular expressions

pcre2-utf16.x86_64 : UTF-16 variant of PCRE2

pcre2-utf32.x86_64 : UTF-32 variant of PCRE2

postfix-pcre.x86_64 : Postfix PCRE map support

rust-grep-pcre2.src : Use PCRE2 with the 'grep' crate

rust-grep-pcre2+default-devel.noarch : Use PCRE2 with the 'grep' crate

rust-grep-pcre2-devel.noarch : Use PCRE2 with the 'grep' crate

rust-pcre2.src : High level wrapper library for PCRE2

rust-pcre2+default-devel.noarch : High level wrapper library for PCRE2

rust-pcre2-devel.noarch : High level wrapper library for PCRE2

rust-pcre2-sys.src : Low level bindings to PCRE2

rust-pcre2-sys+default-devel.noarch : Low level bindings to PCRE2

rust-pcre2-sys-devel.noarch : Low level bindings to PCRE2

====================================================================== Name Matched: pcre =======================================================================

pcre2.x86_64 : Perl-compatible regular expression library

pcre2.src : Perl-compatible regular expression library

rust-grep+grep-pcre2-devel.noarch : Fast line oriented regex searching as a library

rust-grep+pcre2-devel.noarch : Fast line oriented regex searching as a library

[root@cb-ol10 xymon-rrd-abi-compat-cleanup-1.9]#

 

 

Now, again testing to compile using your updated branch https://github.com/bonomani/xymon/archive/refs/heads/rrd-abi-compat-cleanup-1.9.zip I’m getting this:

 

[root@cb-ol10 xymon-rrd-abi-compat-cleanup-1.9]# ./configure

 

Configuration script for Xymon

 

This script asks a few questions and builds a Makefile to compile Xymon

 

Checking your make-utility

Checking pre-requisites for building Xymon

 

Checking for fping ...

Xymon has a built-in ping utility (xymonping)

However, it is not yet fully stable and therefore it

may be best to use the external fping utility instead.

I found fping in /usr/sbin/fping

Do you want to use it [Y/n] ?

y

Checking to see if '/usr/sbin/fping 127.0.0.1' works ...

127.0.0.1 is alive

OK, will use '/usr/sbin/fping' for ping tests

NOTE: If you are using an suid-root wrapper, make sure the 'xymond'

      user is also allowed to run fping without having to enter passwords.

      For 'sudo', add something like this to your 'sudoers' file:

      xymon ALL=(ALL) NOPASSWD: /usr/sbin/fping

 

 

 

Checking for PCRE ...

test-pcre.c:1:10: fatal error: pcre.h: No such file or directory

    1 | #include <pcre.h>

      |          ^~~~~~~~

compilation terminated.

make: *** [Makefile.test-pcre:4: test-compile] Error 1

ERROR: Cannot compile using PCRE library.

/usr/bin/ld: cannot find test-pcre.o: No such file or directory

/usr/bin/ld: cannot find -lpcre: No such file or directory

collect2: error: ld returned 1 exit status

make: *** [Makefile.test-pcre:7: test-link] Error 1

ERROR: Cannot link with PCRE library.

Missing PCRE include- or library-files. These are REQUIRED for xymond

PCRE can be found at http://www.pcre.org/

If you have PCRE installed, use the "--pcreinclude DIR" and "--pcrelib DIR"

options to configure to specify where they are.

[root@cb-ol10 xymon-rrd-abi-compat-cleanup-1.9]#

 

Regards

Christian

 

 

Von: Bruno Manzoni <bruno.manzoni@ubi-network.ch>
Gesendet: Donnerstag, 5. März 2026 17:24
An: Becker Christian <christian.becker@rhein-zeitung.net>; Xymon mailinglist <xymon@xymon.com>
Betreff: Re: AW: [Xymon] Re: Two Draft PRs: PCRE Compatibility and RRDtool 1.9 Support – Request for Testing: Update

 

WARNUNG: Diese E-Mail kam von außerhalb der Organisation. Klicken Sie nicht auf Links oder öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.

 

Hi Christian, 

No problem about the delay.
Nothing urgent - please take your time.

A further question:
It looks to me like Oracle Linux 10.1 does not ship PCRE1 (I am currently blocked on 10.x because it only provides PCRE2). If you managed to build successfully, you must have had PCRE1 available. I looked into how this could be done and found that it is possible via:

sudo dnf -y install https://extras.getpagespeed.com/release-latest.rpm
sudo dnf -y install pcre-devel

Did you use this, or did you do something else?

Bruno

 

Le 05.03.2026 à 11:12, Becker Christian a écrit :

Hi Bruno,

 

sorry for the delay on my end.

 

I did the steps you’ve asked me to do using the updated branch, pls find the results in the attached files.

Further, again I’ve performed the debugging steps as you asked me in one of your earlier emails, the output is included also.

 

The newly installed Xymon is working, rrd graphs show up fine, zooming works as expected.

 

Hope you’ll find the information you’re looking for – for me I couldn’t see any difference compared to my previous install (but I don’t have your developer’s eyes).

 

Regards

Christian

 

 

Von: Bruno Manzoni via Xymon <xymon@xymon.com>
Gesendet: Mittwoch, 4. März 2026 05:43
An: xymon@xymon.com
Cc: Bruno Manzoni <bruno.manzoni@ubi-network.ch>
Betreff: [Xymon] Re: Two Draft PRs: PCRE Compatibility and RRDtool 1.9 Support – Request for Testing: Update

 

WARNUNG: Diese E-Mail kam von außerhalb der Organisation. Klicken Sie nicht auf Links oder öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.

 

HI Christian,

Many thanks for the Oracle Linux 10 details (RRDtool 1.8.0 runtime + devel, repo set).
This exactly confirms the edge case I suspected from your earlier output.

Tracking:
- Issue (includes a clearer explanation of the root cause): Detect RRDtool const-argv API by signature, not version (Oracle Linux 10 / RRDtool 1.8.0)
  https://github.com/xymon-monitoring/xymon/issues/81

- PR (updated to be mergeable: cleanup/reorder + robustness fixes):rrd: detect argv ABI and drop legacy rrdtool gates
  https://github.com/xymon-monitoring/xymon/pull/80

Request:
The PR is still Draft because I changed it after your last successful test.
If you have a moment, could you please recompile and do a quick runtime check again
on the updated branch, https://github.com/bonomani/xymon/archive/refs/heads/rrd-abi-compat-cleanup-1.9.zip
just to confirm it still behaves as expected on OL10?
Your testing is what makes this reliable.

And thanks again for the kind words.
Just to correct the picture a bit: I learned C at school in the 1990s, but I only resumed
seriously about two months ago, so I still make plenty of mistakes. More generally, in most
dev languages I am still a newcomer. I am also learning how to collaborate properly in an
upstream workflow - I am sure I still get things wrong and probably bother people sometimes,
but everyone has been very friendly. (Anyone can do it. The start can be frustrating, but 
at least you learn a lot along the way!).

For now, I am mainly trying to focus on the current blocking problems and help move them
forward, even if they are not easy topics.

Regards,
Bruno


Le 03.03.2026 à 08:53, Becker Christian via Xymon a écrit :

Hi Bruno,

 

wow, respect - reading the output of your commands i understand the difference between a developer (you) and a “normal” linux server admin with “from-now-to-then-programming capabilities” (me) 😉

Pls find the information as requested in the attached file.

 

For further information i issued these commands:

[root@cb-ol10 ~]# rpm -qa | grep -i rrdtool

rrdtool-1.8.0-20.el10.x86_64

rrdtool-devel-1.8.0-20.el10.x86_64

rrdtool-lua-1.8.0-20.el10.x86_64

rrdtool-perl-1.8.0-20.el10.x86_64

[root@cb-ol10 ~]#

[root@cb-ol10 ~]# dnf repolist

repo id                                                        repo name

ol10_UEKR8                                                     Oracle Linux 10 UEK Release 8 (x86_64)

ol10_addons                                                    Oracle Linux 10 Addons (x86_64)

ol10_appstream                                                 Oracle Linux 10 Application Stream Packages (x86_64)

ol10_baseos_latest                                             Oracle Linux 10 BaseOS Latest (x86_64)

ol10_codeready_builder                                         Oracle Linux 10 CodeReady Builder (x86_64) - (Unsupported)

ol10_distro_builder                                            Oracle Linux 10 Distro Builder (x86_64) - (Unsupported)

ol10_u1_developer_EPEL                                         Oracle Linux 10.1 EPEL Packages for Development (x86_64)

[root@cb-ol10 ~]#

 

Hope this helps. Pls let me know if I can do more tests, also some tests on completely new installs won’t be a problem, even with other common (and free) linux distros (the only limiting factor could be my time……).

 

Regards

Christian

 

 

Von: Bruno Manzoni via Xymon <xymon@xymon.com>
Gesendet: Montag, 2. März 2026 23:32
An: xymon@xymon.com
Cc: Bruno Manzoni <bruno.manzoni@ubi-network.ch>
Betreff: [Xymon] Re: Two Draft PRs: PCRE Compatibility and RRDtool 1.9 Support – Request for Testing: Update

 

WARNUNG: Diese E-Mail kam von außerhalb der Organisation. Klicken Sie nicht auf Links oder öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.

 

Hi Christian
This is a quite strange case:
Can you paste this commands:
-------------------
set -x

cat /etc/oracle-release 2>/dev/null || cat /etc/redhat-release 2>/dev/null

rrdtool --version 2>/dev/null || true
pkg-config --modversion librrd 2>/dev/null || echo "no pkg-config/librrd.pc"
pkg-config --cflags librrd 2>/dev/null || true
pkg-config --libs librrd 2>/dev/null || true

ls -l /usr/include/rrd.h /usr/local/include/rrd.h 2>/dev/null || true
readlink -f /usr/include/rrd.h /usr/local/include/rrd.h 2>/dev/null || true

grep -n 'rrd_graph' /usr/include/rrd.h 2>/dev/null | head -n 5 || true
sed -n '170,200p' /usr/include/rrd.h 2>/dev/null || true

echo | cc -E -v -xc - 2>&1 | sed -n '/#include <...> search starts here:/,/End of search list./p'
cc -H -E -xc /dev/null $(pkg-config --cflags librrd 2>/dev/null) 2>&1 | grep -E 'rrd\.h|include' || true

ldconfig -p 2>/dev/null | grep -i librrd || true

set +x

-------------------

and send me the result
Seems like you have a lib 1.8 but the devel package have a 1.9 header or something like that...
If we can confirm that this will be a good confirmation that this PR has some value and if it  resolve problem, I will ask to review/merge it (even it is not a perfect PR at all!: Don't worry seems to me the code is good (at least a part of it!, but the manner I did it is not): more on that also later...
Bruno

Le 02.03.2026 à 09:31, Becker Christian via Xymon a écrit :

Hi Bruno,

 

BOOOOM! Testing with your mentioned branch I was able to configure, make, make install on a fresh installed Oracle Linux 10 (using RRDtool 1.8.0). Congrats!

The configure finished without warning.

The startup of Xymon was normal and as expected, all the graphs came up fine without any problems, also is zooming the graphs.

For your information pls. see the attached files.

If i can or should do other tests pls let me know.

 

Thanks and regards

Christian

 

 

Von: Bruno Manzoni via Xymon <xymon@xymon.com>
Gesendet: Sonntag, 1. März 2026 08:04
An: xymon@xymon.com
Cc: Bruno Manzoni <bruno.manzoni@ubi-network.ch>
Betreff: [Xymon] Re: Two Draft PRs: PCRE Compatibility and RRDtool 1.9 Support – Request for Testing: Update

 

WARNUNG: Diese E-Mail kam von außerhalb der Organisation. Klicken Sie nicht auf Links oder öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.

 

Hi Cristian,

I just realized that you may have hit a weakness in the current 1.9 migration present in main, which I believe I have identified.

I did some additional work on this migration to improve cleanup and robustness, specifically to address the kind of issue you encountered. Since this is not merged into main yet, you may want to test my branch (even though I mentioned in my previous email not to do so):

https://github.com/bonomani/xymon/archive/refs/heads/rrd-abi-compat-cleanup-1.9.zip

It improves RRD version detection and includes several related cleanups. Your feedback on this branch would be very valuable, as I am not able to fully validate this work myself, and it currently relies on testing in real deployed installations.

If you test it, the critical points to verify are:

  1. Correct RRD 1.9.x version detection (no mis-detection or silent fallback)
  2. Clean build and startup (no ABI warnings or errors)
  3. Proper RRD updates at runtime (no crashes)
  4. Correct graph rendering in the web interface

If these behave correctly on your system, that would already provide strong validation.

Bruno

Le 28.02.2026 à 05:25, Bruno Manzoni via Xymon a écrit :

Hi Cristian,

You should stick with the main repository. I am currently running multiple experiments in my own repository (my default branch is focused on the CMake build and other changes), so using it would make collaboration and support more difficult. Apologies if this has caused any confusion.

In principle, it should also work with my repository, as I am trying not to modify the existing configure process. However, for clarity and stability, the main repository remains the recommended reference. Also did not add Oracle linux, will add it to my test.

The main repository (https://github.com/xymon-monitoring/xymon, branch main) should already contain the necessary patches to make this work. Roland carried out the core implementation there. I was not fully aware of this initially and am only proposing some additional adjustments, which are still under evaluation.

That said, there may still be edge cases where this does not work as expected. Please ensure that your repository is clean before compiling:
rm -f Makefile
./configure
make clean
make

Bruno

 

 

Le 27.02.2026 à 13:32, Becker Christian a écrit :

Hello to the list,

 

pls., sorry if it’s a stupid question….. (and I’m sure it is).

Working with Xymon since 2006, further using many own scripts and checks, i’ve read the post about PCRE2 and RRD1.9 compatibility.

During my last tests this was the main fail on an Oracle Linux 10 install.

 

My (probably stupid) question is: how can I do another test on my Oracle Linux 10 installation with any new Xymon sources / or with the most recent Xymon sources that are declared to work?

After doing a “git clone https://github.com/bonomani/xymon” and doing a configure, I’m running in the error with RRDtool:

 

Checking for RRDtool ...

Found RRDtool < 1.9.0 via pkg-config

Not RRDtool 1.0.x, checking for 1.2.x

test-rrd.c: In function ‘main’:

test-rrd.c:32:36: error: passing argument 2 of ‘rrd_graph’ from incompatible pointer type [-Wincompatible-pointer-types]

   32 |         result = rrd_graph(pcount, rrdargs, &calcpr, &xsize, &ysize, NULL, &ymin, &ymax);

      |                                    ^~~~~~~

      |                                    |

      |                                    char **

In file included from test-rrd.c:3:

/usr/include/rrd.h:185:5: note: expected ‘const char **’ but argument is of type ‘char **’

  185 |     const char **,

      |     ^~~~~~~~~~~~~

make: *** [Makefile.test-rrd:4: test-compile] Error 1

ERROR: Cannot compile with RRDtool.

ERROR: Linking with RRDtool fails

RRDtool include- or library-files not found.

These are REQUIRED for trend-graph support in Xymon, but Xymon can

be built without them (e.g. for a network-probe only installation.

 

RRDtool can be found at http://oss.oetiker.ch/rrdtool/

If you have RRDtool installed, use the "--rrdinclude DIR" and "--rrdlib DIR"

options to configure to specify where they are.

 

I’m pretty sure I’ve done something odd or forgot something, since Bruno wrote that he could successfully test with AlmaLinux 8/9/10, so it should also work with Oracle Linux 10?

 

Regards

Christian

 

 

 

Von: Bruno Manzoni via Xymon <xymon@xymon.com>
Gesendet: Montag, 23. Februar 2026 17:20
An: xymon@xymon.com
Cc: Bruno Manzoni <bruno.manzoni@ubi-network.ch>
Betreff: [Xymon] Re: Two Draft PRs: PCRE Compatibility and RRDtool 1.9 Support – Request for Testing: Update

 

WARNUNG: Diese E-Mail kam von außerhalb der Organisation. Klicken Sie nicht auf Links oder öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.

 

Hi All,

Thanks, Scot.

I do my best (but to be honest, I am not sure it is enough):

* It is very difficult to reach a strong level in C programming (and it seems to me that Nicola, Roland, and Mark are the ones for now).
* It is very difficult to understand Xymon (at least for me).
* The build process is also quite difficult.
* The current situation is quite blocking: Mark and Roland maintain FreeBSD and Debian.

  * Their versions have diverged (and they maintain multiple ones), so the first step is to make them converge again without breaking anything. This is quite difficult, because it implies changes to their working branches that could introduce regressions.
  * Then there are new OS versions, with new packaging issues, such as MD5.
  * We also need to understand what to do, how to do it, and learn to work together.
  * At least for me, it is difficult to make progress on the CMake build if packaging and dependencies keep changing.

The main problems I see for now:

1. How to decide what to include in the code base and what not to include.

   * There are already some PRs, but are they done correctly? The PR itself? The code inside it? Do we need guidelines?
   * It seems to me that we need someone to bring consistency to this process. If anyone is willing, could you:
     * Propose guidelines,
     * Take responsibility for driving consistency in reviews and merges,
     * Or suggest a better approach?

2. It seems difficult to perform "real" testing across the full environment of each OS.

   * Docker could help.
   * Any ideas, or would anyone like to help set this up?

Anyway, working a little bit with Nicola and Roland has been very pleasant: professional and very kind.

Bruno

Le 23.02.2026 à 15:54, Scot Kreienkamp a écrit :

Excellent progress.  Thanks for your had work Bruno, the community appreciates it!

 

 

Scot Kreienkamp | Applications Infrastructure Architect | La-Z-Boy Corporate 
(734) 384-6403 | 1-734-915-1444 | Scot.Kreienkamp@la-z-boy.com
One La-Z-Boy Drive | Monroe, Michigan 48162 | la-z-boy.com
facebook.com/lazboy  | instagram.com/lazboy | youtube.com/lazboy

LaZboy Logo

From: Bruno Manzoni via Xymon <xymon@xymon.com>
Sent: Friday, February 20, 2026 5:10 PM
To: xymon@xymon.com
Cc: Bruno Manzoni <bruno.manzoni@ubi-network.ch>
Subject: [Xymon] Re: Two Draft PRs: PCRE Compatibility and RRDtool 1.9 Support – Request for Testing: Update

 

Hi all,

2nd follow-up.

1) PCRE2 - Compatibility layer (PCRE1 + PCRE2) vs full migration

I have successfully built the current codebase using PCRE2 only on all the
following platforms (see list below).

The oldest system tested was CentOS 7, and it builds fine.
Note: CentOS 7 packages are no longer available on the standard RHEL repos,
so an archive mirror must be used.

Next step:
I will drop my compatibility branch and move to Roland's work.

Plan:
- Replace PCRE1 with PCRE2 (option 2)
- Use Roland's branch as the base going forward
- Cut a minor release, even if this could have been a major-release item
- Dcoument


2) RRD1.9

Some patches have been applied, but they still need proper testing.
There are quite a few compilation warnings. I have prepared a cleanup
patch, but I will not apply it at this stage.

3) MD5 warnings

Several systems now mark MD5 as deprecated, which generates warnings
during compilation (notably on newer Linux distributions and macOS).

This does not currently break the build, but it impacts clean
compilation on modern systems and should be addressed.

 

Summary: with the current patch set (still needs review), I successfully built:
Both RRD and PCRE changes (as well as MD5 deprecation) have a direct
impact on installing Xymon on newer systems.

Alpine: 3.19/3.20/3.21/3.22/3.23/edge
Arch Linux: latest/base
Ubuntu: 20.04/22.04/24.04
Debian: 11.11/12.13/13.3
CentOS: 7
Rocky Linux: 8/9
AlmaLinux: 8/9/10
Fedora: 40/41/42
openSUSE: 15.5/15.6/16.0/tumbleweed
FreeBSD: 13.5/14.3/15.0
NetBSD: 9.2/9.3/9.4/10.0/10.1
OpenBSD: 7.6/7.7/7.8
macOS: 14/15/26/latest

 

5) CMake build

Plan:
- Reproduce the current configure / make / make install workflow
- Keep both build systems in parallel for some time

CMake is not intended to replace the current build immediately.
This will be a gradual transition.


Bruno

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. 







_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com






_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com





_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com




_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com