Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

named failed, already fixed?

Discussion in 'General Discussion' started by cz1179, Jan 5, 2005.

  1. cz1179

    cz1179 BANNED

    Joined:
    Dec 27, 2004
    Messages:
    105
    Likes Received:
    0
    Trophy Points:
    166
    Fresh new Centos server, starting nameserver gave the results below (failed)

    named has failed, please contact the sysadmin (result was "named is not running").
    Jan 5 17:25:18 server2 named[20576]: starting BIND 9.2.4rc6 -u named
    Jan 5 17:25:18 server2 named[20576]: using 4 CPUs
    Jan 5 17:25:18 server2 named[20576]: loading configuration from '/etc/named.conf'
    Jan 5 17:25:18 server2 named[20576]: no IPv6 interfaces found
    Jan 5 17:25:18 server2 named[20576]: listening on IPv4 interface lo, 127.0.0.1#53
    Jan 5 17:25:18 server2 named[20576]: listening on IPv4 interface eth1, xx.x.179.254#53
    Jan 5 17:25:18 server2 named[20576]: could not configure root hints from '/etc/namedb/named.ca': file not found
    Jan 5 17:25:18 server2 named[20576]: loading configuration: file not found
    Jan 5 17:25:18 server2 named[20576]: exiting (due to fatal error)
    Jan 5 17:25:18 server2 named[20590]: starting BIND 9.2.4rc6 -u named
    Jan 5 17:25:18 server2 named[20590]: using 4 CPUs
    Jan 5 17:25:18 server2 named[20590]: loading configuration from '/etc/named.conf'
    Jan 5 17:25:18 server2 named: named startup succeeded
    Jan 5 17:25:18 server2 named[20590]: no IPv6 interfaces found
    Jan 5 17:25:18 server2 named[20590]: listening on IPv4 interface lo, 127.0.0.1#53
    Jan 5 17:25:18 server2 named[20590]: listening on IPv4 interface eth1, xx.x.179.254#53
    Jan 5 17:25:18 server2 named[20590]: could not configure root hints from '/etc/namedb/named.ca': file not found
    Jan 5 17:25:18 server2 named[20590]: loading configuration: file not found
    Jan 5 17:25:18 server2 named[20590]: exiting (due to fatal error)


    I ran:
    /scripts/fixndc (says named already fixed)
    Checked for the "-" in rndckey in rndc.conf and named.conf - both already without dash
    /scripts/fixnamed
    /scripts/upcp --force

    How do I correct this?
     
  2. dalem

    dalem Well-Known Member
    PartnerNOC

    Joined:
    Oct 24, 2003
    Messages:
    2,693
    Likes Received:
    71
    Trophy Points:
    203
    Location:
    SLC
    cPanel Access Level:
    DataCenter Provider
    you most likely do not have Yum installed or the key is not installed if so you should have got errors with you upcp as well
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    #2 dalem, Jan 5, 2005
    Last edited: Jan 5, 2005
  3. cz1179

    cz1179 BANNED

    Joined:
    Dec 27, 2004
    Messages:
    105
    Likes Received:
    0
    Trophy Points:
    166
    The dc decided to fix this one :) thanks though
     
  4. aykfounder

    aykfounder Well-Known Member

    Joined:
    Feb 22, 2004
    Messages:
    102
    Likes Received:
    0
    Trophy Points:
    166
    Hey, any idea how they fixed the problem? I am having the same one.

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. aykfounder

    aykfounder Well-Known Member

    Joined:
    Feb 22, 2004
    Messages:
    102
    Likes Received:
    0
    Trophy Points:
    166
    NVM, fixed it. For anyone else who's having the same problem. I just did /scripts/upcp --force then ran /scripts/fixndc and it worked.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice