[Bug 1185794] New: named fails to start
https://bugzilla.suse.com/show_bug.cgi?id=1185794 Bug ID: 1185794 Summary: named fails to start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: robert.koktan@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Updated Tumbleweed this morning to 20210505, bind-9.16.12-2.1.x86_64, now it fails to start, and what's really weird is it's trying to start from /etc/systemd/system/ instead of /usr/lib/systemd/system/... # systemctl status named.service ��� named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/etc/systemd/system/named.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2021-05-07 13:56:31 EDT; 5min ago CPU: 783us May 07 13:56:31 rkoktan-w541 systemd[1]: Starting Berkeley Internet Name Domain (DNS)... May 07 13:56:31 rkoktan-w541 systemd[1210]: named.service: Failed to execute command: No such file or directory May 07 13:56:31 rkoktan-w541 systemd[1210]: named.service: Failed at step EXEC spawning /usr/sbin/named.init: No such file or directory May 07 13:56:31 rkoktan-w541 systemd[1]: named.service: Control process exited, code=exited, status=203/EXEC May 07 13:56:31 rkoktan-w541 systemd[1]: named.service: Failed with result 'exit-code'. May 07 13:56:31 rkoktan-w541 systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 Robert Koktan <robert.koktan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Found By|--- |Field Engineer -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 https://bugzilla.suse.com/show_bug.cgi?id=1185794#c1 --- Comment #1 from Robert Koktan <robert.koktan@suse.com> --- Updated Tumbleweed just now to 20210506, same version of bind-9.16.12-2.1.x86_64, and it still fails to start, still trying to start from /etc/systemd/system/ instead of /usr/lib/systemd/system/, but slightly different error message... # systemctl status named.service ��� named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/etc/systemd/system/named.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2021-05-07 15:24:11 EDT; 1min 0s ago Process: 1078 ExecStart=/usr/sbin/named.init start (code=exited, status=6) CPU: 55ms May 07 15:24:11 rkoktan-w541 systemd[1]: Starting Berkeley Internet Name Domain (DNS)... May 07 15:24:11 rkoktan-w541 named.init[1078]: Starting name server BIND May 07 15:24:11 rkoktan-w541 named.init[1144]: /etc/named.conf:21: change directory to '/var/lib/named' failed: file not found May 07 15:24:11 rkoktan-w541 named.init[1144]: /etc/named.conf:21: parsing failed: file not found May 07 15:24:11 rkoktan-w541 systemd[1]: named.service: Control process exited, code=exited, status=6/NOTCONFIGURED May 07 15:24:11 rkoktan-w541 systemd[1]: named.service: Failed with result 'exit-code'. May 07 15:24:11 rkoktan-w541 systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 https://bugzilla.suse.com/show_bug.cgi?id=1185794#c2 --- Comment #2 from Robert Koktan <robert.koktan@suse.com> --- I just rolled back using snapper to Tumbleweed 20210425, bind-9.16.12-1.1.x86_64, and named starts and runs no problem now... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |josef.moellers@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 https://bugzilla.suse.com/show_bug.cgi?id=1185794#c3 Josef M�llers <josef.moellers@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robert.koktan@suse.com Flags| |needinfo?(robert.koktan@sus | |e.com) --- Comment #3 from Josef M�llers <josef.moellers@suse.com> --- I seem to have problems reproducing the issue: 1) my named.service does reside in # rpm -ql bind | fgrep named.service /usr/lib/systemd/system/named.service 2) the path /var/lib/named is created in /usr/libexec/bind/named.prep so I'm unsure hy it does not exist. Maybe the named.service in /etc/systemd/system is somehow a relic? a) Can you please check if /usr/lib/systemd/system/named.service exists? b) Who owns /etc/systemd/system/named.service ("rpm -qf /etc/systemd/system/named.service") c) Does named start if you remove the entry in /etc/systemd/system? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 https://bugzilla.suse.com/show_bug.cgi?id=1185794#c4 Josef M��llers <josef.moellers@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #4 from Josef M��llers <josef.moellers@suse.com> --- Oh ... btw ... After a "zypper dup": # systemctl start named # systemctl status named ��� named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled) Active: active (running) since Mon 2021-05-10 09:46:40 CEST; 4s ago Process: 1324 ExecStartPre=/usr/libexec/bind/named.prep (code=exited, status=0/SUCCESS) Process: 1326 ExecStart=/usr/sbin/named -u named $NAMED_ARGS (code=exited, status=0/SUCCESS) Main PID: 1327 (named) Tasks: 5 (limit: 2337) CPU: 104ms CGroup: /system.slice/named.service ������1327 /usr/sbin/named -u named : So, in my TW system, it starts perfectly OK. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 https://bugzilla.suse.com/show_bug.cgi?id=1185794#c5 Robert Koktan <robert.koktan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |NEW --- Comment #5 from Robert Koktan <robert.koktan@suse.com> --- I had to roll back to Tumbleweed 20210425, bind-9.16.12-1.1.x86_64, and named starts and runs no problem now... will zypper dup today and report if named goes wonky again. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 https://bugzilla.suse.com/show_bug.cgi?id=1185794#c6 Robert Koktan <robert.koktan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(robert.koktan@sus | |e.com) | --- Comment #6 from Robert Koktan <robert.koktan@suse.com> --- Back up to Tumbleweed 20210507, bind-9.16.12-2.1.x86_64, and named fails... # systemctl status named.service ��� named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/etc/systemd/system/named.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2021-05-10 09:09:46 EDT; 3min 4s ago Process: 950 ExecStart=/usr/sbin/named.init start (code=exited, status=203/EXEC) CPU: 889us May 10 09:09:46 rkoktan-w541 systemd[1]: Starting Berkeley Internet Name Domain (DNS)... May 10 09:09:46 rkoktan-w541 systemd[950]: named.service: Failed to execute command: No such file or directory May 10 09:09:46 rkoktan-w541 systemd[950]: named.service: Failed at step EXEC spawning /usr/sbin/named.init: No such file or directory May 10 09:09:46 rkoktan-w541 systemd[1]: named.service: Control process exited, code=exited, status=203/EXEC May 10 09:09:46 rkoktan-w541 systemd[1]: named.service: Failed with result 'exit-code'. May 10 09:09:46 rkoktan-w541 systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). However, if your suspicions are correct... a) # ll /usr/lib/systemd/system/named.service -rw-r--r-- 1 root root 659 May 2 14:10 /usr/lib/systemd/system/named.service b) # rpm -qf /etc/systemd/system/named.service file /etc/systemd/system/named.service is not owned by any package c) # mv /etc/systemd/system/named.service /etc/systemd/system/named.service.bak # systemctl daemon-reload # 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 2021-05-10 09:17:12 EDT; 6s ago Process: 6974 ExecStartPre=/usr/libexec/bind/named.prep (code=exited, status=0/SUCCESS) Process: 6982 ExecStart=/usr/sbin/named -u named $NAMED_ARGS (code=exited, status=0/SUCCESS) Main PID: 6983 (named) Tasks: 26 (limit: 4915) CPU: 130ms CGroup: /system.slice/named.service ������6983 /usr/sbin/named -u named May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53 May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: network unreachable resolving './NS/IN': 2001:500:9f::42#53 May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53 May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: network unreachable resolving './NS/IN': 2001:500:2::c#53 May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53 May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: network unreachable resolving './NS/IN': 2001:500:2d::d#53 May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53 May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: network unreachable resolving './NS/IN': 2001:500:2f::f#53 May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: managed-keys-zone: Key 20326 for zone . is now trusted (acceptance timer complete) May 10 09:17:12 rkoktan-w541.livingsky.ca named[6983]: resolver priming query complete ... and ... # rpm -qf /usr/lib/systemd/system/named.service bind-9.16.12-2.1.x86_64 ... so... looks like I must have done something between 0425 and 0507, though I cannot think of what , but I'd hazard a guess this is not a bug, but a Rob. Thanks for the assist! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 https://bugzilla.suse.com/show_bug.cgi?id=1185794#c7 Josef M�llers <josef.moellers@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #7 from Josef M�llers <josef.moellers@suse.com> --- Thanks, Rob! I'll close this, then. Feel free to re-open (or file a new bug) if you still have some problems. Stay healthy! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1185794 https://bugzilla.suse.com/show_bug.cgi?id=1185794#c8 --- Comment #8 from Robert Koktan <robert.koktan@suse.com> --- Just a quick followup, I cannot find in my command history how named.service got moved/created to/in /etc/systemd/system between 0427 and 0507... 719 2021-02-09 15:06:15 systemctl status named.service 763 2021-03-12 10:18:41 systemctl show named.service -p TimeoutUSec 764 2021-03-12 10:18:44 systemctl show named.service -p TimeoutSec 765 2021-03-12 10:18:59 systemctl edit --full named.service 766 2021-03-12 10:23:11 vi /etc/systemd/system/named.service 848 2021-05-07 13:42:16 systemctl status named.service 849 2021-05-07 13:42:27 systemctl stop named.service 850 2021-05-07 13:42:30 systemctl start named.service 851 2021-05-07 13:42:46 systemctl status named.service ... I'll leave it to the gremlins! Thanks Josef! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com