[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1

4 views
Skip to first unread message

iulian.timis@arobs.com (JIRA)

unread,
Apr 3, 2019, 2:22:03 AM4/3/19
to jenkinsc...@googlegroups.com
iulian iulian updated an issue
 
Jenkins / Bug JENKINS-56849
Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Change By: iulian iulian
Summary: Unable to connect node to slave using ssh slave . Slave plugin (1.11 and 1.29) and  Jenkins ver. 2.164.1
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

iulian.timis@arobs.com (JIRA)

unread,
Apr 3, 2019, 2:22:03 AM4/3/19
to jenkinsc...@googlegroups.com

iulian.timis@arobs.com (JIRA)

unread,
Apr 3, 2019, 1:52:02 PM4/3/19
to jenkinsc...@googlegroups.com

kuisathaverat@gmail.com (JIRA)

unread,
Jul 21, 2019, 7:23:04 AM7/21/19
to jenkinsc...@googlegroups.com
Ivan Fernandez Calvo updated an issue
Change By: Ivan Fernandez Calvo
I have updated Jenkins to the latest version (Jenkins ver. 2.164.1) and Selenium Grid version is: 3.12.0. Java varsion on master (where run the hub) is: openjdk version "1.8.0_191", on the slave is: java version "1.8.0_191" and SSH Slave plugin version 1.11. When the nod is trying to connect to slave is throw this error:

{code}
[04/02/19 10:17:45] [SSH] Starting sftp client.
    [04/02/19 10:17:45] [SSH] Copying latest slave.jar...
    [04/02/19 10:17:45] [SSH] Copied 789,283 bytes.
    Expanded the channel window size to 4MB
    [04/02/19 10:17:45] [SSH] Starting slave process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar slave.jar

    channel started
    Remoting version: 3.29
    This is a Unix agent
    Evacuated stdout

    Starting Selenium nodes on automation-jenkins-node
    Apr 02, 2019 10:17:47 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn
    WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/

    hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running?
        at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:984)
        at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:137)
        at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:725)
        at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
    Caused by: java.io.IOException: Failed to copy /var/lib/jenkins/plugins/selenium/WEB-INF/lib/selenium-server-standalone-3.12.0.jar to /var/jenkins/selenium-server-standalone-3.12.0.jar
        at hudson.FilePath.copyTo(FilePath.java:2191)
        at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:76)
        at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:23)
        at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3041)
        at hudson.remoting.UserRequest.perform(UserRequest.java:212)
        at hudson.remoting.UserRequest.perform(UserRequest.java:54)
        at hudson.remoting.Request$2.run(Request.java:369)
        at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
... 4 more
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to automation-jenkins-node
{code}


With SSH Slave plugin version 1.29 is throwing a different error:

{code}
[04/02/19 13:52:10] [SSH] Starting sftp client.
[04/02/19 13:52:10] [SSH] Copying latest remoting.jar...
[04/02/19 13:52:10] [SSH] Copied 789,283 bytes.
Expanded the channel window size to 4MB
[04/02/19 13:52:10] [SSH] Starting agent process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar remoting.jar -workDir /var/jenkins
Apr 02, 2019 1:52:10 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using /var/jenkins/remoting as a remoting work directory
Both error and output logs will be printed to /var/jenkins/remoting
<===[JENKINS REMOTING CAPACITY]===>channel started
Remoting version: 3.29
This is a Unix agent
Evacuated stdout
Starting Selenium nodes on automation-jenkins-node
Apr 02, 2019 1:52:13 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn
WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
Slave JVM has not reported exit code. Is it still running?
[04/02/19 13:52:18] Launch failed - cleaning up connection
[04/02/19 13:52:18] [SSH] Connection closed.
ERROR: Connection terminated
java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:358)
at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49)
at hudson.remoting.Command.readFrom(Command.java:140)
at hudson.remoting.Command.readFrom(Command.java:126)
at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Caused: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)

{code}

kuisathaverat@gmail.com (JIRA)

unread,
Jul 21, 2019, 7:28:03 AM7/21/19
to jenkinsc...@googlegroups.com

kuisathaverat@gmail.com (JIRA)

unread,
Jul 21, 2019, 7:28:04 AM7/21/19
to jenkinsc...@googlegroups.com
Ivan Fernandez Calvo commented on Bug JENKINS-56849
 
Re: Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1

it does not work on ssh-slaves 1.11 and 1.29 I guess it is not a bug, it looks like more a configuration issue, to as question about how to configure something please use the user groups see [How to report an issue](https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue)

Reply all
Reply to author
Forward
0 new messages