Dovecot 2.4.0 fails to start with exit code 89
I've been trying to upgrade to 2.4.0. I've gone through the conf files, changing variables per the upgrade instructions. When I try to run sudo systemctl start dovecot.service, I get error 89. Journalctl shows me the error in question is "File name too long." I think it's coming from where 10-ssl.conf looks for the certs, but I'm probably wrong. Can anyone make a suggestion?
Ken
I just recently upgraded and I can say after weeks of testing features and tinkering with configs, successfully.
My biggest advice to accelerate migration process and get past all the issues quickly, is run doveconf -n and pipe its content to dovecot.conf new file, take backup of 2.3 config in conf directory and make sure to move it outside dovecot in another directory, leave only dovecot.conf empty file and go through dovecot upgrading guidelines with all new settings tab opened and confirm each setting still exist from old config and tweak what you should accordingly.
Refer to:- https://doc.dovecot.org/main/core/summaries/settings.html
On 2025-02-09 20:33, Ken Wright via dovecot wrote:
I've been trying to upgrade to 2.4.0. I've gone through the conf files, changing variables per the upgrade instructions. When I try to run sudo systemctl start dovecot.service, I get error 89. Journalctl shows me the error in question is "File name too long." I think it's coming from where 10-ssl.conf looks for the certs, but I'm probably wrong. Can anyone make a suggestion?
Ken
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
On 09/02/2025 22:33 EET Ken Wright via dovecot <dovecot@dovecot.org> wrote: I've been trying to upgrade to 2.4.0. I've gone through the conf files, changing variables per the upgrade instructions. When I try to run sudo systemctl start dovecot.service, I get error 89. Journalctl shows me the error in question is "File name too long." I think it's coming from where 10-ssl.conf looks for the certs, but I'm probably wrong. Can anyone make a suggestion? Ken _______________________________________________ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org You probably have ssl_server_cert_file =< /foo It no longer needs the < Aki
On Sun, 2025-02-09 at 23:24 +0200, Aki Tuomi wrote:
On 09/02/2025 22:33 EET Ken Wright via dovecot <dovecot@dovecot.org> wrote:
I've been trying to upgrade to 2.4.0. I've gone through the conf
files, changing variables per the upgrade instructions. When I try to
run sudo systemctl start dovecot.service, I get error 89. Journalctl
shows me the error in question is "File name too long." I think it's
coming from where 10-ssl.conf looks for the certs, but I'm probably
wrong. Can anyone make a suggestion?
Ken
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-leave@dovecot.org
You probably have
ssl_server_cert_file =< /foo
It no longer needs the <
Aki
Yes, that was the problem! I removed the now-superfluous < signs and it started.
Thanks so much!
Ken
Hi,
I've been trying to upgrade to 2.4.0. I've gone through the conf files, changing variables per the upgrade instructions. When I try to run sudo systemctl start dovecot.service, I get error 89. Journalctl shows me the error in question is "File name too long." I think it's coming from where 10-ssl.conf looks for the certs, but I'm probably wrong. Can anyone make a suggestion?
Remove the < from the cert/key config entries, they are not needed any more.
Regards Bjoern.
participants (4)
-
Aki Tuomi
-
Bjoern Franke
-
Ken Wright
-
Zakaria