Hi Steve,
I've found at least 2 other threads in our forum that include a similar error message. In both cases, the advice from our developers was to check the config/config.php file for typos or other errors, or otherwise delete it, run the web installer again. See for example:
Some other notes and suggestions:
First, make sure the filesystem permissions are properly set. AtoM expects the www-data user to be the owner of all files in the root AtoM directory. You can make sure they are properly applied by running the following:
- sudo chown -R www-data:www-data /usr/share/nginx/atom
Was the new installation working before you tried loading your data? Our upgrade process recommends basically performing a new installation alongside the old one, and then migrating the database. That means you should have been able to get through the final installation steps, including running the web installer. The second thread linked above will be more helpful if you haven't successfully installed the second AtoM site, to the point you can access it successfully in a web browser (even if it has no content loaded yet).
One thing that occurred to me was that if you're installing a new instance of AtoM on the same server, then you may need to give the second site a different database and search index name - possibly also a different Nginx configuration block name as well - to avoid conflicts with the previous installation. Something to try out!
Finally, you can always try repeating the steps - sometimes something doesn't quite take, or a small step is missed along the way. If something's gone wrong after you've tried loading your data, then using AtoM's tools:purge command can also help flush out any data remnants. I've previously given instructions on this in the following thread:
Let us know if these suggestions help!
Dan Gillean, MAS, MLIS