Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bitbucket WARN & ERROR Messages In atlassian-bitbucket.log

     We have a new local install of Bitbucket Server and we're seeing some WARN and ERROR messages in our atlassian-bitbucket.log file.  I've been doing Google searchs for explanations, but haven't found anything.  Here are the WARN'ing messages we have been getting that we don't know if they can be ignored or need to be fixed.  Any help or pointers would be greatly appreciated.

 

WARN [spring-startup] com.hazelcast.instance.Node [10.248.56.20]:5701 [atlbitbucket] [3.11.1] No join method is enabled! Starting standalone.

WARN [FelixStartLevel] o.e.g.b.e.i.s.ExtenderConfiguration Gemini Blueprint extensions bundle not present, annotation processing disabled

WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /com/atlassian/plugin/connect/confluence/ in bundle com.atlassian.plugins.atlassian-connect-plugin; it does not exist

WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /com/atlassian/oauth/shared/servlet/ in bundle com.atlassian.oauth.atlassian-oauth-service-provider-plugin; it does not exist

WARN [pool-124-thread-1] batesb @1KLFGHCx726x8269x0 9bmys0 10.248.38.37 "POST /rest/plugins/self-update/1.0/ HTTP/1.1" c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /com/atlassian/plugin/connect/confluence/ in bundle com.atlassian.plugins.atlassian-connect-plugin; it does not exist

     We transferred our projects from the Cloud Bitbucket to our local server and received several ERROR's like this:

 

ERROR [search-indexing:thread-1] c.a.b.i.s.i.e.DefaultIndexEventWorker Indexing - Failed for repository TEST/item1 (id: 3) with error: Indexing for repository with id 3 failed and should be retried

com.atlassian.bitbucket.internal.search.indexing.exceptions.IndexException: Indexing for repository with id 3 failed and should be retried

Caused by: com.atlassian.bitbucket.internal.search.indexing.exceptions.IndexException: Bulk indexing of files failed: RequestStatistics{failedDocumentIds=[], numRequests=1, numDocumentActions=5, numFailedRequests=0, numPartiallyFailedRequests=1, time=171 ms}

ERROR [search-indexing:thread-1] c.a.b.i.s.i.e.DefaultIndexEventWorker Indexing - Failed for repository TEST/item2 (id: 7) with error: Indexing for repository with id 7 failed and should be retried
com.atlassian.bitbucket.internal.search.indexing.exceptions.IndexException: Indexing for repository with id 7 failed and should be retried

Caused by: com.atlassian.bitbucket.internal.search.indexing.exceptions.IndexException: Bulk indexing of files failed: RequestStatistics{failedDocumentIds=[], numRequests=1, numDocumentActions=380, numFailedRequests=0, numPartiallyFailedRequests=1, time=366 ms}

 

     Thanks.

1 answer

1 vote

Hello,

This is really some list of log outputs you have. There are support tools within all Atlassian applications which will scan your logs for you and help determine which items may or may not be important. They will also link to articles on how to review and possibly solve the outputs. You may find more about this at Support Tools Plugin.

With that said, I do enjoy a challenge and I will do my best to help describe what each one means.

  1. WARN [spring-startup] com.hazelcast.instance.Node [10.248.56.20]:5701 [atlbitbucket] [3.11.1] No join method is enabled! Starting standalone.
    1. This looks to be a warning about starting in single nod vs many. This can be ignored unless you’re meant to be running Bitbucket Datacenter
  2. WARN [FelixStartLevel] o.e.g.b.e.i.s.ExtenderConfiguration Gemini Blueprint extensions bundle not present, annotation processing disabled
    1. The blueprint extension is not present so it’s not going to run the annotation process. Not an issue unless it should be present for you.
  3. WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /com/atlassian/plugin/connect/confluence/ in bundle com.atlassian.plugins.atlassian-connect-plugin; it does not exist
    1. This can be ignored as it’s a reference to Confluence.
  4. WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /com/atlassian/oauth/shared/servlet/ in bundle com.atlassian.oauth.atlassian-oauth-service-provider-plugin; it does not exist
    1. This can be ignored. Unless you’re using OAuth and something isn’t working.
  5. WARN [pool-124-thread-1] batesb @1KLFGHCx726x8269x0 9bmys0 10.248.38.37 "POST /rest/plugins/self-update/1.0/ HTTP/1.1" c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /com/atlassian/plugin/connect/confluence/ in bundle com.atlassian.plugins.atlassian-connect-plugin; it does not exist
    1. Similar to above and can be ignored.
  6. ERROR [search-indexing:thread-1] c.a.b.i.s.i.e.DefaultIndexEventWorker Indexing - Failed for repository TEST/item1 (id: 3) with error: Indexing for repository with id 3 failed and should be retried
      1. com.atlassian.bitbucket.internal.search.indexing.exceptions.IndexException: Indexing for repository with id 3 failed and should be retried
      2. Caused by: com.atlassian.bitbucket.internal.search.indexing.exceptions.IndexException: Bulk indexing of files failed: RequestStatistics{failedDocumentIds=[], numRequests=1, numDocumentActions=5, numFailedRequests=0, numPartiallyFailedRequests=1, time=171 ms}
      3. ERROR [search-indexing:thread-1] c.a.b.i.s.i.e.DefaultIndexEventWorker Indexing - Failed for repository TEST/item2 (id: 7) with error: Indexing for repository with id 7 failed and should be retried
      4. com.atlassian.bitbucket.internal.search.indexing.exceptions.IndexException: Indexing for repository with id 7 failed and should be retried
      5. Caused by: com.atlassian.bitbucket.internal.search.indexing.exceptions.IndexException: Bulk indexing of files failed: RequestStatistics{failedDocumentIds=[], numRequests=1, numDocumentActions=380, numFailedRequests=0, numPartiallyFailedRequests=1, time=366 ms}
    1. This needs to be resolved, please reference Rebuild the bundled Elasticsearch indexes for Bitbucket Server

I hope this information proves helpful and you’re able to resolve some of the errors within your logs.

Regards,
Stephen Sifers

     Thanks for the information.

Like Stephen Sifers likes this

Same issue, tried both methods to delete (through api and on filesystem) and recreate the index. The index files are recreated but the indexing still fails.

The bitbucket internal diagnostic tool also only points me to the same procedure that has been performed multiple time and still no indexing.

I'm also curious on the resolution at this point. We are facing the same issue as well with v6.9.0.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

3,741 views 10 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you