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

Slaves don't come up after graceful shutdown

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • remoting
    • None
    • Platform: HP, OS: Linux

      We discovered this in Hudson v1.309. When a slave is configured with an idle
      delay, it eventually shuts down due to inactivity. When this happens, the
      Hudson master seems to be unable to distinguish this condition from a genuine
      failure, and marks the slave as offline. If the slave is also configured with
      an on-demand delay, then Hudson will attempt to start the slave if its job queue
      is non-empty for the specified time, but will fail because it thinks the slave
      has failed.

          [JENKINS-4302] Slaves don't come up after graceful shutdown

          psandertivo created issue -
          Alan Harder made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Alan Harder made changes -
          Link New: This issue duplicates JENKINS-3890 [ JENKINS-3890 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 134375 ] New: JNJira + In-Review [ 202803 ]

            Unassigned Unassigned
            psandertivo psandertivo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: