Mysql container says 'Access denied for user'

[hrrbrt]

Trying to get piler via docker-compose working. Startup of the different containers works but the 'piler' container is unable to connect to the 'mysql' container. When exposing port 3306 in the docker-compose file I can connect without problems with the same credentials. (mysql -h 127.0.0.1 -P 3306 -u piler -p piler). Any idea where I could get something wrong?

[jsuto]

Assuming that you use the docker-compose.yaml from the piler source tree, set the mysql hostname to "mysql".

[hrrbrt]

Yes, but this is already the case. Attached the slightly modified docker-compose file I'm using. If the host name could not be resolved I guess I could not connect to the mariadb server at all, but 'Access denied' tells me that the process is responding.
I also checked inside the mysql container and the user 'piler'@'%' is granted the configured password. I'm able to successfully connect from the host over the exposed port 3306 to the running mysql container with the same password.
docker-compese-yml.txt

And for the sake of completeness, here is the screenshot of the container startup log.

[jsuto]

It's odd, because piler apparently can read the metadata table. What does piler syslog to /var/log/mail.log regarding the mysql connection?

[hrrbrt]

Here is the /var/log/mail.log of the piler container:

2024-10-13T15:54:06.856420+00:00 b0679190095a piler-smtp[87]: info: cannot open /etc/piler/smtp.acl, piler-smtp accepts smtp connections from everywhere 2024-10-13T15:54:06.856429+00:00 b0679190095a piler-smtp[87]: reloaded config: /etc/piler/piler.conf 2024-10-13T15:54:06.856575+00:00 b0679190095a piler-smtp[87]: created directory: */var/piler/store/00* 2024-10-13T15:54:06.856834+00:00 b0679190095a piler-smtp[87]: created directory: */var/piler/tmp/0* 2024-10-13T15:54:06.856932+00:00 b0679190095a piler-smtp[87]: created directory: */var/piler/tmp/1* 2024-10-13T15:54:06.857715+00:00 b0679190095a piler-smtp[87]: piler-smtp 1.4.6-80dadac starting 2024-10-13T15:54:06.861770+00:00 b0679190095a piler[89]: ERROR: cant connect to mysql server 2024-10-13T15:54:06.861780+00:00 b0679190095a piler[89]: cannot connect to mysql server 2024-10-13T15:54:06.861880+00:00 b0679190095a piler[89]: piler 1.4.6-80dadac starting 2024-10-13T15:54:06.864502+00:00 b0679190095a piler[92]: ERROR: cant connect to mysql server 2024-10-13T15:54:06.864562+00:00 b0679190095a piler[91]: ERROR: cant connect to mysql server 2024-10-13T15:54:11.644437+00:00 b0679190095a piler-smtp[88]: connected from 127.0.0.1:44212 on fd=6 (active connections: 1) 2024-10-13T15:54:11.645925+00:00 b0679190095a piler-smtp[88]: disconnected from 127.0.0.1 on fd=6, slot=0, reason=done (0 active connections) 2024-10-13T15:54:16.866132+00:00 b0679190095a piler[91]: ERROR: cant connect to mysql server 2024-10-13T15:54:16.866177+00:00 b0679190095a piler[92]: ERROR: cant connect to mysql server 2024-10-13T15:54:26.868034+00:00 b0679190095a piler[91]: ERROR: cant connect to mysql server 2024-10-13T15:54:26.868054+00:00 b0679190095a piler[92]: ERROR: cant connect to mysql server 2024-10-13T15:54:31.698330+00:00 b0679190095a piler-smtp[88]: connected from 127.0.0.1:41914 on fd=6 (active connections: 1) 2024-10-13T15:54:31.699742+00:00 b0679190095a piler-smtp[88]: disconnected from 127.0.0.1 on fd=6, slot=0, reason=done (0 active connections) 2024-10-13T15:54:36.869786+00:00 b0679190095a piler[92]: ERROR: cant connect to mysql server 2024-10-13T15:54:36.869815+00:00 b0679190095a piler[91]: ERROR: cant connect to mysql server

[andbez]

Did you delete the "Docker Volumes" (docker volume rm ...) after your Setup-Tries? Maybe you changed the password in your compose-files in the past? What I also did is, to change the service-names and hostnames and insert a prefix "piler_", because I have several mysql-instances running on docker :D Even if I use different networks for every "stack".

[jsuto]

Verify that piler can reach both mysql and manticore databases with the parameters defined in piler.conf.

[hrrbrt]

Hi, my problem is solved and was due to permissions on the host. An old piler.conf was hanging around with a different database password. Thanks a lot for your help!!