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

The Bitbucket Backup Client fails due to "UndeclaredThrowableException: null"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Low
    • None
    • None
    • None
    • None

    Description

      Summary

      The Bitbucket Backup Client does not complete successfully and a backup is not generated.

      Steps to Reproduce

      1. Not Available

      Expected Results

      The Bitbucket Backup Client successfully create a backup.

      Actual Results

      The backup is not created and the below exception is thrown in the Bitbucket Backup Client log file:

      INFO  (100%) Database backup was already manually cancelled on Bitbucket
      INFO  (100%) Unlocking Bitbucket using token: 4c9bfa01ae0138689g6dfab973d9f909883bb61af
      ERROR (100%) A backup could not be created
      java.lang.reflect.UndeclaredThrowableException: null
      	at com.atlassian.bitbucket.internal.backup.client.DefaultBackupClient.archiveHome(DefaultBackupClient.groovy:73) ~[bitbucket-backup-client.jar:3.2.0]
      	at com.atlassian.bitbucket.internal.backup.client.FixedRateProgressPublisher.publishWhileExecuting(FixedRateProgressPublisher.groovy:34) ~[bitbucket-backup-client.jar:3.2.0]
      	... 10 more frames available in the log file
      

      When enabling the debug log level for the Backup Client 404 messages are logged:

      DEBUG (100%) Submitting client progress of 100 to h<BITBUCKET_URL>/mvc/admin/backups/progress/client?token=4c9bfa01ae0138689g6dfab973d9f909883bb61af&percentage=100
      DEBUG (100%) HTTP POST <BITBUCKET_URL>/mvc/admin/backups/progress/client?token=4c9bfa01ae0138689g6dfab973d9f909883bb61af&percentage=100, headers: [Accept:[[application/json]], Content-Length:[[0]], Content-Type:[[application/json]], User-Agent:[[Wink Client v1.1.2]], X-Atlassian-Maintenance-Token:[[4c9bfa01ae0138689g6dfab973d9f909883bb61af]]]
      DEBUG (100%) -> 404 Not Found (@3VK7A8x1355x91334x1)
      

      Notes

      While the exact cause of the problem has not been identified yet, there are some options that could be causing it:

      1. proxy configuration

      Workaround

      If a proxy is used, bypassing it can be used as a workaround:

      1. Stop Bitbucket Server
      2. Add the following lines in $BITBUCKET_HOME/shared/server.xml:
        <Connector executor="tomcatThreadPool"
            port="7995" protocol="HTTP/1.1"
            connectionTimeout="20000" />
        
      3. Start Bitbucket Server
      4. Run the Bitbucket Backup client by using the http://localhost:7995 address

      Attachments

        Activity

          People

            Unassigned Unassigned
            ccurti Caterina Curti
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: