[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian created an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Issue Type: Bug Assignee: Rouke Broersma Components: selenium-plugin, ssh-slaves-plugin Created: 2019-04-02 10:45 Environment: Jenkins ver. 2.164.1 Tried with SSH Slave plugin 1.11 and 1.29. Java version on master: openjdk version "1.8.0_191" Java version on slave: java version "1.8.0_191" Ubuntu 18.04.2 Priority: Major Reporter: iulian iulian 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: [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
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 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:[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.jarchannel startedRemoting version: 3.29This is a Unix agentEvacuated stdoutStarting Selenium nodes on automation-jenkins-nodeApr 02, 2019 10:17:47 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: 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.jarat 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)With SSH Slave plugin version 1.29 is throwing a different error:[04/02/19 09 13 : 29 52 : 28 10 ] [SSH] Starting sftp client.[04/02/19 09 13 : 29 52 : 28 10 ] [SSH] Copying latest slave remoting .jar...[04/02/19 09 13 : 29 52 : 28 10 ] [SSH] Copied 789,283 bytes.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 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:[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.jarchannel startedRemoting version: 3.29This is a Unix agentEvacuated stdoutStarting Selenium nodes on automation-jenkins-nodeApr 02, 2019 10:17:47 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: 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.jarat 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 With SSH Slave plugin version 1.29 is throwing a different error:[04/02/19 13:52:10] [SSH] Starting sftp client.[04/02/19 13:52:10] [SSH] Copying latest remoting.jar...[0
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 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:[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.jarchannel startedRemoting version: 3.29This is a Unix agentEvacuated stdoutStarting Selenium nodes on automation-jenkins-nodeApr 02, 2019 10:17:47 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: 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.jarat 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-nodeWith SSH Slave plugin version 1.29 is throwing a different error:[04/02/19 13:52:10] [SSH] Starting sftp client.[04/02/19 13:52:10] [SSH] Copying latest remoting.jar...[04/02/1
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 Labels: jenkins regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 Labels: jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 Labels: jenkins plugins regression slave Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 Labels: jenkins regression slave Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / 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 Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title
Ivan Fernandez Calvo updated an issue
Jenkins / 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:
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.jarchannel startedRemoting version: 3.29This is a Unix agentEvacuated stdoutStarting Selenium nodes on automation-jenkins-nodeApr 02, 2019 10:17:47 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: 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.jarat 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]
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title Ivan Fernandez Calvo commented on 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) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198509.155420191.17071.1563708480378%40Atlassian.JIRA.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / 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: Ivan Fernandez Calvo Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198509.155420191.17075.1563708480432%40Atlassian.JIRA.
