Help Internal Error 500 during new instalation of AtoM 2.6

201 views
Skip to first unread message

satrio r d

unread,
Oct 8, 2020, 3:26:35 AM10/8/20
to AtoM Users
I have troubled when installed AtoM 2.6 on my linux 18. This is my first attempt of installation, i have followed all documentation steps as written here: 

Things went fine until I proceed to "RUN THE WEB INSTALLER" process. There was a simple web instalation interface containing some configuration detail including 
  • Database name
  • Database username
  • Database password
I done fill those configuration with the same as the configuration that I specified earlier. However the instalation process cannot be continued as an error message appears above says:
"Unable to open PDO connection [wrapped: SQLSTATE[HY000] [2054] The Server requested authentication method unknown to the client]"
I'm sure I wrote the exact database name, username and password. When I try to refresh instalation page it shows internal error 500 page. I've try to search any similar problem inside the forum but can't fine any specific ones.

Here I put some issues:
  1. I try to run the troubleshooting but the problem is remain unsolved
  2. I check the log files and it now says  "Unable to open PDO connection [wrapped: SQLSTATE[HY000] [1045] Access denied for user 'MYUSERNAME'@'localhost' (using password: YES)]"
  3. I changed the password for the database user, but im sure I wrote them down correctly.
thanks for considering my problem. Hope someone here could provide any best advice to solve my problem.

Vincent Paillusson

unread,
Oct 8, 2020, 6:38:46 AM10/8/20
to AtoM Users
Hi,

As you already guessed, your problem could be caused by bad credentials. I read that you already checked that the password you entered matched correctly but how did you do so?

did you check the information written in your  ATOM_ROOT/config/config.php file ?

hope this could help,

Dan Gillean

unread,
Oct 8, 2020, 9:16:29 AM10/8/20
to ICA-AtoM Users
Hi there, 

Vincent has shared an excellent suggestion, of checking the config/config.php file to see what credentials AtoM is expecting based on configuration during installation. You can also check your MySQL credentials in /root/.my.cnf. See: 
If MySQL is not responding for some reason, you could also try restarting the service using systemd: 
  • sudo systemctl restart mysql
A quick note for next steps as well: if you experience timeouts (e.g. 504 errors) while trying to configure additional steps via the web installer, there is a known issue and a simple workaround, described here: 
Cheers,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory
he / him


--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/71efd4ba-f20a-4aec-bc5c-23471ec93febn%40googlegroups.com.

José Raddaoui

unread,
Oct 8, 2020, 12:58:02 PM10/8/20
to AtoM Users
Hi,

MySQL's authentication method needs to be changed in order to work with PHP 7.2:


To change it in a running instance you could edit /etc/mysql/conf.d/mysqld.cnf, adding the following line:

default_authentication_plugin=mysql_native_password

Then restart the MySQL service:

sudo systemctl restart mysql

And update the MySQL user:

sudo mysql -h localhost -u root -p -e "ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';"

Best regards,
Radda.

satrio r d

unread,
Oct 8, 2020, 7:36:37 PM10/8/20
to AtoM Users
Thank you Vincent, Dan and  José , for providing insightful solution. I guess that I enter a wrong password during the instalation process
so my solution is I remove the config.php file, drop the database,  restarting all service and recreate the database with the similar way written in instalation documentation. The instalation page appear once again and i could provide the correct password later. Now my AtoM runs perfectly in my server. I can consider it done :) thanks a lot

PHXHoward

unread,
Aug 22, 2021, 3:29:27 PM8/22/21
to AtoM Users
Thank you Radda for the solution.  I had this issue with a newly created EC2 instance using Ubuntu 18.04 documentation for AtoM 2.6.4.

Howard

Reply all
Reply to author
Forward
0 new messages