nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to start up Confluence - "Fatal error during startup sequence"

Luke Davis_qt11ky

When starting up Confluence 7.2.1 on Windows Server 2019 using MySQL 5.7, the web page displays "Confluence had problems starting up" followed by:

"Unable to start up Confluence. Fatal error during startup sequence: confluence.lifecycle.core:mananagedjobs (Start and stop the Managed Scheduled Jobs)"

"could not extract ResultSet; SQL [n/a]; nested exception is org.hibernate.exception.SQLGrammarException: could not extract ResultSet"

I had to shutdown the server hosting Confluence over the weekend due to a scheduled power outage, I received the above errors when trying to start Confluence back up on Monday morning. No other changes have been made to the server or to Confluence. My Jira Core installation is functioning fine.

Also, not sure this is applicable, but when starting confluence from the command prompt I see this:

"---------------------------------------------------------------------------"
"Using Java: \jre1.8.0_231\bin\java.exe"
Error: Unable to access jarfile C:\Program
Error: Unable to access jarfile C:\Program
"---------------------------------------------------------------------------"

From the atlassian-confluence.log file:

2020-07-11 20:26:59,061 ERROR [Caesium-1-2] [engine.jdbc.spi.SqlExceptionHelper] logExceptions Table 'confluence.scheduler_run_details' doesn't exist
2020-07-11 20:26:59,062 ERROR [Caesium-1-2] [org.hibernate.internal.ExceptionMapperStandardImpl] mapManagedFlushFailure HHH000346: Error during managed flush [org.hibernate.exception.SQLGrammarException: could not execute statement]
2020-07-11 20:26:59,062 WARN [Caesium-1-2] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doCommit Commit failed. Rolling back. Error: Hibernate operation: could not execute statement; bad SQL grammar []; nested exception is com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'confluence.scheduler_run_details' doesn't exist
2020-07-11 20:26:59,062 WARN [Caesium-1-2] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback.

Any assistance pointing me in the right direction to get this back up and running is greatly appreciated!

Accepted answers

Shannon S

Hello Luke,

Thank you for raising this with us. So you confirm that you've been running on Confluence 7.2.1 for a while now, without any issues, until shutting down Confluence since last weekend. Is that right? There haven't been any config changes made in the past, perhaps that didn't apply correctly until this most recent reboot?

Generally, this is related to a collation issue, so you could use Daniel's advice in the thread below just to rule that out. I would recommend running through the steps to check your collation, even if your database was working fine with the current configuration.

Errror after update confluence to latest version

Otherwise, it could be that an expired license is being used, or that there is an issue with the database name. You can review the steps in this article following the steps in Daniel's answer:

Unknown Column Error when upgrading from Confluence 5.x to newer versions

If you continue to have the problem, please let me know, and I can advise you further.

Take care,

Shannon

All comments

Luke Davis_qt11ky

I was able to correct the command prompt error "Error: Unable to access jarfile C:\Program" by creating a Windows environment variable %CATALINA_HOME% and setting it to "C:\Progra~1\Atlassian\Confluence".

However, I am still getting the same "Confluence had problems starting up" errors listed at the top of my original post.

Shannon S

Hello Luke,

Errror after update confluence to latest version

Otherwise, it could be that an expired license is being used, or that there is an issue with the database name. You can review the steps in this article following the steps in Daniel's answer:

Unknown Column Error when upgrading from Confluence 5.x to newer versions

If you continue to have the problem, please let me know, and I can advise you further.

Take care,

Shannon

Luke Davis_qt11ky

Shannon,

Thank you for the reply. Yes, I have been running 7.2.1 since January 2020. No changes have been made since then. I have checked on collation and it is set properly. Also, we have a year license that we bought in January 2020 so we are still set there.

I noticed that the MySql .err log was over 1.3GB - I opened it and noticed the following errors dating back to March 24 2020:

2020-03-24T03:00:09.164786Z 29679 [ERROR] InnoDB: Table `confluence`.`scheduler_run_details` is corrupt.

2020-03-24T08:58:22.270675Z 41908 [Note] InnoDB: Table `confluence`.`scheduler_run_details` is corrupted. Please drop the table and recreate it

2020-03-24T08:58:22.274380Z 41908 [Warning] InnoDB: Cannot open table confluence/scheduler_run_details from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.

Running MySQLCheck --all-databases -u root -p yields:

confluence.scheduler_run_details
Warning : InnoDB: Index PRIMARY is marked as corrupted
Warning : InnoDB: Index job_id_start_time_idx is marked as corrupted
Warning : InnoDB: Index job_id_idx is marked as corrupted
Warning : InnoDB: Index start_time_outcome_idx is marked as corrupted
Warning : InnoDB: Index start_time_idx is marked as corrupted
error : Corrupt

All other tables are OK.

Unfortunately my backups only go back about a month, so I cannot restore from backup.

Can I just drop table "confluence.scheduler_run_details" and re-create it somehow?

Thanks

Shannon S

Hi Luke,

Have you first tried InnoDB recovery?

Forcing InnoDB Recovery

If so, and if that hasn't worked, I found a ticket in our support system where a user had a similar issue. The issue was with the same table, and they did drop it, but they performed the following steps first:

Shutdown MySQL and Confluence.
Started MySQL with the innodb_force_recovery = 2 switched in my.cnf. (In the article I sent you, recovery level 1 is recommended, but in this customer's case, that didn't work, and 2 was what fixed it.)
Confirm that MySQL is running.
Create full MySQL dump.
Then, create a MySQL dump for the individual table. (confluence.scheduler_run_details)
Once you confirm that the MySQL dumps have been successfully created, then you can try to drop the confluence.scheduler_run_details table.
Remove the innodb_force_recovery = 2 switch from my.cnf.
Restart MySQL.
Confirm MySQL is running.
Re-import the confluence.scheduler_run_details table from the dump file.
Restart Confluence.
Confirm Confluence is functioning.

Can you let me know if these steps help you? This isn't quite a supported workaround, as ideally you'll want to restore from a Confluence site backup, but it's worth the try to recover your site. You just want to make sure to take database dumps and a backup now of your data before making any changes.

I hope this helps!

Shannon

Luke Davis_qt11ky

Shannon,

Those steps worked perfectly without any data loss! Thank you so much!

Luke

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence