Problems After MySql 5.1.34

--------------020001090102080600090909
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I recently upgraded an asterisk/trixbox server to mysql 5.1.34 from
5.64. Access to the db seesm fine from the shell, phpmyadmin or even the
Trixbox/FreePBX tool, but trying to apply Trixbox changes, or running a
"pear update" produces the errors below. I created a couple of sl but
this did not seem to fix the problem. Below is the error and contents of
/usr/lib




root@asterisk:~# pear update
PHP Warning: PHP Startup: Unable to load dynamic library
'/usr/lib/php/modules/mysql.so' - /usr/lib/libmysqlclient.so.15: version
`libmysqlclient_15' not found (required by
/usr/lib/php/modules/mysql.so) in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library
'/usr/lib/php/modules/mysqli.so' - /usr/lib/libmysqlclient.so.15:
version `libmysqlclient_15' not found (required by
/usr/lib/php/modules/mysqli.so) in Unknown on line 0
Segmentation fault



root@asterisk:~# ls -la /usr/lib/libmy*

lrwxrwxrwx 1 root root 26 May 6 09:52 /usr/lib/libmysqlclient_r.so
-> libmysqlclient_r.so.16.0.0
lrwxrwxrwx 1 root root 28 May 6 11:26
/usr/lib/libmysqlclient_r.so.15 -> /usr/lib/libmysqlclient_r.so
lrwxrwxrwx 1 root root 28 May 6 11:18
/usr/lib/libmysqlclient_r.so.15.0.0 -> /usr/lib/libmysqlclient_r.so
lrwxrwxrwx 1 root root 26 May 6 09:52
/usr/lib/libmysqlclient_r.so.16 -> libmysqlclient_r.so.16.0.0
-rwxr-xr-x 1 root root 2052884 Mar 31 22:48
/usr/lib/libmysqlclient_r.so.16.0.0
lrwxrwxrwx 1 root root 24 May 6 09:52 /usr/lib/libmysqlclient.so
-> libmysqlclient.so.16.0.0
lrwxrwxrwx 1 root root 26 May 6 11:14
/usr/lib/libmysqlclient.so.15 -> /usr/lib/libmysqlclient.so
lrwxrwxrwx 1 root root 24 May 6 09:52
/usr/lib/libmysqlclient.so.16 -> libmysqlclient.so.16.0.0
-rwxr-xr-x 1 root root 2044464 Mar 31 22:48
/usr/lib/libmysqlclient.so.16.0.0


--
_____________________________________________
Johnny Stork

Open Enterprise Solutions
"Empowering Business With Open Solutions"
http://www.openenterprise.ca

Mountain Hosting
"Secure Hosting Solutions for Business"
http://www.mountainhosting.ca


--------------020001090102080600090909--

Re: Problems After MySql 5.1.34

Typo, moved from 5.0.67 to 5.1.34

Johnny Stork wrote:
> I recently upgraded an asterisk/trixbox server to mysql 5.1.34 from
> 5.64. Access to the db seesm fine from the shell, phpmyadmin or even
> the Trixbox/FreePBX tool, but trying to apply Trixbox changes, or
> running a "pear update" produces the errors below. I created a couple
> of sl but this did not seem to fix the problem. Below is the error and
> contents of /usr/lib
>
>
>
>
> root@asterisk:~# pear update
> PHP Warning: PHP Startup: Unable to load dynamic library
> '/usr/lib/php/modules/mysql.so' - /usr/lib/libmysqlclient.so.15:
> version `libmysqlclient_15' not found (required by
> /usr/lib/php/modules/mysql.so) in Unknown on line 0
> PHP Warning: PHP Startup: Unable to load dynamic library
> '/usr/lib/php/modules/mysqli.so' - /usr/lib/libmysqlclient.so.15:
> version `libmysqlclient_15' not found (required by
> /usr/lib/php/modules/mysqli.so) in Unknown on line 0
> Segmentation fault
>
>
>
> root@asterisk:~# ls -la /usr/lib/libmy*
>
> lrwxrwxrwx 1 root root 26 May 6 09:52
> /usr/lib/libmysqlclient_r.so -> libmysqlclient_r.so.16.0.0
> lrwxrwxrwx 1 root root 28 May 6 11:26
> /usr/lib/libmysqlclient_r.so.15 -> /usr/lib/libmysqlclient_r.so
> lrwxrwxrwx 1 root root 28 May 6 11:18
> /usr/lib/libmysqlclient_r.so.15.0.0 -> /usr/lib/libmysqlclient_r.so
> lrwxrwxrwx 1 root root 26 May 6 09:52
> /usr/lib/libmysqlclient_r.so.16 -> libmysqlclient_r.so.16.0.0
> -rwxr-xr-x 1 root root 2052884 Mar 31 22:48
> /usr/lib/libmysqlclient_r.so.16.0.0
> lrwxrwxrwx 1 root root 24 May 6 09:52 /usr/lib/libmysqlclient.so
> -> libmysqlclient.so.16.0.0
> lrwxrwxrwx 1 root root 26 May 6 11:14
> /usr/lib/libmysqlclient.so.15 -> /usr/lib/libmysqlclient.so
> lrwxrwxrwx 1 root root 24 May 6 09:52
> /usr/lib/libmysqlclient.so.16 -> libmysqlclient.so.16.0.0
> -rwxr-xr-x 1 root root 2044464 Mar 31 22:48
> /usr/lib/libmysqlclient.so.16.0.0
>
>

