Skip to content

[JENKINS-3653] Slave workspaces deleted too often #14286

Closed
Bug
Closed
[JENKINS-3653] Slave workspaces deleted too often#14286
Bug
Labels
component:coreimported-jira-issuepriority:criticalresolution:fixed

Description

@jenkins-infra-bot
jenkins-infra-bot
opened on May 7, 2009

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.

Originally reported by jpschewe, imported from: Slave workspaces deleted too often
  • status: Resolved
  • priority: Critical
  • component(s): core
  • resolution: Fixed
  • resolved: 2014-05-18T13:24:55+00:00
  • votes: 0
  • watchers: 2
  • imported: 2025-11-24
Raw content of original issue 
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.
  • environment: Platform: All, OS: All

Activity

  1. jenkins-infra-bot commented on May 7, 2009

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 7, 2009
    Author
    mdonohue:
    • Original comment link
    • Raw content of original comment: 
      What version of Hudson are you using?   Perhaps issue 3580 is related.

    What version of Hudson are you using? Perhaps issue 3580 is related.

  2. jenkins-infra-bot commented on May 8, 2009

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 8, 2009
    Author
    jpschewe:
    • Original comment link
    • Raw content of original comment: 
      I'm using 1.301.
      


      No I don't believe issue 3580 is the same thing. No subversion checkout is run
between the time that the workspace exists and the time that the workspace is
deleted.

    I'm using 1.301.

    No I don't believe issue 3580 is the same thing. No subversion checkout is run
    between the time that the workspace exists and the time that the workspace is
    deleted.

  3. jenkins-infra-bot commented on May 12, 2009

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 12, 2009
    Author
    mdonohue:

    Perhaps this thread is relevant then:
    http://www.nabble.com/workspace-cleanup-thread-deleting-all-active-workspaces-tt23493027.html

    What security are you using?

  4. jenkins-infra-bot commented on May 13, 2009

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 13, 2009
    Author
    jpschewe:
    • Original comment link
    • Raw content of original comment: 
      I'm using project based security, so that might be it. Do we have a patch that
could fix this? Can it be attached to the bug?

    I'm using project based security, so that might be it. Do we have a patch that
    could fix this? Can it be attached to the bug?

  5. jenkins-infra-bot commented on May 13, 2009

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 13, 2009
    Author
    scm_issue_link:

    Code changed in hudson
    User: : kohsuke
    Path:
    trunk/hudson/main/core/src/main/java/hudson/model/AsyncPeriodicWork.java
    http://fisheye4.cenqua.com/changelog/hudson/?cs=18068
    Log:
    [FIXED JENKINS-3653] Fixed in 1.305

  6. jenkins-infra-bot commented on May 14, 2009

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 14, 2009
    Author
    scm_issue_link:

    Code changed in hudson
    User: : kohsuke
    Path:
    trunk/www/changelog.html
    http://fisheye4.cenqua.com/changelog/hudson/?cs=18101
    Log:
    noting JENKINS-3653 fix in 1.305

  7. jenkins-infra-bot commented on May 16, 2009

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 16, 2009
    Author
    skaze:

    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?

  8. jenkins-infra-bot commented on May 16, 2009

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 16, 2009
    Author
    skaze:

    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?

  9. jenkins-infra-bot commented on May 26, 2009

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 26, 2009
    Author
    mdonohue:
    • Original comment link
    • Raw content of original comment: 
        
	
      • 
	
          
		
        • 
		
            
			
          • Issue 3705 has been marked as a duplicate of this issue. ***
            • 
		
          
		
          • 
	
        
	
        •
        • Issue 3705 has been marked as a duplicate of this issue. ***

  10. jenkins-infra-bot commented on Oct 12, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Oct 12, 2011
    Author
    dannystaple:
    • Original comment link
    • Raw content of original comment: 
      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.

    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.

  11. jenkins-infra-bot commented on May 18, 2014

    @jenkins-infra-bot
    jenkins-infra-bot
    on May 18, 2014
    Author
    danielbeck:
    • Original comment link
    • Raw content of original 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.

    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.

  12. jenkins-infra-bot
    closed this as completedon May 18, 2014

  13. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original is_duplicated_by from Jira: JENKINS-1880]

  14. jenkins-infra-bot
    added
    bugFor changelog: Minor bug. Will be listed after features
    imported-jira-issue
    component:core
    resolution:fixed
    priority:critical
    on Nov 24, 2025

  15. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original is_duplicated_by from Jira: JENKINS-3705]

  16. jenkins-infra-bot
    added the
    Bug
    issue type on Nov 25, 2025
  17. jenkins-infra-bot
    removed
    bugFor changelog: Minor bug. Will be listed after features
    on Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:coreimported-jira-issuepriority:criticalresolution:fixed

    Type

    Bug

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions