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 issue on new installation

Discussion in 'General Discussion' started by webstyler, Sep 2, 2008.

  1. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    Hello

    On server with new WHM installation we have issue on Named:
    named (9.3.4-P1) . failed

    If we try to restart BIND:
    named has failed, please contact the sysadmin (result was "named is not running").

    :/

    any solutions / suggest ?

    Thanks
     
  2. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    With
    /scripts/fixrndc
    we get

    /etc/named.conf and /etc/named.conf.prefixrndc are identical at /scripts/cPScript/FileUtils.pm line 264
    [cPScript::FileUtils]: rcopy('/etc/named.conf', '/etc/named.conf.prefixrndc') failed: Inappropriate ioctl for device
    /etc/named.conf.fixrndc and /etc/named.conf are identical at /scripts/cPScript/FileUtils.pm line 264
    [cPScript::FileUtils]: rcopy('/etc/named.conf.fixrndc', '/etc/named.conf') failed: Inappropriate ioctl for device
     
  3. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,460
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Sounds like you have (or had) bind-chroot installed. cPanel does not support bind-chroot at this time. You'll need to force a re-install of bind-chroot, then remove it to resolve the above errors.
     
  4. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    Hello cpanelkenneth

    ok, can you help for how to make this ?

    Thanks
     
  5. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    I have found this procedure

    It's ok ?

    Code:
    /scripts/updatenow
    /scripts/upcp --force
    mv /etc/named.conf /etc/named.old
    /scripts/rebuildnamedconf > /etc/named.conf
    service named stop
    killall -9 named
    /scripts/fixndc
    /scripts/fixndc
    
    yum remove bind-chroot;touch /etc/named.conf;/scripts/fixndc
     
  6. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,460
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    The above is over kill.

    Use the Configuration File Rollback function in WHM to restore /etc/named.conf. Only if the that function fails should you use /scripts/rebuildnamedconf.

    After restoring /etc/named.conf, verify the settings in /etc/sysconfig/named. Specifically, the ROOTDIR entry should be commented out, like this:

    Code:
    #ROOTDIR=/var/named/chroot
    
    If it is not commented out, then do so.

    Check the Zone files in /var/named. They might be symlinks (this indicates bind-chroot was indeed installed). Whether the Zone files exist as symlinks is irrelevant as long as they exist (broken symlinks need fixed).

    Once the above is verified, restart BIND:

    /etc/init.d/named stop
    /etc/init.d/named start
     
  7. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    We have made this step:

    1.restore named.conf as you write > ok
    2.verify the settings in /etc/sysconfig/named:

    # BIND named process options
    # ~~~~~~~~~~~~~~~~~~~~~~~~~~
    # Currently, you can use the following options:
    #
    # ROOTDIR="/some/where" -- will run named in a chroot environment.
    # you must set up the chroot environment
    # (install the bind-chroot package) before
    # doing this.
    #
    # OPTIONS="whatever" -- These additional options will be passed to named
    # at startup. Don't add -t here, use ROOTDIR instead.
    #
    # ENABLE_ZONE_WRITE=yes -- If SELinux is disabled, then allow named to write
    # its zone files and create files in its $ROOTDIR/var/named
    # directory, necessary for DDNS and slave zone transfers.
    # Slave zones should reside in the $ROOTDIR/var/named/slaves
    # directory, in which case you would not need to enable zone
    # writes. If SELinux is enabled, you must use only the
    # 'named_write_master_zones' variable to enable zone writes.
    #
    # ENABLE_SDB=yes -- This enables use of 'named_sdb', which has support
    # -- for the ldap, pgsql and dir zone database backends
    # -- compiled in, to be used instead of named.
    #
    # DISABLE_NAMED_DBUS=[1y]-- If NetworkManager is enabled in any runlevel, then
    # the initscript will by default enable named's D-BUS
    # support with the named -D option. This setting disables
    # this behavior.
    #
    # KEYTAB_FILE="/dir/file" -- Specify named service keytab file (for GSS-TSIG)
    ROOTDIR=/var/named/chroot

    3. we have commented last row that now is
    # ROOTDIR=/var/named/chroot

    4. stoped and start named

    ----

    NOW bind restart is ok, but under whm named is always under "failed" status :/
     
  8. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    I have restart more times and now seems all ok

    thanks :D
     
Loading...

Share This Page