--
_____________________________________________
Johnny Stork

Open Enterprise Solutions
"Empowering Business With Open Solutions"
http://www.openenterprise.ca

Mountain Hosting
"Secure Hosting Solutions for Business"
http://www.mountainhosting.ca


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

RE: Problems After MySql 5.1.34

Johnny,=20

Welcome to the hell that is php + apache + mysql. If you upgrade your MySq=
l (especially major versions 5.0 =3D> 5.1) you will also need to recompile =
php against the new MySql client libs. We've had very limited success tryi=
ng to get it to work otherwise.

This is why you are receiving the error through PHP.

Of course, I could be wrong, in which case I know people will probably jump=
me for it. If this is the case, please do as I would like to be wrong her=
e as it would make my compiling life easier every time I update MySql on al=
l of my boxes.

Gary

________________________________________
From: Johnny Stork [lists@openenterprise.ca]
Sent: Wednesday, May 06, 2009 1:03 PM
Cc: mysql@lists.mysql.com
Subject: Re: Problems After MySql 5.1.34

Typo, moved from 5.0.67 to 5.1.34

Johnny Stork wrote:
> I recently upgraded an asterisk/trixbox server to mysql 5.1.34 from
> 5.64. Access to the db seesm fine from the shell, phpmyadmin or even
> the Trixbox/FreePBX tool, but trying to apply Trixbox changes, or
> running a "pear update" produces the errors below. I created a couple
> of sl but this did not seem to fix the problem. Below is the error and
> contents of /usr/lib
>
>
>
>
> root@asterisk:~# pear update
> PHP Warning: PHP Startup: Unable to load dynamic library
> '/usr/lib/php/modules/mysql.so' - /usr/lib/libmysqlclient.so.15:
> version `libmysqlclient_15' not found (required by
> /usr/lib/php/modules/mysql.so) in Unknown on line 0
> PHP Warning: PHP Startup: Unable to load dynamic library
> '/usr/lib/php/modules/mysqli.so' - /usr/lib/libmysqlclient.so.15:
> version `libmysqlclient_15' not found (required by
> /usr/lib/php/modules/mysqli.so) in Unknown on line 0
> Segmentation fault
>
>
>
> root@asterisk:~# ls -la /usr/lib/libmy*
>
> lrwxrwxrwx 1 root root 26 May 6 09:52
> /usr/lib/libmysqlclient_r.so -> libmysqlclient_r.so.16.0.0
> lrwxrwxrwx 1 root root 28 May 6 11:26
> /usr/lib/libmysqlclient_r.so.15 -> /usr/lib/libmysqlclient_r.so
> lrwxrwxrwx 1 root root 28 May 6 11:18
> /usr/lib/libmysqlclient_r.so.15.0.0 -> /usr/lib/libmysqlclient_r.so
> lrwxrwxrwx 1 root root 26 May 6 09:52
> /usr/lib/libmysqlclient_r.so.16 -> libmysqlclient_r.so.16.0.0
> -rwxr-xr-x 1 root root 2052884 Mar 31 22:48
> /usr/lib/libmysqlclient_r.so.16.0.0
> lrwxrwxrwx 1 root root 24 May 6 09:52 /usr/lib/libmysqlclient.so
> -> libmysqlclient.so.16.0.0
> lrwxrwxrwx 1 root root 26 May 6 11:14
> /usr/lib/libmysqlclient.so.15 -> /usr/lib/libmysqlclient.so
> lrwxrwxrwx 1 root root 24 May 6 09:52
> /usr/lib/libmysqlclient.so.16 -> libmysqlclient.so.16.0.0
> -rwxr-xr-x 1 root root 2044464 Mar 31 22:48
> /usr/lib/libmysqlclient.so.16.0.0
>
>

