Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Container mailserver-mda-1 fails to start: Timeout after 2m0s waiting on dependencies to become available #279

Open
cmonty14 opened this issue Feb 3, 2024 · 0 comments
Open

Container mailserver-mda-1 fails to start: Timeout after 2m0s waiting on dependencies to become available #279

cmonty14 opened this issue Feb 3, 2024 · 0 comments
Labels
question

Comments

@cmonty14
Copy link

cmonty14 commented Feb 3, 2024 •
edited
Loading

Hi,
I noticed that container mailserver-mda-1 fails to start.
The error message in container's logfile is:

2024/02/03 20:49:27 Waiting for: tcp://db:3306
2024/02/03 20:49:27 Waiting for: file:///media/tls/mailserver.crt
2024/02/03 20:49:27 Waiting for: file:///media/tls/mailserver.key
2024/02/03 20:49:27 Connected to tcp://db:3306
2024/02/03 20:51:27 Timeout after 2m0s waiting on dependencies to become available: [tcp://db:3306 file:///media/tls/mailserver.crt file:///media/tls/mailserver.key]

Port 3306 is pointing to running container mailserver-db-1. This is content of container's logfile:

2024-02-03 20:33:24 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-02-03 20:33:24 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-02-03 20:33:24 0 [Note] Server socket created on IP: '::'.
2024-02-03 20:33:24 0 [Note] mariadbd: Event Scheduler: Loaded 0 events
2024-02-03 20:33:24 0 [Note] mariadbd: ready for connections.
Version: '11.1.2-MariaDB-1:11.1.2+maria~ubu2204'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2024-02-03 20:33:24 0 [Note] InnoDB: Buffer pool(s) load completed at 240203 20:33:24
2024-02-03 20:33:34 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: '172.22.0.2' (This connection closed normally without authentication)
2024-02-03 20:33:34 4 [Warning] Aborted connection 4 to db: 'unconnected' user: 'unauthenticated' host: '172.22.0.5' (This connection closed normally without authentication)
[...]

Can you please advise how to fix this issue?

Imo there's an authentication issue with the database.

I found a very similar issue #175 with this solution:
Please check your database permissions, especially the permitted hosts.

What does this mean?

Please note: this is a test deployment in my homelab on VM running Arch Linux.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jeboehm @cmonty14
  NODES
COMMUNITY 2
Note 7
Project 3
USERS 1