I've triple checked the password in mailman.cfg and used the same username/password directly in MySQL and was able to get to the mailman3 database. I did run a test script in python3 using the PyMySQL connector and got the same error. Is there some permissions issue I need to look for? I ran the install as user root - perhaps the user running the python script doesn't have access somehow?
On Thu, Jul 21, 2022 at 7:48 AM Stephen J. Turnbull < stephenjturnbull@gmail.com> wrote:
Mail Person writes:
Hi Everyone. I'm installing Mailman3 on a Ubunu 18.03 server using MySQL as the backend. After installing using the mailman3-full package and configuring it, I'm getting the following error when trying to start the mailman3 service:
Jul 21 04:28:44 eps mailman3[81963]: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1045, "Access denied for user 'mailman3'@'127.0.0.1' (using password: YES)")
I would guess that the password doesn't match. This can happen because some configuration is done with Python modules (.py files, the configuration is Python code) where strings are *delimited* by quote marks (which are not part of the value) and some (.cfg files) are .ini-style, where all values are read as strings, and so quote marks become part of the value.
The web database (mostly user information) and the mailing list database are separate (because not all Mailman installations use Postorius and HyperKitty). Are you sure you have the right user and password for the mailing list database configured in mailman.cfg?
Other reasons would be in this reference:
Jul 21 04:28:44 eps mailman3[81963]: (Background on this error at: http://sqlalche.me/e/e3q8)
I'm not sure why the access issue is happening. Mailman3-web is running fine and I can see the site at mailman3/postorius/lists (but it says Page Not Found).
"Page not found" is probably a consequence of the same access error. You can probably see it in the database logs.