--
_____________________________________________
Johnny Stork

Open Enterprise Solutions
"Empowering Business With Open Solutions"
http://www.openenterprise.ca

Mountain Hosting
"Secure Hosting Solutions for Business"
http://www.mountainhosting.ca


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgary@primeexalia.co=
m=

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: Problems After MySql 5.1.34

there is nothing you can make.
Any (major)upgrade of mysql client requires the dependent subsystem to upgrade also.
Anything else would be careless since you do not know if the interface has changed.

basicly you can install both version of libraries and hope for the best. i would do this only as last
rescue if an update is not possible. it is in general not clever.

re,
wh

Gary Smith schrieb:
> Johnny,
>
> Welcome to the hell that is php + apache + mysql. If you upgrade your MySql (especially major versions 5.0 => 5.1) you will also need to recompile php against the new MySql client libs. We've had very limited success trying to get it to work otherwise.
>
> This is why you are receiving the error through PHP.
>
> Of course, I could be wrong, in which case I know people will probably jump me for it. If this is the case, please do as I would like to be wrong here as it would make my compiling life easier every time I update MySql on all of my boxes.
>
> Gary
>
> ________________________________________
> From: Johnny Stork [lists@openenterprise.ca]
> Sent: Wednesday, May 06, 2009 1:03 PM
> Cc: mysql@lists.mysql.com
> Subject: Re: Problems After MySql 5.1.34
>
> Typo, moved from 5.0.67 to 5.1.34
>
> Johnny Stork wrote:
>> I recently upgraded an asterisk/trixbox server to mysql 5.1.34 from
>> 5.64. Access to the db seesm fine from the shell, phpmyadmin or even
>> the Trixbox/FreePBX tool, but trying to apply Trixbox changes, or
>> running a "pear update" produces the errors below. I created a couple
>> of sl but this did not seem to fix the problem. Below is the error and
>> contents of /usr/lib
>>
>>
>>
>>
>> root@asterisk:~# pear update
>> PHP Warning: PHP Startup: Unable to load dynamic library
>> '/usr/lib/php/modules/mysql.so' - /usr/lib/libmysqlclient.so.15:
>> version `libmysqlclient_15' not found (required by
>> /usr/lib/php/modules/mysql.so) in Unknown on line 0
>> PHP Warning: PHP Startup: Unable to load dynamic library
>> '/usr/lib/php/modules/mysqli.so' - /usr/lib/libmysqlclient.so.15:
>> version `libmysqlclient_15' not found (required by
>> /usr/lib/php/modules/mysqli.so) in Unknown on line 0
>> Segmentation fault
>>
>>
>>
>> root@asterisk:~# ls -la /usr/lib/libmy*
>>
>> lrwxrwxrwx 1 root root 26 May 6 09:52
>> /usr/lib/libmysqlclient_r.so -> libmysqlclient_r.so.16.0.0
>> lrwxrwxrwx 1 root root 28 May 6 11:26
>> /usr/lib/libmysqlclient_r.so.15 -> /usr/lib/libmysqlclient_r.so
>> lrwxrwxrwx 1 root root 28 May 6 11:18
>> /usr/lib/libmysqlclient_r.so.15.0.0 -> /usr/lib/libmysqlclient_r.so
>> lrwxrwxrwx 1 root root 26 May 6 09:52
>> /usr/lib/libmysqlclient_r.so.16 -> libmysqlclient_r.so.16.0.0
>> -rwxr-xr-x 1 root root 2052884 Mar 31 22:48
>> /usr/lib/libmysqlclient_r.so.16.0.0
>> lrwxrwxrwx 1 root root 24 May 6 09:52 /usr/lib/libmysqlclient.so
>> -> libmysqlclient.so.16.0.0
>> lrwxrwxrwx 1 root root 26 May 6 11:14
>> /usr/lib/libmysqlclient.so.15 -> /usr/lib/libmysqlclient.so
>> lrwxrwxrwx 1 root root 24 May 6 09:52
>> /usr/lib/libmysqlclient.so.16 -> libmysqlclient.so.16.0.0
>> -rwxr-xr-x 1 root root 2044464 Mar 31 22:48
>> /usr/lib/libmysqlclient.so.16.0.0
>>
>>
>
> --


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: Problems After MySql 5.1.34

