No se puede conectar esclavo a maestro

I set up Jenkins on a Windows 7 64 bit PC, and installed a Jenkins slave service on another Win7 64 PC. The master PC gives this error:

Connection was broken Connection reset
    at Source)
    at Source)
    at Source)
    at$PeekInputStream.peek(Unknown Source)
    at$BlockDataInputStream.peek(Unknown Source)
    at$BlockDataInputStream.peekByte(Unknown Source)
    at Source)
    at Source)
    at hudson.remoting.Channel$

¿Qué puedo hacer para diagnosticar el problema?

[Actualizar] The error is shown when I go to the Nodes page. The added slave is displayed as being disconnected. And when I click on the node Name, the above error is displayed.

[Actualización 2] When a job was forced to run on the slave, it just worked. And afterwards, the slave was displayed as being connected in the node page. Now I come to think of it, I did not try to queue multiple jobs. Perhaps that would have triggered the execution to the slave as well?

Anyway, I've got my CI farm up & running now :-)

preguntado el 09 de marzo de 12 a las 13:03

3 Respuestas

I suggest you to start the slave via browser, log as administrator to the slave machine and go to the node page on jenkins, if you are logged as jenkins admin you'll see a slave start icon, this will download and execute the slave process.

start slave screenshot

Once you get this working you can update it as a windows service via the slave java application menu “File->Install as Windows Service”.

respondido 09 mar '12, 13:03

Yes, that's what I already did. I managed to install a slave jenkins installation as a windows service, and on the slave side, it looks ok. It is the master that tells me a connection with the slave could not be established. - El pequeño

@parvus so the web pages shows the node as offline? Or that error appears only when you start a job? - nolito

When a job is started, it is always executed on the master jenkins installation. - El pequeño

@parvus You can force execution on a specific slave in the job configuration. - Chr1stensen

Great! When I did that, it worked! (Well, the run failed, but that was due to a missing environment variable). And afterwards, when I checked the node page again, it was marked as connected! Hurray! - El pequeño

If you're running jenkins through a HTTPS connection using a self signed certificate open jenkins-slave.xml y añade -noCertificateCheck to the arguments list.

Respondido el 24 de enero de 14 a las 16:01

Look in your $JENKINS_HOME folder for the slave logs, they might contain more information.

respondido 09 mar '12, 13:03

Thanks, I wasn't aware of those files. Unfortunately, they do not contain more information. :-( - El pequeño

No es la respuesta que estás buscando? Examinar otras preguntas etiquetadas or haz tu propia pregunta.