java.io.IOException: Remote call on SLAVE_NAME failed

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Google Groups by LnT, 1 month ago
Remote call on JNLP4-connect connection from slav1.applications.com/10.112.17.119:53814 failed
via creadur-dev by Apache Jenkins Server, 1 year ago
Remote call on Channel to Maven [/home/hudson/tools/java/latest1.5/bin/java, -cp, /home/jenkins/jenkins-slave/maven-agent.jar:/home/jenkins/jenkins-slave/classworlds.jar, hudson.maven.agent.Main, /home/hudson/tools/maven/apache-maven-2.2.1, /home
via portals-jetspeed-dev by David Taylor, 1 year ago
Remote call on Channel to Maven [/home/hudson/tools/java/latest1.5/bin/java, -cp, /home/jenkins/jenkins-slave/maven-agent.jar:/home/jenkins/jenkins-slave/classworlds.jar, hudson.maven.agent.Main, /home/hudson/tools/maven/apache-maven-2.2.1
via portals-jetspeed-dev by David Taylor, 1 year ago
Remote call on Channel to Maven [/home/hudson/tools/java/latest1.5/bin/java, -cp, /home/jenkins/jenkins-slave/maven-agent.jar:/home/jenkins/jenkins-slave/classworlds.jar, hudson.maven.agent.Main, /home/hudson/tools/maven/apache-maven-2.2.1
java.io.IOException: Remote call on SLAVE_NAME failed
at hudson.slaves.SlaveComputer.getChannelToMaster(SlaveComputer.java:607)
at hudson.util.ProcessTree.getKillers(ProcessTree.java:158)
at hudson.util.ProcessTree$OSProcess.killByKiller(ProcessTree.java:219)
at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:552)
at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:559)
at hudson.util.ProcessTree.killAll(ProcessTree.java:147)
at hudson.Proc$LocalProc.destroy(Proc.java:379)
at hudson.Proc$LocalProc.kill(Proc.java:371)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.