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