Re: Postfix fails after upgrade from bullseye to bookworm
On Fri, Jan 13, 2023 at 11:37 AM Charles Curley
<charlescurley@charlescurley.com> wrote:
>
> I upgraded an i386 machine from bullseye to bookworm. Postfix now
> refuses to run.
>
> root@white:/var/spool# systemctl start postfix@-.service
> Job for postfix@-.service failed because a timeout was exceeded.
> See "systemctl status postfix@-.service" and "journalctl -xeu postfix@-.service" for details.
> root@white:/var/spool# systemctl status postfix@-.service
> × postfix@-.service - Postfix Mail Transport Agent (instance -)
> Loaded: loaded (/lib/systemd/system/postfix@.service; enabled-runtime; preset: enabled)
> Active: failed (Result: timeout) since Fri 2023-01-13 07:55:51 MST; 17s ago
> Docs: man:postfix(1)
> Process: 5170 ExecStartPre=/usr/lib/postfix/configure-instance.sh - (code=killed, signal=TERM)
> CPU: 1min 29.456s
>
> Jan 13 07:54:21 white systemd[1]: Starting Postfix Mail Transport Agent (instance -)...
> Jan 13 07:55:51 white systemd[1]: postfix@-.service: start-pre operation timed out. Terminating.
> Jan 13 07:55:51 white systemd[1]: postfix@-.service: Control process exited, code=killed, status=15/TERM
> Jan 13 07:55:51 white systemd[1]: postfix@-.service: Failed with result 'timeout'.
> Jan 13 07:55:51 white systemd[1]: Failed to start Postfix Mail Transport Agent (instance -).
> Jan 13 07:55:51 white systemd[1]: postfix@-.service: Consumed 1min 29.456s CPU time.
> root@white:/var/spool# postconf -n
> alias_database = hash:/etc/aliases
> alias_maps = hash:/etc/aliases
> append_dot_mydomain = no
> biff = no
> compatibility_level = 3.6
> inet_interfaces = all
> inet_protocols = ipv4
> mailbox_size_limit = 0
> mydestination = white.localdomain, white.localdomain, white, localhost.localdomain, localhost
> myhostname = white.localdomain
> mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
> myorigin = /etc/mailname
> readme_directory = no
> recipient_delimiter = +
> relayhost = smtp.localdomain
> smtp_tls_CApath = /etc/ssl/certs
> smtp_tls_security_level = may
> smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
> smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
> smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
> smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
> smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
> smtpd_tls_security_level = may
> root@white:/var/spool#
You should provide the output of journalctl. That usually has the
details that are useful in diagnosing a problem.
> Does anybody read signatures any more?
>
> https://charlescurley.com
> https://charlescurley.com/blog/
I try to skip them. There's no point in wasting time on them.
Jeff
Reply to: