-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Waiting for SQL #6171
Comments
Some here - fresh Install. |
Same here, debian 12, fresh install not working. Any workarounds or does not have to get the old version somehow? |
Jup can confirm. It's the docker image. You can try modifying the docker-compose.yml and replace the mariadb:10.5 with mariadb:10.5.26 which is working as intended. |
Even after this fix, the image DOES work and never restart, but mysql inside the image dont seems to start. Nginx is stil listening and waiting in the logs, letting us stuck in the initialising screen |
If you have a fresh mailcow run docker compose down -v to delete all volumes. Again ONLY FOR NEW ONES, as it destroy all volumes... Afterwards do up -d again. |
Thats it. Thanks. |
Ok i debunged it: It's because of thread_stack = 128K (our set value) seems to be to low apparently with that minor version. Nice to not see this in any changelog of mariadb. Good, good... 2024-11b will be out in a few minute addressing exactly this + some more fixes. It was originally planned for next week, but this is important to resolve before the Weekend. |
Thanks bud. |
Thanks very much for the fast response! |
It's now live within 2024-11b for y'all. If you created a new mailcow update with update.sh and then drop all data with docker compose down -v to properly recreate all stuff. If you use a different mysql version as a workaround you can remove that too. |
Hi All, I am facing the same issue, I am installing fresh install, from scratch, 2024-11b, $ sudo docker logs mailcowdockerized-dovecot-mailcow-1 any updates? Thank you in advance. |
Any mysql logs? |
hello , Sorry for the late replay : 15:57:08 0 [Note] Starting MariaDB 10.5.27-MariaDB-ubu2004 source revision 6aa47fae304bd1f3efc0ebd2035bc1481ded73a3 server_uid htq1MTURYLUrMuU4LgOH1bA5G2A= as process 1 |
Mariadb Tables were not created. Delete all volumes followed by recreating mailcow and you should be good to go again. The fixed thread stack variable is live inside the code, so i don't understand why this won't work for you then... |
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian 12
Server/VM specifications:
4
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
KVM
Docker version:
27.3.1
docker-compose version or docker compose version:
Docker Compose version v2.29.7
mailcow version:
2024-11a
Reverse proxy:
None ?
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: