I think I fixed the problem. I added the RequiresMountsFor=/var to
resolvconf, deleted everything below /var on the root partition, and
changed /etc/resolvconf/update.d/bind9 to use /run/named instead of
/var/run/named (the actual reference in named.conf.options already
used /run without the /var
And for the bug report:
-- Forwarded message -
From: Ross Boylan
Date: Sun, Jul 28, 2019 at 5:11 PM
Subject: Re: Bug#933139: bind9 fails on startup: can't find /var/cache/bind
To: Bernhard Schmidt
On Sun, Jul 28, 2019 at 12:36 PM Ross Boylan
wrote:
> On Sun, Jul
Oops, forgot to cc the bug.
-- Forwarded message -
From: Ross Boylan
Date: Sun, Jul 28, 2019 at 12:36 PM
Subject: Re: Bug#933139: bind9 fails on startup: can't find /var/cache/bind
To: Bernhard Schmidt
Cc: Ross Boylan
Thank you for your response. Answers interpolated
Control: tags -1 moreinfo
Am 26.07.19 um 22:50 schrieb Ross Boylan:
Hi Ross,
> * What led up to the situation?
>
>Start or restart the system. bind9 attempts to start, but fails
>with the error that it is unable to cd to /var/cache/bind. This
>happens every time.
>
>New insta
Package: bind9
Version: 1:9.11.5.P4+dfsg-5.1
Severity: normal
Dear Maintainer,
Severity is import for me, but obviously this isn't happening to
everyone. Every time I start bind9 fails, and all the other startup
services that require working DNS end up in various semi-broken
states. I can fix th
5 matches
Mail list logo
