-
-
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
SOGo failing on (at least) newest nightly build on arm #5718
Comments
We did a rebase upon staging. So these might be issues which followed this. |
You can do the following (copy your mailcow-dockerized folder to save your custom changes if you have any):
This will let git completely fetch a clean nightly state and should fix your issues. |
I tried git reset and that did not resolve it, unfortunately |
I also noticed dovecot stopped working. dovecot: imap-login: Disconnected: Connection closed (auth service reported temporary failure): user=[email protected], method=PLAIN, rip=IP_ADDRESS, lip=IP_ADDRESS, TLS: Connection closed, TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) |
changing to the stable branch, but keeping the mysql container version the same, resolved it for me. |
same on x86 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Contribution guidelines
I've found a bug and checked that ...
Description
Largely the whole system becomes unresponsive, I've been unable to determine if it's multiple problems or just side-effects from SOGo going down, but the admin interface ended up not rendering as well. nginx is unable to connect to sogo, cause sogo is waiting for a "schema update" from the database, which never completes for some reason. Eventually the sogo container gets killed, and restarts, ending up back in the same exact loop. Reverting back to deb6f0b fixes this problem, though it's possible that later commits would work as well that one just happens to be the one I tested.
Logs:
Steps to reproduce:
Which branch are you using?
nightly
Which architecture are you using?
ARM64 (aarch64)
Operating System:
Ubuntu 22.04.3 LTS
Server/VM specifications:
4gb, 2c
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
vServer
Docker version:
25.0.3
docker-compose version or docker compose version:
2.24.5
mailcow version:
2024-01d
Reverse proxy:
Caddy
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: