• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue named want start

solucionesuno

Regular Pleskian
Centos 7

after restart the service:

Feb 20 22:28:27 ns1 systemd: named-chroot.service: control process exited, code=exited status=1
Feb 20 22:28:27 ns1 systemd: Failed to start Berkeley Internet Name Domain (DNS).
Feb 20 22:28:27 ns1 systemd: Unit named-chroot.service entered failed state.
Feb 20 22:28:27 ns1 systemd: named-chroot.service failed.
 
rpm -qf /etc/named.conf
bind-9.9.4-38.el7_3.2.x86_64


ls -la /etc/named.conf
lrwxrwxrwx 1 root root 32 nov 29 20:15 /etc/named.conf -> /var/named/chroot/etc/named.conf
 
systemctl status named.service
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since lun 2017-02-20 23:45:26 CET; 4s ago
Process: 15720 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)
Main PID: 2126 (code=exited, status=0/SUCCESS)
 
Service "named-chroot.service" cannot be restarted but you can start it, is it right? Is this reproducible every time?

Could you check "systemctl -l status named-chroot.service" if problem repeated?
 
Last edited:
Back
Top