Hi Johnny, all!


Johnny Stork wrote:
> Typo, moved from 5.0.67 to 5.1.34

Ok, that helps - I checked the contents.

>=20
> Johnny Stork wrote:
>> I recently upgraded an asterisk/trixbox server to mysql 5.1.34 fro=
m
>> 5.64. Access to the db seesm fine from the shell, phpmyadmin or ev=
en
>> the Trixbox/FreePBX tool, but trying to apply Trixbox changes, or
>> running a "pear update" produces the errors below. I created a cou=
ple
>> of sl but this did not seem to fix the problem. Below is the error=
and
>> contents of /usr/lib

Somewhere during this upgrade you seem to have lost the shared librar=
ies
of the MySQL client side which you had with version 5.0.67:
/usr/lib/libmysqlclient_r.so.15.0.0
/usr/lib/libmysqlclient.so.15.0.0
MySQL 5.0 comes with version 15 of these libraries,
MySQL 5.1 comes with version 16.


How these are handled depends on how you install MySQL (assuming Linu=
x):

a) If you use "tar.gz" packages, then MySQL 5.0 has brought version 1=
5
and created symlinks from the unversioned name to the versioned:
/usr/lib/libmysqlclient.so -> /usr/lib/libmysqlclient.so.15
/usr/lib/libmysqlclient.so.15 -> /usr/lib/libmysqlclient.so.15.0=
..0
/usr/lib/libmysqlclient.so.15.0.0 would be a real file.
(Similar for "libmysqlclient_r.so")

Then, upgrading to 5.1 would bring version 16:
/usr/lib/libmysqlclient.so -> /usr/lib/libmysqlclient.so.16
/usr/lib/libmysqlclient.so.16 -> /usr/lib/libmysqlclient.so.16.0=
..0
Again, /usr/lib/libmysqlclient.so.16.0.0 would be a real file.

Note that this installation changes the symlimk for the unversione=
d
name, but would not touch version 15, there still is
/usr/lib/libmysqlclient.so.15 -> /usr/lib/libmysqlclient.so.15.0=
..0
/usr/lib/libmysqlclient.so.15.0.0 would still exist as a real file=
..

b) If you use RPMs, then installing MySQL 5.0 has set up version 15 o=
f
the client libraries in the same way.
However, the upgrade to MySQL 5.1 would have removed the files
brought by 5.0 and just installed the new version 16
(specifically, the 5.1 "shared" RPM does this).

If you use applications that were built against older versions of =
the
MySQL client libraries (like "Trixbox"), you must not lose these
older files.

For this purpose, we provide "shared-compat" RPMs, they contain th=
e
current and all previous versions of the client libraries.
See this contents listing:

>prompt> rpm -qlvp MySQL-shared-compat-5.1.34-0.glibc23.i386.rpm | cu=
t -c1-11,37-
> lrwxrwxrwx 24 Apr 5 23:56 /usr/lib/libmysqlclient.so -> lib=
mysqlclient.so.16.0.0
> lrwxrwxrwx 24 Apr 5 23:56 /usr/lib/libmysqlclient.so.10 -> =
libmysqlclient.so.10.0.0
> -rwxr-xr-x 224606 Apr 5 23:56 /usr/lib/libmysqlclient.so.10.0.0
> lrwxrwxrwx 24 Apr 5 23:56 /usr/lib/libmysqlclient.so.12 -> =
libmysqlclient.so.12.0.0
> -rwxr-xr-x 221492 Apr 5 23:56 /usr/lib/libmysqlclient.so.12.0.0
> lrwxrwxrwx 24 Apr 5 23:56 /usr/lib/libmysqlclient.so.14 -> =
libmysqlclient.so.14.0.0
> -rwxr-xr-x 1267848 Apr 5 23:56 /usr/lib/libmysqlclient.so.14.0.0
> lrwxrwxrwx 24 Apr 5 23:56 /usr/lib/libmysqlclient.so.15 -> =
libmysqlclient.so.15.0.0
> -rwxr-xr-x 1942232 Apr 5 23:56 /usr/lib/libmysqlclient.so.15.0.0
> lrwxrwxrwx 24 Apr 5 23:56 /usr/lib/libmysqlclient.so.16 -> =
libmysqlclient.so.16.0.0
> -rwxr-xr-x 1989112 Apr 5 23:56 /usr/lib/libmysqlclient.so.16.0.0
> lrwxrwxrwx 26 Apr 5 23:56 /usr/lib/libmysqlclient_r.so -> l=
ibmysqlclient_r.so.16.0.0
> lrwxrwxrwx 26 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.10 -=
> libmysqlclient_r.so.10.0.0
> -rwxr-xr-x 230560 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.10.0=
..0
> lrwxrwxrwx 26 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.12 -=
> libmysqlclient_r.so.12.0.0
> -rwxr-xr-x 225752 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.12.0=
..0
> lrwxrwxrwx 26 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.14 -=
> libmysqlclient_r.so.14.0.0
> -rwxr-xr-x 1274796 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.14.0=
..0
> lrwxrwxrwx 26 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.15 -=
> libmysqlclient_r.so.15.0.0
> -rwxr-xr-x 1950652 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.15.0=
..0
> lrwxrwxrwx 26 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.16 -=
> libmysqlclient_r.so.16.0.0
> -rwxr-xr-x 1999100 Apr 5 23:56 /usr/lib/libmysqlclient_r.so.16.0=
..0
> lrwxrwxrwx 21 Apr 5 23:56 /usr/lib/libndbclient.so -> libnd=
bclient.so.2.0.0
> lrwxrwxrwx 21 Apr 5 23:56 /usr/lib/libndbclient.so.2 -> lib=
ndbclient.so.2.0.0
> -rwxr-xr-x 759988 Apr 5 23:56 /usr/lib/libndbclient.so.2.0.0

