nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

bitbucket service is starting and crashing immediately

Dspiliopoulos

hello,

We recently upgraded our bitbucket server to v5.9.1. Today the installed bitbucket service stopped initializing.

It looked like a java upgrade may have caused the inconsistency. We managed to solve the

error pointing us to a non-existent jvm.dll path

The service then would just start and stop. Could you please assist on giving us a lead?

We have considered the following and have not helped or not applied to us.

1. java home environment variable

2. spacing in the environment variable

3. jvm mismatch although there clearly was one on first observation but later corrected

4. we even deleted the existing service and recreated a new one

from the logs we only see the following

StartServiceCtrlDispatcher for 'AtlassianBitbucket' failed
[2018-04-19 09:53:23] [error] [ 320] The service process could not connect to the service controller.
[2018-04-19 09:53:23] [error] [ 320] Commons Daemon procrun failed with exit value: 4 (Failed to run service)
[2018-04-19 09:53:23] [error] [ 320] The service process could not connect to the service controller.
[2018-04-19 09:53:52] [info] [ 564] Commons Daemon procrun (1.0.15.0 64-bit) started

Commons Daemon procrun (1.0.15.0 64-bit) started
[2018-04-19 12:02:38] [info] [ 5332] Running 'BITBUCKET' Service...
[2018-04-19 12:02:38] [info] [ 5864] Starting service...
[2018-04-19 12:02:39] [info] [ 5864] Service started in 1167 ms.
[2018-04-19 12:02:55] [info] [ 5332] Run service finished.
[2018-04-19 12:02:55] [info] [ 5332] Commons Daemon procrun finished

and from window event viewer

The Atlassian Bitbucket BITBUCKET service terminated with the following service-specific error:
Incorrect function.

bitbucket is running on a windows 2012 r2 box (64-bit)

we have installed a 64 bit java

java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode)

Accepted answers

All comments

Christian Glockner

Hi Dimitrios,

Are you able to start Bitbucket Server directly, i.e. not as a service? You can try running <BitbucketInstallationDir>\bin\start-bitbucket.bat from a command window. This will help you understand if there's something wrong with the service or Bitbucket Server itself.

Cheers,

Christian

Premier Support Engineer

Atlassian

Dspiliopoulos

Morning Christian,

Thanks for your feedback mate. Bitbucket server is actually running through the batch file. It was the only way to get the app running.

We deleted the existing service from the upgrade , which was working fine a week now. We reconfigured a new service again yesterday with all necessary permissions to the directories but the behavior is the same. The unfortunate is that the errors I provided give us no lead.

Any ideas?

Dspiliopoulos

Hello Christian,

Hope you are well. Do you have any other ideas? Bitbucket has been working without problems but initialized through the batch. We restarted the host to see if the system anticipated any changes, but the Bitbucket service option still behaves like before. It starts and then stops.

The errors are the ones i listed above.

from the logs we only see the following

and from window event viewer

The Atlassian Bitbucket BITBUCKET service terminated with the following service-specific error:
Incorrect function.

CrownConsult

Hi,

I have similar issue. Did you find a solution?

Erik Hobel

Hello,

I had the same problem with my Stash installation. I solved it within the windows registry. I updated the JavaHome and the Jvm Attribute in the service definition

HKEY_LOCAL_MACHINE/SOFTWARE/Apache Software Foundation/Procrun 2.0/AtlassianStash/Parameters/Java

Sooraj_Ravindran

Hi Erik,

Thanks.

But I couldn't find any similar entry in my registry for bitbucket.

Sooraj_Ravindran

Thanks a lot. it was in different location. This has resolved my issue. Much appreciated.