• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Bind Problem

M

Morphe

Guest
I've just upgraded php on cent os and plesk 8.4 After upgrade, all services are down. I can restart apache, qmail, smtp and pop. But I can't restart, stop or start bind. This is the error:

ERROR: PleskFatalException
Create ShortcutCreate Shortcut
Up LevelUp Level
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:154
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

Any advise?
 
I've tried both. I can't start, restart or stop with command line or plesk panel.
 
Okay, do it from the shell. Given the limited amount of information, I would look at /var/log/messages, see if there are any error in the same timeframe related to named.

Proceed at your own risk:

Make sure that bind-chroot; caching-nameserver; are not installed. You might want to do yum remove the packages, if they do. Other than that, post details of the log files for more information.
 
Hi

The same thing happened to me.
When I started BIND using the shell, it gave me the following:

Starting named:
Error in named configuration:
(snip)
_default/3rdpb.shareserv.co.uk/IN: bad zone
(snip)
[FAILED]


3rdpb.shareserv.co.uk was an expired account. Once I removed it entirely in the Domains screen I could start named successfully.

Hope this helps!
Jon
 
Back
Top