Greetings!
I am experiencing a problem with bind not reloading properly on one of our servers. On an identical server, it is working as it should, but it has some strange issues as well. I can't figure out why they are different, or why one of them is failing to reload bind. Both servers have been set up using Ansible (automation), so they should be exactly the same.
The first issue is the reload problem on web32. The error in the log is:
And sure enough, when checking the status for named.service, this is the output on web32:
While on web33, where everything works as expected, the output is different:
If I check the status of bind9.service on the two servers, they show this for Web32:
And web33:
Both servers have /etc/init.d/bind9 and /etc/systemd/system/named.service and they are identical.
Looking at the processlist on each server, I see two named processes running, which I find strange. In addition, the two servers are different in that regards as well:
Web32:
Web33:
The servers are both running Debian 9(.8), Linux 4.9.0-5-amd64 x86_64, with Directadmin 1.56:
So I guess my three questions are:
1 - Why do one of my servers have an inactive named.service? A reload of bind9.service works as expected.
2 - Why do I have two named processes running in the first place?
3 - How do I resolve 1 and 2?
This is confusing me bigtime. Any help appreciated!
I am experiencing a problem with bind not reloading properly on one of our servers. On an identical server, it is working as it should, but it has some strange issues as well. I can't figure out why they are different, or why one of them is failing to reload bind. Both servers have been set up using Ansible (automation), so they should be exactly the same.
The first issue is the reload problem on web32. The error in the log is:
Code:
Apr 4 11:26:01 web32 systemd[1]: named.service: Unit cannot be reloaded because it is inactive.
And sure enough, when checking the status for named.service, this is the output on web32:
Code:
# systemctl status named.service
● named.service - BIND Domain Name Server
Loaded: loaded (/etc/systemd/system/named.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2019-03-25 14:29:29 CET; 1 weeks 2 days ago
Docs: man:named(8)
Main PID: 4241 (code=exited, status=0/SUCCESS)
Apr 03 12:37:02 web32 systemd[1]: named.service: Unit cannot be reloaded because it is inactive.
While on web33, where everything works as expected, the output is different:
Code:
# systemctl status named.service
● named.service - BIND Domain Name Server
Loaded: loaded (/etc/systemd/system/named.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-04-02 17:02:25 CEST; 1 day 18h ago
Docs: man:named(8)
Main PID: 18657 (named)
Tasks: 7 (limit: 4915)
CGroup: /system.slice/named.service
└─18657 /usr/sbin/named -f -u bind
Apr 04 09:40:25 web33 rndc[24184]: server reload successful
If I check the status of bind9.service on the two servers, they show this for Web32:
Code:
# systemctl status bind9.service
● bind9.service - LSB: Start and stop bind9
Loaded: loaded (/etc/init.d/bind9; generated; vendor preset: enabled)
Active: active (running) since Thu 2019-04-04 10:05:57 CEST; 1h 50min ago
Docs: man:systemd-sysv-generator(8)
CGroup: /system.slice/bind9.service
└─12475 /usr/sbin/named -u bind
And web33:
Code:
# systemctl status bind9.service
● bind9.service - LSB: Start and stop bind9
Loaded: loaded (/etc/init.d/bind9; generated; vendor preset: enabled)
Active: active (running) since Thu 2019-04-04 10:08:35 CEST; 1h 48min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 7 (limit: 4915)
CGroup: /system.slice/bind9.service
└─26631 /usr/sbin/named -u bind
Both servers have /etc/init.d/bind9 and /etc/systemd/system/named.service and they are identical.
Looking at the processlist on each server, I see two named processes running, which I find strange. In addition, the two servers are different in that regards as well:
Web32:
Code:
# ps auxfww | grep name[d]
root 21444 0.0 0.2 389260 21364 ? Ssl Mar21 0:12 named
bind 12475 0.0 0.3 411260 26788 ? Ssl 10:05 0:01 /usr/sbin/named -u bind
Web33:
Code:
# ps auxfww | grep name[d]
bind 18657 0.0 0.3 411000 26332 ? Ssl Apr02 0:09 /usr/sbin/named -f -u bind
bind 26631 0.0 0.3 407620 29176 ? Ssl 10:08 0:00 /usr/sbin/named -u bind
The servers are both running Debian 9(.8), Linux 4.9.0-5-amd64 x86_64, with Directadmin 1.56:
Code:
# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.8 (stretch)
Release: 9.8
Codename: stretch
# uname -srm
Linux 4.9.0-5-amd64 x86_64
# /usr/local/directadmin/directadmin o
Compiled on 'Debian 9.0 64-bit'
Compile time: Mar 18 2019 at 02:18:53
Timestamp: '1552897108'
Compiled with IPv6
# /usr/local/directadmin/directadmin v
Version: DirectAdmin v.1.56.0
So I guess my three questions are:
1 - Why do one of my servers have an inactive named.service? A reload of bind9.service works as expected.
2 - Why do I have two named processes running in the first place?
3 - How do I resolve 1 and 2?
This is confusing me bigtime. Any help appreciated!