-
-
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
Dovecot not starting anymore #6018
Comments
Hello there, Could you please try this command, and let me know if it resolvable via container's DNS. docker exec -it mailcowdockerized-dovecot-mailcow-1 nslookup www.spamassassin.heinlein-support.de Also, try this with docker exec -it mailcowdockerized-dovecot-mailcow-1 curl -v https://www.spamassassin.heinlein-support.de Also try them in your host server, not inside containers. |
THIS IS A AUTOMATED MESSAGE! It seems your issue is not a bug. You can get support either by:
This issue will be closed. If you think your reported issue is not a support case feel free to comment above and if so the issue will reopened. |
@h3ssan here is the output: docker exec -it mailcowdockerized-dovecot-mailcow-1 nslookup www.spamassassin.heinlein-support.de
docker exec -it mailcowdockerized-dovecot-mailcow-1 curl -v https://www.spamassassin.heinlein-support.de
nslookup www.spamassassin.heinlein-support.de
curl -v https://www.spamassassin.heinlein-support.de
SO why can the Host itself access the URL via curl but the the docker? I did not modify any of the settings |
@DerLinkman I disagree with the "not a bug" tag, the website mailcow uses blocks the connection via docker for which reason ever. I reinstalled the whole server and did not change any of the settings regarding to docker / host and still got this behaviour. This should be looked into and is not a support case. Its a bug. |
Hi @DerLinkman, looks like the problem with the container itself not the host server. |
It's not a bug... it's not working for him not all. We have these cases a few times... every case was something broken on their machines regarding docker networking. |
Yeah we could discuss if the dovecot should not start if he can't download the stuff but... i don't know... |
Okay @DerLinkman, as you wish. Final tips for @Sysadminfromhell try mess with OpenSSL, might be the handshake issues related to OpenSSL. |
Wait... let me correct my answer from above: It seems like a partial problem. 1st it was looking like a DNS issue but if you carefully read the logs it said SSL error, so i presume heinlein was not online at the moment. That is indeed a problem... To ease this up: I'll ad a give up section were he continues even if it has failed... but i think he is already doing it no? |
Yes @DerLinkman , it’s already retrying 10 times, but all failed. |
Yea I can confirm that that the dovecot container is not starting. It just retries and then reboots after 10 retries. So the loop has no"end" condition. |
That is not good... i mean that you cannot resolve this either but also that it does not has a exit condition... let me adjust that |
Unfortunately, the issue doesn't seem to be fully fixed.
EDIT: It seems like it never reaches the retry limit. Can't exactly tell why, the container is running and not restarting, but it goes down to 2 restarts left and then starts again at 10. Edited my sa-rules.sh to only have a retry limit of 5 and then it starts successfully. |
I am having the same issue and have no idea how to solve it. Now I cannot send any emails. Has anyone found a way to resolve this issue? |
I've changed the retry limit from 10 to a more reasonable 5 in the file In this section:
Then added an override for the file to the docker compose file with a volume mount
Definitely a quick and dirty workaround, but better than a dead email server. |
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:
2v CPU, 4 GBRAM
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
QEMU KVM VM
Docker version:
27.1.2
docker-compose version or docker compose version:
v2.13.0
mailcow version:
2024-08
Reverse proxy:
Nginx
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: