-
Notifications
You must be signed in to change notification settings - Fork 96
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Issue 6229 - After an initial failure, subsequent online backups fail (…
…#6230) * Issue 6229 - After an initial failure, subsequent online backups will not work Several issues related to backup task error handling: Backends stay busy after the failure Exit code is 0 in some cases Crash if failing to open the backup directory And a more general one: lib389 Task DN collision Solutions: Always reset the busy flags that have been set Ensure that 0 is not returned in error case Avoid closing NULL directory descriptor Use a timestamp having milliseconds precision to create the task DN Issue: #6229 Reviewed by: @droideck (Thanks!) (cherry picked from commit 04a0b6a)
- Loading branch information
1 parent
7f37605
commit 69d86e6
Showing
4 changed files
with
70 additions
and
70 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.