After recently upgrading to Bamboo 4.4.4 everything was running smoothly. A couple days later after a system reboot it no longer starts up. There are complaints about duplicate keys in the log and when I try to access the system I get a HTTP 503 error.
Attached is my log. Hopefully it may help shed some light on what's going on and if there's a way to resolve the problem.
After looking some more, this seems to be the core issue and I have no idea what to do about the unique constraint violation:
2013-04-02 23:29:33,675 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] [BasicResourcePool] com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@309b3e5e -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception:
java.sql.SQLException: error in script file line: 7379 org.hsqldb.HsqlException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_75
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
at org.hsqldb.jdbcDriver.connect(Unknown Source)
Judging from your logs, it seems that Bamboo is having an issue opening connection to your database. Could you please double check if Bamboo connection to the database is working fine and please double check if the database is alive and healthy to server Bamboo.
Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
Hope it helps.
Seems like data corruption might be the cause of the issue as HSQLDB is a memory based database that intended to use only for evaluation purposes. To avoid such occurrences in the future, you might want to migrate your database to an external database, which is much more reliable.
Looking at the log file - it looks like you're running hsqldb which would create the db in your bamboo home ( from your log: /Volumes/Drobo/bamboo ). I would suggest making sure that's mountable and that you can see /Volumes/Drobo/bamboo/database/defaultdb . If you're using this Bamboo instance for a production instance - you should probably switch to an external database.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot