Nagios Support Forum

I've run upgrades using manual method (Update via GUI has never worked) for almost a year now. No issues with it until this upgrade.

Any assistance or direction would be appreciated.

My server runs multiple versions of python3 (3.9 and 3.12 primarily) and there was an issue with pip that I finally got resolved.

Now I get the following and it's a bit over my head. I had to install python3-devel to even get rrdtool to function FYI

Collecting rrdtool
Using cached rrdtool-0.1.16.tar.gz (22 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Building wheels for collected packages: rrdtool
Building wheel for rrdtool (pyproject.toml): started
Building wheel for rrdtool (pyproject.toml): finished with status 'error'
error: subprocess-exited-with-error

× Building wheel for rrdtool (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [26 lines of output]
/tmp/pip-build-env-dg3_y7wa/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py:287: UserWarning: Unknown distribution option: 'test_suite'
warnings.warn(msg)
/tmp/pip-build-env-dg3_y7wa/overlay/lib/python3.12/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

********************************************************************************
Please consider removing the following classifiers in favor of a SPDX license expression:

License :: OSI Approved :: GNU Lesser General Public License v2 (LGPLv2)

See https://packaging.python.org/en/latest/ ... l/#license for details.
********************************************************************************

!!
self._finalize_license_expression()
running bdist_wheel
running build
running build_ext
building 'rrdtool' extension
creating build/temp.linux-x86_64-cpython-312
gcc -pthread -fno-strict-overflow -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC -DPACKAGE_VERSION=\"0.1.16\" -DWITH_FETCH_CB=1 -I/tmp/pip-install-mjs4f0ws/rrdtool_6015064f020f4c018ee04f6b572a1b61 -I/usr/local/include -I/usr/include/python3.12 -c rrdtoolmodule.c -o build/temp.linux-x86_64-cpython-312/rrdtoolmodule.o
rrdtoolmodule.c:25:10: fatal error: Python.h: No such file or directory
#include <Python.h>
^~~~~~~~~~
compilation terminated.
error: command '/usr/bin/gcc' failed with exit code 1
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for rrdtool
Failed to build rrdtool
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> rrdtool

Hi clangbecker,

Sorry to hear about the difficulties. Could you tell us which distro and version you are using ? Based on some of the information provided it looks like you might be using RHEL 8 but we would like to confirm.

So it looks like build of rrdtool is failing because it's looking for a python include file ( Python.h ) and it has a version specific include path in the compilation line ( -I/usr/include/python3.12 ).

Could you run the following commands on your system and let us know what you get back ?
Thanks and kind regards,
Keith

Thank you.

Yes we are running RHEL8. I guess my question is why is this an issue now when it never has been, at least in the past year? What was added to the installer that requires these additional python3 configs?

I primarily run 3.12 but had to keep 3.9 for PagerDuty pdagent as it wasn't compatible at time of install with 3.12

[root@is-nagiosxi-east ~]# find /usr/include -name Python.h -ls
9123731 4 -rw-r--r-- 1 root root 3221 Dec 23 2018 /usr/include/python3.6m/Python.h
1175934 4 -rw-r--r-- 1 root root 3532 Oct 31 12:40 /usr/include/python3.9/Python.h

This looks like I need to get 3.12 added I would assume?

[root@is-nagiosxi-east ~]# ls -laF /usr/bin/python*
lrwxrwxrwx 1 root root 36 Jan 7 07:20 /usr/bin/python -> /etc/alternatives/unversioned-python*
lrwxrwxrwx. 1 root root 9 Dec 1 2023 /usr/bin/python2 -> python2.7*
-rwxr-xr-x. 1 root root 8024 Dec 1 2023 /usr/bin/python2.7*
lrwxrwxrwx 1 root root 25 Mar 26 06:44 /usr/bin/python3 -> /etc/alternatives/python3*
-rwxr-xr-x 1 root root 7752 Mar 3 03:38 /usr/bin/python3.12*
lrwxrwxrwx. 1 root root 31 Nov 28 2023 /usr/bin/python3.6 -> /usr/libexec/platform-python3.6*
lrwxrwxrwx 1 root root 17 Nov 28 2023 /usr/bin/python3.6-config -> python3.6m-config*
lrwxrwxrwx. 1 root root 32 Nov 28 2023 /usr/bin/python3.6m -> /usr/libexec/platform-python3.6m*
lrwxrwxrwx 1 root root 39 Nov 28 2023 /usr/bin/python3.6m-config -> /usr/libexec/platform-python3.6m-config*
lrwxrwxrwx 1 root root 46 Nov 28 2023 /usr/bin/python3.6m-x86_64-config -> /usr/libexec/platform-python3.6m-x86_64-config*
-rwxr-xr-x 1 root root 7776 Nov 26 06:50 /usr/bin/python3.9*
-rwxr-xr-x 1 root root 57 Nov 26 06:49 /usr/bin/python3.9-config*
-rwxr-xr-x 1 root root 3616 Nov 26 06:42 /usr/bin/python3.9-x86_64-config*
lrwxrwxrwx 1 root root 32 Mar 26 07:21 /usr/bin/python3-config -> /etc/alternatives/python3-config*

Well that would explain it.

I had installed python3-devel to get past my initial errors. After doing some research based on the find command you asked me to run, I found the 3.12 headers were missing and were not installed with my previous command. I had to install python3.12-devel and it started processing the upgrade.

Thank you.

Hi clangbecker,

Glad you were able to resolve the problem -- you're a step ahead of us this morning. Unfortunately we've been seeing a number of issues with python and RHEL 8 over the years and some "minor version" issues with packages recently. One general recommendation is keep track of the web of python links in /usr/bin/ and if you start having python issues ( especially after OS updates ) check to see if links have changed.

Once again we're glad you were able to resolve the issue and we'll close out the thread.

Have a great rest of your week !!!
Keith