Forums

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

Unable to start up Confluence

Jacob Creswick
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 12, 2020

Confluence server VM was restarted unexpectedly, now unable to access confluence. Database was not restarted and is functional. 

Environment:

Confluence 7.1.0 on Ubuntu 18.04
MySQL 8.0.18 on Ubuntu 18.04

Error:

Unable to start up Confluence. Fatal error during startup sequence: confluence.lifecycle.core:mananagedjobs (Start and stop the Managed Scheduled Jobs)
2020-04-12 19:13:07fatalJDBC exception on Hibernate data access: SQLException for SQL [select schedulerr0_.id as id1_50_, schedulerr0_.job_id as job_id2_50_, schedulerr0_.start_time as start_ti3_50_, schedulerr0_.duration as duration4_50_, schedulerr0_.outcome as outcome5_50_, schedulerr0_.message as message6_50_ from scheduler_run_details schedulerr0_ where schedulerr0_.job_id=? order by schedulerr0_.start_time desc]; SQL state [S1009]; error code [0]; could not execute query; nested exception is org.hibernate.exception.GenericJDBCException: could not execute query

Confirmed connectivity to database is okay. 

Looking at confluence.log:

2020-04-12 19:13:07,197 ERROR [Catalina-utility-1] [atlassian.config.lifecycle.LifecycleManager] panicAndShutdown Unable to start up Confluence. Fatal error during startup sequence: confluence.lifecycle.core:mananagedjobs (Start and stop the Managed Scheduled Jobs)
org.springframework.orm.hibernate5.HibernateJdbcException: JDBC exception on Hibernate data access: SQLException for SQL [select schedulerr0_.id as id1_50_, schedulerr0_.job_id as job_id2_50_, schedulerr0_.start_time as start_ti3_50_, schedulerr0_.duration as duration4_50_, schedulerr0_.outcome as outcome5_50_, schedulerr0_.message as message6_50_ from scheduler_run_details schedulerr0_ where schedulerr0_.job_id=? order by schedulerr0_.start_time desc]; SQL state [S1009]; error code [0]; could not execute query; nested exception is org.hibernate.exception.GenericJDBCException: could not execute query

....

Caused by: org.hibernate.exception.GenericJDBCException: could not execute query

I have a VM level backup and database dumps, if it comes to it, but would prefer to fix if it's possible.

Thanks!

2 answers

1 accepted

0 votes
Answer accepted
Jacob Creswick
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 13, 2020

Attempted restore of ZIP backup on a fresh install, of same version - got an error with restoring. 

New database, new server, fresh install, restored backup from 2 days prior and we're back up and running. 

Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 15, 2020

Hey Jacob, welcome to the Community! Glad to hear you were able to get things working again. Thanks for updating us and accepting your answer, so we know the problem was solved. Hope to see you around!

B4st13n May 10, 2020

It is not resolved. This is a workaround.

Chris Nevin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 24, 2021

We are experiencing the exact same problem.  Completely rebuilding should not be an acceptable answer.  Atlassian, help to troubleshoot this is what's needed.

Tony Hobson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 21, 2021
0 votes
Tony Hobson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 21, 2021

Hi

We had a similar issue.  Jira started OK but Confluence did not.  This occurred after a server restart after the daylight saving clock change.

Check out this fix:

https://confluence.atlassian.com/confkb/confluence-will-not-start-after-dst-daylight-saving-time-with-mysql-database-and-gives-hour_of_day-1-2-error-1052641715.html

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events