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

Windows slave died

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • core, windows-slaves-plugin
    • None
    • Hudson 1.352 master on Linux, slave (1.352) on Windows Server 2003

      The slave is installed as a windows service.

      The command line was (according to hudson-slave.wrapper.log):
      2010-03-29 12.29.46 - Starting C:\Program Files\Java\jre6\bin\java.exe -Xrs -jar "C:\DeveloperTools\HudsonSlave\slave.jar" -jnlpUrl http://hudson.mondidinamici.com/computer/Ceres/slave-agent.jnlp

      The slave died because of an exception reported in slave.out.log

      #

      1. A fatal error has been detected by the Java Runtime Environment:
        #
      2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x037235e0, pid=1632, tid=1388
        #
      3. JRE version: 6.0_17-b04
      4. Java VM: Java HotSpot(TM) Client VM (14.3-b01 mixed mode, sharing windows-x86 )
      5. Problematic frame:
      6. C 0x037235e0
        #
      7. An error report file with more information is saved as:
      8. C:\WINDOWS\system32\hs_err_pid1632.log
        #
      9. If you would like to submit a bug report, please visit:
      10. http://java.sun.com/webapps/bugreport/crash.jsp
      11. The crash happened outside the Java Virtual Machine in native code.
      12. See problematic frame for where to report the bug.
        #

      I have attached also C:\WINDOWS\system32\hs_err_pid1632.log file.

            Unassigned Unassigned
            mambu Marco Ambu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: