Sorry to jump on this six-month-old bug, but it seems to be describing
exactly what's still going wrong for me. When I reboot my system running
Postfix, no mail is sent, and I get the following output when I run
"mailq":

-Queue ID-  --Size-- ----Arrival Time---- -Sender/Recipient-------
47F291B6B       511 Mon Jun 26 10:53:26  thatcher@XXXXXXXXXXXXXXXXXXXX
(Host or domain name not found. Name service error for name=mail.XXXXXXXXX 
type=MX: Host not found, try again)
                                         thatc...@truman.edu

-- 0 Kbytes in 1 Request.

I put the X's in for privacy, although I don't know that it matters if
you need to see the addresses. All runs normally if I restart Postfix
after the system has finished booting.

Here is the result from the same command run by the original submitter
of this bug:

postfix.service +11ms
└─network-online.target @28.091s
  └─NetworkManager-wait-online.service @19.357s +8.733s
    └─NetworkManager.service @17.565s +1.791s
      └─dbus.service @14.834s
        └─basic.target @14.725s
          └─sockets.target @14.725s
            └─snapd.socket @14.687s +37ms
              └─sysinit.target @14.686s
                └─apparmor.service @13.847s +839ms
                  └─local-fs.target @13.846s
                    └─run-user-121.mount @23.286s
                      └─local-fs-pre.target @4.172s
                        └─systemd-remount-fs.service @4.119s +36ms
                          └─system.slice @1.804s
                            └─-.slice @1.610s
systemd-resolved.service +680ms
└─network.target @20.229s
  └─wpa_supplicant.service @32.364s +374ms
    └─basic.target @14.725s
      └─sockets.target @14.725s
        └─snapd.socket @14.687s +37ms
          └─sysinit.target @14.686s
            └─apparmor.service @13.847s +839ms
              └─local-fs.target @13.846s
                └─run-user-121.mount @23.286s
                  └─local-fs-pre.target @4.172s
                    └─systemd-remount-fs.service @4.119s +36ms
                      └─system.slice @1.804s
                        └─-.slice @1.610s

I don't really understand everything about this output, but it looks
like Postfix is still starting before systemd-resolved.service.

This problem first showed up in Yackety, and I've been keeping on top of
updates since that point. It was certainly not resolved after January.
I've now updated to Zesty using the upgrade tool (not a fresh install),
where the behavior persists.

I did try purging and reinstalling Postscript, but that didn't help. I'm
happy to provide any other diagnostic information you might like, and
thanks for your work on this.

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

Title:
  systemd starts postfix before resolver

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to