[opensuse] named/bind bug? multiple systems, 15.2, after reboot, named service wouldnt autostart
Hi list, already came across this oddity multiple times in recent weeks: named/bind bug? multiple systems, 15.2, after reboot, named service wouldnt autostart people at sites calling me that something doesnt work with their internet. turns out the named/bind resolver on the linux machine was not started up. the status initially within few minutes after a reboot would show e.g. sudo systemctl status named.service [sudo] password for root: ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: inactive (dead) Nov 09 00:24:41 tux systemd[1]: named.service: Job named.service/start deleted to break ordering cycle starting with nss-lookup.target/start I could then manually start up the named by sudo systemctl start named.service then showing it status as sudo systemctl status named.service ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2020-11-09 00:52:49 XYZT; 1s ago Process: 5010 ExecStart=/usr/sbin/named.init start (code=exited, status=0/SUCCESS) Main PID: 5048 (named) Tasks: 20 CGroup: /system.slice/named.service └─5048 /usr/sbin/named -t /var/lib/named -u named ..... What happen? TY. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
09.11.2020 18:59, cagsm пишет:
Hi list,
already came across this oddity multiple times in recent weeks:
named/bind bug? multiple systems, 15.2, after reboot, named service wouldnt autostart
people at sites calling me that something doesnt work with their internet. turns out the named/bind resolver on the linux machine was not started up.
the status initially within few minutes after a reboot would show e.g.
sudo systemctl status named.service [sudo] password for root: ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: inactive (dead)
Nov 09 00:24:41 tux systemd[1]: named.service: Job named.service/start deleted to break ordering cycle starting with nss-lookup.target/start
I could then manually start up the named by
sudo systemctl start named.service
then showing it status as
sudo systemctl status named.service ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2020-11-09 00:52:49 XYZT; 1s ago Process: 5010 ExecStart=/usr/sbin/named.init start (code=exited, status=0/SUCCESS) Main PID: 5048 (named) Tasks: 20 CGroup: /system.slice/named.service └─5048 /usr/sbin/named -t /var/lib/named -u named
.....
What happen?
https://forums.opensuse.org/showthread.php/545542-Systemd-nss_lookup-target-... IMHO time after DNS is redundant dependency. But someone needs to open bug report. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Nov 9, 2020 at 7:20 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
https://forums.opensuse.org/showthread.php/545542-Systemd-nss_lookup-target-... IMHO time after DNS is redundant dependency. But someone needs to open bug report.
thank you for your reply. that forum thread already hints at a freshly created bugreport at <https://bugzilla.opensuse.org/show_bug.cgi?id=1177491> will this be fixed for leap 15.2 etc? why are these kind of bugs being introduced? TY -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10.11.20 00:38, cagsm wrote:
On Mon, Nov 9, 2020 at 7:20 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
https://forums.opensuse.org/showthread.php/545542-Systemd-nss_lookup-target-... IMHO time after DNS is redundant dependency. But someone needs to open bug report.
thank you for your reply. that forum thread already hints at a freshly created bugreport at <https://bugzilla.opensuse.org/show_bug.cgi?id=1177491>
will this be fixed for leap 15.2 etc? why are these kind of bugs being introduced?
I take the blame. I was only recently tasked with maintaining the bind packages and immediately a set of CVEs were reported. Rather than go through the process of finding the patches and backporting them to the currently maintained package versions (9.11), I decided that it would be time to make a jump to the most recent version to benefit from all the recent developments and to keep in sync with upstream. In the aftermath, taking smaller jumps might have been better, but the intermediate versions were not really supported, so there you have it. When the upgrade was submitted, immediately problems started to appear in that, in some configurations (did I say "QA"?), bind would not resolve names any more and analyzing that problem took quite some time. Eventually we found that it was due to the change in the handling of DNSSEC and, in order to get things going again, QA changed their configurations and bind 9.16 was thus released. That it did carry a number of other problems, eg in the upgrade process, was only discovered afterwards and I am working on them. I do apologize for this, I should have been much more careful and I promise to be that in the future. Josef -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrei Borzenkov -
cagsm -
Josef Moellers