Hi there,

I'm having trouble with phpMyAdmin 2.5.7-pl1 (upgraded from 2.5.6 with same problems) on RH9, mysql 4.0.18 and php 4.3.6 + apache2.

Whenever I try to browse a table it comes up with 'Action Cancelled' or a 'Page Not Found' error (IE6 this is). Infact opening sql.php in a new window gives the same errors. However when i tried selectively removing elements from the query string it worked, understandably giving me phpmyadmin errors, such as no db definded or no sql query. I added each element back in turn. However when i put in 'sql_query=SELECT' (invalid sql statement i know) it gave me the PMA sql error screen (naturally!) but when i added in *s and and spaces (make a proper statement) it when back to action cancelled etc again.

Additionally this is giving segmentation faults (11) in my apache error log.

Everything else is working fine - mysql works from commandline and monitor, php is working great with other sites hosted on the box - its only now I want to use the database I've got these problems!

Any help would be greatly appreciated! Is anybody else having / had these problems?

Many thanks,

don

Is the database/table too big? Try to run REPAIR and OPTIMIZE commands on the tables..

Thanks for that Mike_R, I tried repairing and optimizing but i'm afraid I still get the same problems!

I had to use mysql monitor as in PMA they both seem to use sql.php so I got the same Action Cancelled / Page Cannot be Displayed page again! :bawling: Even from the sql query box didn't work..

Still no joy!

I've been sifting thru the PMA code, and narrowed the problem down to a function using mysql_fetch_field() - something which apparently had the potential to cause a segfault according to bug#23490 on the php bug site.

The bug report doesn't seem very conclusive to me (status is 'bogus'?) but I have upgraded mysql to 4.0.20 and will try recompiling php against this... and see what happens!

don

This seems to have cracked it!! I recompiled php against the mysql 4.0.20 libraries and headers and it all works fine now.

According to the bug report there is a mismatch in the MYSQL_FIELD structure between 3.23.x and 4.0.x.

I did have trouble getting PHP to use the correct libraries tho! When i specified the correct path to mysql (--with-mysql=/usr/include/mysql) it didn't accept it - so I found a guy on another forum saying just use "/usr" - so I did & it worked!!

I hope this helps someone else.. although very few people seem to have the problem! Maybe everyone else compiles PHP in the correct way first time.. or they don't use RPMs!

Have fun,

don