Even if so, the first thing I would recommend would be trying this again, as follows:
First, make sure you still have a copy of your backup! We're going to purge the current database, so any data currently loaded will be lost.
Next, let's try dropping and recreating the database:
- mysql -u username -p -e 'drop database atom; create database atom character set utf8 collate utf8_unicode_ci;'
Make sure to swap in your correct MySQL username. I've added "atom" as the database name here, but change this as well if you've used something else.
Next, let's try running the purge task, from AtoM's root installation directory:
This task will purge all data, and then walk you through adding the site information and an administrator user account.
After this, try loading the ICA-AtoM database again, running the upgrade task, and continuing with the instructions from there.
The one other recommendation I would have, which I don't think is causing this issue but may prevent other problems later, is to avoid running the AtoM command-line tasks as sudo. AtoM assigns all permissions to the www-data user, so you can always run AtoM command-line tasks like so, if needed:
- sudo -u www-data php symfony tools:upgrade-sql
If you want to make sure that the filesystem permissions are still properly assigned throughout AtoM, you can run the following:
- sudo chown -R www-data:www-data /usr/share/nginx/atom
Additionally, you might want to make sure you've installed the correct MySQL version - with Ubuntu 18.04 we recommend mysql-server-5.7.
Let us know if this helps! If not, I will follow up with our team and see what further suggestions they might have for you.