Windows Slave - Connection reset when "scheduled slave overwrite" happens.

49 views
Skip to first unread message

Fred Clausen

unread,
Jun 6, 2016, 2:01:03 AM6/6/16
to Jenkins Users
Hello,

As a follow-up to my other question (perhaps the issue on my other question triggers this issue), once the slave agent starts successfully, we're seeing the connection reset seemingly when the "schedule slave overwrite" happens. The full log is available as a Gist but this is how it begins :


Connecting to computer.example.com
Checking if Java exists
java -version returned 1.8.0.
Installing the Jenkins slave service
Copying jenkins-slave.exe
Copying slave.jar
Copying jenkins-slave.xml
Registering the service
Starting the service
Waiting for the service to become ready
Connecting to port 58,749
<===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.57
This is a Windows slave
ERROR: Connection terminated
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:209)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.FilterInputStream.read(FilterInputStream.java:133)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82)
at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72)
at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)
at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
ERROR: Failed to update jenkins-slave.exe
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins Any hints much appreciated!
Fred.

Fred Clausen

unread,
Jun 15, 2016, 3:08:00 AM6/15/16
to Jenkins Users
Just to close the loop here - it was my own mistake. In all my experimentation I had accidentally added to Jenkins computers that were speaking to the same VM so they were stepping on each others toes. Apologies for the wasted electrons and time.

Cheers,

Fred.
Reply all
Reply to author
Forward
0 new messages