nameservers failed to start on vps

service named start
Redirecting to /bin/systemctl start named.service
Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.

[root@dns ~]# service named status
Redirecting to /bin/systemctl status named.service
? named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/named.service.d
+-cpanel.conf
Active: failed (Result: exit-code) since Wed 2017-08-16 08:42:08 CEST; 2min 22s ago
Process: 3199 ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, status=1/FAILURE)
Process: 3196 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf /etc/named.conf; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SUCCESS)

Aug 16 08:42:08 dns.*.eu named[3202]: automatic empty zone: view localhost_resolver: 123.100.IN-ADDR.ARPA
Aug 16 08:42:08 dns.*.eu named[3202]: automatic empty zone: view localhost_resolver: 124.100.IN-ADDR.ARPA
Aug 16 08:42:08 dns.*.eu named[3202]: automatic empty zone: view localhost_resolver: 125.100.IN-ADDR.ARPA
Aug 16 08:42:08 dns.*.eu named[3202]: automatic empty zone: view localhost_resolver: 126.100.IN-ADDR.ARPA
Aug 16 08:42:08 dns.*.eu named[3202]: automatic empty zone: view localhost_resolver: 127.100.IN-ADDR.ARPA
Aug 16 08:42:08 dns.*.eu named[3202]: automatic empty zone: view localhost_resolver: 127.IN-ADDR.ARPA
Aug 16 08:42:08 dns.*.eu systemd[1]: named.service: control process exited, code=exited status=1
Aug 16 08:42:08 dns.*.eu systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Aug 16 08:42:08 dns.*.eu systemd[1]: Unit named.service entered failed state.
Aug 16 08:42:08 dns.*.eu systemd[1]: named.service failed.


problem started after i deleted files from var/logs and var/cache for reducing hard disk size of vps and after that nameservers are not starting

 

UPDATE: Just noticed you use cPanel so removing systemd will break your server.

systemd is a royal pain in the ass and a can of worms... I recommend you to get rid of it specially since you are using a server. Here there is an explanation on how to do it although you may break the system so some experience and a recent backup is a must. http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation

I went for a more drastic solution moving from Linux to OpenBSD without looking back. The DNS is really easy to configure using NSD included in base.[/b][/b]

 

is there any other solution to my issue without removing systemd.


i will be grateful for help

 

If you search in Google "systemd[1]: named.service: control process exited, code=exited status=1" - it's important to use the quotes - there is information about this error.

 

from yesterday searching googling for solution but i didn't find any solution.
thats why opened post on this site for any help to solve issue.

 

ou should check journalctl -xe right after start is failed. Also you can start named in debug mode with such command
/usr/sbin/named -fgd3 -c /etc/named.conf

 

Try to write named log into file.
Add to named configuration:

logging {
    channel bind_log {
    file "/var/log/named/named.log";
    print-time yes;
    print-category yes;
    print-severity yes;
    };
    channel update_debug {
    file "/var/log/named/update-debug.log";
    severity debug 3;
    print-time yes;
    print-category yes;
    print-severity yes;
    };
    channel security_info {
    file "/var/log/named/security-info.log";
    severity info;
    print-time yes;
    print-category yes;
    print-severity yes;
    };
    category default { bind_log;};
    category xfer-in { bind_log;};
    category xfer-out { bind_log;};
    category update { update_debug;};
    category security { security_info;};
};

Code (markup):

And show full log.