Status: Open (View Workflow)
Jenkins 2.121.3 works fine on CentOS 5.11 but fails to start after upgrade to 2.38.1:
Starting Jenkins Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at Main._main(Main.java:227) at Main.main(Main.java:160) Caused by: java.lang.UnsatisfiedLinkError: /tmp/jna--1712433994/jna6461328951212197580.tmp: /lib64/libc.so.6: version `GLIBC_2. 7' not found (required by /tmp/jna--1712433994/jna6461328951212197580.tmp) at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1824) at java.lang.Runtime.load0(Runtime.java:809) at java.lang.System.load(System.java:1086) at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:947) at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:922) at com.sun.jna.Native.<clinit>(Native.java:190) at com.sun.akuma.CLibrary.<clinit>(CLibrary.java:89) at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:128) at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:116) at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104) at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92) at com.sun.akuma.Daemon.daemonize(Daemon.java:106) at com.sun.akuma.Daemon.all(Daemon.java:88) ... 6 more
yum downgrade allowed for easy roll-back.
Personsally, I have no expectation of continuing support for CentOS 5 (I am in the process of migrating to CentOS 7) but report the issue as there is nothing mentioned in the documentation. eg
- relates to
JENKINS-53924 Jenkins 2.136+ is not restartable with GLIBC 2.5
JENKINS-52771 Bump JNA jar to 4.5.1+ for Jenkins to work gracefully on s390x
FTR this is discussed in https://github.com/java-native-access/jna/issues/771 . https://github.com/java-native-access/jna/pull/840 is a pull request which sets 2.7 as a minimum dependency
And yes, CentOS 5 is stuck at 2.5: https://serverfault.com/questions/372243/glibc-2-7-on-centos-5-5 . I see no easy way to support it without reverting the change (which would be unfortunate) or serious changes in Jenkins startup logic.
danielbeck I propose adding end of Centos 5 support to upgrade guidelines
oleg_nenashev Glibc 2.7 is a must and CentOS 5 won't support it as its EOL this year . I don't think revert is the option here as newer things will have dependencies and that would stall everything. We probably add to documentation that CentOS 5 won't be supported anymore.
Is it really newsworthy that Jenkins does not support an OS release that hasn't been supported by its vendor/project for 18 months?
I'm not sure, but feel free to add it to our docs. No need to ping me here.
Documentation patch: https://github.com/jenkins-infra/jenkins.io/pull/1815
Would someone mind commenting here if CentOS 5 is still a valid for the Jenkins build agent?
We do not run Jenkins on CentOS 5 – but we still do use several build machines which are CentOS 5 for backwards compatibility builds. I believe JNA is used by the build agent for some items.
We want to understand if upgrading Jenkins to the latest LTS build will require any special processes to continue to use CentOS 5 build machines.
I am afraid agents will be impacted as well, e.g. process management or SVN checkout with SVNkit.
Have not tested it, but there are a lot of dependencies on JNA in the codebase: https://github.com/search?l=Java&q=org%3Ajenkinsci+jna&type=Code
JENKINS-52771in 2.136 is a root cause of it.
I agree that it needs to be documented at least. GLIBC 2.7 is required