Cannot start after upgrade to v2.1

Community Support
1

Hello,

after a RPM-upgrade to v2.1 on a CentOS Stream 8-testsystem Datagerry cannot be started, this is the error i get:

# /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s -d
[4625] Error loading Python lib '/tmp/_MEI7yGCEN/libpython3.9.so.1.0': 
 dlopen: /lib64/libpthread.so.0: version `GLIBC_2.30' not found (required by /tmp/_MEI7yGCEN/libpython3.9.so.1.0)

# dnf list installed | grep -i glibc
glibc.x86_64                             2.28-241.el8                       @baseos
glibc-common.x86_64                      2.28-241.el8                       @baseos
glibc-devel.x86_64                       2.28-241.el8                       @baseos
glibc-gconv-extra.x86_64                 2.28-241.el8                       @baseos
glibc-headers.x86_64                     2.28-241.el8                       @baseos
glibc-langpack-en.x86_64                 2.28-241.el8                       @baseos

Does this mean that v2.1 cannot be used on a CentOS/RHEL-8 system and we would have to upgrade the OS to v9 first?

(List of supported GLIBC-versions per RHEL-release: What glibc version is shipped with a particular Red Hat Enterprise Linux? - Red Hat Customer Portal)

Kind regards,
Michael

2

Hi @MiB ,
to be able to compile the latest changes into the RPM package we required a higher Version of GLIBC.

You should update your OS to v9 first and then is should work.

We already tryed to make it work on CentOS/RHEL-8 systems but did not found a solution so far.

BR Adnan