MYSQL Updated from 4 to 5.1

K

ktizo

Verified User
Joined
Jan 5, 2006
Messages
46
Hi,

I've just updated mysql from 4.0 to 5.1 via custombuild. This is to meet the requirements of Wordpress installation.

After the update, mysql ver in ssh show 5.1 but Directadmin still shows MySQL 4.0.23 under System Information.

When we tried to install Wordpress, it shows 4.0.23 and installation for Wordpress will halt.

Anyone has this problem? How can I manually change the ver to 5.1

Thanks
 
Did you remember to recompile php after you upgraded mysql? You must always recompile php after upgrade of mysql:

Code: 
cd /usr/local/directadmin/custombuild
./build update
./build php n
 
No, in fact I only did
./build rewrite_confs

Is it not sufficient?
 
tried your suggestion but got this error.

builds/toplevel.mk:43: *** FreeType's build system needs a Make program which supports $(value). Stop

any idea how to resolve this?
 
Code: 
cd /usr/local/directadmin/custombuild
./build update
./build clean
./build php y
 
thanks, after building halfway, this error keeps appearing and it seems to be in a loop

builds/toplevel.mk:43: *** FreeType's build system needs a Make program which supports $(value). Stop
 
You really should learn how to use custombuild first, or hire a system admin for the job. Here is custombuild faq: http://www.directadmin.com/forum/showthread.php?t=29824

Try to recompile freetype and then php:

Code: 
cd /usr/local/directadmin/custombuild
./build update
./build freetype
./build php n

Also do ./build versions to check what needs to be upgraded, and upgrade whats needed.
 
would of thought ./build php y would install freetype
 
All ./build freetype or php goes back to this error.

Done. Making freetype-2.4.10...
Trying to make FreeType...
builds/toplevel.mk:43: *** FreeType's build system needs a Make program which supports $(value). Stop.

*** The make has failed, would you like to try to make again? (y,n):

Anyone had similar experience?
 
update GNU Make to 3.8.2 and build seems to go thru well.
ran a ./build php y. PHP is now showing 5.4.8 now BUT mysql still showing 4.0.23 in Directadmin!

I'm using Centos3
 
There is no way centos 3 is supported. You should be using Centos 5.x or 6.x.
 
scsi said:
There is no way centos 3 is supported. You should be using Centos 5.x or 6.x.
Click to expand...
A very strong second. Problems with old libraries not supporting requirements of new installs. And since yum update no longer works it's way too complex to install all the updated library requirements. We ended up breaking ssl on a system and couldn't find an easy way to fix it (except perhaps to do a static compile) and figured we'd have problems with other servers as well.

If you're running CentOS 3 or any other system from that era, replace before you find yourself with a dead server.

I think I'll ask John to remove it from the DirectAdmin site.

Jeff
 
Hello,

Coincidentally, our CentOS 3 build box died the other day. The drive lastest about 8 years, so can't complain. I've rebuilt it (had to use customapache, and many manual things).. so a fresh install was not fun, nor recommended for anyone.
However, I discovered that the static CentOS 4 DA binaries work just fine on 3, so the next release will use those instead of me adding all development code into the CentOS 3 text box. (internally linked on our end, no changes needed in your license)
So we can keep the CentOS 3 OS in the list with the licenses but I'll remove it from the install page.

John
 
John,

Unless I'm missing something that will work for the DirectAdmin binary, and if you're offering static compiles, for all the software installed through customapache (custombuild?), but not for software which must be kept updated either through yum (yum updates no longer work on CentOS 3) or compiling from source (where new enough libraries for source code aren't available for newest versions).

Am I missing something? Was there an easy way I could have fixed SSL and kept the box in service?

Jeff
 
The CentOS 4 binary is static, so that doesn't matter too much. I can't recall if the CentOS 3 was static or not.. but if it wasn't, moving to the CentOS 4 binaries would likely have nulled any SSL issues with DA.
Not all OS's are static (some refuse to compile as such), but I try to make them static when at all possible.

John
 
Sorry John, but I'm probably not making myself clear; the problem I was having was with ssl and Apache on the server; we tried to fix a problem I really can't remember now; it was something written about on these forums but now I can't even find my notes. But when we rebuilt ssl it broke and we couldn't even shell into the server anymore.

Jeff
 
SSL is one of those services that I like to leave to the package manager. Many (important) things link to it, and changing it could cause the links to break if those services are not recompiled against it (which isn't too common for some services, eg: sshd)
 
Yes, I obviously didn't make myself clear, because I didn't remember clearly. We were attempting to update SSL through the package manager; we couldn't; there was a reason we wanted to update it (can't find my notes :)), so we tried compile from source to latest version, which failed because of library issues. Couldn't move forward easily so we moved sites and shut down the server.

Sorry to have confused the issue. No need to reply.

Jeff
 
You must log in or register to reply here.
Back
Top