Bug#960594: systemd: services (bind9, squid) are started before their filesystems had been mounted

Michael Biebl biebl at debian.org
Tue May 19 13:58:14 BST 2020


Am 19.05.20 um 14:35 schrieb Michael Biebl:
> Am 19.05.20 um 14:05 schrieb Wladimir Mutel:
>> Michael Biebl wrote:
>>
>>> Please attach the output of a journalctl -alb output with
>>> systemd.log_level=debug enabled
>>>
>>> https://freedesktop.org/wiki/Software/systemd/Debugging/#index1h1
>>> -> If You Can Get a Shell
>>
>>     Attached, please have a look
> 
> Thanks for the log.
> It appears that some hook script is triggering the start of bind9.
> I suspect some dhclient or /etc/network/if-up.d script.
> Those hook scripts use ignore-dependencies, breaking the specified
> dependencies/orderings
> 
> Checking the package contents of bind9, I see
> bind9: /etc/network/if-down.d/bind9
> bind9: /etc/network/if-up.d/bind9
> bind9: /etc/ppp/ip-down.d/bind9
> bind9: /etc/ppp/ip-up.d/bind9

Looking more closely, this might actually be a resolvconf hook which
triggers the bind9.service reload/start.

Are you using resolvconf?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200519/77375e35/attachment-0001.sig>


More information about the Pkg-systemd-maintainers mailing list