On Wed, 7 Feb 2018 15:11:15 +0100 Bastian Blank <wa...@debian.org> wrote: > Control: reopen -1 > Control: found -1 3.2.5-1 > > On Fri, Dec 15, 2017 at 06:24:06AM +0000, Debian Bug Tracking System wrote: > > * Rewrite debian/postfix-instance-generator to avoid use of postmulti > > to fix failures when inet_interfaces != all Closes: #882141 > > It now uses postconf -h multi_instance_directories. Why do you think > this would work better? > > | # postconf -h multi_instance_directories > | postconf: fatal: parameter inet_interfaces: no local interface found for 1.2.3.4
Because I don't get that error when I try to replicate the condition. $ systemctl status postfix@-.service ● postfix@-.service - Postfix Mail Transport Agent (instance -) Loaded: loaded (/lib/systemd/system/postfix@.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2018-02-09 01:28:59 EST; 17s ago Docs: man:postfix(1) Process: 3710 ExecStop=/usr/sbin/postmulti -i - -p stop (code=exited, status=0/SUCCESS) Process: 3783 ExecStart=/usr/sbin/postmulti -i - -p start (code=exited, status=1/FAILURE) Process: 3728 ExecStartPre=/usr/lib/postfix/configure-instance.sh - (code=exited, status=0/SUCCESS) Feb 09 01:28:57 relay02 systemd[1]: Starting Postfix Mail Transport Agent (instance -)... Feb 09 01:28:58 relay02 postmulti[3783]: fatal: parameter inet_interfaces: no local interface found for 1.2.3.4 Feb 09 01:28:59 relay02 systemd[1]: postfix@-.service: Control process exited, code=exited status=1 Feb 09 01:28:59 relay02 systemd[1]: Failed to start Postfix Mail Transport Agent (instance -). Feb 09 01:28:59 relay02 systemd[1]: postfix@-.service: Unit entered failed state. Feb 09 01:28:59 relay02 systemd[1]: postfix@-.service: Failed with result 'exit-code'. postconf multi_instance_directories multi_instance_directories = Not sure how to replicate the error you're having. Scott K