I am trying to get some developer time to review this thread and provide some input on possible causes and next steps. It appears that the system isn't finding your files or database tables in the expected locations.
In the meantime, let's make sure that it's not a filesystem permissions issue, and gather some more information that might help the devs offering advice.
Normally, AtoM expects all files and directories below the root installation directory (i.e. /usr/share/nginx/atom, per the recommended installation instructions) to be owned by the www-data user. We can ensure these permissions are properly set with:
It's also possible to declare a specific user when using sudo, so if you ever need to add sudo to a Symfony command to get it to run, you can specify the www-data user explicitly, as in this example below for the search index repopulation command:
- sudo systemctl restart php7.4-fpm
Note as well that all Symfony commands should be run from AtoM's root installation directory (/usr/share/nginx/atom), otherwise they may not work (you will generally get an error message like "Could not open input file:symfony" or similar).
As to the errors - I am not sure why it is not finding PHP-FPM, or the base objects table in your database. Let's at least make sure that something is there.
If you change directories to the expected location (/usr/share/nginx/atom) and run the ls command to look around, do you see the expected AtoM files and folders? You should see files and directories similar to what you see in our code repository:
Let's also confirm that the PHP pool was created as expected during installation. Can you access the following file and see a PHP configuration block?
- sudo nano /etc/php/7.4/fpm/pool.d/atom.conf
This configuration file should have been created during installation, and its contents should match this block from the docs:
Next, let's access the MySQL command-prompt. First, let's double-check the credentials used and the database name given - we can do this by looking at what information got saved and stored in the config/config.php file during installation. From AtoM's root installation directory, run:
- sudo nano config/config.php
Don't share your credentials here for security purposes, but can you confirm that the database created during installation was in fact named atom?
Now, using the credentials listed in the config file, let's access the MySQL command prompt. See:
Once accessed, let's try:
Does this output a table?
Additionally, you could try:
This should output a list of all the database tables for the selected database (defined when we accessed the MySQL prompt - i.e. atom). You should see several dozen, including object, information_object, information_object_i18n, accession, actor, and many more. If you'd like a whole list, you can see the latest database schema diagram on our wiki here:
You can leave the MySQL command prompt by entering exit.
In any case, hopefully checking on the obvious elements above and ensuring the permissions are correct will help with information gathering, and will allow us to rule out some more obvious potential causes. Let us know what you find, and I will have a developer follow up from there.