• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

DNS BIND issue

guntersammet

New Pleskian
Hi all:
I rent a root server from 1&1 in Germany running Plesk 8.1 on Suse Linux. Yesterday one of the harddrives passed away and it got replaced and mirrored from the other disk. It appears that all data is there but for some reason bind doesn't run. Also about half of the domains don't work. I assume this has to do with the bind issue. Here the error when I try to start bind:

Code:
Unable to make action: Unable to manage service by dnsmng: dnsmng: Service /etc/init.d/named failed to start

0: /usr/local/psa/admin/plib/common_func.php3:153
    psaerror(string 'Unable to make action: Unable to manage service by dnsmng: dnsmng: Service /etc/init.d/named failed to start')
1: /usr/local/psa/admin/htdocs/server/restart_services.php:28


/var/log/messages says:


Code:
checkproc: checkproc: Can not handle pid file /var/lib/named/var/run/named/named.pid with pid `'
checkproc: checkproc: Can not handle pid file /var/lib/named/var/run/named/named.pid with pid `'
checkproc: checkproc: Can not handle pid file /var/lib/named/var/run/named/named.pid with pid `'
checkproc: checkproc: Can not handle pid file /var/lib/named/var/run/named/named.pid with pid `'
startproc: startproc: Can not handle pid file /var/lib/named/var/run/named/named.pid with pid `'

Didn't find anything in Google and I am kind of lost. Any hints appreciated!
Thanks,

Gunter
 
Here's what happened with my situation, hopefully it will help someone:

When I ran /etc/init.d/named stop one of my domains returned an error. I didn't get a copy of it, sorry. The point is, though, that I deleted that domain from the Plesk control panel (it was just a domain I was messing with, non-production). After I deleted the domain, /etc/init.d/named start worked just fine.
 
Back
Top