• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Can I update CentOS 5 to 5.1 after installing Plesk 8.4.0?

D

dedidude

Guest
Can I update CentOS 5 to 5.1 after Plesk 8.4.0 is already installed?

If so, how would I go about that? I already used yum to update the OS but it's still 5, not 5.1.

Is it even a good idea?

I also wonder why after running yum to update the OS, PHP is still at 5.1.6 when there are newer versions available already? I do not have it excluded in the yum config.
 
Yum update is all you'd need to do to update the box to 5.1. If its not bringing you up to that version, then its possible someone has modified your yum configs to point to a different archive.

The latest PHP packages from centosplus are at 5.1.x. I have 5.2.x packages in my repo, which you can add with the following:

wget -q -O - http://www.atomicorp.com/installers/atomic |sh
 
I need to update these 3 kernel packages right?

# yum check-update
Loading "installonlyn" plugin
Setting up repositories
extras 100% |=========================| 1.1 kB 00:00
updates 100% |=========================| 951 B 00:00
base 100% |=========================| 1.1 kB 00:00
addons 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished

kernel.x86_64 2.6.18-53.1.21.el5 updates
kernel-devel.x86_64 2.6.18-53.1.21.el5 updates
kernel-headers.x86_64 2.6.18-53.1.21.el5 updates


I would like to modify the grub config to be safe with kernel updates, so that it would only boot one time into the new kernel and only boot into it again if it booted correctly.

I found one howto somewhere how to do that but it did not really help because it was not explained well why to make a certain change in the grub config.

My /etc/grub.conf looks like this at the moment:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=20
#splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-53.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-53.el5 ro root=LABEL=/1 console=tty0 console=ttyS1,19200n8
initrd /initrd-2.6.18-53.el5.img

I also have a /boot/grub/grub.conf and I am not sure which one I would have to modify:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=20
#splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-53.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-53.el5 ro root=LABEL=/1 console=tty0 console=ttyS1,19200n8
initrd /initrd-2.6.18-53.el5.img
 
Back
Top