andryyy
commented
4 years ago Hi, Which kernel are you on?
Closed Pitastic closed 4 years ago
andryyy
commented
4 years ago Hi, Which kernel are you on?
Pitastic
commented
4 years ago Hey !
cat /proc/version => Linux version 4.4.0-154-generic (buildd@lgw01-amd64-049) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10) ) #181-Ubuntu SMP Tue Jun 25 05:29:03 UTC 2019
andryyy
commented
4 years ago You need to install the HWE kernel. :)
Pitastic
commented
4 years ago ....I read about this some where...could you give me a hint? or is apt upgrade enough? The old kernel comes from the old (june 2019) snapshot i use...good point!
andryyy
commented
4 years ago apt-get update apt-get install --install-recommends -y linux-generic-hwe-16.04 reboot
Pitastic
commented
4 years ago In the end of the day I decided to start with a really fresh ubuntu 16, install the HWE kernel, get mailcow running and restore my data from the backup (made with a broken mailcow installation).
It's working again! :smiley: Unfortunatly we will never know if this was just a kernel but I think you were right. I did the HWE update in one of my tries but fail at another problem (mysql password e.g.).
Thanks for your quick reply - you gave me a very nice community support :+1:
andryyy
commented
4 years ago You are welcome
Please try to answer all questions. If you cannot, don't just delete it. If you completely ignore or remove the whole template, your issue is either closed or ignored, too. :( This is (not only) because we are evil. Many awesome mailcow supporters don't bother to reply to an issue, when crucial information is missing. Especially when it could have been answered by using this issue template. We need as much information as possible. Please post all logs, do not copy that one line you think may be interesting. Copy the whole bunch and remove sensible information. :) Thank you!
Prior to placing the issue, please check following: (fill out each checkbox with a
Xonce done)Description of the bug: What kind of issue have you exactly come across? Postfix is closing connections because it is unable for a smtp handshake. I figured out that the dovecot auth service failed or timed out.
Reproduction of said bug: How exactly do you reproduce the bug?
I ran into the problem after an update but I reproduced it with a fresh mailcow install:
docker volume prunedocker-compose up -ddocker-compose downdocker-compose up -dSystem information
I used to run mailcow behind a Proxy but I am now running it without a Proxy to keep it simple. I crashed my old installation by running a
chmod/chown -Raccidently in the mailcow folder :hankey: - now I try to get a fresh install running (first without my backups...). The Postfix-Logline:fatal: no SASL authentication mechanismsled me to a auth failure from dovecot.docker version)docker-compose version)Further notes:
I switched off my iptable rules with
iptables -P INPUT ALLOWandiptables -P OUTPUT ALLOWiptables -L -vn: pastebinip6tables -L -vn: pastebiniptables -L -vn -t nat: pastebinip6tables -L -vn -t nat: pastebindocker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254:151.101.65.69 ; 151.101.193.69 ; 151.101.129.69 ; 151.101.1.69docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @1.1.1.1: `151.101.193.69 ; 151.101.1.69 ; 151.101.65.69 ; 151.101.129.69General logs:
1. mailcow.conf
1. Postfix (with a request from mxtoolbox.com)
2. Dovecot
I read that there is a dovecot bug in 2.3.4 (I think) but I haven't found any problems from mailcow users so maybe that have nothing to do with it.