Named not restarting

fdnven

• November 22, 2013 11:22

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

• 

  cPanelMichael

  • November 22, 2013 16:39

  Hello :) You may need to reinstall the Bind RPMs. However, first, please try rebuilding your /etc/named.conf file via: mv /etc/named.conf /etc/named.conf.backup1 /scripts/rebuilddnsconfig
  Let us know if the issue persists. Thank you.

  0
• 

  fdnven

  • November 22, 2013 17:40

  [quote="cPanelMichael, post: 1513981">Hello :) You may need to reinstall the Bind RPMs. However, first, please try rebuilding your /etc/named.conf file via: mv /etc/named.conf /etc/named.conf.backup1 /scripts/rebuilddnsconfig
  Let us know if the issue persists. Thank you.
  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

  0
• 

  cPanelMichael

  • November 22, 2013 18:10

  Did you take any actions before this issue started? Try reinstalling Bind by first checking to see which Bind RPMs are installed. EX: 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.

  0
• 

  fdnven

  • November 22, 2013 18:20

  [quote="cPanelMichael, post: 1514112">Did you take any actions before this issue started? Try reinstalling Bind by first checking to see which Bind RPMs are installed. EX: 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.
  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

  0
• 

  cPanelMichael

  • November 22, 2013 18:38

  You could remove/reinstall just the bind-9.8.2-0.17.rc1.el6_4.6.x86_64 RPM. Thank you.

  0
• 

  fdnven

  • November 22, 2013 19:06

  [quote="cPanelMichael, post: 1514131">You could remove/reinstall just the bind-9.8.2-0.17.rc1.el6_4.6.x86_64 RPM. Thank you.
  Remove/reinstall fixed the issue. Thank you very much Frank

  0

Please sign in to leave a comment.