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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,281
Community Members
 
Community Events
177
Community Groups

Upgrading bamboo 6.8.1 to 6.10.3 can't find bamboo.cfg.xml

Edited

I recently updated confluence, jira, and was wrapping up the bamboo upgrade by following the instructions here:

https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html?_ga=2.233998810.534527813.1570939997-570080728.1550282310

 

I did everything as instructed and when I start the instance using ./bin/start-bamboo.sh I get the following when I try to go to the bamboo homepage.

Bamboo6-10-3StartupIssue.PNG

I triple checked the configuration file is there, it is owned by bamboo, it is readable and nothing appears wrong.  Hopefully someone else has seen this issue and can help me get this fixed, thank you!

1 answer

1 accepted

0 votes
Answer accepted

Looks like this is a problem that results when you launch the ./bin/start-bamboo.sh file as root (or using sudo).

 

I recommend sudo su <bamboo_user> first then running it, this will ensure that all the files in your home directory remain owned by the <bamboo_user> and not root.

 

I had to go through and remove several write.lock files that were owned by root, had to change ownership of several log files and maybe one or two more files that were owned by root then things started working.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events