Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Non Clustered Confluence: Database is being updated by another Confluence instance. Please see http:

Will Miller February 20, 2019

I've been running Confluence for over a year now, and all of a sudden we can't get into it due the the following error. we are not running it in a cluster environment, just a single install on our server.  We really need to get into our system and are stomped on why this is happening. We have not made any changes to install or ran any updates.

 

Non Clustered Confluence: Database is being updated by another Confluence instance. Please see http://confluence.atlassian.com/x/mwiyCg for more details.     FATAL

Your server id is: B5SM-Q02A-MJNW-TRZ7

1 answer

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2019

This happens when the system is being told that the database is being actively used by another Confluence system.

It's often because someone or something has tried to start a second instance of Confluence without waiting for the existing one to shut down completely, but there can be other causes.

Work your way through the document the error message recommends - until you've done that, there's not a lot we can add.

Will Miller February 22, 2019

No I can not get the service to start.

 

2019-02-22 07:53:53,142 WARN [C3P0PooledConnectionPoolManager[identityToken->1hgeek2a152tvig1d0ef7n|285dcc1a]-HelperThread-#2] [mchange.v2.resourcepool.BasicResourcePool] log Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@e3cdce7 is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2019-02-22 07:53:53,142 WARN [C3P0PooledConnectionPoolManager[identityToken->1hgeek2a152tvig1d0ef7n|285dcc1a]-HelperThread-#1] [mchange.v2.resourcepool.BasicResourcePool] log com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@4ea2baf4 -- 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:
com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "Conf" requested by the login. The login failed. ClientConnectionId:172443ba-459b-420c-8f52-5719473037f6
 at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:260)
 at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:256)
 at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:108)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:4507)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3374)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$100(SQLServerConnection.java:85)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3338)
 at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7342)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2688)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2236)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1897)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1738)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1062)
 at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:572)
 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)

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 22, 2019

It's no longer able to connect to the database.  You'll need to check permissions, logins etc.

Will Miller February 22, 2019

look like the log files need to be shrinked.  I tried to access the database from SQL server to do something, and it warned me that the log file had reached limit.  I'm starting their.  We been running good, and all of a sudden this happened..

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events