I didn't find any similar problem in bugs.mysql.com. To exclude inconsistence
with Apache compile PHP as a command line program and check your queries. May
be you should turn to PHP developers.
Bogdan TARU [EMAIL PROTECTED] wrote:
Hello,
I recently upgraded the MySQL server from 4.0.15 to 4.1.7, without
significant problems. But I continued to use PHP-4.3.9 linked against
the old MySQL 4.0.15 on the webservers for some time. Everything went
ok, up until the point when I tried linking PHP-4.3.9 against
MySQL-4.1.7. After starting the new Apache/PHP (ldd httpd shows
'/usr/local/mysql-4.1.7/lib/mysql/libmysqlclient.so.14'), I get a
whole lot of Segmentation Faults in the Apache error log. Also, I
have noticed in the PHP error log that a lot of MySQL queries aren't
succesfully made (usually the error message is 'unable to save result
set').
Running those queries by hand, in a mysql console yields a valid
row(s), but the table header is completely messed up. Traced the
problem to those queries being cached, so I ran a 'reset query
cache'. Then those queries executed successfully, but I'm still
getting Apache segmentation faults.
Here are some details:
On the MySQL server I have FreeBSD 4.10-STABLE running. MySQL 4.1.7
was compiled from ports with the command line:
make DB_DIR=/db/mysql WITH_LINUXTHREADS=yes OVERWRITE_DB=no
BUILD_OPTIMIZED=yes BUILD_STATIC=yes
The webservers are running FreeBSD 4.10-STABLE as well, Apache/1.3.33
having PHP-4.3.9 compiled as a static module. PHP's configure line
is:
./configure --prefix=/usr/local/php --enable-track-vars
--enable-trans-sid --disable-path-info-check --enable-memory-limit
--without-pear --with-apache=../apache_1.3.33
--with-config-file-path=/usr/local/apache/conf/ --enable-safe-mode
--with-curl --with-mysql=/usr/local/mysql-4.1.7
--with-jpeg-dir=/usr/local/jpeg-6b/
--with-png-dir=/usr/local/libpng-1.2.5/
--with-ttf --with-pdflib --with-gd --enable-gd-native-ttf
--with-zlib-dir=/usr
Any idea what could lead to this incompatibility between PHP using
the 4.1.7 MySQL library and the MySQL 4.1.7 server, incompatibility
which doesn't exist between the same MySQL 4.1.7 server and PHP
linked against MySQL 4.0.15 library?
Thanks,
bogdan
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]