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

Slave workspaces deleted too often

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      Platform: All, OS: All

      Description

      I have a job running on a slave. Once the job runs I can see the workspace in
      hudson. If I wait overnight and check again in the morning the workspace is gone
      with this error:
      Error: no workspace

      1. The project was renamed recently and no build was done under the new name.
      2. The slave this project has run on for the last time was removed.
      3. The workspace directory (null) is removed outside Hudson.

      Run a build to have Hudson create a workspace.

      Turning on more logging, I see the following:
      May 4, 2009 6:44:01 AM hudson.model.WorkspaceCleanupThread
      FINE: Directory
      /nfshomes/hudson/.hudson/jobs/B3_Full_Regression/workspace is not owned
      by any project

      May 4, 2009 6:44:01 AM hudson.model.WorkspaceCleanupThread
      FINE: Directory
      /nfshomes/hudson/.hudson/jobs/B3_Short_Regression/workspace is not owned
      by any project

      May 4, 2009 6:44:01 AM hudson.model.WorkspaceCleanupThread
      FINE: Directory /nfshomes/hudson/.hudson/jobs/PET-linux/workspace is
      only 4 days 20 hr old, so not deleting

      May 4, 2009 6:43:48 AM hudson.model.WorkspaceCleanupThread
      FINE: Directory /hudson/workspace/B3_Full_Regression is not owned by any
      project

      All of these workspaces are owned by a project and should not be deleted.

        Issue Links

          Activity

          Hide
          skaze skaze added a comment -

          I just upgraded from 828 to 304 and now my workspaces are deleting themselves?!

          I presume its ist to do with
          https://hudson.dev.java.net/issues/show_bug.cgi?id=3580 or
          https://hudson.dev.java.net/issues/show_bug.cgi?id=3653 but the fault is so
          severe that I may have to roll back.

          My projects are using scm polling, SVN update and project security. I don't want
          my 400M workspace of libraries deleted each time it checks for updates.

          When is the fix for this planned to be release?

          Show
          skaze skaze added a comment - I just upgraded from 828 to 304 and now my workspaces are deleting themselves?! I presume its ist to do with https://hudson.dev.java.net/issues/show_bug.cgi?id=3580 or https://hudson.dev.java.net/issues/show_bug.cgi?id=3653 but the fault is so severe that I may have to roll back. My projects are using scm polling, SVN update and project security. I don't want my 400M workspace of libraries deleted each time it checks for updates. When is the fix for this planned to be release?
          Hide
          skaze skaze added a comment -

          I just upgraded from 828 to 304 and now my workspaces are deleting themselves?!

          I presume its ist to do with
          https://hudson.dev.java.net/issues/show_bug.cgi?id=3580 or
          https://hudson.dev.java.net/issues/show_bug.cgi?id=3653 but the fault is so
          severe that I may have to roll back.

          My projects are using scm polling, SVN update and project security. I don't want
          my 400M workspace of libraries deleted each time it checks for updates.

          When is the fix for this planned to be release?

          Show
          skaze skaze added a comment - I just upgraded from 828 to 304 and now my workspaces are deleting themselves?! I presume its ist to do with https://hudson.dev.java.net/issues/show_bug.cgi?id=3580 or https://hudson.dev.java.net/issues/show_bug.cgi?id=3653 but the fault is so severe that I may have to roll back. My projects are using scm polling, SVN update and project security. I don't want my 400M workspace of libraries deleted each time it checks for updates. When is the fix for this planned to be release?
          Hide
          mdonohue mdonohue added a comment -
              • Issue 3705 has been marked as a duplicate of this issue. ***
          Show
          mdonohue mdonohue added a comment - Issue 3705 has been marked as a duplicate of this issue. ***
          Hide
          dannystaple Danny Staple added a comment - - edited

          This is being seen again both in hudson 1.393, and in jenkins 1.415.

          JENKINS-10615 shows exactly the same symptoms and looks to be a duplicate.

          Show
          dannystaple Danny Staple added a comment - - edited This is being seen again both in hudson 1.393, and in jenkins 1.415. JENKINS-10615 shows exactly the same symptoms and looks to be a duplicate.
          Hide
          danielbeck Daniel Beck added a comment -

          Jenkins 1.551 changed how the workspace cleanup thread works. So this can be assumed obsolete. Please just file a new issue if this problem occurs on Jenkins 1.551 or newer.

          Also, if this is a problem, you can always set -D hudson.model.WorkspaceCleanupThread.disabled=true to disable workspace cleanup.

          Show
          danielbeck Daniel Beck added a comment - Jenkins 1.551 changed how the workspace cleanup thread works. So this can be assumed obsolete. Please just file a new issue if this problem occurs on Jenkins 1.551 or newer. Also, if this is a problem, you can always set -D hudson.model.WorkspaceCleanupThread.disabled=true to disable workspace cleanup.

            People

            • Assignee:
              Unassigned
              Reporter:
              jpschewe jpschewe
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: