Jenkins slave jobs failing on “Unexpected termination of channel”

Question

I am currently seeing a set of errors across my builds.

Is this expected behaviour if you loose Jenkins (say to a box crash, or a kill -9)?

Or is there somet

Answer 1

You'll see that error if the Jenkins master loses connectivity with the slave. It could be due to any of the three issues you listed above:

• Manually killing the slave process

• The slave server becoming unavailable

• A network problem between the master and the slave

Answer 2

For me the node configuration had a wrong "Remote FS Root". So check if all the config parameters on the master for this slave node are correct. Jenkins doesn't complain a thing but terminates the connection.

I struggled a lot before determining it was the node config. At least the error message on the master should be more explicit or informative.

Answer 3

I resolved it by a simple restart of the master Jenkins server.

Answer 4

Since 1.520, Jenkins requires Java 6 or later, one of the possibility of this error is that you dont have java 6 or later on slave/remote. Resolution is to update your remote machine with java 6 or later or set correct environment variable which SSH uses while it logs in into slave machine.