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

OS packages update after installed of Plesk ?

E

edwin1121

Guest
Hello,

Are there any correct instructions on updating the packages of the OS?

we are running RHEL 5.1, in our rhn console it shows some packages available to update. I'm afraid plesk will not function properly after the update. Or will i be safe to do the update? please advise.

OS: RHEL 5.1
Plesk: 8.4 (autoinstaller)
RH bug fix: all updated
RH package update: none updated

please advise,

regards,
edwin
 
i got Red Hat 5 too. I updated like hell and never noticed a problem :)
 
opps , i have updated the packages.. some are failed ... @.@ ~~~~ and the named service cannot start now!!! help~~~

Locating /var/named/chroot//etc/named.conf failed:

help!!!
 
No Problem my friend :)

1.
uninstalling bind-chroot:
yum remove bind-chroot

2.
add this line back into /etc/sysconfig/named:
ROOTDIR="/var/named/run-root"


Notice:
next time add the following line to your yum.conf file under the [main] section
exclude=bind-chroot


If you have problem write back!
 
Back
Top