For comparison, this is the 5.1.34 "shared" RPM:

>> rpm -qlvp MySQL-shared-5.1.34-0.glibc23.i386.rpm | cut -c1-11,37-
> lrwxrwxrwx 24 Mar 31 22:47 /usr/lib/libmysqlclient.so -> lib=
mysqlclient.so.16.0.0
> lrwxrwxrwx 24 Mar 31 22:47 /usr/lib/libmysqlclient.so.16 -> =
libmysqlclient.so.16.0.0
> -rwxr-xr-x 1998728 Mar 31 22:48 /usr/lib/libmysqlclient.so.16.0.0
> lrwxrwxrwx 26 Mar 31 22:47 /usr/lib/libmysqlclient_r.so -> l=
ibmysqlclient_r.so.16.0.0
> lrwxrwxrwx 26 Mar 31 22:47 /usr/lib/libmysqlclient_r.so.16 -=
> libmysqlclient_r.so.16.0.0
> -rwxr-xr-x 2008716 Mar 31 22:48 /usr/lib/libmysqlclient_r.so.16.0=
..0



Ok, so much for the background. Now how do you fix it?

This should be simple: You need version 15 of the client libraries as
"real" files, but the default (unnamed) must still be a symlink to
version 16 (as shown in the above list).

You have two possibilities:

a) If you are using tar.gz (or if you are using RPMs and don't want t=
o
uninstall "shared", see below), just remove the wrong symlinks (al=
l
about version 15) and manually install the real files,
"/usr/lib/libmysqlclient.so.15.0.0" (and "libmysqlclient_r").
Then, install the symlinks:
/usr/lib/libmysqlclient.so.15 -> libmysqlclient.so.15.0.0
(again, similar for "libmysqlclient_r").

You get them from your backup (you have one, I trust?).

If you don't have them, just download a 5.0.67 tar.gz package for
your platform, and extract only these files.
On Linux, you can also download a 5.0.67 "shared" or "shared-compa=
t"
RPM, or a 5.1.34 "shared-compat" one, and use "rpm2cpio" to extrac=
t
these files.


b) If you are using RPMs, you may uninstall the 5.1.34 "shared" RPM a=
nd
then install the 5.1.34 "shared-compat" (for your platform).

Uninstalling "shared" may complain about breaking dependencies -
don't worry, "shared-compat" will fix this.
So you can forcefully uninstall "shared" and immediately install
"shared-compat", the worst that will happen is that a MySQL client
started in this tiny gap will not come up.

However, I cannot guarantee that installing "shared-compat" will n=
ot
complain about the existing symlinks of version 15, you may need t=
o
remove them manually.


HTH,
Jörg

--=20
Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@Sun.COM
Sun Microsystems GmbH, Komturstraße 18a, D-12099 Berlin
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB1610=
28


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: Problems After MySql 5.1.34

Hi Gary, all,


Gary Smith wrote:
> Johnny,=20
>=20
> Welcome to the hell that is php + apache + mysql. If you upgrade y=
our MySql (especially major versions 5.0 =3D> 5.1) you will also need=
to recompile php against the new MySql client libs. We've had very =
limited success trying to get it to work otherwise.

