Version: 3.9.1-6

On Mon, 18 May 2020 15:10:58 +0200 Imre Jonk <i...@imrejonk.nl> wrote:
I'm experiencing the same issue. Commenting out this line in
/etc/resolvconf/update-libc.d/postfix solved it for me:

/usr/sbin/service postfix status >/dev/null 2>&1 || exit 0

My guess is that the race condition works like this:

1. configure-instance.sh is ran through ExecStartPre before
/etc/resolv.conf has been properly set up. This copies an empty
/etc/resolv.conf to the Postfix chroot.
2. resolvconf sets up /etc/resolv.conf and runs
/etc/resolvconf/update-libc.d/postfix. This script does nothing as the
Postfix service has not been started yet.
3. The Postfix service is started through ExecStart, but still has a
broken resolv.conf file in its chroot.
This has been fixed in 3.9.1-6 finally, - the update-rc.d/postfix
script (and also new similar scripts for NetworkManager) now does
just one thing, namely, copying /etc/resolv.conf to the chroot.

Thanks,

/mjt

Reply via email to