MYSQL server has gone away

[time2see]

I'm getting this error when I click on a contact at the bottom of thier details
Error running count query for Contact List: Query Failed SELECT count(*) c FROM leads where ( leads.contact_id= 'b99ba2fa-028a-f3bd-8056-496d29ec455b' AND leads.deleted=0) AND leads.deleted=0 )::MySQL error 2006: MySQL server has gone away

Running version 5.2.0 CE and have inet googlemap 1.4 as an extra module loaded.

[daniel.passarini]

Probaly, your MySQL server has timed out and closed the connection. But does it occur only with leads?

[letrium]

it seems that is the bad query

[daniel.passarini]

it seems that is the bad query

hum.. i dont think so. Except for the last parenthesis, the query works perfectly. Even if was the query, it should display another error message. Try this query directly in a mysql console or any other IDE. Does this problem occurs in any other part of the system??

[tamaravilhosa]

Hi

When I try to send Queued Emails the following error message appears:

1Retrieving record by id emails:deab2b25-0185-a884-a911-4977bbf2a435 found Query Failed:SELECT emails.* FROM emails WHERE emails.id = 'deab2b25-0185-a884-a911-4977bbf2a435' LIMIT 0,1::MySQL error 2006: MySQL server has gone away

How to solve it?

Tks,
Tamara

[time2see]

It happens with contacts and Accounts.
Every now and again it is ok though....strainge?
Sugar is installed on our hosted webserver if that makes a difference?

[Angel]

It sounds like the MySQL server might be crashing from time to time. Perhaps it depends on how much data the query is returning.

Have you run any diagnostics on the server side to make sure everything is working fine there?

[time2see]

No I have not, what is the best way to do that/

[eggsurplus]

I've had this issue in the past and solved it with this post from the comments at http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

This also happens when you use compression of the mysql connection handler and due to some limitations of mysql server which cannot return easily an error message. Instead, it just kills the connection without a message. So turn off the compression and remove the 'quick' option from /etc/my.cnf if you observe lost connections to get the message.

Read the answer from Michael Widenius:
http://bugs.mysql.com/bug.php?id=1011

<quote>
[19 Aug 2003 15:41] Michael Widenius

Sorry about the last bug entry, but it was not true. Sinisa had a patch pending but I
didn't approve of it as it didn't solve this problem for all cases.

This problem is already documented in the manual section
'MySQL server has gone away Error':

-----
You can also get these errors if you send a query to the server that is
incorrect or too large. If mysqld gets a packet that is too large.
or out of order, it assumes that something has gone wrong with the client and
closes the connection.
-----

We fixed this problem in 4.0 for not compressed packets but for
compressed packets it's VERY hard to fix it without having to allocate
a buffer bigger than max_allowed_packet, which would defeat the
purpose of this flag. Ane problem is that to be able to skip the
packet we have to decompress all packets in the stream and this would
make it easy for someone to force the server to allocate a lot of big
packets even if the MySQL administrator has forbidden this.

I looked into fixing this but didn't come up with a good way to to fix
it without a major amount of work (8-16 hours).

As we have more important things on our todo (this is not a serious
bug) we have to put this on hold for now and look at fixing this in
4.1 or 5.0.

The easy way to avoid this problem is to ensure that max_allowed_packet is set bigger in
the mysqld server than in the client and that all clients uses the same value for
max_allowed_packet.

Regards,
Monty
</quote>