Hi, i just tried to install mailcow on a fresh new Ubuntu VM.
Everything went fine up until first start.
But in the GUI i got
" What is happening?
Please do not stop the stack while we are initializing the database or do other preparations."
I waited but nothing changed so i went into the logs and saw
“php-fpm-mailcow-1 | Waiting for SQL…” gets spammed.
Anyone knows how to fix?

I tried multiple reinstalls and somewhat also got
“ php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again. ”
Anyone knows what up here?

PS : Mysql logs doenst show anything wrong:
2024-07-07 19:22:01-02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.25+mariaubu2004 started.
2024-07-07 19:22:02-02:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2024-07-07 19:22:02-02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.25+mariaubu2004 started.
2024-07-07 19:22:02-02:00 [Note] [Entrypoint]: MariaDB upgrade not required
2024-07-07 19:22:02 0 [Note] Starting MariaDB 10.5.25-MariaDB-ubu2004 source revision 29c185bd771ac441121468b3850d6dc8d13b8a1f as process 1
2024-07-07 19:22:02 0 [Note] InnoDB: Uses event mutexes
2024-07-07 19:22:02 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2024-07-07 19:22:02 0 [Note] InnoDB: Number of pools: 1
2024-07-07 19:22:02 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-07-07 19:22:02 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-07-07 19:22:02 0 [Note] InnoDB: Using Linux native AIO
2024-07-07 19:22:02 0 [Note] InnoDB: Initializing buffer pool, total size = 25165824, chunk size = 25165824
2024-07-07 19:22:02 0 [Note] InnoDB: Completed initialization of buffer pool
2024-07-07 19:22:02 0 [Note] InnoDB: 128 rollback segments are active.
2024-07-07 19:22:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-07-07 19:22:02 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
2024-07-07 19:22:02 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12 MB.
2024-07-07 19:22:02 0 [Note] InnoDB: 10.5.25 started; log sequence number 45187; transaction id 20
2024-07-07 19:22:02 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2024-07-07 19:22:02 0 [Note] InnoDB: Buffer pool(s) load completed at 240707 19:22:02
2024-07-07 19:22:02 0 [Note] Server socket created on IP: ‘::’.
2024-07-07 19:22:03 1 [Note] Event Scheduler: scheduler thread started with id 1
2024-07-07 19:22:03 0 [Note] mysqld: ready for connections.
Version: ‘10.5.25-MariaDB-ubu2004’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution

PS : When i first started the container i got “ php-fpm-mailcow-1 | Waiting for SQL… ”
after i restarted the containers i now get
php-fpm-mailcow-1 | Waiting for SQL…
php-fpm-mailcow-1 | Uptime: 1 Threads: 2 Questions: 1 Slow queries: 0 Opens: 17 Open tables: 10 Queries per second avg: 1.000
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again

PS : When i first started the container i got “ php-fpm-mailcow-1 | Waiting for SQL… ”
after i restarted the containers i now get
php-fpm-mailcow-1 | Waiting for SQL…
php-fpm-mailcow-1 | Uptime: 1 Threads: 2 Questions: 1 Slow queries: 0 Opens: 17 Open tables: 10 Queries per second avg: 1.000
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again

PS : When i first started the container i got “ php-fpm-mailcow-1 | Waiting for SQL… ”
after i restarted the containers i now get
php-fpm-mailcow-1 | Waiting for SQL…
php-fpm-mailcow-1 | Uptime: 1 Threads: 2 Questions: 1 Slow queries: 0 Opens: 17 Open tables: 10 Queries per second avg: 1.000
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again
php-fpm-mailcow-1 | Could not get mysql-mailcow container id… trying again

Sorry the forum is bugy i cant edit / remove my duplicates ( Forum says error try to refresh page)

Hey there,
There are some few steps you need to make sure you follow:

  1. Check Docker Compose
  2. Review Logs
  3. Restart Containers
    And if the issue persists, post on the Mailcow community forum or GitHub for more help.

    Have something to say?

    Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

    harper89
    Already did.. also did a Github issue.. but no luck. And nobody wanna answear on the offical Telegram.

      Did you check the logs of mysql-mailcow?

        Could be that you are not running on a supported hypervisor platform.
        “Do not try to install mailcow on a Synology/QNAP device (any NAS), OpenVZ, LXC or other container platforms. KVM, ESX, Hyper-V and other full virtualization platforms are supported.”

        DocFraggle would you have fully read my post you would see that i even posted mysql logs.

        [unknown]
        My Plattform is supported.
        I had mailcow already running but had to delete the vm and set up a new one.
        Haven’t had any problems whatsoever until now.

          3 months later
          docker compose down --volumes
docker compose up -d

          This worked for me. It will delete your data, make sure you back up first

          No one is typing