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; } } }

Problem when moving from the internal database to MySQL

Tobias Herzner

When we moved the data from the internal database to MySQL we followed this guide https://confluence.atlassian.com/doc/migrating-to-another-database-148867.html

This also has until the import of the XML into the new installation is working. During the import, however, we receive the message:

Error during import. For more information, see your server logs. com.atlassian.confluence.importexport.ImportExportException: Unable to complete import: Error while importing backup: could not execute statement.

However, the logs under C: \ Program Files \ Atlassian \ Confluence \ logs are all empty except for Catalina. We could not find a solution through Google and the community. We hope you can help us.

Many Thanks

Accepted answers

All comments

Shannon S

Hello Tobias,

Welcome to the Community! It's nice to meet you.

Can you just clarify exactly which issue you're having? The following is a bit unclear for me, and I think there might be a typo or some missing words:

This also has until the import of the XML into the new installation is working. During the import, however, we receive the message:

From my understanding, you've setup the new installation, and it's working, but when you attempt to import your XML site backup, this is where it fails. Can you confirm?

Please let us know your Confluence version, MySQL version. Also, can you let me know if you're staying on the same server/version when migrating your data or are if you are also performing an upgrade?

Lastly, I think you might also be looking in the wrong location for the Confluence Server Logs, so let's verify this.

Having a look at Working with Confluence Logs,

Finding the Confluence log files

This section describes Confluence's default logging behavior, and assumes that you have not changed the destination of the logs. In order to unify logging across different application servers, Confluence uses the atlassian-confluence.log as its primary log, not the application server log.

When you start Confluence, log entries will be sent to the application server logs until Confluence has completed its initial bootstrap. Any log entries written to the console will be repeated into the log in the Confluence home directory as described below.

Once the initial startup sequence is complete, all logging will be to <confluence-home>/logs/atlassian-confluence.log. For example: c:/confluence/data/logs/atlassian-confluence.log.

Note that the default location is the Confluence home directory, not the application server's log file. The home directory is specified in <confluence-installation>/confluence/WEB-INF/classes/confluence-init.properties.

You can check the confluence-init.properties file in order to be sure of your home directory location. Once you find that, it should be in that directory, under logs/atlassian-confluence.log.

Looking forward to your reply!

Regards,

Shannon

Tobias Herzner

Hi Shannon,

thank you for your quick response!

From my understanding, you've setup the new installation, and it's working, but when you attempt to import your XML site backup, this is where it fails. Can you confirm?

Thats rigth.

Please let us know your Confluence version, MySQL version. Also, can you let me know if you're staying on the same server/version when migrating your data or are if you are also performing an upgrade?

Confluence version is 6.15.1-x64
MySQL version is 5.7.26.0
Server is a Winows 7 Machine with no Upgrade at this Time.
The Trial of Confluence with the internal Database was on the same Server as the try to install a productive System.

You´ve right i serached on the wrong place for the log. Here is the right one from C:\Program Files\Atlassian\Application Data\Confluence\logs

Many Thanks for your support

Tobias

Tobias Herzner

Unfortunately, the log is apparently too big to be posted here

Shannon S

Hello Tobias,

Thank you for following up with those details. It's very helpful.

As for the log, you don't need to send me the whole file. What you can do is trigger the error message in the UI again, while you tail your Confluence Server logs. Then, you can send me the exact error that occurs in those logs at the same time as the error in the UI.

You can look for lines with the word ERROR in the beginning, and compare the timestamp to the time that you triggered the error. You can then include any follow-up lines after the error message. In particular, any lines that say "caused by" will have further details for us.