On May 10, 2017 12:32:59 PM EDT, Bernhard Schmidt <be...@debian.org> wrote: >Am 10.05.2017 um 17:46 schrieb Scott Kitterman: > >Hi Scott, > >>> I think network-online.target is unnecessary, as I'm not aware of >any >>> common postfix configurations that actually need network access to >>> startup. At least the common case of postfix or SQL the connection >is >> >> If you specify an IP address in inet_interfaces, postfix will fail to >start >> withhout the override to depend on network-online.target. We can >quibble >> about if that qualifies a common or not, but we got bug reports [1], >so it's >> common enough in my opinion. >> >> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844277 > >Has anyone ever confirmed that this setting on postfix.service actually >fixes this issue? I see no communication in the bug about it, and to my >understanding adding _anything_ on postfix.service won't make a >difference (since the only dependencies relevant for startup are on >postfix@.service). > >With ifupdown and resolvconf, and your override in place, I can still >reproduce Bug#844277 (it is easier to trigger by adding > > pre-up /bin/sleep 5 > >to /etc/network/interfaces) > >May 10 18:26:22 voip20 postmulti[638]: fatal: parameter >inet_interfaces: >no local interface found for xx.xx.xx.xx >May 10 18:26:23 voip20 systemd[1]: postfix@-.service: Control process >exited, code=exited status=1 >May 10 18:26:23 voip20 systemd[1]: Failed to start Postfix Mail >Transport Agent (instance -). >May 10 18:26:23 voip20 systemd[1]: postfix@-.service: Unit entered >failed state. >May 10 18:26:23 voip20 systemd[1]: postfix@-.service: Failed with >result >'exit-code'. >May 10 18:26:27 voip20 kernel: [ 7.787458] vmxnet3 0000:0b:00.0 >eth0: >intr type 3, mode 0, 2 vectors allocated >May 10 18:26:27 voip20 kernel: [ 7.787725] vmxnet3 0000:0b:00.0 >eth0: >NIC Link is Up 10000 Mbps >May 10 18:26:29 voip20 systemd[1]: Started Raise network interfaces. > > >Adding the After=postfix.service into postfix@.service fixes this issue >for good (because postfix@.service <- postfix.service <- network.target ><- networking.service) > >NM is a completely different beast, I think you may need to be >After=network-online.target here. But static IP with NetworkManager, >and >having postfix bind to it, should really be seldom enough. > >Bernhard
I recall doing tests. It's possible I got it wrong. I am still trying to figure out the 'simpler' world of systemd. Scott K