Which other approach(es) did you try?

>=20
> This is why you are receiving the error through PHP.
>=20
> Of course, I could be wrong, in which case I know people will proba=
bly jump me for it. If this is the case, please do as I would like t=
o be wrong here as it would make my compiling life easier every time =
I update MySql on all of my boxes.

Please see my other mail:

- Using "tar.gz", the old version of the client libs should not be
touched when you upgrade MySQL.

- Using RPMs, you need to install "shared-compat" (and not "shared") =
if
you are using application binaries built against older version(s).

If you found any problems with this, please tell us!


We are considering to change the contents of "shared-compat" RPMs, so
that they would not replace "shared" any more but just complement it
(bring just the old libs, not the current one).
The advantage would be that you then can install (or uninstall) them
without affecting your clients built against the current version,
especially those coming from MySQL directly.
However, this would mean a change in usage pattern for existing users=
,
and we are not yet sufficiently sure that our users would welcome it.


Regards,
Jörg

--=20
Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@Sun.COM
Sun Microsystems GmbH, Komturstraße 18a, D-12099 Berlin
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB1610=
28


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

RE: Problems After MySql 5.1.34

Gary wrote:

> Welcome to the hell that is php + apache + mysql. If you upgrade your
> MySql (especially major versions 5.0 => 5.1) you will also need to
> recompile php against the new MySql client libs. We've had very
> limited success trying to get it to work otherwise.

Well, you don't actually have to recompile PHP entirely, of course: just
its mysql.so extension.

@TS: Other than that, you basically need to recompile *everything* (or its
mysql dynamic libraries) when you upgrade MySQL. This includes Perl, btw;
so you'd need to build DBD:mysql as well (same for Python, etc).

Walter wrote:

> Any (major)upgrade of mysql client requires the dependent subsystem to
> upgrade also. Anything else would be careless since you do not know if the
> interface has changed.

Actually, you *do* know: that's what the changelog is for. :) When C
header changes are made, an upgrade is in order. If not, when upgrading
between minor versions, say, from 5.0.51 -> 5.0.67 (just an example), you
won't need to recompile all system-wide MySQL client extensions. I've done
this many times, without issue: you just need to be absolutely sure no
header changes were made (when in doubt, recompile).

I recently upgraded to 5.1.34 as well; and it was indeed a hell. :) It's
working just fine, but I spent several hours recompiling MySL client
stuff; without doing so, your apps will likely behave erratically, or just
segfault altogether.

This isn't a MySL hell exclusively, btw. You'll get the same issue
upgrading PostgreSQL, or BerkeleyDB, etc. It's just the nature of the
beast.

- Mark


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

RE: Problems After MySql 5.1.34

------=_NextPart_000_0042_01C9CF27.BF44A170
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Depends on your OS, I guess. On FreeBSD you can just go to the

'php5-extensions' port, run a 'make config', and deselect everything but

the MySQL extension. Then it will only build mysql.so for you. Very easy.

:)

=20

- Mark

=20

=20

From: Martin Gainty [mailto:mgainty@hotmail.com]=20
Sent: donderdag 7 mei 2009 15:15
To: admin@asarian-host.net; mysql@lists.mysql.com
Subject: RE: Problems After MySql 5.1.34

=20

Gary

this isnt mysql's fault that php has such abysmal build tools..try
requesting a web developer to simply download php and run the proprietary
binary tools
after a week of sleepless nights and endless searching for the right
dll/so/lib and endless searching for the right tools i guarantee they will
call no joy=20
and implement the webapp in Java!

Martin=20
______________________________________________=20
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung/Note de
d=E9ni et de confidentialit=E9

This message is confidential. If you should not be the intended receiver,
then we ask politely to report. Each unauthorized forwarding or
manufacturing of a copy is inadmissible. This message serves only for the
exchange of information and has no legal binding effect. Due to the easy
manipulation of emails we cannot take responsibility over the the contents.


Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
dient lediglich dem Austausch von Informationen und entfaltet keine
rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.


Ce message est confidentiel et peut =EAtre privil=E9gi=E9. Si vous n'=EAtes=
pas le
destinataire pr=E9vu, nous te demandons avec bont=E9 que pour satisfaire
informez l'exp=E9diteur. N'importe quelle diffusion non autoris=E9e ou la c=
opie
de ceci est interdite. Ce message sert =E0 l'information seulement et n'aura
pas n'importe quel effet l=E9galement obligatoire. =C9tant donn=E9 que les =
email
peuvent facilement =EAtre sujets =E0 la manipulation, nous ne pouvons accep=
ter
aucune responsabilit=E9 pour le contenu fourni.






