"Unable to save result set" errors?

Anon

Hi folks,

This one has me stumped. Our PHP and MYSQL 3.22.29 website has been working flawlessly for over 5 months without one incident. Suddenly all our php scripts that make use of extracting data out of our mysql database started having problems and spewing out the following errors:

-------+----------------
Warning: MySQL: Unable to save result set in /usr/local/apache/htdocs/ne/index.php3 on line 26
--------+-------------------

Now I have confirmed the following:

1) Not a coding issue. Like i said, this is widespread accross all our php scripts that make use of a mysql database. We havent made any changes that would affect the output.

2) I am able to, via the command line "mysql" option, do a basic query and extract info from the database i.e. SELECT * FROM MEMBERS WHERE USER = 'BLAH' ;

3) Not an issue with the webserver. We run apache 1.3.9 with PHP 3.0.16. Our webserver error log does not indicate any issues

4) Does not seem to be an issue with Mysql as the error log does not show any discrepancies.

I've attempted to search for old posts and documentation but ended up with empty hands. Does anyone have any pointers. I really appreciate your help.

Vinnie

brandonschnell

1) this can be a problem with the mysql libs php is using (the php module/exe file might be damaged)

2) the drive that mysql is on might be out of space

3) check the mysql db tables and make sure its fine. i've run mysql on a bad hard drive before and it can do funky things in php.

http://www.mysql.com/doc/R/E/REPAIR_TABLE.html

the error indicates that mysql server isn't sending what the php mysql libs are expecting to see.

Anon

Aha! Found out one table in my database was corrupted. I ran the following command :

$PATH/mysql/bin/myisamchk -r <table_name>

It it then fixed all the issues I had. For those who use this fix next time, MAKE SURE YOU RESTART MYSQL or you'll be getting some funky data from your queries to the table that was just fixed.

Thanks again!

Anon

hi,

i had the same problem once. it was becos the result of the query was too large, so if you have any query which fetches too much data, trim them down to be more specific

steve

yaroslav

and may be this helps too?

I upgraded to PHP 4, and now mysql keeps telling me "Warning: MySQL: Unable to save result set in ...". What's up?

Most likely what has happened is, PHP 4 was compiled with the '--with-mysql' option, without specifying the path to MySQL. This means PHP is using its built-in MySQL client library. If your system is running applications, such as PHP 3 as a concurrent Apache module, or auth-mysql, that use other versions of MySQL clients, then there is a conflict between the two differing versions of those clients.

Recompiling PHP 4, and adding the path to MySQL to the flag, '--with-mysql=/your/path/to/mysql' usually solves the problem.