Upgrading Your Plesk Control Panel
You can easily install the necessary updates, control panel add-ons, and even upgrade your control panel to the latest available release using Parallels Plesk Panel Updater function within your control panel.
To upgrade your Parallels Plesk Panel or update its components:
1. Go to Home > Updates (in the Help & Support group).
The control panel connects to the Parallels official update server at URL http://autoinstall.plesk.com, retrieves information on the available releases, then analyses the components installed in the system and displays the lists of available releases and component updates. For each release a brief description of available operations is displayed.
Select the release version that you want to update, or upgrade to. A list of available components appears.
Select the check boxes corresponding to the components you wish to install and click Install. A confirmation screen appears.
Specify your e-mail address. You will be sent a notice by e-mail once update is completed. To confirm installation of the selected components, select the check box and click OK. The components/updates you selected will be downloaded and automatically installed in the background mode.
You can check for errors in the autoinstaller.log file located in the /tmp directory on the server hard drive.
Upgrading License Key for Your Plesk Panel
Parallels Plesk Panel comes with a trial license key, which is automatically installed to the control panel. This license key allows you to create one user account, host one Web site and one mail box. Therefore, to fully use the Parallels Plesk Panel as you need, you should obtain a license key from Parallels or one of its resellers and install it to the control panel.
Parallels Plesk Panel will attempt to connect over TCP/IP to the licensing server through port 5224. Please make sure that this is not blocked by a firewall. The update process runs automatically and the Parallels Plesk Panel administrator does not need to do anything unless there is a problem. Should the Parallels Plesk Panel key expire, check your firewall and then go to Home > License Management (in the Help & Support group) and click Retrieve Keys. If the key cannot be updated, contact your reseller or Parallels (if you purchased the license key directly from Parallels).
You can test the connection to the licensing server anytime by going to Home > License Management (in the Help & Support group) and clicking Retrieve Keys.
Upgrading Your Redhat Server.
Check your kernel release before upgrade.
If run without any packages, update will update every currently installed package.
After the upgrade check the kernel release.
yum update
If run without any packages, update will update every currently installed package.
If one or more packages are specified,Yum will only update the listed packages. While updating packages, yum will ensure that all dependencies are satisfied.
If no package matches the given package name(s), they are assumed to be a shell glob and any matches are then installed. If the –obsoletes flag is present yum will include package obsoletes in its calculations - this makes it better for distro-version changes, for example: upgrading from somelinux 8.0 to somelinux 9.
yum upgrade : Is the same as the update command with the –obsoletes flag set.
yum is an interactive, automated update program which can be used for maintaining systems.
Yum Options:
* install package1 [package2] [...]
* update [package1] [package2] [...]
* check-update
* upgrade [package1] [package2] [...]
* remove | erase package1 [package2] [...]
* list [...]
* info [...]
* provides | whatprovides feature1 [feature2] [...]
* clean [ packages | headers | metadata | cache | dbcache | all ]
* makecache
* groupinstall group1 [group2] [...]
* groupupdate group1 [group2] [...]
* grouplist [hidden]
* groupremove group1 [group2] [...]
* groupinfo group1 [...]
* search string1 [string2] [...]
* shell [filename]
* resolvedep dep1 [dep2] [...]
* localinstall rpmfile1 [rpmfile2] [...]
* localupdate rpmfile1 [rpmfile2] [...]
* deplist package1 [package2] [...]
FILES
/etc/yum.conf
/etc/yum/repos.d/
/etc/yum/pluginconf.d/
/var/cache/yum/
SEE ALSO
yum.conf (5)
http://linux.duke.edu/yum/
http://wiki.linux.duke.edu/YumFaq