Re: Postfix fails after upgrade from bullseye to bookworm
On Fri, 13 Jan 2023 12:00:31 -0500
Dan Ritter <dsr@randomstring.org> wrote:
> Run the postfix executable by hand as root, and look for error
> messages and log entries in /var/log/mail.log among other locations.
Well, that was interesting. Thanks.
In mail.log I found the following from an earlier run:
2023-01-13T06:00:11.188254-07:00 white postfix/postfix-script[3068]: warning: /var/spool/postfix/etc/localtime and /etc/localtime differ
2023-01-13T06:00:11.303294-07:00 white postfix/postfix-script[3073]: warning: /var/spool/postfix/lib/i386-linux-gnu/libnss_systemd.so.2 and /lib/i386-linux-gnu/libnss_systemd.so.2 differ
2023-01-13T06:00:11.479941-07:00 white postfix/postfix-script[3080]: warning: /var/spool/postfix/lib/i386-linux-gnu/libgcc_s.so.1 and /lib/i386-linux-gnu/libgcc_s.so.1 differ
(I've pasted these in unwrapped, but they may get mangled in transit or
by your mail reader.)
The message isn't quite correct: the three files under /var/spool/…
were missing. I copied the originals into place.
From a run just now:
root@white:~# postfix start
postfix: Postfix is using backwards-compatible default settings
postfix: See http://www.postfix.org/COMPATIBILITY_README.html for details
postfix: To disable backwards compatibility use "postconf compatibility_level=3.6" and "postfix reload"
postfix/postfix-script: starting the Postfix mail system
root@white:~#
and ps indicates a slew of postfix jobs running, and a whole bunch of
test emails were delivered. That suggests there's something wrong with
the way systemd is starting postfix. I will look into that later today.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: