A while ago, named would not start any more after I rebooted my Tumbleweed systems.
I had this behaviour on multiple systems, each installed quite a while ago and kept up-to-date with zypper dist-upgrade so it looked like a systematic issue.
Below are steps in researching the problem together with the helpful people on the IRC channel opensuse-factory.
Background reading for some of the commands: [WayBack] How To Use Systemctl to Manage Systemd Services and Units | DigitalOcean.
Both systemctl status named.service and systemctl status named would show the same output:
# systemctl status named
● named.service - LSB: Domain Name System (DNS) server, named
Loaded: loaded (/etc/init.d/named; generated; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
Getting the log from events around a reboot would show a successful shutdown, but no start:
# journalctl --unit named --catalog --pager-endApr 28 13:19:27 laurel systemd[1]: Stopping LSB: Domain Name System (DNS) server, named... -- Subject: Unit named.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named.service has begun shutting down. Apr 28 13:19:28 laurel named[20360]: no longer listening on 192.168.124.27#53 Apr 28 13:19:28 laurel named[20360]: no longer listening on 192.168.124.27#53 Apr 28 13:19:32 laurel named[20360]: received control channel command 'stop' Apr 28 13:19:32 laurel named[20360]: shutting down: flushing changes Apr 28 13:19:32 laurel named[20360]: stopping command channel on 127.0.0.1#953 Apr 28 13:19:32 laurel named[20360]: no longer listening on ::#53 Apr 28 13:19:32 laurel named[20360]: no longer listening on ::#53 Apr 28 13:19:32 laurel named[20360]: no longer listening on 127.0.0.1#53 Apr 28 13:19:32 laurel named[20360]: no longer listening on 127.0.0.1#53 Apr 28 13:19:32 laurel named[20360]: exiting Apr 28 13:19:34 laurel named[30705]: Shutting down name server BIND waiting for named to shut down ..done Apr 28 13:19:34 laurel systemd[1]: Stopped LSB: Domain Name System (DNS) server, named. -- Subject: Unit named.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named.service has finished shutting down.
Similar results in these files:
/var/lib/named/log/general.log
28-Apr-2017 13:19:32.465 general: shutting down: flushing changes
28-Apr-2017 13:19:32.468 general: stopping command channel on 127.0.0.1#953
28-Apr-2017 13:19:32.622 general: exiting
/var/lib/named/log/named.log
28-Apr-2017 13:19:32.489 network: no longer listening on ::#53
28-Apr-2017 13:19:32.489 network: no longer listening on 127.0.0.1#53
With systemctl, I got this:
# systemctl is-enabled named named.service is not a native service, redirecting to systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install is-enabled named enabled # systemctl is-active named inactive # systemctl is-failed named inactive
After this, I was out of systemd and sysv knowledge, so I asked for help on the #openSUSE-factory IRC channel, where ismail was of great help.
In this article, we will explain you how to restrict a SSH user access to a specific directory using chrooted jail in Linux systems.
The Wiert Corner - irregular stream of stuff 