-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
1.580, Ubuntu 12.04 LTS 64
We've had this issue for a while, mostly after a slave is started where the maven command insist on using /bin/java. We do not have a /bin/java since we want to control the version of Java on a per job basis, so adding it is not an option.
00:00:06.627 Parsing POMs 00:00:07.322 maven3-agent.jar already up to date 00:00:07.331 maven3-interceptor.jar already up to date 00:00:07.341 maven3-interceptor-commons.jar already up to date 00:00:07.347 [build-shnproxy-trunk] $ /bin/java -Xmx6000m -XX:MaxPermSize=2000m -cp /shn/builder/maven3-agent.jar:/shn/builder/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /shn/builder/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5 /shn/builder/slave.jar /shn/builder/maven3-interceptor.jar /shn/builder/maven3-interceptor-commons.jar 33037 00:00:07.353 ERROR: Failed to parse POMs 00:00:07.353 java.io.IOException: Cannot run program "/bin/java" (in directory "/shn/builder/workspace/build-shnproxy-trunk"): java.io.IOException: error=2, No such file or directory 00:00:07.353 at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) 00:00:07.353 at hudson.Proc$LocalProc.<init>(Proc.java:244) 00:00:07.353 at hudson.Proc$LocalProc.<init>(Proc.java:216) 00:00:07.353 at hudson.Launcher$LocalLauncher.launch(Launcher.java:802) 00:00:07.353 at hudson.Launcher$ProcStarter.start(Launcher.java:380) 00:00:07.353 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1135) 00:00:07.353 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1100) 00:00:07.353 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 00:00:07.353 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 00:00:07.353 at hudson.remoting.Request$2.run(Request.java:328) 00:00:07.353 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 00:00:07.353 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 00:00:07.353 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 00:00:07.353 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) 00:00:07.353 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) 00:00:07.353 at java.lang.Thread.run(Thread.java:662) 00:00:07.353 Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory 00:00:07.353 at java.lang.UNIXProcess.<init>(UNIXProcess.java:148) 00:00:07.353 at java.lang.ProcessImpl.start(ProcessImpl.java:65) 00:00:07.353 at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) 00:00:07.353 ... 15 more
Usually after a few failed builds the slave gets the correct version of java and works:
Parsing POMs maven3-agent.jar already up to date maven3-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [build-shnproxy-trunk] $ /shn/builder/tools/hudson.model.JDK/JDK7/jdk1.7.0_51/bin/java -Xmx6000m -XX:MaxPermSize=2000m -cp /shn/builder/maven3-agent.jar:/shn/builder/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /shn/builder/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5 /shn/builder/slave.jar /shn/builder/maven3-interceptor.jar /shn/builder/maven3-interceptor-commons.jar 58912 <===[JENKINS REMOTING CAPACITY]===>���channel started
This time it has been stuck for 2 jobs for the past 2 days, with no end in sight. I can't figure out why it keeps on pointing to /bin/java
