• 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.

Can I update the bind package from the CentOS repo?

GiorgosP

New Pleskian
This is my first post to the parallels forum, so please be patient with me :)

I am running Plesk 8.6.0 on a CentOS release 5.2 (Final).

The problem is that named (bind) has this strange behavior: It restarts at some intervals (this is OK), but sometimes does not start again, without leaving any error messages:

...
...
messages:Feb 3 17:33:38 xxx named[5793]: zone xxxx.gr/IN: loaded serial 2009112001
messages:Feb 3 17:33:38 xxx named[5793]: zone xxxgr/IN: loaded serial 2010012102
messages:Feb 3 17:33:38 xxx named[5793]: zone xxxxgr/IN: loaded serial 2009060501
messages:Feb 3 17:33:38 xxx named[5793]: running
messages:Feb 3 17:33:47 xxx named[5793]: shutting down: flushing changes
messages:Feb 3 17:33:47 xxx named[5793]: stopping command channel on 127.0.0.1#953
messages:Feb 3 17:33:47 xxx named[5793]: no longer listening on 127.0.0.1#53
messages:Feb 3 17:33:47 xxx named[5793]: no longer listening on xxxx#53
messages:Feb 3 17:33:47 xxx named[5793]: exiting

Normally, after reloading the zones, it should restart. Afterwards, when I saw that it is down, I just started it from the panel and all was working again.

Bind version is
Version : 9.3.4
Release : 6.0.2.P1.el5_2
Repo : installed

and the CentOS repo has:

Available Packages
Version : 9.3.6
Release : 4.P1.el5_4.2
Repo : updates


So I have two questions: If I upgrade my bind, will I have problem with the Plesk version I'm running?
And the same question in general: The versions of plesk require specific package versions? Because I'm seeing many updates from yum that I fear upgrading in order not to break Plesk...

Thanks!
Giorgos
 
Back
Top