• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

MySQL 5?

Mysql5 on Debian Guide

Okay, this is a very rough guide, i'm a tech, not a writer. No guarantees, but it worked for me no problem.

Generic Sarge Install - no desktop, nothing special. Added Plesk.

Installed xinetd

ran psa installer to get

which installed a ton of stuff.


rebooted for good measure

Verified that plesk logs in and works (accept license, admin, default client account, all that jazz.)

installed phpmyadmin in a seperate non plesk directory /var/www/pma, and had it talking to current mysql.

Server version: 4.1.11-Debian_4sarge7-log

So now plesk is installed and ready to upgrade mysql5.

Added the following to sources.list


deb http://autoinstall.plesk.com/debian/PSA_8.1.0 sarge all
deb http://packages.dotdeb.org stable all
deb-src http://packages.dotdeb.org stable all

Did an apt-get update

apt-get install mysql-server-5.0

The following extra packages will be installed:
libmysqlclient15off mysql-client-5.0 mysql-common
Suggested packages:
tinyca
The following packages will be REMOVED:
mysql-client-4.1 mysql-common-4.1 mysql-server-4.1
The following NEW packages will be installed:
libmysqlclient15off mysql-client-5.0 mysql-common mysql-server-5.0


Say yes. This will take a few minutes.

Set the password

Answer the account question

configuration file - I kept current

At that point mysqld will restart as 5.

You may or may not need the privilege step, but I ran just in case.

/usr/bin/mysql_fix_privilege_tables


find that file, then run it with your permissions as such

./mysql_fix_privilege_tables --user=admin --password=password

That will import the sql file to make schema changes on the privilege database.

I fired up phpmyadmin

Server version: 5.0.30-Debian_0.dotdeb.1-log

Loaded up the plesk console - no errors. Tried to edit an existing database, all good, tried to create a new database, all good.

Works with both the seperate phpmyadmin, and the built in (and much older) version.

Mysql5 on debian with Plesk 8.1


Good luck with it. I'm going to try php5 next, then will attempt to update it to etch rc3.
 
Re: Re: Mysql5 on Debian Guide

Originally posted by VIB-host
Forbidden
You don't have permission to access /debian/PSA_8.1.0/ on this server.
Click to expand...

Are you trying to browse to it? or use it as an apt source?
 
I was trying to browse it to see if there was anything for freebsd6 i could use :/
 
Hi Vengent,

THX a lot for your detailed instructions :) But it doesn't work on my server... Think is only a litte problem, but I can't get it. I do a:

--------------------->
apt-get install mysql-server-5.0
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
mysql-server-5.0: Depends: mysql-client-5.0 (>= 5.0.30-0.dotdeb.1) but it is not going to be installed
Depends: libmysqlclient15off (>= 5.0.24-2) but it is not going to be installed
PreDepends: mysql-common (>= 5.0.30-0.dotdeb.1)
E: Broken packages
--------------------->

Here is my sources.list:

--------------------->
#deb file:///cdrom/ sarge main

# Stable
deb http://ftp.de.debian.org/debian/ stable main non-free contrib
deb-src http://ftp.de.debian.org/debian/ stable main non-free contrib
deb http://security.debian.org/ stable/updates main non-free contrib
deb-src http://security.debian.org/ stable/updates main non-free contrib

# PSA
deb http://autoinstall.plesk.com/debian/PSA_8.1.0 sarge all

# DotDeb
deb http://packages.dotdeb.org stable all
deb-src http://packages.dotdeb.org stable all

# Typo3
deb http://typo3.sunsite.dk/software/debian/ sarge all
--------------------->

Do you have any idea what could be wrong? Of course I did a "apt-get update" first.

Greets and big THX again,
Dawn
 
You may need to get apt-get happy with other dependencies first.

I didn't have that problem with mysql, but on the php5 upgrade, I had to install the dotdeb upgrades to php4 first.

Might try an apt-get upgrade once you've updated with dotdeb, and perhaps an apt-get -f install.
 
I've outcommented the official Debian mirrors, did an apt-get update and then installed the mysql-server. Works great :)

Only one thing is strange:
When I login to phpmyadmin I can see:
Server Version: 5.0.30-Debian_0.dotdeb.1-log
BUT MySQL-Client-Version: 4.1.11

When I try to install mysql-client-5.0 then I get the message it's allready installed. Can you verify that?

Greets,
Dawn

PS: If you need help with PHP 5 let me know
 
Hmm, my client version in pma is that as well.

MySQL client version: 4.1.15

but dpkg returns

dpkg -l | grep mysql-client
ii mysql-client-5 5.0.30-0.dotde mysql database client binaries

I'm all good to go on php5, but thank you very much =)
 
