-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins ver. 1.549
OS of master node: Linux version 2.6.32-431.11.2.el6.centos.plus.x86_64
OS of slave node: Linux version 2.6.32-431.11.2.el6.x86_64 (mockbuild@c6b8.bsys.dev.centos.org)
ssh-slaves plugin version: 1.6
hi
we are starting our slave via "launch slave agents on unix machines via SSH"
the slave is working properly but whenever Jenkins master is restarted, the slave is gone and needs to be created again.
is this epected bahavior?
thanks
- duplicates
-
JENKINS-22525 "incompatible InnerClasses attribute" error in IBM J9 VM
-
- Resolved
-
That is not the expected behavior. Since you said that the slave is configured be be launched from the master, that means it is not a "swarm" slave, so it should automatically attempt to restart after reboot, and should remain in the list even if the restart fails.
I suspect there is a problem in your Jenkins configuration, rather than a problem in Jenkins. If Jenkins were behaving like that in general, I would expect many users to complain. You may want to investigate if something is reverting your Jenkins configuration when the master restarts, or if something is somehow removing the slave definition files on the master server.
You might also consider switching from 1.549 to the long term support release (currently 1.554.1). Unless you need to be "on the cutting edge", the LTS version tends to be more stable than the development versions