-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
UNIX Solaris 10, Jenkins 1.415, ThinBackup 1.4
We have ThinBackup set to run at 1am on Sunday mornings (i.e. Backup schedule for full backups = "0 1 * * 0"). The past run failed immediately with messages every 1 minute like the following:
Dec 11, 2011 1:01:30 AM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted.
Dec 11, 2011 1:02:30 AM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted.
Dec 11, 2011 1:03:30 AM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted.
Dec 11, 2011 1:04:30 AM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted.
The problem continued until someone noticed later that day that regular build jobs were being blocked from running due to a "prepare for shutdown" block that ThinBackup triggers before running that never got canceled. The shutdown block was manually canceled to clear the job backlog.
Our logs show no other entries or errors to identify the cause of the problem, or why a "ThinBackup Worker Thread thread" would be running, as if multiple ThinBackup workers were in progress and blocking each other.
The first previous ThinBackup log entries were from a week before:
Dec 4, 2011 11:41:10 PM org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink doBackupManual
INFO: Starting manual backup.
Dec 4, 2011 11:42:25 PM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobs
INFO: Found 79 jobs to back up.
I had kicked off a manual backup, and I had seen it successfully complete in the UI, yet I see no log entry that indicates it did actually finished, either because the logging level for such messages is now FINEST, or because it never actually terminated the thread, resulting in the issue I'm reporting here.
Either this is a problem with manual "Backup Now" runs, or it is a 1.4 issue. Note: I upgraded on Dec 4 from 1.2 to 1.4 in order to pickup a fix (suggested by JENKINS-9117) for backup failures never recovering and canceling the build block.
- is related to
-
-
- Open
-
[JENKINS-12096] ThinBackup Worker Thread thread is still running. Execution aborted.
| Assignee | Original: Thomas Fürer [ tofuatjava ] | New: Daniel Kirkdorffer [ dankirkd ] |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Reopening because there does still appear something that blocked this from running as it should have. Other things I have been able to see should not be related to the problem I've written about.
| Assignee | Original: Daniel Kirkdorffer [ dankirkd ] | New: Thomas Fürer [ tofuatjava ] |
| Resolution | Original: Not A Defect [ 7 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Thomas Fürer
made changes -
| Status | Original: Reopened [ 4 ] | New: Open [ 1 ] |
Thomas Fürer
added a comment - cannot reproduce this issue.
Only if the backup is already/still running and a new backup will be trigger this happens. But I don't think that some have such a tight schedule. The other thing is that something on the filesystem could block the backup. In this case you should watch out for permission settings or parallel file operations.
in all this cases I cannot handle the issue in the backup plugin, so I decided to close this one.
Thomas Fürer
added a comment - cannot reproduce this issue.
Only if the backup is already/still running and a new backup will be trigger this happens. But I don't think that some have such a tight schedule. The other thing is that something on the filesystem could block the backup. In this case you should watch out for permission settings or parallel file operations.
in all this cases I cannot handle the issue in the backup plugin, so I decided to close this one. Thomas Fürer
made changes -
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Karthic Bala
added a comment - Now i am getting same warning message in our jenkins logs
Jenkins - Upgraded from v1.565 to 1.606
Thinbackup : 1.7.4
Logs:
Jul 06, 2015 2:31:48 PM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted.
Jul 06, 2015 2:32:00 PM hudson.plugins.accurev.FindAccurevClientExe invoke
INFO: Path to the AccuRev client: /usr/bin/accurev
Jul 06, 2015 2:32:48 PM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted.
Jul 06, 2015 2:33:48 PM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted.
Karthic Bala
added a comment - Now i am getting same warning message in our jenkins logs
Jenkins - Upgraded from v1.565 to 1.606
Thinbackup : 1.7.4
Logs:
Jul 06, 2015 2:31:48 PM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted.
Jul 06, 2015 2:32:00 PM hudson.plugins.accurev.FindAccurevClientExe invoke
INFO: Path to the AccuRev client: /usr/bin/accurev
Jul 06, 2015 2:32:48 PM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted.
Jul 06, 2015 2:33:48 PM org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork doRun
WARNING: ThinBackup Worker Thread thread is still running. Execution aborted. Karthic Bala
added a comment - Seeing this issue again.. Karthic Bala
made changes -
| Resolution | Original: Cannot Reproduce [ 5 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
After writing this defect I discovered more about the issue and feel I need to write a different defect or update
JENKINS-9117because I have a scenario that appears to indicate that ThinBackup hit an issue during backup and didn't cancel shutdown mode correctly.