Hello.
Have a look here:
http://dev.mysql.com/doc/refman/5.0/en/communication-errors.html
Doug Dalton wrote:
>
> I found a log error after turning on warning running the server manually:
>
> 051215 17:32:42 [Warning] Aborted connection 3961 to db: 'db' user:
> 'user' host: `clie
I found a log error after turning on warning running the server manually:
051215 17:32:42 [Warning] Aborted connection 3961 to db: 'db' user:
'user' host: `client' (Got timeout reading communication packets)
Any idea what this error is ? the interfaces show no errors from a
network perspect
Gleb,
I watched the server during this error, the server continued to run...
it didnt crash... and no warning or logged error?
Regards,
Doug
Doug Dalton wrote:
Gleb Paharenko wrote:
Hello.
Check that MySQL doesn't die during the query. See:
http://dev.mysql.com/doc/refman/5.0/en/gone-a
Gleb Paharenko wrote:
Hello.
Check that MySQL doesn't die during the query. See:
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html
Gleb,
I should mention that I get no log errors and I even have it set to warn
does this mean mysql could die and not log the error? I have gone
th
Hello.
Check that MySQL doesn't die during the query. See:
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html
oug Dalton wrote:
> I am running mysql 4.1.13 on Suse 10 and I get an error on a simple
> select query, I have checked the threads on lost connection and my
> connection
I am running mysql 4.1.13 on Suse 10 and I get an error on a simple
select query, I have checked the threads on lost connection and my
connection times as well as making sure my calls are all made from non
forking processes etc... I cannot seem to resolve this error? can
someone point me in
