version `GLIBC_2.25' not found (required by /opt/splunk/bin/temp_splunk-preinstall)

[elio]

Dear fellas,

I am trying to upgrade the Splunk Enterprise from version 9.4.3 to 10.0.0 but i face these errors which don't let me install it. My system is CentOS Linux release 7.9.2009. Please any help is appreciated 🙂

Errors:

warning: splunk-10.0.0-e8eb0c4654f8.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID b3cd4420: NOKEY
verify that this sytem has all the commands we will require to perform the preflight step
This looks like an upgrade of an existing Splunk Server. Checking to see what component we are installing
extracting splunk_preinstall_base64 into splunk/bin directory
Adding execution bit
/opt/splunk/bin/temp_splunk-preinstall: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /opt/splunk/bin/temp_splunk-preinstall)
result: 1
splunk-preinstall upgrade check failed, exit
error: %pre(splunk-10.0.0-e8eb0c4654f8.x86_64) scriptlet failed, exit status 1
error: splunk-10.0.0-e8eb0c4654f8.x86_64: install failed
error: splunk-9.4.3-237ebbd22314.x86_64: erase skipped

[livehybrid]

Hi @elio 

/opt/splunk/bin/temp_splunk‑preinstall: /lib64/libc.so.6: version 'GLIBC_2.25' not found
means that the pre‑install script and/or its dependencies are require a minimum of glibc 2.25 .

CentOS 7 ships with glibc 2.17. 

Splunk 10.0 does not support CentOS 7, the supported OS and architectures can be seen at https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/10.0/plan-your-splunk-e... 

Typically CentOS isnt listed here but you should usually find that a matched RHEL version to CentOS version should mean compatibility (although Im not sure it strictly means its supported!)

I believe upgrade glibc is a pretty awful task as underpins much of the OS libraries, therefore all you would be able to do it upgrade the OS to a supported version.

🌟 Did this answer help you? If so, please consider:

• Adding karma to show it was useful
• Marking it as the solution if it resolved your issue
• Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

[elio]

Thank you @livehybrid

I will update the OS since it's the most reliable solution. I tried even to update glibc to version 2.25 but seems complicated.

[PickleRick]

Theoretically, glibc should be pretty much backward compatible so upgrading glibc to 2.25 should not break your system. Having said that - "should not" is not something I'd rely on in production.

Also - finding the more recent glibc packages (especially trustworthy ones) could prove to be a nigh-impossible task. And I wouldn't advise to compile it on site.

Furthermore - CentOS 7 is way past its EoL date...

[elio]

I totally agree u @PickleRick. Seems like the solution is upgrading the OS, tried so many things on updating it but is difficult. 

[livehybrid]

Ye @elio Upgrading glibc is a pain and ultimately risky, and still wont leave you in a supported state. Fingers crossed the OS upgrade goes smoothly for you!

🌟 Did this answer help you? If so, please consider:

• Adding karma to show it was useful
• Marking it as the solution if it resolved your issue
• Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing