Looks like a JVM is being asked, not to fork, but to launch a program that happens to be called “java”. My first guess is that the slave doesn’t have a path to java in its environment.
Is this happening when you launch the slave, or when you run a job on it? If the former, whatever you’re using to launch it doesn’t know where to find a JVM. If the latter, your slave may have an environment issue. --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Mata Sent: Thursday, July 05, 2012 3:38 PM To: jenkinsci-users@googlegroups.com Subject: Problem running slaves Hello. Does anybody know why jenkisn slave cab give this to me? Thank you all 21:31:43 java.io.IOException<http://stacktrace.jenkins-ci.org/search?query=java.io.IOException>: Cannot run program "java" (in directory "/shared/cis/slavejenkins/workspace/ext-libs"): java.io.IOException: error=2, No such file or directory 21:31:43 at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)<http://stacktrace.jenkins-ci.org/search/?query=java.lang.ProcessBuilder.start&entity=method> 21:31:43 at hudson.Proc$LocalProc.<init>(Proc.java:244)<http://stacktrace.jenkins-ci.org/search/?query=hudson.Proc$LocalProc.%3Cinit%3E&entity=method> 21:31:43 at hudson.Proc$LocalProc.<init>(Proc.java:216)<http://stacktrace.jenkins-ci.org/search/?query=hudson.Proc$LocalProc.%3Cinit%3E&entity=method> 21:31:43 at hudson.Launcher$LocalLauncher.launch(Launcher.java:709)<http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$LocalLauncher.launch&entity=method> 21:31:43 at hudson.Launcher$ProcStarter.start(Launcher.java:338)<http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$ProcStarter.start&entity=method> 21:31:43 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:934)<http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$RemoteLaunchCallable.call&entity=method> 21:31:43 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:901)<http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$RemoteLaunchCallable.call&entity=method> 21:31:43 at hudson.remoting.UserRequest.perform(UserRequest.java:118)<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.UserRequest.perform&entity=method> 21:31:43 at hudson.remoting.UserRequest.perform(UserRequest.java:48)<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.UserRequest.perform&entity=method> 21:31:43 at hudson.remoting.Request$2.run(Request.java:287)<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request$2.run&entity=method> 21:31:43 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.InterceptingExecutorService$1.call&entity=method> 21:31:43 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)<http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.FutureTask$Sync.innerRun&entity=method> 21:31:43 at java.util.concurrent.FutureTask.run(FutureTask.java:138)<http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.FutureTask.run&entity=method> 21:31:43 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)<http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor$Worker.runTask&entity=method> 21:31:43 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)<http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor$Worker.run&entity=method> 21:31:43 at java.lang.Thread.run(Thread.java:662)<http://stacktrace.jenkins-ci.org/search/?query=java.lang.Thread.run&entity=method> The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle & Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle & Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
