That log file shows a stuck thread, but that appears to clear and does not clearly show a problem to me. I would like to gather a more complete set of logs from your environment so we can better understand this problem. To do that I have created a support case on your behalf in https://getsupport.atlassian.com/servicedesk/customer/portal/20/GHS-165434
Please see the instructions there so we can try to help troubleshoot this further.
I understand you are trying to migrate databases between MySQL and PostgreSQL, but I am unclear as to exactly what steps you are following to attempt to do this. In regards to a Jira database, I would suggest trying to follow the steps in Switching databases.
This process has you creating an XML backup .zip file in Jira and then creating a new blank database for Jira to use. This way you can then import that data using Jira's setup wizard to import that backup into this new empty database.
While it might be possible to use some kind of native database tool to try to convert this data, I don't have any experience in getting this part to work. I would though recommend checking to make sure that your version of Jira is listed as a supported platform with the specific version of Postgres that you are trying to migrate to. You can do this by checking against the appropriate Jira Supported Platforms page.
Please let me know if this helps.
I'm not sure I follow what you mean. Specifically the line:
Export window goes to installation window.
I don't know what you mean by this. Do you mean that in the middle of trying to create the XML backup file that Jira takes you to the installation view? Or that there are startup logs being generated in the backup itself?
Unfortunately, our community site will not allow you to attach a file here. So you would need to upload this file first to another service like Google Drive or Dropbox and then share a link to that file here. I'd be happy to take a closer look at that log to see if we can learn more about the problem here.
I'm thinking that something has gone horribly wrong on a SQL level or something else within Jira. You should not be taken back to the installation wizard page during this import. Instead when the import is complete, Jira should restart and take you to the login page. If you are not getting that far, then there is most likely something wrong with the database, or Jira's ability to use that database as expected.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events