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

Where is the database password stored in properties file for BAMBOO

Deleted user December 15, 2017

Upgraded bamboo to 6.25,  now when I go to start the service and go to localhost:8085  I get

 

Bamboo error reporting - Atlassian Bamboo

You cannot access Bamboo at present. Look at the table below to identify the reasons:

TimeLevelTypeDescriptionException

2017-12-15 17:08:52fatalbootstrapBamboo bootstrap failed: Your Bamboo instance could not start because health check failed. Contact Atlassian Support at https://support.atlassian.com

 

 

 

 

Mssql user is correct bamboouser, and I test the password with visualstudio and it works, but may have been recently changed.

 

Looking at log I see:

 

2017-12-15 17:07:51,766 WARN [C3P0PooledConnectionPoolManager[identityToken->2rxcoc9spl2w34j55dcm|21c78bfd]-HelperThread-#0] [BasicResourcePool] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@361f18ef is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2017-12-15 17:07:51,767 ERROR [localhost-startStop-1] [BootstrapUpgradeManagerImpl] Task 4410 failed
java.lang.RuntimeException: java.sql.SQLException: Connections could not be acquired from the underlying database!
at com.google.common.base.Throwables.propagate(Throwables.java:160)
at com.atlassian.bamboo.upgrade.AbstractBootstrapUpgradeTask.getDatabaseConnection(AbstractBootstrapUpgradeTask.java:43)
at com.atlassian.bamboo.upgrade.AbstractBootstrapUpgradeTask.withDatabaseConnection(AbstractBootstrapUpgradeTask.java:58)
at com.atlassian.bamboo.upgrade.tasks.validation.BranchKeyStartsWithMastersChainKey.doUpgrade(BranchKeyStartsWithMastersChainKey.java:41)
at com.atlassian.bamboo.upgrade.BootstrapUpgradeManagerImpl.runValidationTask(BootstrapUpgradeManagerImpl.java:131)
at com.atlassian.bamboo.upgrade.BootstrapUpgradeManagerImpl.runValidationTasks(BootstrapUpgradeManagerImpl.java:91)
at com.atlassian.bamboo.setup.DefaultBootstrapManager.runValidationTasks(DefaultBootstrapManager.java:374)
at com.atlassian.bamboo.setup.DefaultBootstrapManager.performPersistenceUpgrade(DefaultBootstrapManager.java:278)
at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.init(DefaultAtlassianBootstrapManager.java:77)
at com.atlassian.bamboo.setup.BootstrapLoaderListener.contextInitialized(BootstrapLoaderListener.java:117)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4842)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5303)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1407)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1397)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:118)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:692)
at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:140)
at org.hibernate.c3p0.internal.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:73)
at com.atlassian.bamboo.upgrade.BootstrapTaskConnectionProvider.getConnection(BootstrapTaskConnectionProvider.java:68)
at com.atlassian.bamboo.upgrade.AbstractBootstrapUpgradeTask.getDatabaseConnection(AbstractBootstrapUpgradeTask.java:40)
... 17 more
Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.
at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1469)
at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:644)
at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:554)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutAndMarkConnectionInUse(C3P0PooledConnectionPool.java:758)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:685)
... 21 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'bamboouser'. ClientConnectionId:1dd7f443-9abe-4f57-a1a0-422552059d4d
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:232)
at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:291)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:111)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:4376)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3188)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$100(SQLServerConnection.java:61)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3151)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7535)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2438)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1973)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1616)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1447)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:788)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1187)
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:175)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:220)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:206)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:203)
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1138)
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPendingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1125)
at com.mchange.v2.resourcepool.BasicResourcePool.access$700(BasicResourcePool.java:44)
at com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.run(BasicResourcePool.java:1870)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)
2017-12-15 17:07:51,767 WARN [C3P0PooledConnectionPoolManager[identityToken->2rxcoc9spl2w34j55dcm|21c78bfd]-HelperThread-#2] [BasicResourcePool] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@361f18ef is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2017-12-15 17:07:51,767 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] ---------------------------------------------------------
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] 51010 : Check if lucene index root dir exists (bootstrap)
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] ---------------------------------------------------------
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] Task 51010 completed successfully.
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] -----------------------------------------------------------------------------
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] 51012 : Make sure that MySQL server uses InnoDB engine for tables (bootstrap)
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] -----------------------------------------------------------------------------
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] Task 51012 completed successfully.
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] --------------------------------------------------------------------------
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] 51102 : Make sure server key has been initialized and is valid (bootstrap)
2017-12-15 17:07:51,768 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] --------------------------------------------------------------------------
2017-12-15 17:07:51,771 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] Task 51102 completed successfully.
2017-12-15 17:07:51,771 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] -------------------------------------------
2017-12-15 17:07:51,771 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] 51111 : Verify DB compatibility (bootstrap)
2017-12-15 17:07:51,771 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] -------------------------------------------

1 answer

0 votes
somethingblue
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 18, 2017

Hi David,

Take a look at the knowledge base article Changing Bamboo database settings:

The Bamboo database configuration is persisted in the <Bamboo-Home>/bamboo.cfg.xml file. You can change the database settings by editing this file, as detailed in the instructions below:

 

Changing the Bamboo database username and password.

If you want to change the database username and password, edit the following line,

    <property name="hibernate.connection.password">YOUR_PASSWORD</property>
    <property name="hibernate.connection.username">YOUR_USERNAME</property>

Changing the Bamboo database URL

If you want to change the database URL, edit the following line,

    <property name="hibernate.connection.url">DATABASE_URL</property>

(warning) You need to restart the Bamboo application server for the changes to take effect. If you have any elastic agents running, ensure that they are shut down before you restart the Bamboo server. If you do not shut down your elastic instances before restarting, they will continue to run and become orphaned from your Bamboo server.

Another article that may help is titled Connections could not be acquired from the underlying database which also provides some MySQL specific issues, The URL for the database is incorrect, etc.  Take a look at the above information to check your password and the Connections could not be acquired from the underlying database knowledge base article and let us know the outcome.

Hopefully this helps!

Cheers,

Branden

Deleted user December 18, 2017

Thanks, perfect.  Now I have to fix port # someplace.

somethingblue
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 18, 2017

Hi David,

You're going to change the startup port in the <Bamboo install directory>/conf/server.xml:

Changing the Bamboo start port

  1. Stop Bamboo.
  2. Edit <Bamboo install directory>/conf/server.xml
  3. Update the following so that Connector port is set to the port value you require:

     <Service name="Catalina">
            <Connector port="8085"
                       maxThreads="150"
                       minSpareThreads="25"
                       connectionTimeout="20000"
                       enableLookups="false"
                       maxHttpHeaderSize="8192"
                       protocol="HTTP/1.1"
                       useBodyEncodingForURI="true"
                       redirectPort="8443"
                       acceptCount="100"
                       disableUploadTimeout="true"/>
  4. Restart Bamboo.

If you're using a proxy you'll also need to take that configuration into account as well.  Here are the SSL guides for the common proxy servers:

Cheers,

Branden

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events