I have Confluence 6.15.2 installed on a server with Postgres. I have a backup of a Confluence Cloud instance that I am trying to restore into the server instance. During the restore (less than five minutes in) I get an error message:
Then if I try to do anything in Confluence I am just brought to an error screen:
In the database if I run the query
SELECT * FROM cwd_app_dir_mapping
I get 0 rows returned.
Hello Kristin,
Thank you for reaching out!
I've done some investigation here and I discovered that a few other users are having he same issue. We're looking through error logs right now to determine the cause.
If you'd like to assist, please enable Detailed SQL Logging and review the Confluence server logs while replicating the error again.
You can send the error messages you see there. If needed, you can send via Dropbox or something like Pastebin, since sometimes pasting logs can cause Lithium (the software Community runs on) a bit of trouble.
Regards,
Shannon
Hi Shannon, thanks for the update. I have since restarted Confluence from scratch and instead of doing a full site restore I imported spaces individually. I am not sure that the error logs have any relevant data anymore but I would be happy to send you the support zip if there is a way I can send it directly to Atlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kristin,
Thank you for letting me know that. Keep in mind that when you restore from each space at a time you will lose some data and settings outside of the space content. I just wanted to point it out in case you run into any issues like this in the future.
As for the error, no worries about sending us the logs. What I'll do is watch the support cases that we're working on, and once a resolution or bug is confirmed, I will update it here. At least it can help other users in the future.
Take care,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Kristin,
We have confirmed that this behavior you were experiencing is a bug. Have a look below:
This is caused to recent changes for GDPR.
Should you need to re-attempt the import, you can apply the workaround as listed on the bug report.
Let me know if you have any questions about that!
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.