GLIBC-2.27 not found

Answered

I'm using IntelliJ IDEA 2025.2 on CentOS 7.9.

Upon startup, I encounter the following error: 

Cannot start the runtime

Caused by:
 0: Failed to load 'libjvm.so'
 1: /usr/lib64/libm.so.6: version `GLIBC_2.27' not found (required by /local/***/ideaIC-252.223892.409/jbr/lib/server/libjvm.so)

I don't have root permissions, but I do have access to glibc-2.27. I tried setting LD_LIBRARY_PATH and modifying idea's rpath, but neither approach worked.

Is there any workaround or recommended solution for this situation?

0
10 comments

Unfortunately, this workaround doesn't apply. 

The linked solution addresses a JDK mismatch, but my logs confirm that the bundled JetBrains Runtime (JBR) is already being used.

0
How did you manage to update/install GLIBC 2.27 in CentOS 7.9? What is the output of "ldd --version"?
0

I downloaded the glibc 2.27 source code and compiled it to /local/***/glibc2.27. 

I set LD_LIBRARY_PATH to /local/***/glibc2.27:$LD_LIBRARY_PATH and also used patchelf --set-rpath /local/***/glibc2.27/lib idea. 

And ldd --version reports ldd (GNU libc) 2.17.

0
I'm afraid this can not be easily done without risks. The real problem here is how to update glibc in an EOL OS rather than an IDE issue. I'd suggest you to update the OS to a newer version.

Someone made it in below blog

https://blog.51cto.com/ting0119/13815148
0

I found the solution — I had missed the --set-interpreter step. After adding it, the "glibc 2.27 not found" error no longer appears.

0
Where did you set it?
0

I don't have root permissions, but I do have access to glibc-2.27. I tried setting LD_LIBRARY_PATH and modifying idea's rpath, but neither approach worked. Baseball Bros

0
This is a system requirement, not a setting you can override. Starting with 2025.1, IntelliJ IDEA on Linux requires glibc 2.28 or newer. Your system has glibc 2.27, which is below that minimum, so the bundled JetBrains Runtime won't start.

That's also why the LD_LIBRARY_PATH and rpath changes didn't help. glibc and its dynamic loader (ld-linux.so) are a matched pair, and the runtime is linked against the system glibc. Pointing those at a newer libc copy usually crashes the process rather than loading it, so you can't inject a newer glibc this way without root-level changes to the machine.

Since you don't have root, a few things that work without changing the system glibc:

1. Use an older IDE build. Versions 2024.3 and earlier were built against the older glibc requirement, so they should start on your machine. You can install one without root by extracting the .tar.gz into your home directory and running bin/idea.sh. Older builds are listed on the JetBrains download page under previous/other versions.
2. Use Remote Development. Run the IDE backend on a host that has glibc 2.28 or newer and connect to it from your current machine with the lightweight client. Your old-glibc machine only runs the client.
3. If you can get the machine upgraded later, the real fix is a distribution that ships glibc 2.28 or newer.

You can read more about the requirement here:
- System requirements: https://www.jetbrains.com/help/idea/2025.3/installation-guide.html#requirements 
- Background on the change: https://blog.jetbrains.com/idea/2025/01/updated-system-requirements-for-linux-gnu-c-library-glibc/
0

Please sign in to leave a comment.