> From: admin@asarian-host.net
> Subject: RE: Problems After MySql 5.1.34
> Date: Thu, 7 May 2009 12:57:42 +0000
> To: mysql@lists.mysql.com
>=20
> Gary wrote:
>=20
> > Welcome to the hell that is php + apache + mysql. If you upgrade your
> > MySql (especially major versions 5.0 =3D> 5.1) you will also need to
> > recompile php against the new MySql client libs. We've had very
> > limited success trying to get it to work otherwise.
>=20
> Well, you don't actually have to recompile PHP entirely, of course: just
> its mysql..so extension.
>=20
> @TS: Other than that, you basically need to recompile *everything* (or its
> mysql dynamic libraries) when you upgrade MySQL. This includes Perl, btw;
> so you'd need to build DBD:mysql as well (same for Python, etc).
>=20
> Walter wrote:
>=20
> > Any (major)upgrade of mysql client requires the dependent subsystem to
> > upgrade also. Anything else would be careless since you do not know if
the
> > interface has changed.
>=20
> Actually, you *do* know: that's what the changelog is for. :) When C
> header changes are made, an upgrade is in order. If not, when upgrading
> between minor versions, say, from 5.0.51 -> 5.0.67 (just an example), you
> won't need to recompile all system-wide MySQL client extensions. I've done
> this many times, without issue: you just need to be absolutely sure no
> header changes were made (when in doubt, recompile)..
>=20
> I recently upgraded to 5.1.34 as well; and it was indeed a hell. :) It's
> working just fine, but I spent several hours recompiling MySL client
> stuff; without doing so, your apps will likely behave erratically, or just
> segfault altogether.
>=20
> This isn't a MySL hell exclusively, btw. You'll get the same issue
> upgrading PostgreSQL, or BerkeleyDB, etc. It's just the nature of the
> beast.
>=20
> - Mark
>=20
>=20
> --=20
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dmgainty@hotmail.com
>=20

_____

Windows Live=99: Keep your life in sync. Check it out.
=
=20


------=_NextPart_000_0042_01C9CF27.BF44A170--

RE: Problems After MySql 5.1.34

Typically we see the problems with RH/Cent when you upgrade through those c=
hannels and then do an install of the 5.1.x series on top of that. I tried=
it about 9 months ago, so the details are fuzzy. I do know that in attemp=
ts to recover we extracted the RPM contents and tried to copy them manually=
to satisfy the dependency but in the end that didn't work for us for some =
reason.

We ended up just creating a new RPM for 5.1.x and then recompiling the depe=
ndent apps against that and storing all of them in our own repo for yum upd=
ate.

________________________________________
From: Joerg.Bruehe@Sun.COM [Joerg.Bruehe@Sun.COM]
Sent: Thursday, May 07, 2009 2:40 AM
To: Gary Smith
Cc: mysql@lists.mysql.com
Subject: Re: Problems After MySql 5.1.34

Hi Gary, all,


Gary Smith wrote:
> Johnny,
>
> Welcome to the hell that is php + apache + mysql. If you upgrade your My=
Sql (especially major versions 5.0 =3D> 5.1) you will also need to recompil=
e php against the new MySql client libs. We've had very limited success tr=
ying to get it to work otherwise.

Which other approach(es) did you try?

>
> This is why you are receiving the error through PHP.
>
> Of course, I could be wrong, in which case I know people will probably ju=
mp me for it. If this is the case, please do as I would like to be wrong h=
ere as it would make my compiling life easier every time I update MySql on =
all of my boxes.

Please see my other mail:

- Using "tar.gz", the old version of the client libs should not be
touched when you upgrade MySQL.

- Using RPMs, you need to install "shared-compat" (and not "shared") if
you are using application binaries built against older version(s).

If you found any problems with this, please tell us!


We are considering to change the contents of "shared-compat" RPMs, so
that they would not replace "shared" any more but just complement it
(bring just the old libs, not the current one).
The advantage would be that you then can install (or uninstall) them
without affecting your clients built against the current version,
especially those coming from MySQL directly.
However, this would mean a change in usage pattern for existing users,
and we are not yet sufficiently sure that our users would welcome it.


Regards,
Jörg

--
Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@Sun.COM
Sun Microsystems GmbH, Komturstraße 18a, D-12099 Berlin
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB161028


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgary@primeexalia.co=
m=

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

RE: Problems After MySql 5.1.34

