Centos 4.4

Highland · Unread post by **Highland** » Thu Aug 31, 2006 6:24 pm

Any caveats in upgrading? Any problems with Plesk?

Unread post by **scott** » Sat Sep 02, 2006 1:32 pm

Not really, Centos 4.4/RHEL 4.4 aren't really new versions, they're mainly just the normal CentOS/RHEL with all the updates applied.

Highland · Unread post by **Highland** » Tue Sep 05, 2006 8:10 pm

Thank goodness I have blogs on my server that I read or I probably would not have found this nasty problem until my boss yelled at me. I did a yum upgrade all and went to Centos 4.4. No problems reported and I assumed all was well. This evening I get home to find the sites unreachable. I thought perhaps the server had locked up again (I suspect 1and1 hardware) but SSH went right in. A quick check confirmed that httpd was running but named was not. If you opt for a full yum upgrade to 4.4 it WILL break Plesk. After about 30 mins of searching I found that this problem is inherent to RHEL overwriting the named.conf symlink. The quick fix is this

1. remove the bind-chroot package

Code: Select all

#rpm -e bind-chroot

2. Renamed named.conf and restore the symlink to the Plesk BIND setup.

Code: Select all

#ln -s /var/named/run-root/etc/named.conf /etc/named.conf

named should restart after this.

breun · Unread post by **breun** » Wed Sep 06, 2006 9:49 am

I have already upgraded at least four boxes running Plesk to CentOS 4.4 and I didn't have this problem. My boxes also don't have the bind-chroot package installed. I guess installing bind-chroot might have killed that symlink.

Highland · Unread post by **Highland** » Thu Sep 07, 2006 9:45 am

I forgot to do a -q to see if it was installed before I did a -e but the named.conf was definitely replaced. Did you use yum update or manually specify packages?

breun · Unread post by **breun** » Thu Sep 07, 2006 9:56 am

Just a plain yum update.