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?
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.
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.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs