Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[pfoo]

As far as I can tell, we're hitting multiple issues :
- before #873957, /lib/systemd/system-generators/postfix-instance-generator 
"if" could never have matched at all but the else saved us
- after #873957, /lib/systemd/system-generators/postfix-instance-generator "if" 
started working, but using postmulti at this point seems to be a bad idea (some 
network interfaces/ip might not be up in early boot stages)
- systemd not throwing any error when manually starting postfix. This might be 
related to how debian (badly ?) designed postfix launch sequence for systemd 
(/etc/systemd/system/multi-user.target.wants/postfix.service starting /bin/true 
?)
- systemd not logging the failure of 
/lib/systemd/system-generators/postfix-instance-generator. This might be fixed 
by intercepting postmulti exit code.

Is generating postfix systemd startup files on each boot a good idea at all ? 
If you need multiple instances, you should configure them once and for all. 
Depending on a boot-time script auto-generating which instances are going to be 
started feels like a very bad idea.

Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[Jan Wagner]

Hi there,

Am 16.10.17 um 22:58 schrieb Scott Kitterman:
> I've just upgraded several systems to 9.2 (and rebooted) and am unable to 
> reproduce the problem.  For the original submitter (or anyone else who had 
> the 
> problem) do you use multi-instance postfix?  Is there anything unusual about 
> your configuration?

as described in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877992#10 I had
postfix bound with "inet_interfaces=" to a specific IP (which was not
available in early bootstage).

/lib/systemd/system-generators/postfix-instance-generator is doing a the
following:

if [ -f /etc/postfix/main.cf ]; then
for NAME in $(postmulti -l -a | awk '{ print $1}'); do
ln -s "$SERVICEFILE" "$WANTDIR/postfix@$NAME.service"
done
else
ln -s "$SERVICEFILE" "$WANTDIR/postfix@-.service"
fi

As "postmulti -l -a" failed in early bootstage in my case, it doesn't
generate the needed links.

I worked around the problem by removing the inet_interfaces-config
statement.

As every other reporter is affected at boot time, this seems the source
of the problem.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877992#20 indicates
the same and a reinstall seems to trigger generating the links.
I guess "postmulti -l -a" doesn't fail when the system is up and
running, but in early boot stage.

For everybody affected. You can try to boot into "/bin/sh" by adding
"init=/bin/sh" to your bootprompt. Be aware you will have no network in
this case.

I reproduced the issue in this case by running:

# ip link set lo up
# postmulti -l -a

Cheers, Jan.



signature.asc
Description: OpenPGP digital signature

Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[Bea]

I had the problem. I run only one instance of postfix and the configuration is 
a classic one.

Bea

Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[Kurt Roeckx]

I ran into this too. As it's explained a little in
/usr/share/doc/postfix/README.Debian, I had to run:

systemctl enable postfix@-

And then to start it:
systemctl enable postfix@-


Kurt

Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[Heiner Markert]

On Tue, 10 Oct 2017 11:38:01 +0200 m-a-...@web.de wrote:
>
> Same problem here.
>
> "apt-get install --reinstall postfix" helped to fix this problem.
>
>

Same problem here.

The fix "apt-get install --reinstall postfix" only helps partially:
1) after executing the command, postfix starts
2) however, after another reboot, postfix again does not start up and I 
need to repeat the reinstall command


This means that after each reboot, postfix will not come up 
automatically -- please fix.

Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[m-a-m-o]

Same problem here.
 
"apt-get install --reinstall postfix" helped to fix this problem.

Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[Daniel Haid]

I have the same problem:

/lib/systemd/system-generators/postfix-instance-generator

does not generate the required links on boot, but it does on reinstall.

Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[Jan Wagner]

Hi there,

Am 08.10.17 um 12:28 schrieb Thomas L.:
> yesterday I did an upgrade from Debian Stretch 9.1 to 9.2. Postfix was 
> updated. During the update, no error accured.
> After a reboot, "systemctl status postfix" showed this:
> 
> ● postfix.service - Postfix Mail Transport Agent
>Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor 
> preset: enabled)
>Active: active (exited) since Sun 2017-10-08 12:10:45 CEST; 2min 7s ago
>   Process: 485 ExecReload=/bin/true (code=exited, status=0/SUCCESS)
>   Process: 447 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
>  Main PID: 447 (code=exited, status=0/SUCCESS)
> Tasks: 0 (limit: 4915)
>Memory: 0B
>   CPU: 0
>CGroup: /system.slice/postfix.service
> 
> When I did "netstat -tulpn" no postfix processed were bound to any IP 
> addresses and htop showed me not a single postfix process. The error log 
> /var/log/mail.log was not touched.
> 
> "systemctl restart postfix" changed nothing, postfix was dead.
> 
> Only "apt-get install --reinstall postfix" helped. After re-installing 
> postfix, everything was working again. I could reproduce this problem on 4 of 
> my hosts. 

in my case the problem was having "inet_interfaces=" specified in
main.cf.
Booting with "init=/bin/sh" "postmulti -l -a" failed with:

postmulti: fatal: parameter inet_interfaces: no local interface found
for 

So /lib/systemd/system-generators/postfix-instance-generator failed to
create /run/systemd/generator/postfix.service.wants.

This seems to be a regression introduced by fixing #873957.

Cheers, Jan.
-- 
Never write mail to , you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M+ V- PS
PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y
--END GEEK CODE BLOCK--



signature.asc
Description: OpenPGP digital signature

Bug#877992: postfix: Postfix does not start services after upgrade to stretch 9.2 and reboot

[Thomas L.]

Package: postfix
Version: 3.1.6-0+deb9u1
Severity: important

Dear Maintainer,

yesterday I did an upgrade from Debian Stretch 9.1 to 9.2. Postfix was updated. 
During the update, no error accured.
After a reboot, "systemctl status postfix" showed this:

● postfix.service - Postfix Mail Transport Agent
   Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor preset: 
enabled)
   Active: active (exited) since Sun 2017-10-08 12:10:45 CEST; 2min 7s ago
  Process: 485 ExecReload=/bin/true (code=exited, status=0/SUCCESS)
  Process: 447 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 447 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
   Memory: 0B
  CPU: 0
   CGroup: /system.slice/postfix.service

When I did "netstat -tulpn" no postfix processed were bound to any IP addresses 
and htop showed me not a single postfix process. The error log 
/var/log/mail.log was not touched.

"systemctl restart postfix" changed nothing, postfix was dead.

Only "apt-get install --reinstall postfix" helped. After re-installing postfix, 
everything was working again. I could reproduce this problem on 4 of my hosts. 


-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postfix depends on:
ii  adduser3.115
ii  cpio   2.11+dfsg-6
ii  debconf [debconf-2.0]  1.5.61
ii  dpkg   1.18.24
ii  init-system-helpers1.48
ii  libc6  2.24-11+deb9u1
ii  libdb5.3   5.3.28-12+deb9u1
ii  libicu57   57.1-6
ii  libsasl2-2 2.1.27~101-g0780600+dfsg-3
ii  libssl1.1  1.1.0f-3
ii  lsb-base   9.20161125
ii  netbase5.4
ii  postfix-sqlite 3.1.6-0+deb9u1
ii  ssl-cert   1.0.39

Versions of packages postfix recommends:
ii  python3  3.5.3-1

Versions of packages postfix suggests:
ii  dovecot-core [dovecot-common]  1:2.2.27-3+deb9u1
ii  libsasl2-modules   2.1.27~101-g0780600+dfsg-3
ii  mailutils [mail-reader]1:3.1.1-1
pn  postfix-cdb
pn  postfix-doc
pn  postfix-ldap   
pn  postfix-lmdb   
ii  postfix-mysql  3.1.6-0+deb9u1
pn  postfix-pcre   
pn  postfix-pgsql  
pn  procmail   
ii  resolvconf 1.79
pn  sasl2-bin  
pn  ufw

-- debconf information:
  postfix/rfc1035_violation: false
* postfix/main_mailer_type: No configuration
  postfix/not_configured:
  postfix/dynamicmaps_conversion_warning:
  postfix/relayhost:
  postfix/chattr: false
  postfix/mailname: /etc/mailname
  postfix/compat_conversion_warning: true
  postfix/lmtp_retired_warning: true
  postfix/root_address:
  postfix/retry_upgrade_warning:
  postfix/procmail:
  postfix/sqlite_warning:
  postfix/mydomain_warning:
  postfix/kernel_version_warning:
  postfix/destinations:
  postfix/bad_recipient_delimiter:
  postfix/relay_restrictions_warning:
  postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
  postfix/mailbox_limit: 0
  postfix/protocols:
  postfix/recipient_delim: +
  postfix/main_cf_conversion_warning: true
  postfix/tlsmgr_upgrade_warning: