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

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.