Editing Centos Upgrade 4.x to 5.x

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 14: Line 14:
 
</pre>
 
</pre>
  
 +
== Enter container ==
 +
<pre>
 +
vzctl enter $CTID
 +
</pre>
  
 
==Install centos-5-release packages==
 
==Install centos-5-release packages==
Use <code>vzctl exec</code> to execute the rpm install command on the container:
 
  
 
<pre>
 
<pre>
vzctl exec $CTID rpm -Uvh http://mirror.centos.org/centos/5/os/i386/CentOS/centos-release-notes-5.6-0.i386.rpm \ http://mirror.centos.org/centos/5/os/i386/CentOS/centos-release-5-6.el5.centos.1.i386.rpm
+
rpm -Uvh http://mirror.centos.org/centos/5/os/i386/CentOS/centos-release-notes-5.6-0.i386.rpm \ http://mirror.centos.org/centos/5/os/i386/CentOS/centos-release-5-6.el5.centos.1.i386.rpm
 
</pre>
 
</pre>
 
Note: centos-release-5 depends on notes-package, start with that one.
 
Note: centos-release-5 depends on notes-package, start with that one.
Line 25: Line 28:
 
==Backup dev==
 
==Backup dev==
  
Backup the container /dev/ directory, as initscripts needs udev and will remove vzdev you'll need the backup:
+
Backup your /dev/ directory, as initscripts needs udev and will remove vzdev you'll need the backup:
  
 
<pre>
 
<pre>
tar -cf $CTID.dev.tar -C /vz/private/$CTID dev
+
tar -cf dev.tar ./dev
 
</pre>
 
</pre>
  
==Install initscripts package==
+
==Install initscripts package (forced and with no deps)==
 
 
Install initscripts package (forced and with no deps), as per below:
 
  
 
<pre>
 
<pre>
vzctl exec $CTID rpm -Uvh http://mirror.centos.org/centos/5/os/i386/CentOS/initscripts-8.45.33-1.el5.centos.i386.rpm --force --nodeps
+
rpm -Uvh http://mirror.centos.org/centos/5/os/i386/CentOS/initscripts-8.45.33-1.el5.centos.i386.rpm --force --nodeps
 
</pre>
 
</pre>
  
 
Note: If the "transfer failed", go to the [http://mirror.centos.org/centos/5/os/i386/CentOS/ CentOS5 mirror] and find the latest initscripts rpm and use that instead.
 
Note: If the "transfer failed", go to the [http://mirror.centos.org/centos/5/os/i386/CentOS/ CentOS5 mirror] and find the latest initscripts rpm and use that instead.
 +
 +
==Exit from container==
 +
<pre>
 +
exit
 +
</pre>
  
 
==Update conf file==
 
==Update conf file==
Line 54: Line 60:
 
Alternatively, use the 'sed' command to replace it:
 
Alternatively, use the 'sed' command to replace it:
 
<pre>
 
<pre>
sed -i 's#OSTEMPLATE="centos-4#OSTEMPLATE="centos-5#g' /etc/vz/conf/$CTID.conf
+
sed -i 's#OSTEMPLATE="centos-4#OSTEMPLATE="centos-5#g' /etc/vz/conf/$CSID.conf
 
</pre>
 
</pre>
  
Line 113: Line 119:
 
vzctl exec $CTID rpm --import http://mirrors.kernel.org/centos/RPM-GPG-KEY-CentOS-5
 
vzctl exec $CTID rpm --import http://mirrors.kernel.org/centos/RPM-GPG-KEY-CentOS-5
 
</pre>
 
</pre>
 
==Test your VE==
 
Check you can enter your VE:
 
<pre>
 
vzctl enter $CTID
 
</pre>
 
 
All went OK? Exit the VE:
 
<pre>
 
exit
 
</pre>
 
 
===Troubleshooting===
 
 
<pre>
 
Unable to open pty: No such file or directory
 
</pre>
 
If you see errors like this, see the [[VPS_enter_failed]] article.
 
  
 
==Stop your VE==
 
==Stop your VE==
Line 137: Line 125:
 
</pre>
 
</pre>
  
==Restore dev==
+
==Replace the new /dev/ with the old one==
 
 
This will replace the new /dev/ with the old one:
 
 
<pre>
 
<pre>
mv /vz/private/$CTID/dev /vz/private/$CTID/dev.old
+
cd /vz/private/$CTID
tar -xvf $CTID.dev.tar -C /vz/private/$CTID
+
mv dev dev.old
 +
tar -xvf dev.tar
 
</pre>
 
</pre>
  

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Templates used on this page: