The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Named not restarting

Discussion in 'General Discussion' started by fdnven, Nov 22, 2013.

  1. fdnven

    fdnven Well-Known Member

    Joined:
    Feb 14, 2006
    Messages:
    109
    Likes Received:
    0
    Trophy Points:
    16
    Hi,

    Name wishes not to restart with this error in log:
    Starting named:
    Error in named configuration:
    /etc/init.d/named: line 175: /usr/sbin/named-checkconf: No such file or directory
    [FAILED]


    And indeed the file named-checkconf does not exist in /usr/sbin/.

    Thanks
    Frank
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    650
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    You may need to reinstall the Bind RPMs. However, first, please try rebuilding your /etc/named.conf file via:

    Code:
    mv /etc/named.conf /etc/named.conf.backup1
    /scripts/rebuilddnsconfig
    
    Let us know if the issue persists.

    Thank you.
     
  3. fdnven

    fdnven Well-Known Member

    Joined:
    Feb 14, 2006
    Messages:
    109
    Likes Received:
    0
    Trophy Points:
    16
    After issuing the commands:

    'Named could not be restarted, any obvious config errors should show up below this line.
    No critical problems found, will attempt to regenerate keys regardless.
    Creating rndc.conf
    rndc-confgen not located on system, please check the Bind installation at /usr/local/cpanel/scripts/fixrndc line 337."

    Thanks
    Frank
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    650
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Did you take any actions before this issue started? Try reinstalling Bind by first checking to see which Bind RPMs are installed. EX:

    Code:
    rpm -qa|grep bind
    Use the "rpm -e --nodeps package-name" command to remove the Bind RPMs and then reinstall them through YUM.

    Thank you.
     
  5. fdnven

    fdnven Well-Known Member

    Joined:
    Feb 14, 2006
    Messages:
    109
    Likes Received:
    0
    Trophy Points:
    16
    Hi,

    The only issue server had crashed (due to high load) and a FSCK was performed.

    As your commands:
    root@wja [~]# rpm -qa|grep bind
    bind-devel-9.8.2-0.17.rc1.el6_4.6.x86_64
    bind-utils-9.8.2-0.17.rc1.el6_4.6.x86_64
    bind-9.8.2-0.17.rc1.el6_4.6.x86_64
    rpcbind-0.2.0-11.el6.x86_64
    bind-libs-9.8.2-0.17.rc1.el6_4.6.x86_64

    So I need to remove and reinstall all the above?

    Thanks
    Frank
     
  6. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    650
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
  7. fdnven

    fdnven Well-Known Member

    Joined:
    Feb 14, 2006
    Messages:
    109
    Likes Received:
    0
    Trophy Points:
    16
    Remove/reinstall fixed the issue.

    Thank you very much

    Frank
     
Loading...

Share This Page