After updating webmin from 1.998-1 to 1.999-1 (i had to redo the same today with 1.999-2), i’ve received alerts like:
→ Service monitor : BIND DNS Server uninstalled
–>The BIND DNS server version 8 or 9 does not appear to be installed on your system, or has not yet been set up properly in Webmin’s …
→ BIND version 9.11, under chroot /var/named/chroot… The primary configuration file for BIND /var/named/chroot/etc/named.conf does not exist, or is not valid. Create it?
To fix this in /etc/webmin/bind8/config
delete or comment lines starting by ‘auto_chroot’, ‘chroot’ and set ‘no_chroot’ to 0 if equal to 1
|------------------------------|-------------------------------|
| OS type and version | CentOS Linux 7.9.2009 |
| Webmin version | webmin-1.999-2.noarch |
Hmm, perhaps this is related to the issues I had with BIND. BIND stopped working three days ago and it caused my Virtualmin backups to fail. I ended up fixing things but I got lucky.
We’re trying to figure it out. It doesn’t happen on our test systems, at least so far. So, we’re still trying to reproduce it. It’s apparently happening to a lot of folks…so, we know something is wrong, we just can’t figure out what.
For those it happened – can you please share Webmin Bind config before the breakage? From a backup, for example? The file in question is located at /etc/bind8/config.
And, after! We need to know if the new one is identical to the one shipped with Webmin, rather than one that’s had the tweaks the Virtualmin install performs.
After update 2 or 3 lines were modified
chroot=/var/named/chroot
auto_chroot=sh -c ‘. /etc/sysconfig/named && echo “$ROOTDIR”’
I’m not sure if “no_chroot=0” were modified in 1.999-1 or not.
in case you ask me: /etc/sysconfig/named
# BIND named process options
# ~~~~~~~~~~~~~~~~~~~~~~~~~~
#
# OPTIONS="whatever" -- These additional options will be passed to named
# at startup. Don't add -t here, enable proper
# -chroot.service unit file.
# Use of parameter -c is not supported here. Extend
# systemd named*.service instead. For more
# information please read the following KB article:
# https://access.redhat.com/articles/2986001
#
# DISABLE_ZONE_CHECKING -- By default, service file calls named-checkzone
# utility for every zone to ensure all zones are
# valid before named starts. If you set this option
# to 'yes' then service file doesn't perform those
# checks.
ulimit -HSn 4096
I looked deeper into the code and it seems that theoretically it’s possible to have new directives merged into your existing configs. Although, at the moment I see this is only possible if your actual detected OS on Webmin config is incorrect. What is the output of the following command on your systems @jmunjr@keerby@DonX ?
grep os_ /etc/webmin/config
os_version=15.9
real_os_type=CentOS Linux
os_type=redhat-linux
real_os_version=7.9.2009
Thanks for sorting this out. As I stated, my system corrected itself, I think after I made a change in the module config to how chroot was handled, and then changing back, though I am not 100% sure about that.
Yes, this issue doesn’t happen with 1.994 and it doesn’t happen with 1.999-3 (locally built). Moreover, it doesn’t happen with 1.999-2 if installed initially, however the issue pops up if you reinstall 1.999-2 using package manager like dnf reinstall webmin …
Install Virtualmin on Centos 7 After updating BIND version 9.11, BIND does not start. ERROR : Failed to start BIND : sh: /etc/rc.d/init.d/named: No such file or directory
Output of grep os_ /etc/webmin/config
os_type=redhat-linux
os_version=15.9
real_os_type=CentOS Linux
real_os_version=7.9.2009
@Ilia Please let me know how to fix the issue or when will be updating the software.