Hi folks,

In a moment of inspiration (!) I upgraded MySQL from 4.1 to 5.0. Well, that PHPMYAdmin thing told me to do so...!

That caused a conflict with Apache, resulting in Apache breaking completely.

So I searched the interweb for a solution, and the solution was to rebuild Apache to take into account the new MySQL. Fair enough.

Now, the problem is that (apparently) there is a problem with the Red Hat Network repository hosted by The Planet. Which means that "yum" cannot download the necessary files, and it cannot rebuild Apache. This is even if I try to build the most basic version of Apache.

I raised a ticket about this (5189225PLNT) and the response seems to be that they don't know how long it will take to fix the repository problem.

In the meantime, all my sites are down because Apache is broken and I'm losing money by the hour

If I try to restart Apache, I get this error message:

"Syntax error on line 9 of /usr/local/apache/conf/php.conf: Cannot load /usr/local/apache/modules/libphp5.so into server: /usr/lib/libmysqlclient.so.14: version `libmysqlclient_14' not found (required by /usr/local/apache/modules/libphp5.so)"

Is there something I'm missing?! Or can anyone suggest something I could do to get back online?!

Thanks in advance. I am using this opportunity to backup my databases and make sure I've got offline backups of everything. Thankfully, SSH and FTP are unaffected.

Update: The Planet are saying that the repository problem is fixed. However, "yum update" still gives errors:

There was an error communicating with RHN.
RHN support will be disabled.
Error communicating with server. The message was:
Internal Server Error
Setting up Update Process
Setting up repositories
No Repositories Available to Set Up
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
Skipping security plugin, no data

It seems part of the problem may be that there should be some repository files listed in /etc/yum.repos.d which are missing.

Update your PHP --- the php-mysql package is out of date --- or downgrade your MySQL. That'll be first to getting httpd back up and running.

As for the repo ... are you on CentOS or RHEL?

Looks like the issue has been resolved per the last update to your ticket Can you attempt the process again?

As an observer, I'm curious about this potential single point of failure.

Once you update mysql (e.g. from 4 to 5) if you upgrade your databases in the process, can you easily downgrade to the previous version?

If you have the misfortune for the Planet's repository to go offline while upgrading, is there a workaround of using a different repository so you're not stuck?

Not a biggie if you mysqldump all your databases first and them simply `mysql < dumpfile` ...

Again, what OS is running? If it's CentOS, you can use the regular CentOS repos...

Even if you have upgraded, the vast majority of data files are still in the same format for backwards compatibility, its only newer features which change the files, and even then can typically be loaded into an older SQL just ignored. As it sounds like it was just an upgrade to please some software, id say those features werent used, and a downgrade is safe.


As for the errors, its not apache, apache is simply crashing because theres a bad module being loaded, that module being the php library, which was compiled against a version 4 mysql library

The auto php install, from yum or otherwise, if set to compile with mysql, will auto find the highest version, so that should solve your problem in one.

Thanks for the replies. Yes, the problem was fixed when the repository problem was fixed. I was able to rebuild Apache and everything kicked off from where it was left. It was a pretty stressful weekend though :-(

I am running RHEL.

For future reference, it might be useful to be able to check the status of the repository before even contemplating any kind of software upgrade. A quick "yum check-update" might do that?