Hi, I realize this is related to Centos, but all the sudden chroot bind failed to start up with any meaningful errors.
Anyone know what might be the issue here? I have no clues on that the issue is. Paul Job for named-chroot.service failed because the control process exited with error code. See "systemctl status named-chroot.service" and "journalctl -xe" for details. [r...@ns1.frv.ma:/var/named/meganet]#systemctl status named-chroot.service -l ● named-chroot.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2022-03-15 08:46:11 EDT; 6min ago Process: 3045 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -t /var/name d/chroot -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE) Mar 15 08:46:11 ns1.frv.ma systemd[1]: named-chroot.service: control process exited, code=exited status=1 Mar 15 08:46:11 ns1.frv.ma systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). Mar 15 08:46:11 ns1.frv.ma systemd[1]: Unit named-chroot.service entered failed state. Mar 15 08:46:11 ns1.frv.ma systemd[1]: named-chroot.service failed.
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
