Missed Team ’24? Catch up on announcements here.

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

Bitbucket error message at startup

Nicolas Bauland May 5, 2019

Bitbucket server on Linux 64.

When I start Bitbucket server I have the Following error:

[2019-05-05T11:14:56,905][WARN ][o.e.c.l.LogConfigurator ] [bitbucket_bundled] Some logging configurations have %marker but don't have %node_name. We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace `%node_name` with `[%node_name]%marker ` in these locations:

Bitbucket starts and seems to be correctly working but it was annoying.

Someone have any idea to remove error message ? 

3 answers

1 accepted

0 votes
Answer accepted
Nicolas Bauland May 8, 2019

Finally, I install bitbucket on a fresh server and copy/paste log4j2.properties from new one to old one.

It resolves the problem. Maybe, I have changed it by mistake ?

Jimmy Seddon
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 8, 2019

I'm gald you were able to figure it out!

Nicolas Bauland May 8, 2019

Thanks for helping me.

0 votes
Nicolas Bauland May 6, 2019

This location is:
/var/atlassian/application-data/bitbucket/shared/search/log4j2.properties

0 votes
Jimmy Seddon
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 6, 2019

Hi Nicolas,

Just reading the error message:

"We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace `%node_name` with `[%node_name]%marker ` in these locations:"

Do you see a list of location provided under this log line?  And do you make use of a custom log4j2.properties file or do you have any plugins installed that might be using this?

Just a couple of things to check.  I hope that helps!

-James

Nicolas Bauland May 6, 2019

I Don't have custom plugins. I have just bundled plugins.

log4j2.properties is created by installer it is default one.

Should I erase 'config-Template' directory ?

Should I modify log4j2.properties ?

And finally, yes it helps: I don't have a solution yet, but it could be soon ! Thanks for helping.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events