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 will not start after new Installation

Matthew McLeod

We installed Bitbucket via the Linux installer and left all of the defaults. Git and all of the other prerequisites are already installed on the server. Attempting to start Bitbucket using the service "service atlbitbucket start" results in an error message in the log file and then nothing more. The java process is up and running but the web application is never available. There are no issues with firewall or SELinux config. The following is the last message in the $HOME/log/atlassian-bitbucket.log.

2018-01-23 14:11:16,922 INFO [spring-startup] c.a.s.i.hazelcast.HazelcastLifecycle Updating Hazelcast instance capabilities
2018-01-23 14:16:03,819 ERROR [Caesium-1-4] c.a.scheduler.core.JobLauncher Scheduled job with ID 'IndexingAnalyticsJob' failed
rx.exceptions.OnErrorNotImplementedException: null
at rx.observables.BlockingObservable$8.call(BlockingObservable.java:642)
at rx.observables.BlockingObservable$8.call(BlockingObservable.java:639)
at rx.observables.BlockingObservable$9.onError(BlockingObservable.java:673)
at rx.internal.operators.NotificationLite.accept(NotificationLite.java:147)
at rx.observables.BlockingObservable.subscribe(BlockingObservable.java:528)
at rx.observables.BlockingObservable.subscribe(BlockingObservable.java:665)
at rx.observables.BlockingObservable.subscribe(BlockingObservable.java:639)
at com.atlassian.bitbucket.search.internal.analytics.IndexingAnalyticsJob.runJob(IndexingAnalyticsJob.java:51)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:438)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:462)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)
at java.lang.Thread.run(Unknown Source)
Caused by: com.atlassian.bitbucket.search.client.ElasticsearchClientNotConfiguredException: null
at com.atlassian.bitbucket.search.client.DefaultConfigurableElasticsearchClient.lambda$execute$2(DefaultConfigurableElasticsearchClient.java:35)
at java.util.Optional.orElseGet(Unknown Source)
at com.atlassian.bitbucket.search.client.DefaultConfigurableElasticsearchClient.execute(DefaultConfigurableElasticsearchClient.java:35)
... 14 common frames omitted

Accepted answers

All comments

Caterina Curti

Hi Matthew,

The log lines don't explain why the application is not available in the user interface.

Are the CPU (2+ cores) and memory (3+ GB) requirements met on this server?

See Supported Platforms.

Cheers,

Caterina - Atlassian Support

Matthew McLeod

Thanks for the reply. We were able to figure out the problem as a permissions issue. The error in the log file was a red herring as it is thrown if you haven't finished the bitbucket setup which we of course hadn't as the web server was not accessible.

Praveen_Kumar_ou6gef

Hi Matthew,

What exactly the solution to overcome this problem. I strucked at the same point and same error message.

Matthew McLeod

Make sure that the top level folder for the Bitbucket install (both install and data locations) is owned by the bitbucket user. If you followed the installation guide then the permissions on the top level folder should be set recursively for user atlbitbucket. That error message doesn't mean anything at the point of the install as it will be there since the Bitbucket setup has not been completed.

theQuestion

Great find Matthew, I agree.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket