Ok had to move a few of our sites around and for some reason now with software that worked fine before is getting errors now..

This error is from phpAdsNew from http://sourceforge.net/projects/phpadsnew
Both 2 beta 6.1 and 2 beta 5 are giving this error.

MySQL-Error:
Lost connection to MySQL server during query

SQL Query:
SELECT count(*) as qnt FROM adviews WHERE t_stamp >= 20020122000000 AND t_stamp < 20020123000000


Also in VBuliiten gives this error. With vBulletin 2.2.0 or vBulletin 2.2.1

Database error in vBulletin 2.2.0:

Invalid SQL: SELECT findword,replaceword FROM replacement WHERE replacementsetid IN(-1,'1') ORDER BY replacementsetid DESC,replacementid DESC
mysql error: Lost connection to MySQL server during query

mysql error number: 2013

Date: Tuesday 22nd of January 2002 01:08:29 AM


I am at a loss here as to what couldbe wronf php and mySQL seem to work right for every thing else but ging problems on this.

This has PHP 4.1.1 and mySQL MySQL 3.23.47 all on FreeBSD 4.3

Any ideas or help would be great. I am not the best with mySQL and php but this just seem odd.

Try issuing those queries by hand. If it works correctly, the problem is with PHP I guess. If not, it is the MySQL server.

it was MySQL 3.23.47 i think there is some thing up with the ver. tested the stuff just using anther server and works great. So going to downgrade to 3.23.39 and see how it goes now.. :(

if those are big tables, mysql may be timing out getting the results. If this is the problem it probably has to deal with a big table with lots of rows and a CPU that just can't handle it. I highly doubt that is the problem but it could be. Its something to try i guess.

The problem was in mySQL we had the new ver. from mySQL.com and installed it on FreeBSD 4.2 and would not work right. So we downgraded to the same ver. in Plesk 2.0 that we use on FreeBSD and worked great.


Had know idea a new ver. of mySQL qould not work with just 2 releases back on FreeBSD..

Did you dump the data bases (mysqldump) or did you just copy over the files? I had a similar problem back when we upgraded mysql and I had to go back and dump all the databases from the old mysql and load them back into the new mysql. That worked.

Did not try that.. I will see if that works next.. :)