Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7186

Master Cannot Start slave.jar on Windows Slaves

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Blocker Blocker
    • windows-slaves-plugin
    • None
    • Windows 7 - Master, Windows XP - Slave

      I set up a Windows XP slave as a Windows service. It was working for a while, but then suddenly the master machine (which is Windows 7) wasn't able to start the slave.jar.

      Log Output:
      Connecting to GMS2S2HLF1
      Checking if Java exists
      java full version "1.6.0_17-b04"
      Copying slave.jar
      Starting the service

      ...And it just hangs here. I have no idea what has caused this. I've tried setting up different slave machines (all Windows XP) and they all do the same thing.

          [JENKINS-7186] Master Cannot Start slave.jar on Windows Slaves

          Sorin Sbarnea added a comment - - edited

          I do encounter the same problem on a different setup: master osx and slave running windows 7 x64 (started as service)

          My luck is that after a lot of time I obtained some expection:

          ERROR: The handle is invalid.
          jcifs.smb.SmbException: The handle is invalid.
          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.SmbFileOutputStream.writeDirect(SmbFileOutputStream.java:245)
          at jcifs.smb.SmbFileOutputStream.write(SmbFileOutputStream.java:216)
          at hudson.Util.copyStream(Util.java:418)
          at hudson.Util.copyStreamAndClose(Util.java:430)
          at hudson.os.windows.ManagedWindowsServiceLauncher.copySlaveJar(ManagedWindowsServiceLauncher.java:293)
          at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:239)
          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:637)

          Sorin Sbarnea added a comment - - edited I do encounter the same problem on a different setup: master osx and slave running windows 7 x64 (started as service) My luck is that after a lot of time I obtained some expection: ERROR: The handle is invalid. jcifs.smb.SmbException: The handle is invalid. 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.SmbFileOutputStream.writeDirect(SmbFileOutputStream.java:245) at jcifs.smb.SmbFileOutputStream.write(SmbFileOutputStream.java:216) at hudson.Util.copyStream(Util.java:418) at hudson.Util.copyStreamAndClose(Util.java:430) at hudson.os.windows.ManagedWindowsServiceLauncher.copySlaveJar(ManagedWindowsServiceLauncher.java:293) at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:239) 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:637)

          SauravSengupta added a comment -

          I'm seeing this too, started today. Master is ubuntu 32-bit, slave is a Windows XP 32-bit VM. The weird thing is, I can't think of anything that changed recently, unless the Windows machine auto-downloaded some updates.

          SauravSengupta added a comment - I'm seeing this too, started today. Master is ubuntu 32-bit, slave is a Windows XP 32-bit VM. The weird thing is, I can't think of anything that changed recently, unless the Windows machine auto-downloaded some updates.

          Sorin Sbarnea added a comment -

          Is there anything we can to narrow down this critical bug?

          Sorin Sbarnea added a comment - Is there anything we can to narrow down this critical bug?

          SauravSengupta added a comment -

          For what it's worth - I found that the Windows XP VM had downloaded an updated related to daylight savings time changes. My current workaround was to switch that slave to the JNLP launch method, and then set it up as a service. This allowed the master to connect to the slave.

          SauravSengupta added a comment - For what it's worth - I found that the Windows XP VM had downloaded an updated related to daylight savings time changes. My current workaround was to switch that slave to the JNLP launch method, and then set it up as a service. This allowed the master to connect to the slave.

          Manfred Koch added a comment -

          I have the same problem with a Windows 2003 Master and a Windows XP client. The strange thing is that on the slave exists no log file.

          Manfred Koch added a comment - I have the same problem with a Windows 2003 Master and a Windows XP client. The strange thing is that on the slave exists no log file.

          Sorin Sbarnea added a comment -

          Here you can find more details about the issue http://stackoverflow.com/questions/3914813/hudson-slaves-failing-to-start-on-windows-xp-java-net-sockettimeoutexception

          Shortly, what I suspect is that for some reason the slave.jar is not properly downloaded.

          Sorin Sbarnea added a comment - Here you can find more details about the issue http://stackoverflow.com/questions/3914813/hudson-slaves-failing-to-start-on-windows-xp-java-net-sockettimeoutexception Shortly, what I suspect is that for some reason the slave.jar is not properly downloaded.

          Sorin Sbarnea added a comment -

          Here is something that could be the cause of our issues:
          http://issues.jenkins-ci.org/browse/JENKINS-7755

          Sorin Sbarnea added a comment - Here is something that could be the cause of our issues: http://issues.jenkins-ci.org/browse/JENKINS-7755

          Mark Waite added a comment -

          Not related to the WMI Windows Agents plugin and will not receive any attention.

          Mark Waite added a comment - Not related to the WMI Windows Agents plugin and will not receive any attention.

            Unassigned Unassigned
            abyrd abyrd
            Votes:
            7 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: