[MacPorts] #58844: Unbound does not start after reboot, but it does start when started by hand with port reload unbound

[MacPorts]

#58844: Unbound does not start after reboot, but it does start when started by hand
with port reload unbound
----------------------+----------------------
  Reporter:  gctwnl   |      Owner:  nerdling
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.5.4
Resolution:           |   Keywords:
      Port:  unbound  |
----------------------+----------------------

Comment (by gctwnl):

 Additional info I was able to coax some error messages from launchd:


 {{{
 2019-08-16 16:53:59 unbound: Starting process
 2019-08-16 16:53:59 unbound: Running start-cmd
 /opt/local/etc/LaunchDaemons/org.macports.unbound/unbound.wrapper start
 Aug 16 16:54:00 unbound-albus[219:0] error: can't bind socket: Can't
 assign requested address for 192.168.2.66 port 53
 Aug 16 16:54:00 unbound-albus[219:0] fatal error: could not open ports
 }}}

 by changing the Startup call in the wrapper to


 {{{
 (/opt/local/sbin/unbound-anchor -a /opt/local/etc/unbound/root.key 2>&1)
 || : && (chown unbound:unbound /opt/local/etc/unbound/root.key 2>&1) &&
 (/opt/local/sbin/unbound 2>&1)
 }}}

 (stdout is faithfully reported by launchd, stderr is a black hole)

 It seems the wrapper runs without proper authorisation (i.e. root) or the
 port has already been taken. The latter is not the case (no after boot
 anyway, during boot it is highly unlikely). Still investigating. I've
 tried with only the unbound binary start, no difference, so it's not the
 && part sof the shell statement.

-- 
Ticket URL: <https://trac.macports.org/ticket/58844#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS