2024-02-16 17:19:39,200 DEBUG [mesh-grpc-request:thread-3] c.a.s.i.scm.git.mesh.MeshChannel Sidecar#0 (http://localhost:7777): Connectivity state updated t
o TRANSIENT_FAILURE
2024-02-16 17:19:39,206 DEBUG [spring-startup] c.a.s.i.i18n.PluginI18nService No values found in any valid locale for key bitbucket.service.mesh.node.unava
ilable and locales [en_US, en]
2024-02-16 17:19:39,206 DEBUG [spring-startup] c.a.s.i.i18n.PluginI18nService No values found in any valid locale for key bitbucket.service.mesh.node.unava
ilable and locales [en_US, en]
2024-02-16 17:19:39,206 ERROR [spring-startup] c.a.s.i.mesh.DefaultMeshController Failed to configure sidecar on initialization
com.atlassian.stash.internal.mesh.SidecarUnavailableException: Sidecar is currently unavailable
at com.atlassian.stash.internal.mesh.DefaultMeshController.maybeConfigureSidecar(DefaultMeshController.java:276)
at com.atlassian.stash.internal.mesh.DefaultMeshController.lambda$maybeConfigureSidecar$3(DefaultMeshController.java:266)
at java.base/java.util.Optional.ifPresent(Optional.java:178)
Hi jiqbal_c,
From the stack trace, It appears that the Mesh sidecar process, which is a child process of Bitbucket's main process, is not starting. As of Bitbucket 8.X and later versions, all repository interactions take place through the mesh process, and if it doesn't start or crash in the middle, an error "Repository not available - offline" appears.
I suggest you review the KB Error "Repository not available - offline" occurs when accessing a repository in Bitbucket Server and if it doesn't resolve your problem please raise a ticket with Atlassian support to check the underlying cause of the issue.
Regards,
Aman
Thanks. the issue issue resolved, when i make the entries of servername & IP's inside the server /etc/hosts file. and removed 127.0.0.1 localhost entry.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, I have the same issue. Could you please provide more details about your solution? I changed the /etc/hosts
file and specified the IP address of the server and its servername instead of 127.0.0.1 localhost
, but it did not solve my problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.