Troubleshoot sidecar startup
Administer Bitbucket Data Center and Server
- Users and groups
- Advanced repository management
- External user directories
- Global permissions
- Setting up your mail server
- Integrate with Atlassian applications
- Connect Bitbucket to an external database
- Migrating Bitbucket Server to another server
- Migrate Bitbucket Server from Windows to Linux
- Run Bitbucket in AWS
- Specify the Bitbucket base URL
- Configuring the application navigator
- Managing apps
- View and configure the audit log
- Update your license key
- Configuration properties
- Change Bitbucket's context path
- Data recovery and backups
- Disable HTTP(S) access to Git repositories
- Mirrors
- Bitbucket Mesh
- Export and import projects and repositories
- Git Large File Storage
- Git Virtual File System (GVFS)
- Enable SSH access to Git repositories
- Secret scanning
- Use diff transcoding
- Change the port Bitbucket listens on
- Lockout recovery process
- Proxy and secure Bitbucket
- High availability for Bitbucket
- Diagnostics for third-party apps
- Enabling JMX counters for performance monitoring
- Bitbucket guardrails
- Enable debug logging
- Scaling Bitbucket Server
- Add a shortcut link to a repository
- Administer code search
- Adding additional storage for your repository data
- Add a system-wide announcement banner
- Configuring Project links across Applications
- Improving instance stability with rate limiting
- Use a CDN with Atlassian Data Center applications
- Managing HTTP access tokens
- Manage keys and tokens
- Link to other applications
- Setting a system-wide default branch name
- Automatically decline inactive pull requests
- Encrypt database password
- Data pipeline
- Monitor application performance
- Troubleshoot sidecar startup
On this page
Related content
- No related content found
If you're starting your Bitbucket Data Center application and see the “Sidecar failed to start” error message in your browser, you’ll need to investigate the logs of Bitbucket Mesh for further details.
Check your Mesh logs
Although you may not have any Bitbucket Mesh nodes set up, Bitbucket always starts a local Bitbucket Mesh node called the sidecar for Git operations.
To find the specific log file for further investigation:
- Navigate to the Mesh log directory of your Bitbucket app node:
$BITBUCKET_HOME/mesh/log - Open the
atlassian-mesh.loglog file
At the bottom of the atlassian-mesh.log file, you’ll find the root cause of why the sidecar failed to start and more details about what needs to be done to fix the problem.
Some of the most common causes for this error include:
- You have an unsupported version of Git installed on your server which is trying to be used for your Bitbucket application and your sidecar. For more information on the supported Git versions, see Supported platforms.
- The sidecar process has been killed by something before Bitbucket could be fully started. Restarting your Bitbucket instance will restart your sidecar process.
If you find that the information presented in the atlassian-mesh.log file does not provide you with enough information to help resolve your problem, contact the Atlassian support team for further assistance.
Related content
- No related content found