Troubleshooting Bitbucket Data Center
- An error message "User Lookup Failed" appears on integrating Xcode with Bitbucket Data Center
- Bitbucket Data Center clustering does not work on Docker default network
- Bitbucket Data Center cluster node located in another subnet is not joining the cluster
- Bitbucket data center displays the message "Path does not correspond to a valid repository ID" when performing integrity checks.
- Bitbucket Data Center fails to start with a 'Lock file .../shared/.lock cannot be created in home directory' error
- Bitbucket Data Center is not coming up after an upgrade with "ORA-00257: Archiver error" error message in logs
- Bitbucket Data Center Migration export failed with command timed out exception
- Bitbucket Data Center Migration feature fails unexpectedly
- Bitbucket Data Center node fails to join cluster - Current node is unable to service requests
- Bitbucket Data Center node hangs on startup - Initializing spring context
- Bitbucket Data Center NodePassivationException when adding node to the cluster
- Bitbucket Data Center shows "command timed out" error on creating a repository
- Bitbucket Data Center UI throws error: 404. This page cannot be found.
- Bitbucket fails to start in disaster recovery mode.
- Bitbucket nodes do not form a cluster if the nodes have multiple network interfaces and Multicast discovery is used
- Bitbucket Server Data Center cluster only contains one node
- Bitbucket Server URL is not accessible while accessing through Browser
- Bitbucket Server webhook is not providing git URL is response payload.
- Delete build status API unable to delete a specific build in Bitbucket Data Center
- Error 500 and null pointer on a try to login with SAML connector for Bitbucket Data Center
- Filtering for active repositories on the Repository Management page also displays archived ones in Bitbucket Data Center
- Getting -1001 status codes for SSH connections in Bitbucket Server
- Git operations on Bitbucket Data Center fail due to issues with file locking
- Hazelcast network partition causing Plugin Issues in Bitbucket Data Center
- How to enable Client IP Forwarding For SSH Sessions by setting up Proxy protocol for Bitbucket Data Center.
- How to force Bitbucket Data Center to use IPv4 instead of IPv6
- How to remove the Inactive or disabled user visible in Bitbucket Data Center UI ?
- HTTP timeouts and errors 502, 503, 504, 499 logged by reverse proxy with Bitbucket Data Center
- Inodes utilization on a NFS-mounted BITBUCKET_HOME/shared is high with Bitbucket Data Center
- Node encounters OutOfMemory with hundreds of "Asking if operation execution has been started" WARN messages
- Node fails to join cluster with error: nodes are connected to the same database but different shared homes
- Nodes in the Bitbucket Data Center abruptly leave the cluster
- One of node in Bitbucket Data Center cluster is not coming up after restart with no error in logs.
- One or more Bitbucket Data Center nodes does not start successfully
- Pull Requests in Bitbucket Data Center do not get updated with the latest commit
- Recover missing node caused by split-brain in Bitbucket Data Center
- REPLICA_STATE_MISSING error on Remote Mesh Nodes of Bitbucket Data Center
- Required property 'buildHash' error when joining a Bitbucket Server node to a cluster
- Unable to create packed-refs.lock: File exists on Bitbucket Data Center
- Unable to start HAProxy Load Balancer after an upgrade to higher version with Bitbucket Server.
- When attempting to clone a repository from Bitbucket Data Center, an error message stating that "fatal: fetch-pack: invalid index-pack output" appears on the client terminal.
Last modified on Feb 27, 2017
Powered by Confluence and Scroll Viewport.