You are right. I misspoke regarding mysql -> php -> apache hell. It happe=
ns anytime an interface changes. =20

________________________________________
From: Mark [admin@asarian-host.net]
Sent: Thursday, May 07, 2009 5:57 AM
To: mysql@lists.mysql.com
Subject: RE: Problems After MySql 5.1.34

Gary wrote:

> Welcome to the hell that is php + apache + mysql. If you upgrade your
> MySql (especially major versions 5.0 =3D> 5.1) you will also need to
> recompile php against the new MySql client libs. We've had very
> limited success trying to get it to work otherwise.

Well, you don't actually have to recompile PHP entirely, of course: just
its mysql.so extension.

@TS: Other than that, you basically need to recompile *everything* (or its
mysql dynamic libraries) when you upgrade MySQL. This includes Perl, btw;
so you'd need to build DBD:mysql as well (same for Python, etc).

Walter wrote:

> Any (major)upgrade of mysql client requires the dependent subsystem to
> upgrade also. Anything else would be careless since you do not know if th=
e
> interface has changed.

Actually, you *do* know: that's what the changelog is for. :) When C
header changes are made, an upgrade is in order. If not, when upgrading
between minor versions, say, from 5.0.51 -> 5.0.67 (just an example), you
won't need to recompile all system-wide MySQL client extensions. I've done
this many times, without issue: you just need to be absolutely sure no
header changes were made (when in doubt, recompile).

I recently upgraded to 5.1.34 as well; and it was indeed a hell. :) It's
working just fine, but I spent several hours recompiling MySL client
stuff; without doing so, your apps will likely behave erratically, or just
segfault altogether.

This isn't a MySL hell exclusively, btw. You'll get the same issue
upgrading PostgreSQL, or BerkeleyDB, etc. It's just the nature of the
beast.

- Mark


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgary@primeexalia.co=
m=

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: Problems After MySql 5.1.34 - THANKS

Thanks to everyone that offered all the valuable suggestions. SImply
replaced the shared-community with shared-compat and all seesm fine.
Will live with, or deal with, the missmatch in php libraries later, but
for now everything seems to work.

Thanks again to everyone that offered such detailed and helpful
suggestions :)

Gary Smith wrote:
> You are right. I misspoke regarding mysql -> php -> apache hell. It happens anytime an interface changes.
>
> ________________________________________
> From: Mark [admin@asarian-host.net]
> Sent: Thursday, May 07, 2009 5:57 AM
> To: mysql@lists.mysql.com
> Subject: RE: Problems After MySql 5.1.34
>
> Gary wrote:
>
>
>> Welcome to the hell that is php + apache + mysql. If you upgrade your
>> MySql (especially major versions 5.0 => 5.1) you will also need to
>> recompile php against the new MySql client libs. We've had very
>> limited success trying to get it to work otherwise.
>>
>
> Well, you don't actually have to recompile PHP entirely, of course: just
> its mysql.so extension.
>
> @TS: Other than that, you basically need to recompile *everything* (or its
> mysql dynamic libraries) when you upgrade MySQL. This includes Perl, btw;
> so you'd need to build DBD:mysql as well (same for Python, etc).
>
> Walter wrote:
>
>
>> Any (major)upgrade of mysql client requires the dependent subsystem to
>> upgrade also. Anything else would be careless since you do not know if the
>> interface has changed.
>>
>
> Actually, you *do* know: that's what the changelog is for. :) When C
> header changes are made, an upgrade is in order. If not, when upgrading
> between minor versions, say, from 5.0.51 -> 5.0.67 (just an example), you
> won't need to recompile all system-wide MySQL client extensions. I've done
> this many times, without issue: you just need to be absolutely sure no
> header changes were made (when in doubt, recompile).
>
> I recently upgraded to 5.1.34 as well; and it was indeed a hell. :) It's
> working just fine, but I spent several hours recompiling MySL client
> stuff; without doing so, your apps will likely behave erratically, or just
> segfault altogether.
>
> This isn't a MySL hell exclusively, btw. You'll get the same issue
> upgrading PostgreSQL, or BerkeleyDB, etc. It's just the nature of the
> beast.
>
> - Mark
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=gary@primeexalia.com
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=lists@openenterprise.ca
>
>

--
_____________________________________________
Johnny Stork

Open Enterprise Solutions
"Empowering Business With Open Solutions"
http://www.openenterprise.ca

Mountain Hosting
"Secure Hosting Solutions for Business"
http://www.mountainhosting.ca


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org