Upgrade CentOS 4.x to 5.x, any problems with it?

6 posts / 0 new
Last post
#1 Sat, 03/29/2008 - 03:46

Upgrade CentOS 4.x to 5.x, any problems with it?

Have there been any problems upgrading from, say CentOS 4.6 to CentOS 5.x as opposed to using a new install? I'm comfortable that 4.x will be supported for the next 4 years but I would like to get a good start on 5.x as an enterprise right away.

Has anyone tried this yet? I'd be basically out of the box with the VM changes already up to date.



Fri, 04/04/2008 - 06:17

damn forum software double posting!<br><br>Post edited by: SteveHeinsch, at: 2008/04/04 06:18

Fri, 04/11/2008 - 11:38 (Reply to #2)

well, I answered my own question.

I did the 5.1 upgrade from 4.6 using the 6 install CDs. I was worried when I saw it messing with SELinux since it's supposed to be turned off. But after about 75 minutes it finshed, rebooted and......no picture!!!

THe first thing, upgrade misconfigured the gui (I set level 5 to easily fix what might get broke in webmin from the console) so that there's nothing but a dark screen.

I was able to go the work station and log into webmin remotely only to find Apache, Dovecot, and ProFTP broken right from the start.

I replaced the httpd.conf with the rpm and apache worked, but since there aren't any domains that this won't be the VM tweaked apache. I did the same with the ProFTP as nothing should really matter on that. I then reamed the rpmsave to httpd.conf and got the following error on restart:
ttpd: Syntax error on line 147 of /etc/httpd/conf/httpd.conf: Cannot load /etc/httpd/modules/mod_access.so into server: /etc/httpd/modules/mod_access.so: cannot open shared object file: No such file or directory

Dovecot on the other hand keeps failing due to config errors:
"Starting Dovecot Imap: Error: Error in configuration file /etc/dovecot.conf line 23: Unknown setting: imap_listen

updates showed up for VM, Usermin and webmin and I ran those, but they didn't help the config errors.

Fri, 04/11/2008 - 13:19 (Reply to #3)
Joe's picture

You'll need to update your yum configuration for the Virtualmin repo to point to the right OS version. Edit /etc/yum.repos.d/virtualmin.repo, change the 4.x to a 5.x, save it, and then try upgrading Apache and ProFTPd.

The dovecot configuration will need to be cleaned up manually, as they changed configuration file formats in incompatible ways. Just make a backup of the existing dovecot.conf, and copy the new dovecot.conf.rpmnew into place. Then edit it to make sure the pop3 UID field is set and not commented out, and the imap and pop3 protocols are enabled. I don't think anything else needs changing.

Once that's done...holler with further problems, and I'll try to guide you along.


Check out the forum guidelines!

Sat, 04/12/2008 - 13:08 (Reply to #4)

After spending quite a bit of time with it I had to go back and do a fresh install. Not being VM's fault the CentOS upgrade process is faulty being that getting the video to work from legacy was far too much work, you'd think that 1 year old equipment wouldn't have been a problem and it wasn't. Apparently the Xorg upgrade didn't keep suffient track of what was going on or where it put things. The fresh install went fine. I just have to go through setting up VM the way I want it again. (or is there a way to back VM up, restore it then update it?).

For the record I give the OS upgrade a thumbs down

Fri, 04/04/2008 - 06:17

I am interested in this as well. Im running CentOS4.4. One thing that has held me back in this regard is that the VM repos for 4.4 have a more up to date version of php than the centos5 stack. That and Im deathly afraid of upgrading the OS. Things are running smooth as silk and I really dont want to mess it up, but I do want to run the current version .

Topic locked