[Bug 1649453] Re: systemd starts postfix before resolver

[Scott Kitterman]

On Tuesday, January 03, 2017 12:34:12 AM you wrote:
> Any idea when the fix will appear in updates for yakkety?

We plan on an upload to Debian in the next day or two.  It'll follow into 
Ubuntu shortly there after.  A Yakkety SRU is work for someone involved in 
Ubuntu to do, so no.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1649453

Title:
  systemd starts postfix before resolver

Status in postfix package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New

Bug description:
  Postfix starts before systemd-resolved.service, resulting in postfix
  reporting that it can't find MX records for outgoing mail, as shown in
  the trace below:

  $ systemd-analyze critical-chain postfix.service systemd-resolved.service
  The time after the unit is active or started is printed after the "@" character.
  The time the unit takes to start is printed after the "+" character.

  postfix.service +1ms
  └─network.target @5.811s
    └─NetworkManager.service @5.690s +91ms
      └─dbus.service @5.627s
        └─basic.target @5.597s
          └─sockets.target @5.597s
            └─snapd.socket @5.597s +269us
              └─sysinit.target @5.596s
                └─systemd-timesyncd.service @5.420s +175ms
                  └─systemd-tmpfiles-setup.service @5.408s +8ms
                    └─local-fs.target @5.390s
                      └─zfs-mount.service @3.879s +1.511s
                        └─zfs-import-cache.service @2.539s +1.303s
                          └─systemd-udev-settle.service @256ms +2.252s
                            └─systemd-udev-trigger.service @208ms +47ms
                              └─systemd-udevd-control.socket @148ms
                                └─-.mount @122ms
                                  └─system.slice @124ms
                                    └─-.slice @122ms
  systemd-resolved.service +268ms
  └─network.target @5.811s
    └─NetworkManager.service @5.690s +91ms
      └─dbus.service @5.627s
        └─basic.target @5.597s
          └─sockets.target @5.597s
            └─snapd.socket @5.597s +269us
              └─sysinit.target @5.596s
                └─systemd-timesyncd.service @5.420s +175ms
                  └─systemd-tmpfiles-setup.service @5.408s +8ms
                    └─local-fs.target @5.390s
                      └─zfs-mount.service @3.879s +1.511s
                        └─zfs-import-cache.service @2.539s +1.303s
                          └─systemd-udev-settle.service @256ms +2.252s
                            └─systemd-udev-trigger.service @208ms +47ms
                              └─systemd-udevd-control.socket @148ms
                                └─-.mount @122ms
                                  └─system.slice @124ms
                                    └─-.slice @122ms

  The postfix service needs to start after systemd-resolved.service.

  $ lsb_release -rd
  Description:	Ubuntu 16.10
  Release:	16.10

  $ apt-cache policy systemd
  systemd:
    Installed: 231-9ubuntu1
    Candidate: 231-9ubuntu1
    Version table:
   *** 231-9ubuntu1 500
          500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       231-9git1 500
          500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 Packages

  $ apt-cache policy postfix
  postfix:
    Installed: 3.1.0-5
    Candidate: 3.1.0-5
    Version table:
   *** 3.1.0-5 500
          500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 Packages
          100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1649453/+subscriptions