I've got:
ii mysql-client-5 5.0.30-0.dotde mysql database client binaries

too.

But do you have any idea why the old client version occures in phpmyadmin?

Nice to hear that PHP 5 works @ your server :) I'm feeling really lucky that it worked without any problems. Now finally PHP5 and MySQL 5 works :)

Greets,
Dawn
 
I think I found the culprit.

ii libmysqlclient 4.0.24-10sarge mysql database client library
ii libmysqlclient 4.1.15-0.dotde mysql database client library
ii libmysqlclient 5.0.30-0.dotde mysql database client library


Trying to remove the old ones also tries to remove all of psa.

I'm thinking it's probably an || dependency, so if removing the old one with dpkg and force-depends, should push it to use the newer one.

I blew up my test box trying to upgrade to etch (like badly heh.) So will be a few days before I can try it.
 
Upgrading to etch seems to be really difficult. I hope that will works because I heared Etch will be stable in january.

Thanks for your great help and the time you've spent to help me.

I hope there is any way to remove all MySQL 4.x Stuff. It would be nice if you can tell me if you get it to work. I don't have any idea how to remove it.

Have a really nice and realaxing weekend!

Greets from Switzerland,
Dawn
 
Turns out the answer is no, can't just remove the older libmysqlclient. Still numerous dependencies problems that won't switch over to the newer one.

It may be intentional.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326978

But, we're using the dotdeb packages, not native debian, so not sure there's a real alternative here.

Here's to hoping Etch solves most of this.
 
Originally posted by Dawn
Did anybody find a solution?

Would be very nice..

Regards,
Dawn
Click to expand...

No luck here.

I did finish getting plesk8 + php5 + mysql5 + etch all functioning.

But even with all native etch packages, its still showing a client library of 4.x

dpkg -l shows that both the 4 and 5 are installed, but trying to remove the 4 generates some dependencies.

I haven't tried forcing it, will put it on my list to try.
 
php is going to look for the mysql client library path that it was linked against at compile time. Presumably your php package was linked against a 4.1 library, so you can either symlink around that (and this is always messy), or rebuild php against the native mysql5 client library.
 
Originally posted by atomicturtle
php is going to look for the mysql client library path that it was linked against at compile time. Presumably your php package was linked against a 4.1 library, so you can either symlink around that (and this is always messy), or rebuild php against the native mysql5 client library.
Click to expand...

If its encapsulated within the packaging system, wouldn't that (in theory) automatically handle that linking?

Or a secondary question, it seems like most of the big 5 features don't require the upgraded client library, that I know of at least. Is their a compelling reason to relink that without a specific problem that requires it?

Thanks for the info.
 
It can, but there are a lot of things that can screw it up. With an RPM you're going to get a library dependency check included when the package is built. So for example when I build against mysql 4.1, which uses:

/usr/lib/mysql/libmysqlclient.so.14.0.0

when you run ldconfig, this creates symlinks like this:
/usr/lib/mysql/libmysqlclient.so

So assuming php links against libmysqlclient.so, and ldconfig is keeping things up to date you shouldn't have to do anything special. Unfortunately it appears that php links directly to the client library:
ldd -v mysql.so
libmysqlclient.so.14 => /usr/lib/mysql/libmysqlclient.so.14 (0x00df6000)

Its something you can fix in an RPM, for example making a package that forces links from the old version to the new one. The fallout here is that you run the risk of breaking other applications when you do that. I don't really think of this as a bug though, since the PHP folks probably have a really good reason to go straight to the real library.

In my case with the older PHP 4.3 and 4.4 rpms mixed with Mysql 4/5 I ended up linking mysql against the native mysql, and including a mysql-compat package with the older client libraries. That got around issues with breaking other applications linked against mysql 3 on the box, and saved me a lot of time and trouble rebuilding all those apps against mysql4.
 
Any Solutiion to the Client =4.x??

I seem to have this on my system. Also it behaves as mysql4
A script with a connect to mysqli is an undefined op.

Any help would be appreciated.

Joe
 
You must log in or register to reply here.

Similar threads

andreios
Issue Database connection fails for no reason
Replies
10
Views
323
andreios
andreios
dash
  • Sticky
Question Try our new tool to upgrade your old MariaDB server from Plesk UI
2 3
Replies
45
Views
5K
VNick
V
J
Issue Table 'psa.DomainKeys' doesn't exist
Replies
7
Views
312
Peter Debik
P
P
Resolved "Column count of mysql.proc is wrong" : Cannot export database from Plesk
Replies
11
Views
2K
scsa20
scsa20
I
Issue maria DB update plesk 18.0.50
Replies
10
Views
3K
Maarten.
M
Back
Top