>> Hello Nuno, >> >> Tuesday, July 26, 2005, 8:53:33 PM, you wrote: >> >> >>>[EMAIL PROTECTED] wrote: >>>(...) >>> >>>>When i try to execute the following query >>> >>>(...) >>> >>>>i get this error: >>>> >>>>ERROR 2006 (HY000): MySQL server has gone away >>>>No connection. Trying to reconnect... >>>>Connection id: 6 >>>>Current database: test >>>>ERROR 2013 (HY000): Lost connection to MySQL server during query >>>> >>>> >>>>but if i change my query to this one everything is fine >>>>SELECT >>>> COUNT(DISTINCT field1) as value1, >>>> CONCAT(field2, '') as value2 >>>>FROM >>>> table1, >>>> table2 >>>>GROUP >>>> BY value2 >>>> >>>>(here CONCAT(field2, '-') is replaced with CONCAT(field2, '') ) >>>> >>>>does anyone know what the matter is? >> >> >>>Did you try to make the first query for a second time, when you execute >>>the second query? It seems that the server abords or closes the >>>connection meanwhile. Did you waited too long to write/send the query? >> >> Each time i try to execute the 'buggy' query the server crashet. >> It crashes IMMEDIATELY (without any human-perceptible timeout) > > Can you provide the output of the logs? ---- mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.
key_buffer_size=16777216 read_buffer_size=258048 max_used_connections=1 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 050727 10:39:41 mysqld restarted ---- "It is possible that mysqld could use up to 92783 K bytes of memory." I don't think the problem has anything to do with available memory size for a) there is enough free memory b) if not there is a good piece of swap c) even if i suggest the problem is in insufficient memory it is not clear why so much is required for execution of such a simple query > >>>Check this for more help >>>http://dev.mysql.com/doc/mysql/en/gone-away.html > > Does following the steps in that page helps? > >>>Try this query and output the result >> >> >>>SHOW VARIABLES LIKE '%time%'; >> >> mysql> SHOW VARIABLES LIKE '%time%'; >> +--------------------------+-------------------+ >> | Variable_name | Value | >> +--------------------------+-------------------+ >> | connect_timeout | 5 | >> | datetime_format | %Y-%m-%d %H:%i:%s | >> | delayed_insert_timeout | 300 | >> | flush_time | 0 | >> | innodb_lock_wait_timeout | 50 | >> | interactive_timeout | 28800 | >> | long_query_time | 10 | >> | net_read_timeout | 30 | >> | net_write_timeout | 60 | >> | slave_net_timeout | 3600 | >> | slow_launch_time | 2 | >> | sync_replication_timeout | 0 | >> | system_time_zone | MSD | >> | time_format | %H:%i:%s | >> | time_zone | SYSTEM | >> | wait_timeout | 28800 | >> +--------------------------+-------------------+ >> 16 rows in set (0.00 sec) > > The variables seems OK. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
