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

Bitbucket WARN & ERROR Messages In atlassian-bitbucket.log

bbates July 23, 2019

     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.

2 answers

1 vote
Jörg Regiert December 1, 2022

similar here !

2022-12-01 14:03:22,929 WARN [ThreadPoolAsyncTaskExecutor::Thread 4] c.a.p.s.s.r.i.ComponentImportBeanFactoryPostProcessor Unable to load class 'com.atlassian.confluence.admin.criteria.WritableDirectoryExistsCriteria' for component importation purposes. Skipping...
2022-12-01 14:03:22,929 WARN [ThreadPoolAsyncTaskExecutor::Thread 4] c.a.p.s.s.r.i.ComponentImportBeanFactoryPostProcessor Unable to load class 'com.atlassian.confluence.setup.settings.SettingsManager' for component importation purposes. Skipping...
2022-12-01 14:03:22,929 WARN [ThreadPoolAsyncTaskExecutor::Thread 4] c.a.p.s.s.r.i.ComponentImportBeanFactoryPostProcessor Unable to load class 'com.atlassian.confluence.user.SignupManager' for component importation purposes. Skipping...
2022-12-01 14:03:22,929 WARN [ThreadPoolAsyncTaskExecutor::Thread 4] c.a.p.s.s.r.i.ComponentImportBeanFactoryPostProcessor Unable to load class 'com.atlassian.confluence.util.UserChecker' for component importation purposes. Skipping...
2022-12-01 14:03:28,717 WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /extension/build-status/ in bundle com.atlassian.bitbucket.server.bitbucket-frontend; it does not exist
2022-12-01 14:03:29,250 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
2022-12-01 14:03:29,325 WARN [spring-startup] c.a.p.c.r.OsgiBundledPathScanner Cannot scan directory /page/ in bundle com.atlassian.bitbucket.server.bitbucket-policies as it does not exist
2022-12-01 14:03:29,340 WARN [spring-startup] c.a.p.c.r.StaticPluginPathScanner Cannot scan directory /static/bitbucket/internal/feature/admin/ratelimit/ in web static as it does not exist
2022-12-01 14:03:30,220 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
2022-12-01 14:03:30,493 WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /com/atlassian/oauth/shared/servlet/ in bundle tac.bitbucket.languages.de_DE; it does not exist
2022-12-01 14:03:30,495 WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /extension/build-status/ in bundle tac.bitbucket.languages.de_DE; it does not exist
2022-12-01 14:03:30,498 WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /com/atlassian/oauth/shared/servlet/ in bundle tac.bitbucket.languages.fr_FR; it does not exist
2022-12-01 14:03:30,499 WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /extension/build-status/ in bundle tac.bitbucket.languages.fr_FR; it does not exist
2022-12-01 14:03:30,502 WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /com/atlassian/oauth/shared/servlet/ in bundle tac.bitbucket.languages.ja_JP; it does not exist
2022-12-01 14:03:30,503 WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /extension/build-status/ in bundle tac.bitbucket.languages.ja_JP; it does not exist
2022-12-01 14:03:30,571 INFO [spring-startup] c.a.s.internal.scm.PluginScmService Bitbucket is using /usr/bin/git version 2.20.1

and the log keeps reamining here.

also the tomcat does not read the proxy directive tho the request to our URL will be redirected to localhost.

any answer =)

JRE

1 vote
Stephen Sifers
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 6, 2019

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

bbates August 16, 2019

     Thanks for the information.

Like Stephen Sifers likes this
MartinHerren January 6, 2021

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.

LQ March 19, 2021

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
AUG Leaders

Atlassian Community Events