daemondo fails to launch unbound daemon at boot, how to debug?

[Gerben Wierda]

I have two ports active: unbound and an (updated by me, not yet committed) nsd.

Both have a startupitem that is identical, in that it uses the wrapper.

Both should launch at boot, but unbound doesn’t while nsd does. After boot, two daemondo instances are running, one for unbound and one for nsd. But only the one for nsd has actually spawned  nsd. The daemondo service for unbound has not launched an unbound instance.

When I do port load unbound after boot, the instance doesn’t load
When I do port reload unbound, the unbound instance loads without a problem

Apart from getting to the logging of unbound to look for clues, and increasing verbosity for daemondo in the startupitem, are there otherthings within macports I can do to debug?

Gerben Wierda
Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
Architecture for Real Enterprises <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld
On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20190816/83dee500/attachment.html>