bamboo 启动报错，无法正常访问

刺骨的言语ヽ痛彻心扉 2022-08-26 08:40 349阅读 0赞

分析过程：

早上发现bamboo无法访问,便使用命令

ps -ef | grep 8085

发现没有任何服务占用8085端口(bamboo使用tomcat作为内嵌服务器,端口使用8085),

原来是服务器没有启动,于是重启bamboo服务,结果仍然无法正常访问;

查看日志,报错信息如下:

2014-04-01 10:12:54,652 INFO \[localhost-startStop-1\] \[MessageDatabase\] Database /opt/app/bamboo/atlassian-bamboo-4.4.4-home/jms-store/bamboo/KahaDB/lock is locked...  
waiting 10 seconds for the database to be unlocked.  
Reason: java.io.IOException: File '/opt/app/bamboo/atlassian-bamboo-4.4.4-home/jms-store/bamboo/KahaDB/lock' could not be locked.

猜测大概是因为程序锁定了数据库导致。  
但是有点搞不明白,既然都没有服务启动,而数据库又是内置的,非共享的数据库,怎么会出现数据库锁定呢???  
google查找原因,发现以下回复:  
\-----------------------------------------  
after so much serach i found more than one instace were running.  
ps -ax | grep bamboo  
then I kill all the process and restart the server.  
and its fixed.  
thanks for all your help.  
\-----------------------------------------  
以上转载自：[https://answers.atlassian.com/questions/197611/bamboo-database-problem][https_answers.atlassian.com_questions_197611_bamboo-database-problem]

\-----------------------------------------  
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.  
\-------------------------------------------

以上转载自：[https://answers.atlassian.com/questions/17926/server-won-t-restart-after-crashing-due-to-a-lock-file-issue][https_answers.atlassian.com_questions_17926_server-won-t-restart-after-crashing-due-to-a-lock-file-issue]

尝试之,发现竟然有多个bamboo的实例;何其诡异哪!!!!!

杀死所有进程,重启bamboo Server,搞定...

[https_answers.atlassian.com_questions_197611_bamboo-database-problem]: https://answers.atlassian.com/questions/197611/bamboo-database-problem
[https_answers.atlassian.com_questions_17926_server-won-t-restart-after-crashing-due-to-a-lock-file-issue]: https://answers.atlassian.com/questions/17926/server-won-t-restart-after-crashing-due-to-a-lock-file-issue