Folks, here: https://gitlab.isc.org/isc-
projects/bind9/-/merge_requests/5514
(I haven't tested it yet, but you can follow the progress there...)
It will most probably make it into 9.18.0 (in December 2021).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I know this one is closed, but as a follow up to Aristarkh's last
comment, it seems this is getting some upstream attention, thanks to
Ondřej :)
https://gitlab.isc.org/isc-projects/bind9/-/issues/1176
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Athos, many thanks for taking care of this issue. I hope that BIND
developers would pick up the sd_notify() proposal to make the fix for
the issue even better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package bind9 - 1:9.16.8-1ubuntu3.2
---
bind9 (1:9.16.8-1ubuntu3.2) impish; urgency=medium
* d/bind9.named.service: use systemd Type=forking to signal daemon init. This
fixes a regression of #900788 where services whose startup depend on name
Although the proposed patch addresses this bug request, there is still a
race condition that may result in having a service that should start
"After=" nss-lookup.target to fail resolving names during start-up and,
consequently, failing to start.
This should be dealt with upstream, and in fact,
Using a long zone file and limiting the resources of the system I was
using to test these changes (just limiting lxc CPU cycles) I found a set
up where I can constantly hit the issue.
As Andreas pointed out, we are seeing a race condition here.
After forking, bind9 signals that it is ready by
Thanks for the reply, Andreas and Dan.
Dan, that is what the patch in the linked MP is doing (set the type to
forking and removing the -f option from the named binary) and that is
where I am observing the described behavior (but just in impish, where
there is an ExecStartPre for the nginx unit).
> Do you have any idea for the described behavior with nginx then
I looked in hirsute, so not sure if things are different upstream, but
in that release the named.service is:
[Service]
EnvironmentFile=-/etc/default/named
ExecStart=/usr/sbin/named -f $OPTIONS
ExecReload=/usr/sbin/rndc reload
I think you are seeing races, that's all. The result can go either way.
I worry the dep8 test might be flaky.
I initially thought that switching to Type=forking would make things
even worse, but apparently that's not the case. Now we even get config
errors reported in the "systemctl start bind9",
Thanks, Dan!
Do you have any idea for the described behavior with nginx then? I could
only observe that when the ExecStartPre= is present, and right after
reboots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> un-commenting the Wants bit does the trick and get everything to start
in the expected order.
> Is this just the expected systemd behaviour
yes.
After= only causes the service to start after the requested unit(s) when
part of a single "transaction", like bootup (i.e. when the transaction
is
I filed an MP for impish and and MR for Debian at
https://salsa.debian.org/dns-team/bind9/-/merge_requests/17 with the
missing commit and a regression autopkgtest test case.
I will start working on SRUs after I get reviews on those.
Note that there may be an issue with testing the changes using
** Merge proposal linked:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/bind9/+git/bind9/+merge/404397
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899902
Title:
systemd unit
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899902
Title:
systemd unit service file does not wait for
** Changed in: bind9 (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899902
Title:
systemd unit service file does not wait for bind9 to be ready
To
https://salsa.debian.org/dns-
team/bind9/-/commit/40fd1691a9b07c36573373eb872139b4e836b722 is the
missing commit, both in ubuntu and current debian sid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After consulting with Andreas it seems on the switch between 9.11 ->
9.16 a few things got lost in Debian as that was branched earlier - [1]
is an effort to bring some back. This might be one more of them.
Subscribing the team to take a deeper look.
[1]:
Thank you for the report Aristarkh.
It is odd that this was fixed so long ago - 1:9.11.4+dfsg-1 is what the debian
bug states.
That was only pushed to Debian buster in:
195 bind9 (1:9.11.4+dfsg-1) unstable; urgency=medium
196
** Bug watch added: Debian Bug tracker #900788
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900788
** Also affects: bind9 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900788
Importance: Unknown
Status: Unknown
--
You received this bug notification because
19 matches
Mail list logo
