I am experiencing an issue where my Jenkins agent goes offline with the error message: “This node is offline because the JVM version of the agent is incompatible with the controller one.” This issue started after updating some plugins.
This node is offline because the JVM version of the agent is incompatible with the controller one.
Details:
****Jenkins version: 2.426.3
Jenkins Controller Java Version: 17.0.14
Jenkins Agent Java Version: 17.0.9 Steps Taken:
Verified that both the controller and the agent are running Java 17.
Set the JAVA_HOME environment variable on both the controller and the agent.
Updated the remoting.jar file.
Additional Information:
The issue started after updating some plugins.
Any assistance or suggestions to resolve this issue would be greatly appreciated.
I figured out the issue, and it was due to the plugin Versions Node Monitors. I adjusted the node monitor settings, which resolved the problem. Thank you for your response.
In case it helps someone, we had a similiar issue where after upgrading to Java 17, agents would randomly disconnect with the following error:
I/O error in channel
java.io.StreamCorruptedException: invalid stream header: 636F7272
java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:958)
at java.base/java.io.ObjectInputStream.<init>(ObjectInputStream.java:392)
at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:50)
at hudson.remoting.Command.readFrom(Command.java:141)
We do not use the Versions Monitors plugin
After digging, we discovered that certain versions of OpenJDK were causing the issues. For example 17.0.13 in the Agents and the Main Jenkins server. The issue went away after upgrading and keeping consistent OpenJDK Version numbers. We are planning an upgrade to Java 21 soon and we are hoping we won’t experience the same issues there