Server won't restart after crashing due to a lock file issue

[Dan DiCara]

I noticed that our Bamboo server was down. When I went to restart it, the bamboo.log contained the following line repeatedly:

2011-10-27 08:00:28,120 INFO main MessageDatabase Database /xchip/cga2/bamboo/bamboo-home/jms-store/bamboo/KahaDB/lock is locked... waiting 10 seconds for the database to be unlocked. Reason: java.io.IOException: File '/xchip/cga2/bamboo/bamboo-home/jms-store/bamboo/KahaDB/lock' could not be locked.

Is this an issue with my database, or with Bamboo itself? Can I just delete the lock file and then restart?

[ArmenA]

You can shut down your Bamboo, make sure that there are no other Bamboo instances running (ps -ax | grep bamboo), delete 'BambooHome/jms-store' directory and start your Bamboo instance.

Armen

[fleeber]

I didn't need to delete bambooHome/jms-store. With (ps -ax | grep bamboo), i see many instances running. i've killed all the process, and bamboo starts normally. Thanks, Armen.

[Jason Britton]

worked for me as well.  Thanks Armen.

[Maxfield B]

This also happened to me. Extra Bamboos running somehow.

[Jason Smith]

For me I just had extra Bamboos running somehow. Compared to JIRA and Confluence they really haven't spent much time making Bamboo a simple administrative experience. :/ Lots of manual stuff going on.

[Martin Faust]

Its absolutely terrible, no installer, no automatic install as service ...

[John Webber]

Also had this. I agree with the terrible administrative experience.

[ReneR]

KahaDB is a persistence component that's part of Apache ActiveMQ. Bamboo uses ActiveMQ for inter-process communication. So no, it's not part of your Build Plan data.

If this lockfile is being found that means that there's probably already an instance of JMS (Java Message Service) running. Do you have two instances of Bamboo accidentally running? Did you stop Bamboo and restart it and perhaps didn't not shutdown cleanly?

You should definitely contact support.atlassian.com and provide them your server logs for this kind of situation. If you do have two Bamboo instances running or orphaned java processes they'll want to know about it and can help you to resolve it.

[CD]

I managed to cause this problem by adding a <context> to the wrong place in service.xml. I was trying to add GMail support to Bamboo, but struggled with the doc for that, which caused this problem.

[Vijit Jain]

I have the same problem. There are no extra instances running, and deleting the JMS-Store directory does not help either.

and using all the methods documented in this thread, I still cannot start my bamboo instance.

Advice?

*Update*

Works now.