It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

stash database backup failed using backup client

Backup was working for some time. But it started failing after we migrated more repositories to stash. The error we received is:

WARN [threadpool:thread-995154] admin 1320x3126501x1 1utuvpt 172.16.100.94,0:0:0:0:0:0:0:1 "POST /mvc/admin/backups HTTP/1.1" c.a.s.i.m.LatchAndDrainDatabaseStep The DataSource could not be drained; some database connections are still open. Aborting migration...

WARN [threadpool:thread-995154] admin 1320x3126501x1 1utuvpt 172.16.100.94,0:0:0:0:0:0:0:1 "POST /mvc/admin/backups HTTP/1.1" c.a.s.i.m.DefaultMaintenanceTaskMonitor BACKUP maintenance has failed (Cause: BackupException: A backup file could not be created.)

...
Caused by: com.atlassian.stash.internal.migration.MigrationException: One or more database connections were not closed within the allotted timeout. To prevent corruption due to inconsistent state, the migration has been aborted. Please try your migration again when the system is under less load.
The time out happened within 1min when it tried to drain the data source. Is there a way to increase the timeout? I don't see such an option in the backup client config file.
the external database we are using is mysql.
Thanks.

4 answers

I got the NPE error. Looks like it's a known issue for back up client 1.3.0. I'm planning to install 1.3.1 which has the debug enabled and let Atlassian investigate more.

It looks like that there are several issues with Stash Backup Client 1.3.0 ;-(

I just got notified the final fix is just released. It can be downloaded at Atlassian Marketplace. Look for Stash Backup Client 1.3.1. I installed their beta release before this and it worked already. The release was to fix the NPE error.

Thanks for the notification

Hi Vivian, did you end up getting to the bottom of this issue? I'm having the same problem with Stash 3.2.2 using PostgreSQL

@Xavier:

If you are using Stash 3.2.2 you have to update to latest Stash Backup Client 1.3.0

But ... There is a known issue with Stash Backup Client 1.3.0 - which fails due to locked ".lock" file.

2014-08-27 04:40:42,852 ERROR [main] c.a.s.i.b.c.layout.DefaultStashHome E:\GitRepo\shared\.lock could not be read

This can be resolved by excluding those lock files.

For the time being, you can add this line in <tt>backup-config.properties</tt> to exclude <tt>.lock</tt> files as a workaround:

stash.home.excludes=**/.lock

(suggested by Atlassian support desk)

Thanks for the notification

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Powering DevOps with Bitbucket Server & Data Center

Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster   ! While we’re all excited about the new improvements to Bitbucket ...

1,535 views 0 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you