-
Bug
-
Resolution: Not A Defect
-
Major
-
None
I've upgraded to latest Hudson 1.366 from 1.361 and my windows slave stopped working.
Even though I've configured the slave box to have %JAVA_HOME% set and %JAVA_HOME%/bin, "java" command works just fine on cmd.exe shell
C:\WINDOWS>java -fullversion
java full version "1.6.0_21-b06"
Hudson fails to recognize it and tries to install jdk which also fails.
Connecting to w2k3fm1 Checking if Java exists 'java' is not recognized as an internal or external command, operable program or batch file. No Java found. Downloading JDK Installing JDK ERROR: Failed to prepare Java jcifs.smb.SmbException: Cannot create a file when that file already exists. at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:545) at jcifs.smb.SmbTransport.send(SmbTransport.java:646) at jcifs.smb.SmbSession.send(SmbSession.java:244) at jcifs.smb.SmbTree.send(SmbTree.java:119) at jcifs.smb.SmbFile.send(SmbFile.java:770) at jcifs.smb.SmbFile.mkdir(SmbFile.java:2518) at jcifs.smb.SmbFile.mkdirs(SmbFile.java:2544) at hudson.os.windows.WindowsRemoteFileSystem.mkdirs(WindowsRemoteFileSystem.java:58) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:167) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:184) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Copying slave.jar Starting the service
- is blocking
-
JENKINS-7186 Master Cannot Start slave.jar on Windows Slaves
-
- Closed
-
- is related to
-
JENKINS-8957 JDK installation influences already installed java instances, reinstall of Java had to be done to get back up and running
-
- Resolved
-
-
JENKINS-7701 error launching slave agent to w2k8 server
-
- Closed
-
Same issue experienced here with Master on Windows 2003 R2 32bit, JDK 1.6.0_20, Tomcat 6.0.20 and Hudson Slaves on Windows 2008 64bit, with JDK 1.6.0_20, JAVA_HOME set correctly and java binary available on path.
All nodes (Master and Slaves) have their own JDK section(s) like the following:
It seems the new feature is too eager to attempt a remote JDK install/deployment without verifying first the actual node setup.
Switching back to 1.365 resolves the experience issue.