1. Advertising
    y u no do it?

    Advertising (learn more)

    Advertise virtually anything here, with CPM banner ads, CPM email ads and CPC contextual links. You can target relevant areas of the site and show ads based on geographical location of the user if you wish.

    Starts at just $1 per CPM or $0.10 per CPC.

nameservers failed to start on vps

Discussion in 'Site & Server Administration' started by hmk20009, Aug 16, 2017.

  1. #1
    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
     
    hmk20009, Aug 16, 2017 IP
  2. badger_

    badger_ Greenhorn

    Messages:
    52
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    20
    #2
    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]
     
    Last edited: Aug 16, 2017
    badger_, Aug 16, 2017 IP
  3. hmk20009

    hmk20009 Active Member

    Messages:
    42
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    73
    #3
    is there any other solution to my issue without removing systemd.


    i will be grateful for help
     
    hmk20009, Aug 16, 2017 IP
  4. badger_

    badger_ Greenhorn

    Messages:
    52
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    20
    #4
    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.
     
    badger_, Aug 16, 2017 IP
  5. hmk20009

    hmk20009 Active Member

    Messages:
    42
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    73
    #5
    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.
     
    hmk20009, Aug 16, 2017 IP
  6. polusweb

    polusweb Peon

    Messages:
    11
    Likes Received:
    1
    Best Answers:
    0
    Trophy Points:
    1
    #6
    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
     
    polusweb, Aug 19, 2017 IP
  7. Quarind

    Quarind Peon

    Messages:
    6
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    1
    #7
    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.
     
    Quarind, Aug 30, 2017 IP