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

Bamboo bootstrap failed: Your Bamboo instance could not start because Bamboo home directory does not

Amit Anand January 8, 2021

Bamboo bootstrap failed: Your Bamboo instance could not start because Bamboo home directory does not match database. Contact Atlassian Support at https://support.atlassian.com

 

Atlassian Bamboo version 6.6.2 build 60606

3 answers

1 vote
Ganesh Babu
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 10, 2021

Hi @Amit Anand 

This is caused by a version mismatch between the database and home directory.

Here is a related question : Bamboo home directory does not match database

From the link there is a suggestion that fixes the problem by running this DB query.

delete from BANDANA where BANDANA_KEY = 'bamboo.db.version';

Before running, please check the version by executing the query and also the version in the  bamboo.cfg.xml

Amit Anand January 10, 2021

Hi @Ganesh Babu 

Not able to get data?

Hipsql (13.1 (Ubuntu 13.1-1.pgdg16.04+1), server 9.6.20)
You are now connected to database "bamboo" as user "postgres".
bamboo=# select * from bamboo.bandana where bandana_key = 'bamboo.db.version';
ERROR: relation "bamboo.bandana" does not exist
LINE 1: select * from bamboo.bandana where bandana_key = 'bamboo.db....
^
bamboo=#

 

Thanks

Amit Anand

Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 10, 2021

Please kindly refer to my answer at the bottom. The query is not valid for newer versions anymore.

Like Amit Anand likes this
0 votes
Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 9, 2021

Hi @Amit Anand
Not a solution this time but a question - did this happen right after an upgrade or came it "out of the blue" after a restart of Bamboo?
I am just asking because all references to this error message are found to happen after an upgrade.

If an upgrade took place lately could you kindly state from which version to which version you have upgraded?

Regards,
Daniel

Amit Anand January 10, 2021

Dear @Daniel Ebers ,

I am trying to import data from one instance to other.

Followed below practice for same:
For Export :https://confluence.atlassian.com/bamboo/exporting-data-for-backup-289277255.html

For Import:https://confluence.atlassian.com/bamboo/importing-data-from-backup-289277260.html

Bamboo server started well with fresh/default data but when i have imported other instance data then i face this issue.

Also Updated to avoid JVM issue.

JVM_MINIMUM_MEMORY/JVM_MAXIMUM_MEMORY arguments inside the <Bamboo server installation directory>/bin/setenv.sh file

Thanks
Amit Anand

Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 10, 2021

Thanks for clarification. From my understanding both source and destination (system) should be on the same Bamboo version. Is this the case?

Amit Anand January 10, 2021

Yes indeed !

Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 10, 2021

You could try the database queries Ganesh and Gonchik posted but they are for newer versions not recommended anymore and were removed from a corresponding bug issue - so it might be the case running the database query does not help anymore or cause more damage than it helps.
You could test it on a non-production copy of your Bamboo server first.
If this does not help, Bamboo support could probably advise further.

0 votes
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 8, 2021

Hi @Amit Anand 

 

Could you check the user you're using to start Bamboo is the owner of the bamboo-home and installation directories? Of course, you hope information in the file atlassian-bamboo/WEB-INF/classes/bamboo-init.properties is correct. (https://confluence.atlassian.com/bamboo/locating-important-directories-and-files-289277247.html)

 

Have you checked the bamboo-home/logs/atlassian-bamboo.log file to see if there are details about the error there? Please, if you find any [FATAL] error, paste the details here so we can better understand why your instance is failing to start.

Amit Anand January 10, 2021

Dear @Gonchik Tsymzhitov ,

There is fatal error :

2021-01-11 09:43:24,329 FATAL [localhost-startStop-1] [DefaultBootstrapManager] Validation tests failed: Your Bamboo instance could not start because Bamboo home directory does not match database. Contact Atlassian Support at https://support.atlassian.com
2021-01-11 09:43:24,331 INFO [localhost-startStop-1] [lifecycle] Bamboo home directory: /var/atlassian/application-data/bamboo-home

 

I can see in screen

:Continuous integration powered by Atlassian Bamboo version 6.6.2 build 60606 - 14 Aug 18

Capture.GIFThanks

Amit Anand

Like Gonchik Tsymzhitov likes this
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 10, 2021

Hi @Amit Anand 

So situation it's  the similar as many the same requests. :(

This is caused by a version mismatch between the database and home directory.

Here is a related question : Bamboo home directory does not match database

From the link there is a suggestion that fixes the problem by running this DB query.

delete from BANDANA where BANDANA_KEY = 'bamboo.db.version';

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events