Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-7000

Can't unlock stash neither cancel backup

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Handled by Support
    • Icon: Highest Highest
    • None
    • 3.3.0
    • Maintenance - Backup / Restore
    • None

      We are updating our stash instances and used the backup-client to save all our data before proceeding. The backup failed at the database backup step and just stopped running. Our stash instance is now locked. We tried the following:

      1. Unlocking it via the Web interface, but, as described in STASH-5182, this does not work.
      2. Use the REST maintenance API to manually unlock the instance, but we got a 404 status code while specifying the given token.

      How can we unlock the stash instance? We are neither able to connect to its Web interface, nor to start another backup (the "lock" request seems to be running forever).

            [BSERV-7000] Can't unlock stash neither cancel backup

            Brent P added a comment -

            nicolas.nunge - This is a support request and I've asked our support engineers to move this to http://support.atlassian.com so we can gather logs. In the meantime, the lock will go away if you shutdown Stash using the stop-stash.sh or stop-stash.bat script (in the bin directory) or kill the Stash process and restart the server.

            Brent P added a comment - nicolas.nunge - This is a support request and I've asked our support engineers to move this to http://support.atlassian.com so we can gather logs. In the meantime, the lock will go away if you shutdown Stash using the stop-stash.sh or stop-stash.bat script (in the bin directory) or kill the Stash process and restart the server.

              Unassigned Unassigned
              3d10c133dda6 Nicolas Nunge
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: