Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
2014/1/7 h...@tbbs.net 2014/01/06 17:07 +0100, Reindl Harald what about look in the servers logfiles most likely max_allowed_packet laughable low Is this then, too, likly when the server and the client are the same machine? I left this out, that it only then happens when the client has been idle, and right afterwards the client repeats the request and all goes well. The message is no more than an irritatind break between request and fulfillment. Hello, That happens when you're trying to re-use an existing connection which wasn't properly closed and as you said, it's been idle. When you repeat the operation, the thread is created again and thus everything goes normal. Review the following variables wait_timeout net_write_timeout net_read_timeout Manu
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
2014/01/06 17:07 +0100, Reindl Harald what about look in the servers logfiles most likely max_allowed_packet laughable low Is this then, too, likly when the server and the client are the same machine? I left this out, that it only then happens when the client has been idle, and right afterwards the client repeats the request and all goes well. The message is no more than an irritatind break between request and fulfillment. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
ERROR 2013 (HY000): Lost connection to MySQL server during query
Now that I installed 5.6.14 on our Vista machine, when using mysql I often see that error-message, which under 5.5.8 I never saw. What is going on? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Am 06.01.2014 15:36, schrieb h...@tbbs.net: Now that I installed 5.6.14 on our Vista machine, when using mysql I often see that error-message, which under 5.5.8 I never saw. What is going on? what about look in the servers logfiles most likely max_allowed_packet laughable low signature.asc Description: OpenPGP digital signature
Lost connection to MySQL server - need help.
Hello, I got a strange problem related to a production server. It has been working OK for months, but yesterday it start to fail. There are several batch scripts using the database in addition to a web application using it. The php scripts running in batch mode began to get: mysql_connect(): Lost connection to MySQL server at 'reading initial communication packet', system error: 111 I stopped the server and restarted it and everything seems to work OK for hours but when the load start to increase, the errors begin to appear again. Today I noticed that after I starte phpMyAdmin and selected one of the databases, phpMyAdmin was hanging and the batch scripts began to fail again. Seems like the server does not handle much load anymore. What's strange is the memory usage. The server is a quad core cpu with 48 Gb memory, where 28 Gb is allocated to innodb (we mostly use innodb). But when using top command, I noticed this: VIRT: 33.9g RES: 9.4g SWAP: 23g at this time over 11G memory is free. vm.swappiness is set to 0. I find it strange that the server is not able to use physical memory but use swap instead. The amount of cpu time used for swapping is rather high during sql queries. The amount of RESident memory may increase slowly over time but very slowly (it can take hours before it increase to 20+ Gb). [PS: I also got a MySQL server running at a dedicated host at home, where the it seem to use the memory as I except it to use: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ SWAP DATA COMMAND 1462 mysql 20 0 30.0g 27g 3900 S 0.3 87.3 2633:14 844m 29g mysqld ] I would like to have some suggestions what I can do to solve this problem. I have google'd it but found nothing that seem to solve my case. Server: OS: Debian 6 MySQL: 5.1.61-0+squeeze1 my.cnf: # # The MySQL database server configuration file. # [client] port= 3306 socket = /var/run/mysqld/mysqld.sock # Here is entries for some specific programs # The following values assume you have at least 32M ram # This was formally known as [safe_mysqld]. [mysqld_safe] socket = /var/run/mysqld/mysqld.sock nice= 0 [mysqld] # # * Basic Settings # user= mysql pid-file= /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port= 3306 basedir = /usr datadir = /database/mysql tmpdir = /tmp language= /usr/share/mysql/english skip-external-locking # # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. bind-address= 127.0.0.1 ## All applications use 127.0.0.1 when connectiong to the db. # # * Fine Tuning # #key_buffer = 16M max_allowed_packet = 64M thread_stack= 192K #thread_cache_size = 8 # This replaces the startup script and checks MyISAM tables if needed # the first time they are touched myisam-recover = BACKUP # # * Query Cache Configuration # query_cache_limit = 1M # # The following can be used as easy to replay backup logs or for replication. # note: if you are setting up a replication slave, see README.Debian about # other settings you may need to change. #server-id = 1 #log_bin= /var/log/mysql/mysql-bin.log expire_logs_days= 10 max_binlog_size = 100M #binlog_do_db = include_database_name #binlog_ignore_db = include_database_name # # * InnoDB # # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. # Read the manual for more InnoDB related options. There are many! thread_cache_size = 192 table_cache = 768 ## key_buffer = 64M ## sort_buffer_size = 256K ## read_buffer_size = 256K ## read_rnd_buffer_size = 256K tmp_table_size=32M max_heap_table_size=32M query_cache_size=128M query_cache_type=2 innodb_open_files=1000 innodb_buffer_pool_size = 28G innodb_additional_mem_pool_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_support_xa = 0 innodb_lock_wait_timeout = 50 ## innodb_flush_method=O_DIRECT innodb_log_files_in_group = 2 ## innodb_log_file_size = 128M innodb_log_buffer_size = 8M innodb_thread_concurrency = 14 innodb_file_per_table max_connections = 100 binlog_cache_size = 1M sort_buffer_size= 16M join_buffer_size= 16M ft_min_word_len = 1 ft_max_word_len = 84 ft_stopword_file= '' default_table_type = InnoDB key_buffer = 2G read_buffer_size= 2M read_rnd_buffer_size= 16M bulk_insert_buffer_size = 64M myisam_sort_buffer_size = 128M myisam_max_sort_file_size = 10G myisam_max_extra_sort_file_size = 10G myisam_repair_threads = 1 myisam_recover [mysqldump] quick quote-names max_allowed_packet = 16M [mysql] #no-auto-rehash # faster start of mysql but no tab
Re: Lost connection to MySQL server - need help.
You might want to comment bind-address= 127.0.0.1 in your my.cnf and restart mysql server. On 12/10/13 10:49, Jørn Dahl-Stamnes wrote: Hello, I got a strange problem related to a production server. It has been working OK for months, but yesterday it start to fail. There are several batch scripts using the database in addition to a web application using it. The php scripts running in batch mode began to get: mysql_connect(): Lost connection to MySQL server at 'reading initial communication packet', system error: 111 I stopped the server and restarted it and everything seems to work OK for hours but when the load start to increase, the errors begin to appear again. Today I noticed that after I starte phpMyAdmin and selected one of the databases, phpMyAdmin was hanging and the batch scripts began to fail again. Seems like the server does not handle much load anymore. What's strange is the memory usage. The server is a quad core cpu with 48 Gb memory, where 28 Gb is allocated to innodb (we mostly use innodb). But when using top command, I noticed this: VIRT: 33.9g RES: 9.4g SWAP: 23g at this time over 11G memory is free. vm.swappiness is set to 0. I find it strange that the server is not able to use physical memory but use swap instead. The amount of cpu time used for swapping is rather high during sql queries. The amount of RESident memory may increase slowly over time but very slowly (it can take hours before it increase to 20+ Gb). [PS: I also got a MySQL server running at a dedicated host at home, where the it seem to use the memory as I except it to use: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ SWAP DATA COMMAND 1462 mysql 20 0 30.0g 27g 3900 S 0.3 87.3 2633:14 844m 29g mysqld ] I would like to have some suggestions what I can do to solve this problem. I have google'd it but found nothing that seem to solve my case. Server: OS: Debian 6 MySQL: 5.1.61-0+squeeze1 my.cnf: # # The MySQL database server configuration file. # [client] port= 3306 socket = /var/run/mysqld/mysqld.sock # Here is entries for some specific programs # The following values assume you have at least 32M ram # This was formally known as [safe_mysqld]. [mysqld_safe] socket = /var/run/mysqld/mysqld.sock nice= 0 [mysqld] # # * Basic Settings # user= mysql pid-file= /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port= 3306 basedir = /usr datadir = /database/mysql tmpdir = /tmp language= /usr/share/mysql/english skip-external-locking # # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. bind-address= 127.0.0.1 ## All applications use 127.0.0.1 when connectiong to the db. # # * Fine Tuning # #key_buffer = 16M max_allowed_packet = 64M thread_stack= 192K #thread_cache_size = 8 # This replaces the startup script and checks MyISAM tables if needed # the first time they are touched myisam-recover = BACKUP # # * Query Cache Configuration # query_cache_limit = 1M # # The following can be used as easy to replay backup logs or for replication. # note: if you are setting up a replication slave, see README.Debian about # other settings you may need to change. #server-id = 1 #log_bin= /var/log/mysql/mysql-bin.log expire_logs_days= 10 max_binlog_size = 100M #binlog_do_db = include_database_name #binlog_ignore_db = include_database_name # # * InnoDB # # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. # Read the manual for more InnoDB related options. There are many! thread_cache_size = 192 table_cache = 768 ## key_buffer = 64M ## sort_buffer_size = 256K ## read_buffer_size = 256K ## read_rnd_buffer_size = 256K tmp_table_size=32M max_heap_table_size=32M query_cache_size=128M query_cache_type=2 innodb_open_files=1000 innodb_buffer_pool_size = 28G innodb_additional_mem_pool_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_support_xa = 0 innodb_lock_wait_timeout = 50 ## innodb_flush_method=O_DIRECT innodb_log_files_in_group = 2 ## innodb_log_file_size = 128M innodb_log_buffer_size = 8M innodb_thread_concurrency = 14 innodb_file_per_table max_connections = 100 binlog_cache_size = 1M sort_buffer_size= 16M join_buffer_size= 16M ft_min_word_len = 1 ft_max_word_len = 84 ft_stopword_file= '' default_table_type = InnoDB key_buffer = 2G read_buffer_size= 2M read_rnd_buffer_size= 16M bulk_insert_buffer_size = 64M myisam_sort_buffer_size = 128M myisam_max_sort_file_size = 10G myisam_max_extra_sort_file_size = 10G myisam_repair_threads
Re: Lost connection to MySQL server - need help.
On Saturday 12 October 2013 12:01, nixofortune wrote: You might want to comment bind-address= 127.0.0.1 in your my.cnf and restart mysql server. It does not explain why it works under low load and not under high load. However, I seem to have found something. When I started phpMyAdmin and selected one of the database, the server went away again and I found this in /var/log/syslog: Oct 12 11:53:33 cebycny mysqld: 131012 11:53:33 InnoDB: Assertion failure in thread 140182892447488 in file ../../../storage/innobase/handler/ha_innodb.cc line 8066 Oct 12 11:53:33 cebycny mysqld: InnoDB: Failing assertion: auto_inc 0 Oct 12 11:53:33 cebycny mysqld: InnoDB: We intentionally generate a memory trap. Oct 12 11:53:33 cebycny mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com. Oct 12 11:53:33 cebycny mysqld: InnoDB: If you get repeated assertion failures or crashes, even Oct 12 11:53:33 cebycny mysqld: InnoDB: immediately after the mysqld startup, there may be Oct 12 11:53:33 cebycny mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to Oct 12 11:53:33 cebycny mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html Oct 12 11:53:33 cebycny mysqld: InnoDB: about forcing recovery. Oct 12 11:53:33 cebycny mysqld: 09:53:33 UTC - mysqld got signal 6 ; Oct 12 11:53:33 cebycny mysqld: This could be because you hit a bug. It is also possible that this binary Oct 12 11:53:33 cebycny mysqld: or one of the libraries it was linked against is corrupt, improperly built, Oct 12 11:53:33 cebycny mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Oct 12 11:53:33 cebycny mysqld: We will try our best to scrape up some info that will hopefully help Oct 12 11:53:33 cebycny mysqld: diagnose the problem, but since we have already crashed, Oct 12 11:53:33 cebycny mysqld: something is definitely wrong and this may fail. Oct 12 11:53:33 cebycny mysqld: Oct 12 11:53:33 cebycny mysqld: key_buffer_size=2147483648 Oct 12 11:53:33 cebycny mysqld: read_buffer_size=2097152 Oct 12 11:53:33 cebycny mysqld: max_used_connections=8 Oct 12 11:53:33 cebycny mysqld: max_threads=100 Oct 12 11:53:33 cebycny mysqld: thread_count=2 Oct 12 11:53:33 cebycny mysqld: connection_count=2 Oct 12 11:53:33 cebycny mysqld: It is possible that mysqld could use up to Oct 12 11:53:33 cebycny mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3941387 K bytes of memory Oct 12 11:53:33 cebycny mysqld: Hope that's ok; if not, decrease some variables in the equation. Oct 12 11:53:33 cebycny mysqld: Oct 12 11:53:33 cebycny mysqld: Thread pointer: 0x7f7f1bf997c0 Oct 12 11:53:33 cebycny mysqld: Attempting backtrace. You can use the following information to find out Oct 12 11:53:33 cebycny mysqld: where mysqld died. If you see no messages after this, something went Oct 12 11:53:33 cebycny mysqld: terribly wrong... Oct 12 11:53:33 cebycny mysqld: stack_bottom = 7f7edf81fe88 thread_stack 0x3 Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7f7edff62b59] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x483) [0x7f7edfd774a3] Oct 12 11:53:33 cebycny mysqld: /lib/libpthread.so.0(+0xeff0) [0x7f7edf4c9ff0] Oct 12 11:53:33 cebycny mysqld: /lib/libc.so.6(gsignal+0x35) [0x7f7eddf6c1b5] Oct 12 11:53:33 cebycny mysqld: /lib/libc.so.6(abort+0x180) [0x7f7eddf6efc0] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(ha_innobase::innobase_peek_autoinc()+0x8f) [0x7f7edfe1fa2f] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(ha_innobase::info_low(unsigned int, bool)+0x18f) [0x7f7edfe2524f] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(ha_innobase::update_create_info(st_ha_create_information*)+0x29) [0x7f7edfe256b9] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(+0x49e3dc) [0x7f7edfd953dc] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(mysqld_show_create(THD*, TABLE_LIST*)+0x7a8) [0x7f7edfd9d388] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x184a) [0x7f7edfc7cb0a] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x3fb) [0x7f7edfc80dbb] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x115a) [0x7f7edfc81f2a] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(do_command(THD*)+0xea) [0x7f7edfc8285a] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(handle_one_connection+0x235) [0x7f7edfc74435] Oct 12 11:53:33 cebycny mysqld: /lib/libpthread.so.0(+0x68ca) [0x7f7edf4c18ca] Oct 12 11:53:33 cebycny mysqld: /lib/libc.so.6(clone+0x6d) [0x7f7ede00992d] Oct 12 11:53:33 cebycny mysqld: Oct 12 11:53:33 cebycny mysqld: Trying to get some variables. Oct 12 11:53:33 cebycny mysqld: Some pointers may be invalid and cause the dump to abort. Oct 12 11:53:33 cebycny mysqld: Query (7f7f1c0dcbc0): SHOW CREATE TABLE `calculation` Oct 12
Re: Lost connection to MySQL server - need help.
Could be a crash related to innodb data dictionary being out of sync. Could be a bug. http://bugs.mysql.com/bug.php?id=55277 On 12 Oct 2013 11:21, Jørn Dahl-Stamnes sq...@dahl-stamnes.net wrote: On Saturday 12 October 2013 12:01, nixofortune wrote: You might want to comment bind-address= 127.0.0.1 in your my.cnf and restart mysql server. It does not explain why it works under low load and not under high load. However, I seem to have found something. When I started phpMyAdmin and selected one of the database, the server went away again and I found this in /var/log/syslog: Oct 12 11:53:33 cebycny mysqld: 131012 11:53:33 InnoDB: Assertion failure in thread 140182892447488 in file ../../../storage/innobase/handler/ha_innodb.cc line 8066 Oct 12 11:53:33 cebycny mysqld: InnoDB: Failing assertion: auto_inc 0 Oct 12 11:53:33 cebycny mysqld: InnoDB: We intentionally generate a memory trap. Oct 12 11:53:33 cebycny mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com. Oct 12 11:53:33 cebycny mysqld: InnoDB: If you get repeated assertion failures or crashes, even Oct 12 11:53:33 cebycny mysqld: InnoDB: immediately after the mysqld startup, there may be Oct 12 11:53:33 cebycny mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to Oct 12 11:53:33 cebycny mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html Oct 12 11:53:33 cebycny mysqld: InnoDB: about forcing recovery. Oct 12 11:53:33 cebycny mysqld: 09:53:33 UTC - mysqld got signal 6 ; Oct 12 11:53:33 cebycny mysqld: This could be because you hit a bug. It is also possible that this binary Oct 12 11:53:33 cebycny mysqld: or one of the libraries it was linked against is corrupt, improperly built, Oct 12 11:53:33 cebycny mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Oct 12 11:53:33 cebycny mysqld: We will try our best to scrape up some info that will hopefully help Oct 12 11:53:33 cebycny mysqld: diagnose the problem, but since we have already crashed, Oct 12 11:53:33 cebycny mysqld: something is definitely wrong and this may fail. Oct 12 11:53:33 cebycny mysqld: Oct 12 11:53:33 cebycny mysqld: key_buffer_size=2147483648 Oct 12 11:53:33 cebycny mysqld: read_buffer_size=2097152 Oct 12 11:53:33 cebycny mysqld: max_used_connections=8 Oct 12 11:53:33 cebycny mysqld: max_threads=100 Oct 12 11:53:33 cebycny mysqld: thread_count=2 Oct 12 11:53:33 cebycny mysqld: connection_count=2 Oct 12 11:53:33 cebycny mysqld: It is possible that mysqld could use up to Oct 12 11:53:33 cebycny mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3941387 K bytes of memory Oct 12 11:53:33 cebycny mysqld: Hope that's ok; if not, decrease some variables in the equation. Oct 12 11:53:33 cebycny mysqld: Oct 12 11:53:33 cebycny mysqld: Thread pointer: 0x7f7f1bf997c0 Oct 12 11:53:33 cebycny mysqld: Attempting backtrace. You can use the following information to find out Oct 12 11:53:33 cebycny mysqld: where mysqld died. If you see no messages after this, something went Oct 12 11:53:33 cebycny mysqld: terribly wrong... Oct 12 11:53:33 cebycny mysqld: stack_bottom = 7f7edf81fe88 thread_stack 0x3 Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7f7edff62b59] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x483) [0x7f7edfd774a3] Oct 12 11:53:33 cebycny mysqld: /lib/libpthread.so.0(+0xeff0) [0x7f7edf4c9ff0] Oct 12 11:53:33 cebycny mysqld: /lib/libc.so.6(gsignal+0x35) [0x7f7eddf6c1b5] Oct 12 11:53:33 cebycny mysqld: /lib/libc.so.6(abort+0x180) [0x7f7eddf6efc0] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(ha_innobase::innobase_peek_autoinc()+0x8f) [0x7f7edfe1fa2f] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(ha_innobase::info_low(unsigned int, bool)+0x18f) [0x7f7edfe2524f] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(ha_innobase::update_create_info(st_ha_create_information*)+0x29) [0x7f7edfe256b9] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(+0x49e3dc) [0x7f7edfd953dc] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(mysqld_show_create(THD*, TABLE_LIST*)+0x7a8) [0x7f7edfd9d388] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x184a) [0x7f7edfc7cb0a] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x3fb) [0x7f7edfc80dbb] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x115a) [0x7f7edfc81f2a] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(do_command(THD*)+0xea) [0x7f7edfc8285a] Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(handle_one_connection+0x235) [0x7f7edfc74435] Oct 12 11:53:33 cebycny mysqld: /lib/libpthread.so.0(+0x68ca) [0x7f7edf4c18ca] Oct 12 11:53:33 cebycny mysqld: /lib/libc.so.6(clone+0x6d) [0x7f7ede00992d] Oct 12
Re: Lost connection to MySQL server - need help.
On Saturday 12 October 2013 13:07, Andrew Moore wrote: Could be a crash related to innodb data dictionary being out of sync. Could be a bug. Seems like a bug yes. However, we had a strange situation yesterday when we had several processes in the state copying to tmp table (if i remember the exact phrase). After witing 2 seconds, I restarted the server. It seemed to work OK until the backup started. Perhaps we should restore the database that I suspect cause this, in order to rebuild the complete database. -- Jørn Dahl-Stamnes homepage: http://photo.dahl-stamnes.net/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Lost connection to MySQL server - need help.
Am 12.10.2013 17:02, schrieb Jørn Dahl-Stamnes: On Saturday 12 October 2013 13:07, Andrew Moore wrote: Could be a crash related to innodb data dictionary being out of sync. Could be a bug. Seems like a bug yes. However, we had a strange situation yesterday when we had several processes in the state copying to tmp table (if i remember the exact phrase). After witing 2 seconds, I restarted the server. It seemed to work OK until the backup started so someone did optimize table on a large table you do yourself not a favour restarting the server in such a moment signature.asc Description: OpenPGP digital signature
Re: Lost connection to MySQL server - need help.
On Saturday 12 October 2013 17:36, Reindl Harald wrote: so someone did optimize table on a large table you do yourself not a favour restarting the server in such a moment 7 hours before the server was shut down, we did a alter table to add a primary key to a table that is read-only from the web application. -- Jørn Dahl-Stamnes homepage: http://photo.dahl-stamnes.net/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Lost connection to MySQL server - need help.
Am 12.10.2013 19:45, schrieb Jørn Dahl-Stamnes: On Saturday 12 October 2013 17:36, Reindl Harald wrote: so someone did optimize table on a large table you do yourself not a favour restarting the server in such a moment 7 hours before the server was shut down, we did a alter table to add a primary key to a table that is read-only from the web application. which means the table is most likely completly copied in a temp file and depending on the table size this takes time - you killed the alter table i guess signature.asc Description: OpenPGP digital signature
Re: Lost connection to MySQL server - need help.
We had a similar issue a bit back - and although it sounds similar - based on your followups it probably isnt, but will just toss this out there anyhows. We were experiencing connection timeouts when load would ramp up. Doing some digging we learned that our firewall between the servers bandwidth would get consumed by a large wordpress load - and this in essence backed up the rest of the requests until they timed out. We fixed that load issue which reduced the data passing through and have expereinced a significant performance boost in our app let alone reduction of these timeout issues On Sat, Oct 12, 2013 at 12:56 PM, Reindl Harald h.rei...@thelounge.netwrote: Am 12.10.2013 19:45, schrieb Jørn Dahl-Stamnes: On Saturday 12 October 2013 17:36, Reindl Harald wrote: so someone did optimize table on a large table you do yourself not a favour restarting the server in such a moment 7 hours before the server was shut down, we did a alter table to add a primary key to a table that is read-only from the web application. which means the table is most likely completly copied in a temp file and depending on the table size this takes time - you killed the alter table i guess
Re: Lost connection to MySQL server - need help.
sounds like a scheduler issue did you try deadline? http://en.wikipedia.org/wiki/Deadline_scheduler on Linux systems pass elevator=deadline as kernel param Am 12.10.2013 20:58, schrieb Chris McKeever: We had a similar issue a bit back - and although it sounds similar - based on your followups it probably isnt, but will just toss this out there anyhows. We were experiencing connection timeouts when load would ramp up. Doing some digging we learned that our firewall between the servers bandwidth would get consumed by a large wordpress load - and this in essence backed up the rest of the requests until they timed out. We fixed that load issue which reduced the data passing through and have expereinced a significant performance boost in our app let alone reduction of these timeout issues On Sat, Oct 12, 2013 at 12:56 PM, Reindl Harald h.rei...@thelounge.netwrote: Am 12.10.2013 19:45, schrieb Jørn Dahl-Stamnes: On Saturday 12 October 2013 17:36, Reindl Harald wrote: so someone did optimize table on a large table you do yourself not a favour restarting the server in such a moment 7 hours before the server was shut down, we did a alter table to add a primary key to a table that is read-only from the web application. which means the table is most likely completly copied in a temp file and depending on the table size this takes time - you killed the alter table i guess signature.asc Description: OpenPGP digital signature
Re: Exporting to CSV. Error Code: 2013. Lost connection to MySQL server during query
Hi Monty, First of all, thanks so much for responding to my question! I am using MySQLworkbench 5.2.37CE. I'm pretty sure the issue has to do with something on the administrator side of things. We managed to get it so that I can click the icon to export the file, but he's still working on getting it so that we can write an sql query to do this. So for all practical purposes on my end, the question is being resolved. But I don't understand how clicking the icon after running a select query works for exporting, but the command to outfile in a sql query would not work. Thanks again On Tue, Jul 31, 2012 at 5:36 AM, Michael Widenius mo...@askmonty.orgwrote: Hi! Fred == Fred G Fred writes: Fred Thanks Dhaval. Putting the join condition before INTO outfile doesn't seem Fred to work, either. Fred When I try to use the same outfile name 'test123.csv' I get Error Code: Fred 1086 File 'test123.csv' already exists. But then when I try to find the Fred csv file on my computer, there is a folder with that name, but weird files Fred in it, none of which are a csv-- and certainly not in the location that I Fred thought it would be (the same directory that the .sql query is in). It's the mysqld server that is writing the .csv file. This means that the path is related to the mysql data directory and not to where your .sql file is. When using select into outfile it's always best to give a full path! Fred Additionally, when I try to identify a different path, such as 'C:\\' etc, Fred I get an error. This error is: Error Code: 1. Can't create/write to file Fred C:\test123.csv(Errocde: 2). This probably means that you don't have write access to C:\ Fred I tried running the query outputting to a different named .csv file, but it Fred is still just running... and seems like it was like yesterday where after Fred 10 minutes I will get the Error that the MySQL connection was lost. The reason that your connection is lost are ether: - There is timeout in the client you are using (The server never gives a timeout for running queries). - The mysqld server died (not likely but possible). - Some process in your system is killing quries that runs too long. One way to quickly check that things are working are by adding LIMIT 1 to the query. Fred Does anyone have an idea of what is going on? The query without exporting the file works fine, in about 12 sec/77 sec. I read online how to export MySQL queries into csv's, and I'm not sure what I am doing wrong. I keep getting the error: Error Code: 2013. Lost connection to MySQL server during query, where the duration/fetch values are 600.547 sec (~10 minutes). What is the exact error message? Which client are you using to do the query? It's strange that the query works fine when you are not using select into outfile. What MySQL version are you using Regards, Monty Creator of MySQL and MariaDB
Re: Exporting to CSV. Error Code: 2013. Lost connection to MySQL server during query
Hi! Fred == Fred G Fred writes: Fred Thanks Dhaval. Putting the join condition before INTO outfile doesn't seem Fred to work, either. Fred When I try to use the same outfile name 'test123.csv' I get Error Code: Fred 1086 File 'test123.csv' already exists. But then when I try to find the Fred csv file on my computer, there is a folder with that name, but weird files Fred in it, none of which are a csv-- and certainly not in the location that I Fred thought it would be (the same directory that the .sql query is in). It's the mysqld server that is writing the .csv file. This means that the path is related to the mysql data directory and not to where your .sql file is. When using select into outfile it's always best to give a full path! Fred Additionally, when I try to identify a different path, such as 'C:\\' etc, Fred I get an error. This error is: Error Code: 1. Can't create/write to file Fred C:\test123.csv(Errocde: 2). This probably means that you don't have write access to C:\ Fred I tried running the query outputting to a different named .csv file, but it Fred is still just running... and seems like it was like yesterday where after Fred 10 minutes I will get the Error that the MySQL connection was lost. The reason that your connection is lost are ether: - There is timeout in the client you are using (The server never gives a timeout for running queries). - The mysqld server died (not likely but possible). - Some process in your system is killing quries that runs too long. One way to quickly check that things are working are by adding LIMIT 1 to the query. Fred Does anyone have an idea of what is going on? The query without exporting the file works fine, in about 12 sec/77 sec. I read online how to export MySQL queries into csv's, and I'm not sure what I am doing wrong. I keep getting the error: Error Code: 2013. Lost connection to MySQL server during query, where the duration/fetch values are 600.547 sec (~10 minutes). What is the exact error message? Which client are you using to do the query? It's strange that the query works fine when you are not using select into outfile. What MySQL version are you using Regards, Monty Creator of MySQL and MariaDB -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Exporting to CSV. Error Code: 2013. Lost connection to MySQL server during query
Thanks Dhaval. Putting the join condition before INTO outfile doesn't seem to work, either. When I try to use the same outfile name 'test123.csv' I get Error Code: 1086 File 'test123.csv' already exists. But then when I try to find the csv file on my computer, there is a folder with that name, but weird files in it, none of which are a csv-- and certainly not in the location that I thought it would be (the same directory that the .sql query is in). Additionally, when I try to identify a different path, such as 'C:\\' etc, I get an error. This error is: Error Code: 1. Can't create/write to file C:\test123.csv(Errocde: 2). I tried running the query outputting to a different named .csv file, but it is still just running... and seems like it was like yesterday where after 10 minutes I will get the Error that the MySQL connection was lost. Does anyone have an idea of what is going on? On Wed, Jul 25, 2012 at 9:22 PM, Dhaval Jaiswal dhaval.jais...@via.comwrote: SELECT * FROM test INTO OUTFILE '/home/test.csv' FIELDS TERMINATED BY ',' ENCLOSED BY '' LINES TERMINATED BY '\n' as above give your join condition before INTO OUTFILE. On Thu, Jul 26, 2012 at 1:32 AM, Fred G bayespoker...@gmail.com wrote: Hi-- I'm trying to do the following: SELECT db.emp.emp_fname, db.emp.emp_fname, db.sale.sale_date, db.sale.sale_no, db.sale.sale_total_amt into outfile 'test123.csv' FIELDS terminated by ',' FROM db.emp LEFT OUTER JOIN db.sale ON db.sale.emp_id = db.emp.emp_id; The query without exporting the file works fine, in about 12 sec/77 sec. I read online how to export MySQL queries into csv's, and I'm not sure what I am doing wrong. I keep getting the error: Error Code: 2013. Lost connection to MySQL server during query, where the duration/fetch values are 600.547 sec (~10 minutes). I'm wondering: a) What is going on? b) How do I fix it? Thanks so much!! -- [image: Inline image 2] http://www.via.com/ *Dhaval* | Database System *E:* dhaval.jais...@via.com ra...@via.com| *T:* 080 4043 3000 | *M:* +91 - 8095 397 843 [image: all-icon.jpg] http://www.via.com/
Re: Exporting to CSV. Error Code: 2013. Lost connection to MySQL server during query
2012/07/26 06:52 +0530, Dhaval Jaiswal SELECT * FROM test INTO OUTFILE '/home/test.csv' FIELDS TERMINATED BY ',' ENCLOSED BY '' LINES TERMINATED BY '\n' as above give your join condition before INTO OUTFILE. Right: MySQL server writes into some directory where it is, not where MySQL client is. If less than a full path name is given, almost certainly the server will attempt to write into a directory to which it has no permission, and almost certainly also not into one that you want it to write into. If server and client run on separate machines with separate disks, there is no means through OUTFILE of there setting the output where the client is, only through client s standard output, where you get no choice of field separator, line separator, or field-quote character (there is none), although you can keep or skip the column names (-N for skipping them), and suppress the one-character escape character (-r), same as FIELDS ESCAPED BY ''. There is no means of skipping NULL or \N for nulls, which is not CSV format. And if your MySQL is under Windows, be sure to read all instructions about entering full pathnames. It is best to avoid the backslash (\), because that is a C-escape introduced (along with much other C-stuff) into SQL s original PL1. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Exporting to CSV. Error Code: 2013. Lost connection to MySQL server during query
Thanks! On Thu, Jul 26, 2012 at 12:05 AM, h...@tbbs.net wrote: 2012/07/26 06:52 +0530, Dhaval Jaiswal SELECT * FROM test INTO OUTFILE '/home/test.csv' FIELDS TERMINATED BY ',' ENCLOSED BY '' LINES TERMINATED BY '\n' as above give your join condition before INTO OUTFILE. Right: MySQL server writes into some directory where it is, not where MySQL client is. If less than a full path name is given, almost certainly the server will attempt to write into a directory to which it has no permission, and almost certainly also not into one that you want it to write into. If server and client run on separate machines with separate disks, there is no means through OUTFILE of there setting the output where the client is, only through client s standard output, where you get no choice of field separator, line separator, or field-quote character (there is none), although you can keep or skip the column names (-N for skipping them), and suppress the one-character escape character (-r), same as FIELDS ESCAPED BY ''. There is no means of skipping NULL or \N for nulls, which is not CSV format. And if your MySQL is under Windows, be sure to read all instructions about entering full pathnames. It is best to avoid the backslash (\), because that is a C-escape introduced (along with much other C-stuff) into SQL s original PL1. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Exporting to CSV. Error Code: 2013. Lost connection to MySQL server during query
Hi-- I'm trying to do the following: SELECT db.emp.emp_fname, db.emp.emp_fname, db.sale.sale_date, db.sale.sale_no, db.sale.sale_total_amt into outfile 'test123.csv' FIELDS terminated by ',' FROM db.emp LEFT OUTER JOIN db.sale ON db.sale.emp_id = db.emp.emp_id; The query without exporting the file works fine, in about 12 sec/77 sec. I read online how to export MySQL queries into csv's, and I'm not sure what I am doing wrong. I keep getting the error: Error Code: 2013. Lost connection to MySQL server during query, where the duration/fetch values are 600.547 sec (~10 minutes). I'm wondering: a) What is going on? b) How do I fix it? Thanks so much!!
Re: Exporting to CSV. Error Code: 2013. Lost connection to MySQL server during query
SELECT * FROM test INTO OUTFILE '/home/test.csv' FIELDS TERMINATED BY ',' ENCLOSED BY '' LINES TERMINATED BY '\n' as above give your join condition before INTO OUTFILE. On Thu, Jul 26, 2012 at 1:32 AM, Fred G bayespoker...@gmail.com wrote: Hi-- I'm trying to do the following: SELECT db.emp.emp_fname, db.emp.emp_fname, db.sale.sale_date, db.sale.sale_no, db.sale.sale_total_amt into outfile 'test123.csv' FIELDS terminated by ',' FROM db.emp LEFT OUTER JOIN db.sale ON db.sale.emp_id = db.emp.emp_id; The query without exporting the file works fine, in about 12 sec/77 sec. I read online how to export MySQL queries into csv's, and I'm not sure what I am doing wrong. I keep getting the error: Error Code: 2013. Lost connection to MySQL server during query, where the duration/fetch values are 600.547 sec (~10 minutes). I'm wondering: a) What is going on? b) How do I fix it? Thanks so much!! -- [image: Inline image 2] http://www.via.com/ *Dhaval* | Database System *E:* dhaval.jais...@via.com ra...@via.com| *T:* 080 4043 3000 | *M:* +91 - 8095 397 843 [image: all-icon.jpg] http://www.via.com/
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
If you did not work directly on mysql server (login by mysql command), please try this. Using script (PHP, ...) may lose connection, as my experience. Best --- On Mon, 3/5/12, Singer X.J. Wang w...@singerwang.com wrote: From: Singer X.J. Wang w...@singerwang.com Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query To: javad bakhshi javadbakh...@yahoo.com Cc: mysql@lists.mysql.com mysql@lists.mysql.com Date: Monday, March 5, 2012, 10:40 PM Checking your firewall settings.. S On Mon, Mar 5, 2012 at 08:39, javad bakhshi javadbakh...@yahoo.com wrote: Hi, Still have the same problem and changing connect_timeout didn't help. Any other Ideas? Is there even any solution to this? Best regards, Javad Bakhshi, From: mail...@securitylabs.it mail...@securitylabs.it To: mysql@lists.mysql.com Sent: Thursday, March 1, 2012 11:09 AM Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query Il 01/03/2012 11:03, javad bakhshi ha scritto: Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi, In order to resolve the problem you may need to increase these two values in mysql.ini or my.cnf, and restart mysql: wait_timeout = 28800 connect_timeout = 28800 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql -- -- Pythian proud winner of Oracle North America Titan Award for Exadata Solution...watch the video on pythian.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Hi, Still have the same problem and changing connect_timeout didn't help. Any other Ideas? Is there even any solution to this? Best regards, Javad Bakhshi, From: mail...@securitylabs.it mail...@securitylabs.it To: mysql@lists.mysql.com Sent: Thursday, March 1, 2012 11:09 AM Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query Il 01/03/2012 11:03, javad bakhshi ha scritto: Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi, In order to resolve the problem you may need to increase these two values in mysql.ini or my.cnf, and restart mysql: wait_timeout = 28800 connect_timeout = 28800 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Checking your firewall settings.. S On Mon, Mar 5, 2012 at 08:39, javad bakhshi javadbakh...@yahoo.com wrote: Hi, Still have the same problem and changing connect_timeout didn't help. Any other Ideas? Is there even any solution to this? Best regards, Javad Bakhshi, From: mail...@securitylabs.it mail...@securitylabs.it To: mysql@lists.mysql.com Sent: Thursday, March 1, 2012 11:09 AM Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query Il 01/03/2012 11:03, javad bakhshi ha scritto: Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi, In order to resolve the problem you may need to increase these two values in mysql.ini or my.cnf, and restart mysql: wait_timeout = 28800 connect_timeout = 28800 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- -- Pythian proud winner of Oracle North America Titan Award for Exadata Solution...watch the video on pythian.com
ERROR 2013 (HY000): Lost connection to MySQL server during query
Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi,
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Il 01/03/2012 11:03, javad bakhshi ha scritto: Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi, In order to resolve the problem you may need to increase these two values in mysql.ini or my.cnf, and restart mysql: wait_timeout = 28800 connect_timeout = 28800 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Lost connection to MySQL server during query
Can you provide more details? network layout, type of client/app used, connectors,etc,etc? Thanks Claudio 2009/9/9 stutiredboy stutired...@gmail.com hi,all: we met a problem that: * Lost connection to MySQL server during query SHOW TABLE STATUS WHERE ENGINE='MyISAM' *sometimes it works well, sometimes not our mysql version is 5.0.84 our system is FreeBSD 6.2 thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=claudio.na...@gmail.com -- Claudio
Re: Lost connection to MySQL server during query
Since it is very unlikely that you lose connection on the socket file, I guess you are using a PHP app, that uses the mysql driver and the problem must be in the driver. I would not look at mysql but at the PHP and PHP2MYSQL layer, mainly at the later one. Try different PHP (and driver) versions. Claudio 2009/9/9 stutiredboy stutired...@gmail.com the application program and mysql server are in the same host and i have add skip-name-resolv to the my.cnf and extend the max_allowed_packet from 16M to 32M our application connected to mysql server from mysql.sock before the query which cause lost connection to MySQLserver.. we only ran some sql that create table(s) i have read this article http://dev.mysql.com/doc/refman/5.1/en/gone-away.html and can get rid of the problems this article referred it seems that our problem is similar to this bug: http://lists.mysql.com/commits/9447 http://bugs.mysql.com/bug.php?id=15752 but, this bug has been fixed in 5.0.25 are there any suggestions ? or any other informaion (s) should i post here? thanks! stutiredboy Claudio Nanni wrote: Can you provide more details? network layout, type of client/app used, connectors,etc,etc? Thanks Claudio 2009/9/9 stutiredboy stutired...@gmail.com mailto:stutired...@gmail.com hi,all: we met a problem that: * Lost connection to MySQL server during query SHOW TABLE STATUS WHERE ENGINE='MyISAM' *sometimes it works well, sometimes not our mysql version is 5.0.84 our system is FreeBSD 6.2 thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=claudio.na...@gmail.com -- Claudio -- Claudio
Re: Lost connection to MySQL server during query
the application program and mysql server are in the same host and i have add skip-name-resolv to the my.cnf and extend the max_allowed_packet from 16M to 32M our application connected to mysql server from mysql.sock before the query which cause lost connection to MySQLserver.. we only ran some sql that create table(s) i have read this article http://dev.mysql.com/doc/refman/5.1/en/gone-away.html and can get rid of the problems this article referred it seems that our problem is similar to this bug: http://lists.mysql.com/commits/9447 http://bugs.mysql.com/bug.php?id=15752 but, this bug has been fixed in 5.0.25 are there any suggestions ? or any other informaion (s) should i post here? thanks! stutiredboy Claudio Nanni wrote: Can you provide more details? network layout, type of client/app used, connectors,etc,etc? Thanks Claudio 2009/9/9 stutiredboy stutired...@gmail.com mailto:stutired...@gmail.com hi,all: we met a problem that: * Lost connection to MySQL server during query SHOW TABLE STATUS WHERE ENGINE='MyISAM' *sometimes it works well, sometimes not our mysql version is 5.0.84 our system is FreeBSD 6.2 thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=claudio.na...@gmail.com -- Claudio -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Lost connection to MySQL server during query
hi,all: we met a problem that: * Lost connection to MySQL server during query SHOW TABLE STATUS WHERE ENGINE='MyISAM' *sometimes it works well, sometimes not our mysql version is 5.0.84 our system is FreeBSD 6.2 thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Per Jessen wrote: It happened agaIn this morning, but slightly different: [snip] thd=0x7fe0140c7e00 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xb, backtrace may not be correct. Bogus stack limit or frame pointer, fp=0xb, stack_bottom=0x4514, thread_stack=262144, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x1355140 = INSERT IGNORE INTO quarantine_archive SELECT * FROM quarantine WHERE state=1 AND domain='example.com' thd-thread_id=1493537 The context is the same as previously, except the query: INSERT IGNORE INTO quarantine_archive SELECT * FROM quarantine WHERE state=1 AND domain='example.com' This is not exactly reproducable, but it is fairly predictable - happens every morning towards 0600 - I have an archive job starting at 0500. For the last three days, the query has been roughly the same, except the 'example.com' varies. Is there nothing I can do to attempt to diagnose crashes such as this? Still no suggestions? /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Per Jessen wrote: I have just discovered that my mysql server was restarted this morning, which is what gave me the 2013. In the log I found this: [snip] It happened agaIn this morning, but slightly different: [snip] thd=0x7fe0140c7e00 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xb, backtrace may not be correct. Bogus stack limit or frame pointer, fp=0xb, stack_bottom=0x4514, thread_stack=262144, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x1355140 = INSERT IGNORE INTO quarantine_archive SELECT * FROM quarantine WHERE state=1 AND domain='example.com' thd-thread_id=1493537 The context is the same as previously, except the query: INSERT IGNORE INTO quarantine_archive SELECT * FROM quarantine WHERE state=1 AND domain='example.com' It's getting to be a bit annoying - not all our apps were written to be able to handle the database connection disappearing at any time. Yes, they should have been, but it is a pretty unusual situation after all. Is there nothing I can do to attempt to diagnose crashes such as this? /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
mysql error 2013 Lost connection to MySQL server during query
This weekend we completed migrating a large(ish) mysql server from 5.0.26 on 32bit to 5.0.51a on 64bit. Everything went relatively smoothly, until this morning when I noticed an application had choked on getting Error 2013 Lost connection to MySQL server during query. The application is running remotely on 32bit using mysql library from version 5.0.67. I've been googling quite a bit, but haven't really found anything of any use. I've checked the two configurations, and they are the same. Can anyone help point me in the right direction? Thanks. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Per Jessen wrote: This weekend we completed migrating a large(ish) mysql server from 5.0.26 on 32bit to 5.0.51a on 64bit. Everything went relatively smoothly, until this morning when I noticed an application had choked on getting Error 2013 Lost connection to MySQL server during query. I have just discovered that my mysql server was restarted this morning, which is what gave me the 2013. In the log I found this: 090525 6:04:35 - 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=6442450944 read_buffer_size=258048 max_used_connections=43 max_connections=100 threads_connected=26 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 6367855 Kbytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x7fa6fc0173e0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xb, backtrace may not be correct. Bogus stack limit or frame pointer, fp=0xb, stack_bottom=0x41a6, thread_stack=262144, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x1340aa0 = SELECT domain,domain FROM dodgy_domain,spamdns_ipaddr WHERE dodgy_domain.ipaddr=spamdns_ipaddr.ipaddr group by domain having min(first)='2009-05-25 00:00:00' thd-thread_id=434983 /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Michael Dykman wrote: It might be helpful if you could tell us how you affected your data migration Sorry, I'm not familiar with reporting problems in/on mysql. The data migration was done with a full database dump (mysqldump) from the 32bit system, then a reload on the new 64bit system. I think it took 6-8 hours. and what kind of job was running at the time it went down. The job executing the SQL mentioned in the log ran on another server. It is a SELECT running from the command line (in a Makefile). I'm not sure what else to tell you. Having the server go away mid-query generally does mean you have run into a bug of some sort but, more often than not, you were doing something ill-advised at the time. The setup has been running for at least two years with no such problems. Let me know what other info would be interesting. best regards Per Jessen -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
just a thought: Did you run mysql_upgrade after the import? On Mon, May 25, 2009 at 10:19 AM, Per Jessen p...@computer.org wrote: Michael Dykman wrote: It might be helpful if you could tell us how you affected your data migration Sorry, I'm not familiar with reporting problems in/on mysql. The data migration was done with a full database dump (mysqldump) from the 32bit system, then a reload on the new 64bit system. I think it took 6-8 hours. and what kind of job was running at the time it went down. The job executing the SQL mentioned in the log ran on another server. It is a SELECT running from the command line (in a Makefile). I'm not sure what else to tell you. Having the server go away mid-query generally does mean you have run into a bug of some sort but, more often than not, you were doing something ill-advised at the time. The setup has been running for at least two years with no such problems. Let me know what other info would be interesting. best regards Per Jessen -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=mikeisgr...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Michael Steinfeld wrote: just a thought: Did you run mysql_upgrade after the import? No, I didn't - I didn't think of it as I really only moved the data across. best regards Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Per Jessen wrote: Michael Steinfeld wrote: just a thought: Did you run mysql_upgrade after the import? No, I didn't - I didn't think of it as I really only moved the data across. Okay, have done a mysqlcheck --check-upgrade - came back all clean. I don't see a need to run mysql_fix_privilege as I manually copied the necessary privilege data. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Have you tried running the offending SQL manually against you new installation? Does it come back clean in the isolated case? Is there anything else which runs against this database at night? crons? Could you post the script that you are running to give some context to the statement which winds up in your error log? Considering that you did use mysqldump to manually inject your data, cross-version incompatibilities are pretty much out of the question. - michael On Mon, May 25, 2009 at 11:19 AM, Per Jessen p...@computer.org wrote: Per Jessen wrote: Michael Steinfeld wrote: just a thought: Did you run mysql_upgrade after the import? No, I didn't - I didn't think of it as I really only moved the data across. Okay, have done a mysqlcheck --check-upgrade - came back all clean. I don't see a need to run mysql_fix_privilege as I manually copied the necessary privilege data. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=mdyk...@gmail.com -- - michael dykman - mdyk...@gmail.com - All models are wrong. Some models are useful. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
On Mon, May 25, 2009 at 11:19 AM, Per Jessen p...@computer.org wrote: Per Jessen wrote: Michael Steinfeld wrote: just a thought: Did you run mysql_upgrade after the import? No, I didn't - I didn't think of it as I really only moved the data across. I suspect that will solve your issue. Keep me posted. Okay, have done a mysqlcheck --check-upgrade - came back all clean. I don't see a need to run mysql_fix_privilege as I manually copied the necessary privilege data. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=mikeisgr...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Michael Dykman wrote: Have you tried running the offending SQL manually against you new installation? Does it come back clean in the isolated case? No, not manually, but the job/the SQL is run several times a day, maybe 2-3 times per hour. Is there anything else which runs against this database at night? crons? Yes, lots of stuff. Cron-jobs, jobs submitted by daemons, etc. Could you post the script that you are running to give some context to the statement which winds up in your error log? I'm generating a zonefile for rbldnsd with entries from my table since midnight. Entries from before midnight are put in a main-table, entries after are in this regular diff. The statement is this: SELECT domain,domain FROM dodgy_domain,spamdns_ipaddr WHERE dodgy_domain.ipaddr=spamdns_ipaddr.ipaddr group by domain having min(first)='midnight' Tonight it will be changed to: (single domain, not domain,domain) SELECT domain FROM dodgy_domain,spamdns_ipaddr WHERE dodgy_domain.ipaddr=spamdns_ipaddr.ipaddr group by domain having min(first)='midnight' Additional context: The server is brandnew, an HP Proliant with dual quad-core Xeons and 10Gb RAM. The filesystem is JFS on hardware RAID6. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Per Jessen wrote: Michael Dykman wrote: Have you tried running the offending SQL manually against you new installation? Does it come back clean in the isolated case? No, not manually, but the job/the SQL is run several times a day, maybe 2-3 times per hour. I've also just run the query manually a couple of times, no problems. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Given the new hardware, I'm now suspecting the RAID controller. I have seen misconfigured RAIDs or bad RAID drivers take out a server in just such a manner. I had a debian server connected to an EMC SAN.. As debian isn't supported, we had this open-source driver which gave us no end of problems. If a logical drive acts up or does something unexpected, MySQL could react to that in a manner consistent with what you are seeing in your log. I would be tempted to put the hardware through a stress test. I know that's not much help. - michael On Mon, May 25, 2009 at 12:02 PM, Per Jessen p...@computer.org wrote: Per Jessen wrote: Michael Dykman wrote: Have you tried running the offending SQL manually against you new installation? Does it come back clean in the isolated case? No, not manually, but the job/the SQL is run several times a day, maybe 2-3 times per hour. I've also just run the query manually a couple of times, no problems. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=mdyk...@gmail.com -- - michael dykman - mdyk...@gmail.com - All models are wrong. Some models are useful. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Michael Dykman wrote: Given the new hardware, I'm now suspecting the RAID controller. I have seen misconfigured RAIDs or bad RAID drivers take out a server in just such a manner. I had a debian server connected to an EMC SAN.. As debian isn't supported, we had this open-source driver which gave us no end of problems. If a logical drive acts up or does something unexpected, MySQL could react to that in a manner consistent with what you are seeing in your log. Shouldn't/wouldn't the filesystem complain first? There is a lot of activity on the filesystem, mysql is just a tiny part of it. I would be tempted to put the hardware through a stress test. I know that's not much help. I really have no reason to suspect the hardware. It's new, but it's been running in burn-in mode for about a month (although not with much load, mostly idling). I might as well suspect the mysql build and try upgrading to a newer one. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
The issues that we saw only came to light under stress. The application I am referring to ran under a fair bit of load at the best of times but it was during sustained spikes that the flaws in our driver made themselves apparent. Mind you, we weren't using JFS, so I'm not sure how that would have reacted. - michael On Mon, May 25, 2009 at 12:19 PM, Per Jessen p...@computer.org wrote: Michael Dykman wrote: Given the new hardware, I'm now suspecting the RAID controller. I have seen misconfigured RAIDs or bad RAID drivers take out a server in just such a manner. I had a debian server connected to an EMC SAN.. As debian isn't supported, we had this open-source driver which gave us no end of problems. If a logical drive acts up or does something unexpected, MySQL could react to that in a manner consistent with what you are seeing in your log. Shouldn't/wouldn't the filesystem complain first? There is a lot of activity on the filesystem, mysql is just a tiny part of it. I would be tempted to put the hardware through a stress test. I know that's not much help. I really have no reason to suspect the hardware. It's new, but it's been running in burn-in mode for about a month (although not with much load, mostly idling). I might as well suspect the mysql build and try upgrading to a newer one. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=mdyk...@gmail.com -- - michael dykman - mdyk...@gmail.com - All models are wrong. Some models are useful. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Hi Per, Maybe you need to beef up your CONNECT_TIMEOUT setting in your .my.cnf file. Are these queries appearing in your slow query logs?What is your LOG_QUERY_TIMES set too? Here are some other settings you may want to play around wtih CONNECT_TIMEOUT INTERACTIVE_TIMEOUT WAIT_TIMEOUT NET_WRITE_TIMEOUT NET_READ_TIMEOUT MAX_CONNECT_ERRORS On Mon, May 25, 2009 at 3:06 AM, Per Jessen p...@computer.org wrote: This weekend we completed migrating a large(ish) mysql server from 5.0.26 on 32bit to 5.0.51a on 64bit. Everything went relatively smoothly, until this morning when I noticed an application had choked on getting Error 2013 Lost connection to MySQL server during query. The application is running remotely on 32bit using mysql library from version 5.0.67. I've been googling quite a bit, but haven't really found anything of any use. I've checked the two configurations, and they are the same. Can anyone help point me in the right direction? Thanks. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=dstepli...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql error 2013 Lost connection to MySQL server during query
Darryle Steplight wrote: Hi Per, Maybe you need to beef up your CONNECT_TIMEOUT setting in your .my.cnf file. Are these queries appearing in your slow query logs?What is your LOG_QUERY_TIMES set too? Here are some other settings you may want to play around wtih CONNECT_TIMEOUT INTERACTIVE_TIMEOUT WAIT_TIMEOUT NET_WRITE_TIMEOUT NET_READ_TIMEOUT MAX_CONNECT_ERRORS Hi Darryle I did notice references to some of those when I was googling, but because I didn't change any settings in my migration except up the key_buffer space, I didn't really pay much attention. /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
? Solved ? Re: mysqldump: Error 2 013: Lost connection to MySQL server
On Tue, 2009-01-13 at 12:19 +0530, Chandru wrote: Hi, Did u try using this command mysqldump --opt db_name db_name.sql -p 2bkp.err Not quite. Firstly, I had to alter the normal backup cron job, and that doesn't happen until late at night. Secondly, yes I added the redirection to capture errors. There were none ( empty file this time ). Thirdly, I didn't use '--opt'. I had no other suggestions yesterday ( before I went to bed anyway - there's 1 in my inbox this morning ), so I did some experimenting of my own and changed the dump command to: mysqldump --skip-opt --add-drop-table --add-locks --create-options --quick --lock-tables --set-charset --disable-keys dbmail dbmail.sql -pSOME_PASSWORD 2bkp.err This made mysql do 1 insert per record. The backup *appears* to have completed successfully. At least the end of the dump file looks valid. It ends dumping the last table, then a view, then I get: -- Dump completed on 2009-01-13 17:23:13 Previously it just finished part-way through dumping a blob. I have yet to do extensive testing on it. I suppose I should try importing the dump file into another server and see if I get the correct number of rows in each table ... The only issue now is that the dump file is much smaller than I would have expected. When using --opt, I was getting 30GB dump files. I would have expected the current format ( 1 insert statement per record ) to be much bigger, but it's 23GB. Now having said that, I did email the current DB administrator and ask him to get people to archive all emails with huge attachments somewhere on a network share ( people have some pretty big attachments ). Also I asked him to get people to clean out their Trash ( which happens only when we tell them to ). So I suppose it's not completely infeasible that this alone is responsible for the difference. Anyway, it's been a very disconcerting experience. It goes without saying that people would expect that anything that gets into a MySQL database should be able to be backed up by mysqldump. And it's worrying that the default --opt can't do that. When I get some time I'll enter a bug ... Thanks for you help Chandru. Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: ? Solved ? Re: mysqldump: Error 2013: Lost connection to MySQL server
This sounds like you need to raise max_allowed_packet for mysqldump (and possibly mysqld) - these are separate settings for both the client and the server. You can do this via the my.cnf (or ~/.my.cnf) or specify it as an option on the command line mysqldump --opt ... --max_allowed_packet=1G dbname backup-file. On Tue, Jan 13, 2009 at 2:58 PM, Dan d...@entropy.homelinux.org wrote: On Tue, 2009-01-13 at 12:19 +0530, Chandru wrote: Hi, Did u try using this command mysqldump --opt db_name db_name.sql -p 2bkp.err Not quite. Firstly, I had to alter the normal backup cron job, and that doesn't happen until late at night. Secondly, yes I added the redirection to capture errors. There were none ( empty file this time ). Thirdly, I didn't use '--opt'. I had no other suggestions yesterday ( before I went to bed anyway - there's 1 in my inbox this morning ), so I did some experimenting of my own and changed the dump command to: mysqldump --skip-opt --add-drop-table --add-locks --create-options --quick --lock-tables --set-charset --disable-keys dbmail dbmail.sql -pSOME_PASSWORD 2bkp.err This made mysql do 1 insert per record. The backup *appears* to have completed successfully. At least the end of the dump file looks valid. It ends dumping the last table, then a view, then I get: -- Dump completed on 2009-01-13 17:23:13 Previously it just finished part-way through dumping a blob. I have yet to do extensive testing on it. I suppose I should try importing the dump file into another server and see if I get the correct number of rows in each table ... The only issue now is that the dump file is much smaller than I would have expected. When using --opt, I was getting 30GB dump files. I would have expected the current format ( 1 insert statement per record ) to be much bigger, but it's 23GB. Now having said that, I did email the current DB administrator and ask him to get people to archive all emails with huge attachments somewhere on a network share ( people have some pretty big attachments ). Also I asked him to get people to clean out their Trash ( which happens only when we tell them to ). So I suppose it's not completely infeasible that this alone is responsible for the difference. Anyway, it's been a very disconcerting experience. It goes without saying that people would expect that anything that gets into a MySQL database should be able to be backed up by mysqldump. And it's worrying that the default --opt can't do that. When I get some time I'll enter a bug ... Thanks for you help Chandru. Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=andrew.b.gar...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: ? Solved ? Re: mysqldump: Error 2013: Lost connection to MySQL server
On Tue, 13 Jan 2009 18:34:44 -0600, Andrew Garner andrew.b.gar...@gmail.com wrote: This sounds like you need to raise max_allowed_packet for mysqldump (and possibly mysqld) - these are separate settings for both the client and the server. You can do this via the my.cnf (or ~/.my.cnf) or specify it as an option on the command line mysqldump --opt ... --max_allowed_packet=1G dbname backup-file. This is certainly the most common advice for this error, yes. I increased the max_allowed_packet size from 1M to 128M when the problem initially occured. This didn't fix anything. Since dbmail splits up all email body / attachments into small chunks and inserts these chunks in separate records, I really don't see how a max_allowed_packet size of 128M would fail ... especially since the data got in there with a max_allowed_packet size of 1M to begin with. The biggest email in the database is 50M. So even if dbmail *hadn't* split the email into separate records, a max_allowed_packet size of 128M should be *easily* big enough, shouldn't it? As for a max_allowed_packet size of 1G, that just sounds dangerous. The server has 900MB or so of chip RAM and 512MB of swap. It's also running a LOT of other services. I don't want something stupid happening like Linux's out-of-memory-killer coming along and killing MySQL, causing database corruption. Can someone please comment on this? If it's not dangerous, I will try it. As noted in a prior post, I 'successfully' completed a backup last night, and I'm testing it now, but it took 10 hours to complete, and was still running when people came in this morning, which is obviously not desirable, so if I can somehow still use the --opt option of mysqldump by making max_allowed_packet to some absolutely astronomical level without endangering things, maybe that's the way to go. Maybe ... Anyway, thanks for the comments Andrew. Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: ? Solved ? Re: mysqldump: Error 2013: Lost connection to MySQL server
On Tue, Jan 13, 2009 at 6:06 PM, Dan d...@entropy.homelinux.org wrote: On Tue, 13 Jan 2009 18:34:44 -0600, Andrew Garner andrew.b.gar...@gmail.com wrote: This sounds like you need to raise max_allowed_packet for mysqldump (and possibly mysqld) - these are separate settings for both the client and the server. You can do this via the my.cnf (or ~/.my.cnf) or specify it as an option on the command line mysqldump --opt ... --max_allowed_packet=1G dbname backup-file. This is certainly the most common advice for this error, yes. I increased the max_allowed_packet size from 1M to 128M when the problem initially occured. This didn't fix anything. My apologies. I hadn't read up-thread where this was discussed, and given that, max_allowed_packet is almost certainly not the problem. Sorry for the noise. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
mysqldump: Error 2013: Lost connection to MySQL server
Hi all. I have a 30GB innodb-only database in mysql-5.0.54. I have always done nightly backups with: mysqldump --opt db_name db_name.sql -p Recently this started failing with: Error 2013: Lost connection to MySQL server I have checked all tables for corruption - nothing found. Also as far as I can tell there are no issues with clients using the database. There have been no crashes since I did a full restore. So I assume we can rule out corruption. I have searched around for the error message, and found people discussing the max_allowed_packet option. I've tried increasing the server's max_allowed_packet to many different values. Currently it's at 128M, which is *way* over the default. I have also used the --max_allowed_packet option simultaneously with mysqldump. And lastly, I have been restarting the server after each my.cnf change. The data was inserted via the 'dbmail' application ( http://www.dbmail.org ), while the server was set up with the default max_allowed_packet size. DBMail breaks up message into chunks, and stores these chunks in individual records. I'm not sure what the default size of these chunks is, but I belive it's a reasonable value anyway. What next? I *must* get regular backups working again ... Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysqldump: Error 2013: Lost connection to MySQL server
Hi, please increase your interactive_timeout variable to some big number and also try to log the erros if any thing by using the command: mysqldump --opt db_name db_name.sql -p 2bkp.err check if you get some thing in the bkp.err file. Regards, Chandru, www.mafiree.com On Mon, Jan 12, 2009 at 9:07 AM, Daniel Kasak d...@entropy.homelinux.orgwrote: Hi all. I have a 30GB innodb-only database in mysql-5.0.54. I have always done nightly backups with: mysqldump --opt db_name db_name.sql -p Recently this started failing with: Error 2013: Lost connection to MySQL server I have checked all tables for corruption - nothing found. Also as far as I can tell there are no issues with clients using the database. There have been no crashes since I did a full restore. So I assume we can rule out corruption. I have searched around for the error message, and found people discussing the max_allowed_packet option. I've tried increasing the server's max_allowed_packet to many different values. Currently it's at 128M, which is *way* over the default. I have also used the --max_allowed_packet option simultaneously with mysqldump. And lastly, I have been restarting the server after each my.cnf change. The data was inserted via the 'dbmail' application ( http://www.dbmail.org ), while the server was set up with the default max_allowed_packet size. DBMail breaks up message into chunks, and stores these chunks in individual records. I'm not sure what the default size of these chunks is, but I belive it's a reasonable value anyway. What next? I *must* get regular backups working again ... Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=chandru@gmail.com
Re: mysqldump: Error 2013: Lost connection to MySQL server
| | | ssl_capath | | | ssl_cert| | | ssl_cipher | | | ssl_key | | | storage_engine | MyISAM | | sync_binlog | 0 | | sync_frm| ON | | system_time_zone| EST | | table_cache | 64 | | table_lock_wait_timeout | 50 | | table_type | MyISAM | | thread_cache_size | 0 | | thread_stack| 196608 | | time_format | %H:%i:%s| | time_zone | SYSTEM | | timed_mutexes | OFF | | tmp_table_size | 33554432| | tmpdir | /tmp/ | | transaction_alloc_block_size| 8192| | transaction_prealloc_size | 4096| | tx_isolation| REPEATABLE-READ | | updatable_views_with_limit | YES | | version | 5.0.54-log | | version_comment | Gentoo Linux mysql-5.0.54 | | version_compile_machine | i686| | version_compile_os | pc-linux-gnu| | wait_timeout| 28800 | +-+-+ Thanks again. Dan Regards, Chandru, www.mafiree.com On Mon, Jan 12, 2009 at 9:07 AM, Daniel Kasak d...@entropy.homelinux.orgwrote: Hi all. I have a 30GB innodb-only database in mysql-5.0.54. I have always done nightly backups with: mysqldump --opt db_name db_name.sql -p Recently this started failing with: Error 2013: Lost connection to MySQL server I have checked all tables for corruption - nothing found. Also as far as I can tell there are no issues with clients using the database. There have been no crashes since I did a full restore. So I assume we can rule out corruption. I have searched around for the error message, and found people discussing the max_allowed_packet option. I've tried increasing the server's max_allowed_packet to many different values. Currently it's at 128M, which is *way* over the default. I have also used the --max_allowed_packet option simultaneously with mysqldump. And lastly, I have been restarting the server after each my.cnf change. The data was inserted via the 'dbmail' application ( http://www.dbmail.org ), while the server was set up with the default max_allowed_packet size. DBMail breaks up message into chunks, and stores these chunks in individual records. I'm not sure what the default size of these chunks is, but I belive it's a reasonable value anyway. What next? I *must* get regular backups working again ... Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=chandru@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysqldump: Error 2013: Lost connection to MySQL server
I'm also having a similar issue with some tables I've been trying to dump (total data set is around 3TB). I'm dumping directly from one host to another (mysqldump -hSOURCE DATABASE | mysql -hLOCALHOST DATABASE) using mysql 4.1.22. One system is Solaris 10 SPARC, while the other is Solaris 10 x64 (64bit MySQL as well). I wrote a script that starts a mysqldump process for each table within a database, which shouldn't be a problem since the host currently has around 12G unused memory. Midway through the dump I seem to lose the connection as Dan described. After attempting to drop/re-import (using a single process), the larger tables continue to fail (though at different points) while some of the small-medium sized tables made it across. Anyone else run into this before? Ideas? Thanks, -Aaron
Re: lost connection to mysql server during query errors
In my experiences, there're three reasons below. 1. Your network is not stable. 2. Your mysqld's parameter called max_allowed_packet is adjusted too small, trying to increase it. 3. Your mysqld's parameter called connect_timeout is adjusted too small, trying to increase it. On Thu, Oct 30, 2008 at 1:05 PM, mos [EMAIL PROTECTED] wrote: At 10:21 PM 10/29/2008, you wrote: I've never had a lot of luck tracking down this sort of problem. One thing I've found to be a good first step is to add each server involved to the other server's /etc/hosts file (and restart MySQL so it notices). Don't have much more to offer other than the usual suspects: recent versions, persistent vs. non-persistent connections, etc. A long shot would be to make sure your always talking to the same database server- if you're doing, say, DNS round-robin or load balancing or something, maybe you're getting shunted to a different db server and it's killing the connection... don't know what your setup is. Another long shot in a multi-db-server config would be to make sure they all have different server ID's. Good luck... hopefully someone else has better advice :) Jake Just a guess, but maybe it's your network card? I'm using MySQL 5.01 with MyISAM tables and my application will occasionally hang for hours in the midst of executing a simple 1 table Select statement. I usually end up killing the program. There are no processes running on the MySQL server. I think the problem was the number of connections the program created. Although there were only at most 10 simultaneous connections, my program when the query finished executing, it threw the connection away and recreated a new one for each query, and MySQL reported there were some 10k connections made to the server. I ended up using connection pooling and now the number of connections reaches a high of around 10 and I haven't had the problem since. Mike On Wed, Oct 29, 2008 at 2:47 AM, Waynn Lue [EMAIL PROTECTED] wrote: We've started seeing mysql errors in the logs, and when i look at the output of mysql_error() (in php), i get lost connection to mysql server during query. Here's an example stack trace: 'Can't connect to name database [Lost connection to MySQL server during query]' Similarly, we're seeing stack traces here as well: 'Can't connect to name database []' I usually only see this mesasge when I don't use a connection for awhile and it timeouts, but in this case, the connection is only opened for the duration of a script, which can't be running for more than a second. The mysql error logs don't show anything, and wait_timeout is set to 28800. At first, I thought it was because I was calling mysql_select_db too much, so I ended up using two mysql connections per page load, but that didn't seem to change anything. How can we prevent this error from happening, what else can I do to diagnose this further? Google brings up some more discussions about it, but nothing seems related to this, like packetsize. This is happening when we select two ids from a database. And SHOW PROCESSLIST shows that the number of connections aren't even coming close to max connections. Thanks for any advice, Waynn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
lost connection to mysql server during query errors
We've started seeing mysql errors in the logs, and when i look at the output of mysql_error() (in php), i get lost connection to mysql server during query. Here's an example stack trace: 'Can't connect to name database [Lost connection to MySQL server during query]' Similarly, we're seeing stack traces here as well: 'Can't connect to name database []' I usually only see this mesasge when I don't use a connection for awhile and it timeouts, but in this case, the connection is only opened for the duration of a script, which can't be running for more than a second. The mysql error logs don't show anything, and wait_timeout is set to 28800. At first, I thought it was because I was calling mysql_select_db too much, so I ended up using two mysql connections per page load, but that didn't seem to change anything. How can we prevent this error from happening, what else can I do to diagnose this further? Google brings up some more discussions about it, but nothing seems related to this, like packetsize. This is happening when we select two ids from a database. And SHOW PROCESSLIST shows that the number of connections aren't even coming close to max connections. Thanks for any advice, Waynn
Re: lost connection to mysql server during query errors
I've never had a lot of luck tracking down this sort of problem. One thing I've found to be a good first step is to add each server involved to the other server's /etc/hosts file (and restart MySQL so it notices). Don't have much more to offer other than the usual suspects: recent versions, persistent vs. non-persistent connections, etc. A long shot would be to make sure your always talking to the same database server- if you're doing, say, DNS round-robin or load balancing or something, maybe you're getting shunted to a different db server and it's killing the connection... don't know what your setup is. Another long shot in a multi-db-server config would be to make sure they all have different server ID's. Good luck... hopefully someone else has better advice :) Jake On Wed, Oct 29, 2008 at 2:47 AM, Waynn Lue [EMAIL PROTECTED] wrote: We've started seeing mysql errors in the logs, and when i look at the output of mysql_error() (in php), i get lost connection to mysql server during query. Here's an example stack trace: 'Can't connect to name database [Lost connection to MySQL server during query]' Similarly, we're seeing stack traces here as well: 'Can't connect to name database []' I usually only see this mesasge when I don't use a connection for awhile and it timeouts, but in this case, the connection is only opened for the duration of a script, which can't be running for more than a second. The mysql error logs don't show anything, and wait_timeout is set to 28800. At first, I thought it was because I was calling mysql_select_db too much, so I ended up using two mysql connections per page load, but that didn't seem to change anything. How can we prevent this error from happening, what else can I do to diagnose this further? Google brings up some more discussions about it, but nothing seems related to this, like packetsize. This is happening when we select two ids from a database. And SHOW PROCESSLIST shows that the number of connections aren't even coming close to max connections. Thanks for any advice, Waynn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: lost connection to mysql server during query errors
At 10:21 PM 10/29/2008, you wrote: I've never had a lot of luck tracking down this sort of problem. One thing I've found to be a good first step is to add each server involved to the other server's /etc/hosts file (and restart MySQL so it notices). Don't have much more to offer other than the usual suspects: recent versions, persistent vs. non-persistent connections, etc. A long shot would be to make sure your always talking to the same database server- if you're doing, say, DNS round-robin or load balancing or something, maybe you're getting shunted to a different db server and it's killing the connection... don't know what your setup is. Another long shot in a multi-db-server config would be to make sure they all have different server ID's. Good luck... hopefully someone else has better advice :) Jake Just a guess, but maybe it's your network card? I'm using MySQL 5.01 with MyISAM tables and my application will occasionally hang for hours in the midst of executing a simple 1 table Select statement. I usually end up killing the program. There are no processes running on the MySQL server. I think the problem was the number of connections the program created. Although there were only at most 10 simultaneous connections, my program when the query finished executing, it threw the connection away and recreated a new one for each query, and MySQL reported there were some 10k connections made to the server. I ended up using connection pooling and now the number of connections reaches a high of around 10 and I haven't had the problem since. Mike On Wed, Oct 29, 2008 at 2:47 AM, Waynn Lue [EMAIL PROTECTED] wrote: We've started seeing mysql errors in the logs, and when i look at the output of mysql_error() (in php), i get lost connection to mysql server during query. Here's an example stack trace: 'Can't connect to name database [Lost connection to MySQL server during query]' Similarly, we're seeing stack traces here as well: 'Can't connect to name database []' I usually only see this mesasge when I don't use a connection for awhile and it timeouts, but in this case, the connection is only opened for the duration of a script, which can't be running for more than a second. The mysql error logs don't show anything, and wait_timeout is set to 28800. At first, I thought it was because I was calling mysql_select_db too much, so I ended up using two mysql connections per page load, but that didn't seem to change anything. How can we prevent this error from happening, what else can I do to diagnose this further? Google brings up some more discussions about it, but nothing seems related to this, like packetsize. This is happening when we select two ids from a database. And SHOW PROCESSLIST shows that the number of connections aren't even coming close to max connections. Thanks for any advice, Waynn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Error 2013 (Lost Connection to MySQL Server) On A Solaris 10 Box
Hi, We copied over a test copy of a multi-GB database to a new Sun V440 box running Solaris 10 (64-bit) with a 64-bit MySQL install. When trying to connect to the database, we consistently get Error 2013. Any pointers? TIA. Sincerely, Raj Mehrotra hccs [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Re: Error 2013 (Lost Connection to MySQL Server) On A Solaris 10 Box
Rajesh Mehrotra wrote: Hi, We copied over a test copy of a multi-GB database to a new Sun V440 box running Solaris 10 (64-bit) with a 64-bit MySQL install. When trying to connect to the database, we consistently get Error 2013. Any pointers? Check the server's error log and see if there's anything in it. Baron -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
A question about how to debug the error 2013, 'Lost connection to MySQL server during query'
I am running the 64 bit version of mysql server 5.1.18, and on the client side I am running python with the mysqldb module. While running a very large insert query I get the following error : 2013, 'Lost connection to MySQL server during query' I have --log-warnings set to 3, but I get no corresponding errors in the error log. The question is : how do I go about debugging this problem? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: A question about how to debug the error 2013, 'Lost connection to MySQL server during query'
[EMAIL PROTECTED] schrieb: I am running the 64 bit version of mysql server 5.1.18, and on the client side I am running python with the mysqldb module. While running a very large insert query I get the following error : 2013, 'Lost connection to MySQL server during query' I have --log-warnings set to 3, but I get no corresponding errors in the error log. The question is : how do I go about debugging this problem? the most common error in this case is a crash of the thread processing your query -- Sebastian Mendel www.sebastianmendel.de -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
ERROR 2013 (HY000): Lost connection to MySQL server during query, 061220 14:48:44 mysqld restarted
I have MySQL 4.1.22 source installation on a 1.66 Intel Core Duo Mac Mini running OS X Server 10.4.8. It is a slave replicating to a master over ssl. Replication works fine, however I get this error always if I execute the STOP SLAVE statement ([EMAIL PROTECTED]) (none) stop slave; ERROR 2013 (HY000): Lost connection to MySQL server during query ([EMAIL PROTECTED]) (none) 061220 14:48:44 mysqld restarted Also, if I execute mysqladmin shutdown, it restarts also slmini:/usr/local admin$ mysqladmin -u root -p shutdown Enter password: slmini:/usr/local admin$ 061220 14:59:19 mysqld restarted The source has been compiled with SSL feature. I have exact same installation on a single CPU powerpc G4 XServe with no problems. My installation procedure/flags are here: Any ideas what the problem might be? Should I just rebuild the OS from scratch? Could it be corrupt data that needs to be recopied form the master? I'm baffled at this point. Regards, Kieran -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query, 061220 14:48:44 mysqld restarted
I left out URL to source compilation procedure and flags in original message. Here it is: http://homepage.mac.com/kelleherk/iblog/C711669388/E20061121141451/ index.html ANy advice would be really appreciated. Regards, Kieran On Dec 20, 2006, at 3:08 PM, Kieran Kelleher wrote: I have MySQL 4.1.22 source installation on a 1.66 Intel Core Duo Mac Mini running OS X Server 10.4.8. It is a slave replicating to a master over ssl. Replication works fine, however I get this error always if I execute the STOP SLAVE statement ([EMAIL PROTECTED]) (none) stop slave; ERROR 2013 (HY000): Lost connection to MySQL server during query ([EMAIL PROTECTED]) (none) 061220 14:48:44 mysqld restarted Also, if I execute mysqladmin shutdown, it restarts also slmini:/usr/local admin$ mysqladmin -u root -p shutdown Enter password: slmini:/usr/local admin$ 061220 14:59:19 mysqld restarted The source has been compiled with SSL feature. I have exact same installation on a single CPU powerpc G4 XServe with no problems. My installation procedure/flags are here: Any ideas what the problem might be? Should I just rebuild the OS from scratch? Could it be corrupt data that needs to be recopied form the master? I'm baffled at this point. Regards, Kieran -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query, 061220 14:48:44 mysqld restarted
Replying to myself again... OK, some more light on the subject. I did a complete dump of the master and reloaded the slave thinking maybe I had corrupt tables or something. Having started the slave with skip-start-slave, I found that I could stop mysqld on command line using mysqladmin without problems. As soon as I started the slave and tried to issue a stop slave, then the crash happened again. So basically the crash only happens if we try and stop the slave threads. This wouls explain why mysaadmin shutdown crashed when slave IO was on, but not when slave IO was stopped. Here is error I got this time for stop slave: stop slave; ERROR 2013 (HY000): Lost connection to MySQL server during query ([EMAIL PROTECTED]) (none) /usr/local/mysql/bin/mysqld_safe: line 1: 401 Illegal instruction nohup /usr/local/mysql/libexec/ mysqld --defaults-extra-file=/usr/local/mysql/data/my.cnf --basedir=/ usr/local/mysql --datadir=/usr/local/mysql/data --user=mysql --pid- file=/usr/local/mysql/data/slmini.local.pid --socket=/tmp/mysql.sock --skip-slave-start /usr/local/mysql/data/slmini.local.err 21 061220 16:02:05 mysqld restarted Any ideas what could be wrong here or is this possibly a bug? Regards, Kieran On Dec 20, 2006, at 3:08 PM, Kieran Kelleher wrote: I have MySQL 4.1.22 source installation on a 1.66 Intel Core Duo Mac Mini running OS X Server 10.4.8. It is a slave replicating to a master over ssl. Replication works fine, however I get this error always if I execute the STOP SLAVE statement ([EMAIL PROTECTED]) (none) stop slave; ERROR 2013 (HY000): Lost connection to MySQL server during query ([EMAIL PROTECTED]) (none) 061220 14:48:44 mysqld restarted Also, if I execute mysqladmin shutdown, it restarts also slmini:/usr/local admin$ mysqladmin -u root -p shutdown Enter password: slmini:/usr/local admin$ 061220 14:59:19 mysqld restarted The source has been compiled with SSL feature. I have exact same installation on a single CPU powerpc G4 XServe with no problems. My installation procedure/flags are here: Any ideas what the problem might be? Should I just rebuild the OS from scratch? Could it be corrupt data that needs to be recopied form the master? I'm baffled at this point. Regards, Kieran -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
lost connection to MySQL server during qu ery
i've done a non-stop insert test for 3 days, using mysql++ to connect to MySQL server i only use one connection, if it fails to execute ,it will reconnect during this test , this exception came out twice is that because of the server or the client?
ERROR 2013 (HY000): Lost connection to MySQL server during query
Hi, I am getting this error. Can anyone please help? mysql create table sfgbackup.advEmail select * from sfg.advEmail; ERROR 2013 (HY000): Lost connection to MySQL server during query Bye [EMAIL PROTECTED] mgandikota]$ mysql -V mysql Ver 14.7 Distrib 5.0.2-alpha, for pc-linux (i686) Thanks Murthy __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Hello That version is quite old and is an alpha version. I think you can download a release for production use. Gu Lei - Original Message - From: murthy gandikota [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Thursday, June 08, 2006 9:04 PM Subject: ERROR 2013 (HY000): Lost connection to MySQL server during query Hi, I am getting this error. Can anyone please help? mysql create table sfgbackup.advEmail select * from sfg.advEmail; ERROR 2013 (HY000): Lost connection to MySQL server during query Bye [EMAIL PROTECTED] mgandikota]$ mysql -V mysql Ver 14.7 Distrib 5.0.2-alpha, for pc-linux (i686) Thanks Murthy __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
ERROR 2013 (HY000): Lost connection to MySQL server during query
Hello, again, I'm having problems with InnoDB tables. A certain table cannot be dropped. If I'm issueing the drop table statement, the connection is lost and I get the following in the logfile: 060327 14:38:11 InnoDB: error: space object of table db15670/mw_pagelinks, InnoDB: space id 12 did not exist in memory. Retrying an open. InnoDB: Error: trying to add tablespace 12 of name './db15670/mw_pagelinks.ibd' InnoDB: to the tablespace memory cache, but tablespace InnoDB: 12 of name './db15720/admin.ibd' already exists in the tablespace InnoDB: memory cache! 060327 14:38:11 InnoDB: Error: page 3 log sequence number 0 153218641 InnoDB: is in the future! Current system log sequence number 0 14322402. InnoDB: Your database may be corrupt. 060327 14:38:11InnoDB: Assertion failure in thread 196621 in file fsp0fsp.c line 3202 InnoDB: Failing assertion: xdes_get_bit(descr, XDES_FREE_BIT, buf_frame_get_page_no(header) % FSP_EXTENT_SIZE, mtr) == FALSE InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. 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=402653184 read_buffer_size=2093056 max_used_connections=12 max_connections=1000 threads_connected=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 290904 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a000c18 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbe1fbe08, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80a43b4 0x82bf71c 0x820a5fd 0x81b64f5 0x8169f26 0x81a4bc7 0x81a4224 0x81a36c2 0x817f332 0x817e57d 0x819376b 0x8125411 0x811ba68 0x812abe0 0x812a500 0x80b76b2 0x80bbb72 0x80b54bd 0x80b5102 0x80b48f9 0x82bb001 0x82ed89a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x8bb38e0 = drop table mw_pagelinks thd-thread_id=220 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 060327 14:38:12 mysqld restarted 060327 14:38:12 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. The whole mysql-server crashed just because something is wrong in one innodb table. The force-recovery-hint didn't help at all, because it just made it possible do drop the table, but nothing was fixed and I couldn't create the table back then. Why does this happen? Regards Marten -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Marten, can you email the complete .err log from the server to [EMAIL PROTECTED] I am interested in what caused the very first crash in the server. Now your database seems to be seriously corrupt, since the log sequence number in the log files is only 14 MB, while it is = 153 MB in a data file! Did you move around or delete ib_logfiles or ibdata files or .ibd files, or edit my.cnf while mysqld was running? Are you using some exotic file system? The output looks like ib_logfiles and data files from different servers would be mixed. Best regards, Heikki Oracle Corp./Innobase Oy InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php - Original Message - From: Marten Lehmann [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Monday, March 27, 2006 3:46 PM Subject: ERROR 2013 (HY000): Lost connection to MySQL server during query Hello, again, I'm having problems with InnoDB tables. A certain table cannot be dropped. If I'm issueing the drop table statement, the connection is lost and I get the following in the logfile: 060327 14:38:11 InnoDB: error: space object of table db15670/mw_pagelinks, InnoDB: space id 12 did not exist in memory. Retrying an open. InnoDB: Error: trying to add tablespace 12 of name './db15670/mw_pagelinks.ibd' InnoDB: to the tablespace memory cache, but tablespace InnoDB: 12 of name './db15720/admin.ibd' already exists in the tablespace InnoDB: memory cache! 060327 14:38:11 InnoDB: Error: page 3 log sequence number 0 153218641 InnoDB: is in the future! Current system log sequence number 0 14322402. InnoDB: Your database may be corrupt. 060327 14:38:11InnoDB: Assertion failure in thread 196621 in file fsp0fsp.c line 3202 InnoDB: Failing assertion: xdes_get_bit(descr, XDES_FREE_BIT, buf_frame_get_page_no(header) % FSP_EXTENT_SIZE, mtr) == FALSE InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. 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=402653184 read_buffer_size=2093056 max_used_connections=12 max_connections=1000 threads_connected=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 290904 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a000c18 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbe1fbe08, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80a43b4 0x82bf71c 0x820a5fd 0x81b64f5 0x8169f26 0x81a4bc7 0x81a4224 0x81a36c2 0x817f332 0x817e57d 0x819376b 0x8125411 0x811ba68 0x812abe0 0x812a500 0x80b76b2 0x80bbb72 0x80b54bd 0x80b5102 0x80b48f9 0x82bb001 0x82ed89a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x8bb38e0 = drop table mw_pagelinks thd-thread_id=220 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 060327 14:38:12 mysqld restarted 060327 14:38:12 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. The whole mysql-server crashed just because something is wrong in one innodb table. The force-recovery-hint didn't help at all, because it just made it possible do drop the table, but nothing was fixed and I couldn't create the table back then. Why does this happen? Regards Marten -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Lost connection to MySQL server during query
Check out: http://dev.mysql.com/doc/refman/5.0/en/communication-errors.html http://dev.mysql.com/doc/refman/5.0/en/gone-away.html (I've noticed this has come up a lot recently on the list. . .) -Sheeri On 1/24/06, Jonathan Mangin [EMAIL PROTECTED] wrote: I got exactly that error message last night when doing a numeric comparison on a varchar column. Oops. Kind of misleading, though. - Original Message - From: David Godsey [EMAIL PROTECTED] To: George Law [EMAIL PROTECTED] Cc: mysql@lists.mysql.com Sent: Tuesday, January 24, 2006 4:43 PM Subject: RE: Lost connection to MySQL server during query Thanks for the reply. I'm not using persistend connections though. It appears that it looses the connection in the middle of the query or in other words, before the procedure returns. So that means I not getting the data I need. So for debug purposes, are you saying to do a check status from PHP or in the procedure? From the procedure it wouldn't do any good right? From PHP it would be after I didn't get the data, so I would have to reconnect and rerun the query. That won't really work for me either. David Godsey David, Are you using persistent connections? Sounds like perhaps a persistent connection is timing out. Maybe a quick work around would be to call a check status routine (ie - do a show status), just to see if the connection is still there. If this fails, just do a mysql_connect... Before continuing. -- George -Original Message- From: David Godsey [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 24, 2006 4:09 PM To: mysql@lists.mysql.com Subject: Lost connection to MySQL server during query I am getting this error when connecting to mysql with PHP: Lost connection to MySQL server during query This happens only when I use this procedure, but it doesn't necessarily fail when this procedure is called. The error will happen frequently, however it is not consistent. This is my first procedure I've written, so I'm sure I've done something wrong here. I assume the error message means I'm hitting some kind of timeout? Any ideas would be welcome. Thanks. create procedure getElement (IN n VARCHAR(255),IN ptime DOUBLE) BEGIN DECLARE mfid INT UNSIGNED; DECLARE pid INT UNSIGNED; DECLARE foffset INT UNSIGNED; DECLARE flength INT UNSIGNED; DECLARE vid INT UNSIGNED; DECLARE rfid INT UNSIGNED; DECLARE tpid INT UNSIGNED; DECLARE fdata BLOB; DECLARE fdata_tmp BLOB; DECLARE fdata_bigint BIGINT UNSIGNED; DECLARE fdata_signed INT; DECLARE fdata_unsigned INT UNSIGNED; DECLARE fdata_float DOUBLE; DECLARE data_type VARCHAR(20); DECLARE byte_order VARCHAR(20); DECLARE conv_param VARCHAR(255); SELECT major_frame_desc_id, parent_id, frame_offset, frame_length, version_id, top_level_parent_id FROM MajorFrameDescription WHERE name=n INTO mfid,pid,foffset,flength,vid,tpid; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=NormalizedType INTO data_type; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ConvParams INTO conv_param; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ByteOrder INTO byte_order; SELECT MAX(raw_major_frame_id) FROM RawMajorFrames WHERE major_frame_desc_id=tpid INTO rfid; IF rfid 0 THEN SELECT payload_time, SUBSTR(BINARY(frame_data), FLOOR(foffset/8)+1, CEIL((flength + (foffset %8 ))/8)) FROM RawMajorFrames WHERE raw_major_frame_id=rfid INTO ptime,fdata; call toBigInt(fdata,fdata_bigint); IF (foffset %8) 0 THEN SET @mask_off=foffset%8; call mask_data(fdata,@mask_off,fdata_bigint); END IF; IF (8-((flength+(foffset%8)) %8)) 0 THEN SELECT (fdata_bigint (8-((flength+(foffset%8)) %8))) INTO fdata_bigint
Lost connection to MySQL server during query
I am getting this error when connecting to mysql with PHP: Lost connection to MySQL server during query This happens only when I use this procedure, but it doesn't necessarily fail when this procedure is called. The error will happen frequently, however it is not consistent. This is my first procedure I've written, so I'm sure I've done something wrong here. I assume the error message means I'm hitting some kind of timeout? Any ideas would be welcome. Thanks. create procedure getElement (IN n VARCHAR(255),IN ptime DOUBLE) BEGIN DECLARE mfid INT UNSIGNED; DECLARE pid INT UNSIGNED; DECLARE foffset INT UNSIGNED; DECLARE flength INT UNSIGNED; DECLARE vid INT UNSIGNED; DECLARE rfid INT UNSIGNED; DECLARE tpid INT UNSIGNED; DECLARE fdata BLOB; DECLARE fdata_tmp BLOB; DECLARE fdata_bigint BIGINT UNSIGNED; DECLARE fdata_signed INT; DECLARE fdata_unsigned INT UNSIGNED; DECLARE fdata_float DOUBLE; DECLARE data_type VARCHAR(20); DECLARE byte_order VARCHAR(20); DECLARE conv_param VARCHAR(255); SELECT major_frame_desc_id, parent_id, frame_offset, frame_length, version_id, top_level_parent_id FROM MajorFrameDescription WHERE name=n INTO mfid,pid,foffset,flength,vid,tpid; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=NormalizedType INTO data_type; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ConvParams INTO conv_param; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ByteOrder INTO byte_order; SELECT MAX(raw_major_frame_id) FROM RawMajorFrames WHERE major_frame_desc_id=tpid INTO rfid; IF rfid 0 THEN SELECT payload_time, SUBSTR(BINARY(frame_data), FLOOR(foffset/8)+1, CEIL((flength + (foffset %8 ))/8)) FROM RawMajorFrames WHERE raw_major_frame_id=rfid INTO ptime,fdata; call toBigInt(fdata,fdata_bigint); IF (foffset %8) 0 THEN SET @mask_off=foffset%8; call mask_data(fdata,@mask_off,fdata_bigint); END IF; IF (8-((flength+(foffset%8)) %8)) 0 THEN SELECT (fdata_bigint (8-((flength+(foffset%8)) %8))) INTO fdata_bigint; END IF; CASE data_type WHEN Float THEN call toFloat(fdata_bigint,fdata_float); IF(!ISNULL(conv_param)) THEN call polyConv(fdata_float,conv_param,fdata_float); END IF; SET @fdata_converted=fdata_float; WHEN Double THEN call toFloat(fdata_bigint,fdata_float); IF(!ISNULL(conv_param)) THEN call polyConv(fdata_float,conv_param,fdata_float); END IF; SET @fdata_converted=fdata_float; WHEN Signed THEN call toSigned(fdata_bigint,fdata_signed); SET @fdata_converted=fdata_signed; WHEN Unsigned THEN SET @fdata_converted=fdata_bigint; ELSE SET @fdata_converted=HEX(fdata); END CASE; call enumConv(fdata_bigint,mfid,@fdata_enum); IF(!ISNULL(@fdata_enum)) THEN SET @[EMAIL PROTECTED]; END IF; SELECT mfid AS major_frame_desc_id
RE: Lost connection to MySQL server during query
David, Are you using persistent connections? Sounds like perhaps a persistent connection is timing out. Maybe a quick work around would be to call a check status routine (ie - do a show status), just to see if the connection is still there. If this fails, just do a mysql_connect... Before continuing. -- George -Original Message- From: David Godsey [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 24, 2006 4:09 PM To: mysql@lists.mysql.com Subject: Lost connection to MySQL server during query I am getting this error when connecting to mysql with PHP: Lost connection to MySQL server during query This happens only when I use this procedure, but it doesn't necessarily fail when this procedure is called. The error will happen frequently, however it is not consistent. This is my first procedure I've written, so I'm sure I've done something wrong here. I assume the error message means I'm hitting some kind of timeout? Any ideas would be welcome. Thanks. create procedure getElement (IN n VARCHAR(255),IN ptime DOUBLE) BEGIN DECLARE mfid INT UNSIGNED; DECLARE pid INT UNSIGNED; DECLARE foffset INT UNSIGNED; DECLARE flength INT UNSIGNED; DECLARE vid INT UNSIGNED; DECLARE rfid INT UNSIGNED; DECLARE tpid INT UNSIGNED; DECLARE fdata BLOB; DECLARE fdata_tmp BLOB; DECLARE fdata_bigint BIGINT UNSIGNED; DECLARE fdata_signed INT; DECLARE fdata_unsigned INT UNSIGNED; DECLARE fdata_float DOUBLE; DECLARE data_type VARCHAR(20); DECLARE byte_order VARCHAR(20); DECLARE conv_param VARCHAR(255); SELECT major_frame_desc_id, parent_id, frame_offset, frame_length, version_id, top_level_parent_id FROM MajorFrameDescription WHERE name=n INTO mfid,pid,foffset,flength,vid,tpid; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=NormalizedType INTO data_type; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ConvParams INTO conv_param; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ByteOrder INTO byte_order; SELECT MAX(raw_major_frame_id) FROM RawMajorFrames WHERE major_frame_desc_id=tpid INTO rfid; IF rfid 0 THEN SELECT payload_time, SUBSTR(BINARY(frame_data), FLOOR(foffset/8)+1, CEIL((flength + (foffset %8 ))/8)) FROM RawMajorFrames WHERE raw_major_frame_id=rfid INTO ptime,fdata; call toBigInt(fdata,fdata_bigint); IF (foffset %8) 0 THEN SET @mask_off=foffset%8; call mask_data(fdata,@mask_off,fdata_bigint); END IF; IF (8-((flength+(foffset%8)) %8)) 0 THEN SELECT (fdata_bigint (8-((flength+(foffset%8)) %8))) INTO fdata_bigint; END IF; CASE data_type WHEN Float THEN call toFloat(fdata_bigint,fdata_float); IF(!ISNULL(conv_param)) THEN call polyConv(fdata_float,conv_param,fdata_float); END IF; SET @fdata_converted=fdata_float; WHEN Double THEN call toFloat(fdata_bigint,fdata_float); IF(!ISNULL(conv_param)) THEN call polyConv(fdata_float,conv_param,fdata_float); END IF; SET @fdata_converted=fdata_float; WHEN Signed THEN call toSigned(fdata_bigint,fdata_signed); SET @fdata_converted=fdata_signed; WHEN Unsigned
RE: Lost connection to MySQL server during query
Thanks for the reply. I'm not using persistend connections though. It appears that it looses the connection in the middle of the query or in other words, before the procedure returns. So that means I not getting the data I need. So for debug purposes, are you saying to do a check status from PHP or in the procedure? From the procedure it wouldn't do any good right? From PHP it would be after I didn't get the data, so I would have to reconnect and rerun the query. That won't really work for me either. David Godsey David, Are you using persistent connections? Sounds like perhaps a persistent connection is timing out. Maybe a quick work around would be to call a check status routine (ie - do a show status), just to see if the connection is still there. If this fails, just do a mysql_connect... Before continuing. -- George -Original Message- From: David Godsey [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 24, 2006 4:09 PM To: mysql@lists.mysql.com Subject: Lost connection to MySQL server during query I am getting this error when connecting to mysql with PHP: Lost connection to MySQL server during query This happens only when I use this procedure, but it doesn't necessarily fail when this procedure is called. The error will happen frequently, however it is not consistent. This is my first procedure I've written, so I'm sure I've done something wrong here. I assume the error message means I'm hitting some kind of timeout? Any ideas would be welcome. Thanks. create procedure getElement (IN n VARCHAR(255),IN ptime DOUBLE) BEGIN DECLARE mfid INT UNSIGNED; DECLARE pid INT UNSIGNED; DECLARE foffset INT UNSIGNED; DECLARE flength INT UNSIGNED; DECLARE vid INT UNSIGNED; DECLARE rfid INT UNSIGNED; DECLARE tpid INT UNSIGNED; DECLARE fdata BLOB; DECLARE fdata_tmp BLOB; DECLARE fdata_bigint BIGINT UNSIGNED; DECLARE fdata_signed INT; DECLARE fdata_unsigned INT UNSIGNED; DECLARE fdata_float DOUBLE; DECLARE data_type VARCHAR(20); DECLARE byte_order VARCHAR(20); DECLARE conv_param VARCHAR(255); SELECT major_frame_desc_id, parent_id, frame_offset, frame_length, version_id, top_level_parent_id FROM MajorFrameDescription WHERE name=n INTO mfid,pid,foffset,flength,vid,tpid; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=NormalizedType INTO data_type; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ConvParams INTO conv_param; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ByteOrder INTO byte_order; SELECT MAX(raw_major_frame_id) FROM RawMajorFrames WHERE major_frame_desc_id=tpid INTO rfid; IF rfid 0 THEN SELECT payload_time, SUBSTR(BINARY(frame_data), FLOOR(foffset/8)+1, CEIL((flength + (foffset %8 ))/8)) FROM RawMajorFrames WHERE raw_major_frame_id=rfid INTO ptime,fdata; call toBigInt(fdata,fdata_bigint); IF (foffset %8) 0 THEN SET @mask_off=foffset%8; call mask_data(fdata,@mask_off,fdata_bigint); END IF; IF (8-((flength+(foffset%8)) %8)) 0 THEN SELECT (fdata_bigint (8-((flength+(foffset%8)) %8))) INTO fdata_bigint; END IF; CASE data_type WHEN Float THEN call toFloat(fdata_bigint,fdata_float); IF(!ISNULL(conv_param)) THEN call polyConv(fdata_float,conv_param,fdata_float); END IF; SET @fdata_converted=fdata_float; WHEN Double THEN call toFloat(fdata_bigint,fdata_float); IF(!ISNULL(conv_param
Re: Lost connection to MySQL server during query
I got exactly that error message last night when doing a numeric comparison on a varchar column. Oops. Kind of misleading, though. - Original Message - From: David Godsey [EMAIL PROTECTED] To: George Law [EMAIL PROTECTED] Cc: mysql@lists.mysql.com Sent: Tuesday, January 24, 2006 4:43 PM Subject: RE: Lost connection to MySQL server during query Thanks for the reply. I'm not using persistend connections though. It appears that it looses the connection in the middle of the query or in other words, before the procedure returns. So that means I not getting the data I need. So for debug purposes, are you saying to do a check status from PHP or in the procedure? From the procedure it wouldn't do any good right? From PHP it would be after I didn't get the data, so I would have to reconnect and rerun the query. That won't really work for me either. David Godsey David, Are you using persistent connections? Sounds like perhaps a persistent connection is timing out. Maybe a quick work around would be to call a check status routine (ie - do a show status), just to see if the connection is still there. If this fails, just do a mysql_connect... Before continuing. -- George -Original Message- From: David Godsey [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 24, 2006 4:09 PM To: mysql@lists.mysql.com Subject: Lost connection to MySQL server during query I am getting this error when connecting to mysql with PHP: Lost connection to MySQL server during query This happens only when I use this procedure, but it doesn't necessarily fail when this procedure is called. The error will happen frequently, however it is not consistent. This is my first procedure I've written, so I'm sure I've done something wrong here. I assume the error message means I'm hitting some kind of timeout? Any ideas would be welcome. Thanks. create procedure getElement (IN n VARCHAR(255),IN ptime DOUBLE) BEGIN DECLARE mfid INT UNSIGNED; DECLARE pid INT UNSIGNED; DECLARE foffset INT UNSIGNED; DECLARE flength INT UNSIGNED; DECLARE vid INT UNSIGNED; DECLARE rfid INT UNSIGNED; DECLARE tpid INT UNSIGNED; DECLARE fdata BLOB; DECLARE fdata_tmp BLOB; DECLARE fdata_bigint BIGINT UNSIGNED; DECLARE fdata_signed INT; DECLARE fdata_unsigned INT UNSIGNED; DECLARE fdata_float DOUBLE; DECLARE data_type VARCHAR(20); DECLARE byte_order VARCHAR(20); DECLARE conv_param VARCHAR(255); SELECT major_frame_desc_id, parent_id, frame_offset, frame_length, version_id, top_level_parent_id FROM MajorFrameDescription WHERE name=n INTO mfid,pid,foffset,flength,vid,tpid; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=NormalizedType INTO data_type; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ConvParams INTO conv_param; SELECT attribute_value FROM MajorFrameAttributes WHERE major_frame_desc_id=mfid AND attribute_name=ByteOrder INTO byte_order; SELECT MAX(raw_major_frame_id) FROM RawMajorFrames WHERE major_frame_desc_id=tpid INTO rfid; IF rfid 0 THEN SELECT payload_time, SUBSTR(BINARY(frame_data), FLOOR(foffset/8)+1, CEIL((flength + (foffset %8 ))/8)) FROM RawMajorFrames WHERE raw_major_frame_id=rfid INTO ptime,fdata; call toBigInt(fdata,fdata_bigint); IF (foffset %8) 0 THEN SET @mask_off=foffset%8; call mask_data(fdata,@mask_off,fdata_bigint); END IF; IF (8-((flength+(foffset%8)) %8)) 0 THEN SELECT (fdata_bigint (8-((flength+(foffset%8)) %8))) INTO fdata_bigint; END IF; CASE data_type WHEN Float THEN call toFloat(fdata_bigint,fdata_float); IF(!ISNULL(conv_param
Re: localhost vs. 127.0.0.1 error: 'Lost connection to MySQL server during query'
=20 | | slave_net_timeout | 3600 =20 | | slave_transaction_retries | 0=20 | | slow_launch_time| 2=20 | | socket | /var/run/mysqld/mysqld.sock =20 | | sort_buffer_size| 2097144 =20 | | sql_mode| =20 | | storage_engine | MyISAM =20 | | sql_notes | ON =20 | | sql_warnings| ON =20 | | sync_binlog | 0=20 | | sync_replication| 0=20 | | sync_replication_slave_id | 0=20 | | sync_replication_timeout| 0=20 | | sync_frm| ON =20 | | system_time_zone| EST =20 | | table_cache | 64 =20 | | table_type | MyISAM =20 | | thread_cache_size | 0=20 | | thread_stack| 131072 =20 | | time_format | %H:%i:%s =20 | | time_zone | SYSTEM =20 | | tmp_table_size | 33554432 =20 | | tmpdir | /tmp =20 | | transaction_alloc_block_size| 8192 =20 | | transaction_prealloc_size | 4096 =20 | | tx_isolation| REPEATABLE-READ =20 | | version | 4.1.11-Debian_4sarge2-log=20 | | version_bdb | Sleepycat Software: Berkeley DB 4.1.24: (April 1, 2005) | | version_comment | Source distribution =20 | | version_compile_machine | i386 =20 | | version_compile_os | pc-linux-gnu =20 | | wait_timeout| 28800=20 | +-+= --+ [EMAIL PROTECTED]:~# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain [EMAIL PROTECTED]:~# iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination [EMAIL PROTECTED]:~# ipchains --list ipchains: Incompatible with this kernel [EMAIL PROTECTED]:~# telnet localhost 43306 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. [EMAIL PROTECTED]:~# telnet 127.0.0.1 43306 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Connection closed by foreign host. [EMAIL PROTECTED]:~# netstat -an |grep LISTEN tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:43306 0.0.0.0:* LISTEN Now for the fun part [EMAIL PROTECTED]:~# mysqladmin -h localhost -u root -p ping Enter password: mysqld is alive [EMAIL PROTECTED]:~# mysqladmin -h 127.0.0.1 -u root -p ping Enter password: mysqladmin: connect to server at '127.0.0.1' failed error: 'Lost connection to MySQL server during query' ok so my issue is the software that i am using is hardcoded to use 127.0.0.1 and not localhost. Even if i add the bind-address to my.cnf I still get the same error. If I bind it to an external ip address I then can still connect to localhost but not 127.0.0.1 nor the external IP adress
localhost vs. 127.0.0.1 error: 'Lost connection to MySQL server during query'
| | table_type | MyISAM | | thread_cache_size | 0 | | thread_stack| 131072 | | time_format | %H:%i:%s | | time_zone | SYSTEM | | tmp_table_size | 33554432 | | tmpdir | /tmp | | transaction_alloc_block_size| 8192 | | transaction_prealloc_size | 4096 | | tx_isolation| REPEATABLE-READ | | version | 4.1.11-Debian_4sarge2-log | | version_bdb | Sleepycat Software: Berkeley DB 4.1.24: (April 1, 2005) | | version_comment | Source distribution | | version_compile_machine | i386 | | version_compile_os | pc-linux-gnu | | wait_timeout| 28800 | +-+--+ [EMAIL PROTECTED]:~# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain [EMAIL PROTECTED]:~# iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination [EMAIL PROTECTED]:~# ipchains --list ipchains: Incompatible with this kernel [EMAIL PROTECTED]:~# telnet localhost 43306 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. [EMAIL PROTECTED]:~# telnet 127.0.0.1 43306 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Connection closed by foreign host. [EMAIL PROTECTED]:~# netstat -an |grep LISTEN tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:43306 0.0.0.0:* LISTEN Now for the fun part [EMAIL PROTECTED]:~# mysqladmin -h localhost -u root -p ping Enter password: mysqld is alive [EMAIL PROTECTED]:~# mysqladmin -h 127.0.0.1 -u root -p ping Enter password: mysqladmin: connect to server at '127.0.0.1' failed error: 'Lost connection to MySQL server during query' ok so my issue is the software that i am using is hardcoded to use 127.0.0.1 and not localhost. Even if i add the bind-address to my.cnf I still get the same error. If I bind it to an external ip address I then can still connect to localhost but not 127.0.0.1 nor the external IP adress. Any ideas or point me to some good documentation on this would be great. I tried to search through several search engines but they all lead me nowhere, any help is appreciated. --Lance -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: HELP [nativecode=2013 ** Lost connection to MySQL server during query]
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: `client' (Got timeout reading communication packets) Any idea what this error is ? the interfaces show no errors from a network perspective: db machine eth0 Link encap:Ethernet HWaddr 00:30:48:2E:E1:F2 inet addr:10.0.0.10 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe2e:e1f2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7973410 errors:0 dropped:0 overruns:0 frame:0 TX packets:9299327 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:746369778 (711.7 Mb) TX bytes:8126772010 (7750.2 Mb) Base address:0x2000 Memory:da20-da22 client machine: eth1 Link encap:Ethernet HWaddr 00:30:48:55:92:4F inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe55:924f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:19720381 errors:0 dropped:0 overruns:0 frame:0 TX packets:16126186 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16315799815 (15559.9 Mb) TX bytes:1696496582 (1617.9 Mb) Base address:0xc400 Memory:fc9a-fc9c and the query runs fine a second time? so the query isnt malformed Regards, Doug -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: HELP [nativecode=2013 ** Lost connection to MySQL server during query]
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 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 the right direction? I notice if I remove the LIMIT statement I get fewer errors... but that cannot be the cause of the problem [14-Dec-2005 17:32:20] DB_Error Object ( [error_message_prefix] = [mode] = 1 [level] = 1024 [code] = -14 [message] = DB Error: no database selected [userinfo] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativecode=2013 ** Lost connection to MySQL server during query] [backtrace] = Array ( [0] = Array ( [file] = /usr/share/php5/PEAR/DB.php [line] = 888 [function] = PEAR_Error [class] = DB_Error [type] = - [args] = Array ( [0] = DB Error: no database selected [1] = -14 [2] = 1 [3] = 1024 [4] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativec ode=2013 ** Lost connection to MySQL server during query] ) ) -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: HELP [nativecode=2013 ** Lost connection to MySQL server during query]
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 through this document for the last week rewritten code based on the suggestions and still get the error. Regards, Doug 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 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 the right direction? I notice if I remove the LIMIT statement I get fewer errors... but that cannot be the cause of the problem [14-Dec-2005 17:32:20] DB_Error Object ( [error_message_prefix] = [mode] = 1 [level] = 1024 [code] = -14 [message] = DB Error: no database selected [userinfo] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativecode=2013 ** Lost connection to MySQL server during query] [backtrace] = Array ( [0] = Array ( [file] = /usr/share/php5/PEAR/DB.php [line] = 888 [function] = PEAR_Error [class] = DB_Error [type] = - [args] = Array ( [0] = DB Error: no database selected [1] = -14 [2] = 1 [3] = 1024 [4] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativec ode=2013 ** Lost connection to MySQL server during query] ) ) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: HELP [nativecode=2013 ** Lost connection to MySQL server during query]
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-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 through this document for the last week rewritten code based on the suggestions and still get the error. Regards, Doug 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 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 the right direction? I notice if I remove the LIMIT statement I get fewer errors... but that cannot be the cause of the problem [14-Dec-2005 17:32:20] DB_Error Object ( [error_message_prefix] = [mode] = 1 [level] = 1024 [code] = -14 [message] = DB Error: no database selected [userinfo] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativecode=2013 ** Lost connection to MySQL server during query] [backtrace] = Array ( [0] = Array ( [file] = /usr/share/php5/PEAR/DB.php [line] = 888 [function] = PEAR_Error [class] = DB_Error [type] = - [args] = Array ( [0] = DB Error: no database selected [1] = -14 [2] = 1 [3] = 1024 [4] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativec ode=2013 ** Lost connection to MySQL server during query] ) ) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: HELP [nativecode=2013 ** Lost connection to MySQL server during query]
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 perspective: db machine eth0 Link encap:Ethernet HWaddr 00:30:48:2E:E1:F2 inet addr:10.0.0.10 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe2e:e1f2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7973410 errors:0 dropped:0 overruns:0 frame:0 TX packets:9299327 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:746369778 (711.7 Mb) TX bytes:8126772010 (7750.2 Mb) Base address:0x2000 Memory:da20-da22 client machine: eth1 Link encap:Ethernet HWaddr 00:30:48:55:92:4F inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe55:924f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:19720381 errors:0 dropped:0 overruns:0 frame:0 TX packets:16126186 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16315799815 (15559.9 Mb) TX bytes:1696496582 (1617.9 Mb) Base address:0xc400 Memory:fc9a-fc9c and the query runs fine a second time? so the query isnt malformed Regards, Doug Doug Dalton wrote: 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-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 through this document for the last week rewritten code based on the suggestions and still get the error. Regards, Doug 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 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 the right direction? I notice if I remove the LIMIT statement I get fewer errors... but that cannot be the cause of the problem [14-Dec-2005 17:32:20] DB_Error Object ( [error_message_prefix] = [mode] = 1 [level] = 1024 [code] = -14 [message] = DB Error: no database selected [userinfo] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativecode=2013 ** Lost connection to MySQL server during query] [backtrace] = Array ( [0] = Array ( [file] = /usr/share/php5/PEAR/DB.php [line] = 888 [function] = PEAR_Error [class] = DB_Error [type] = - [args] = Array ( [0] = DB Error: no database selected [1] = -14 [2] = 1 [3] = 1024 [4] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativec ode=2013 ** Lost connection to MySQL server during query] ) ) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
HELP [nativecode=2013 ** Lost connection to MySQL server during query]
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 the right direction? I notice if I remove the LIMIT statement I get fewer errors... but that cannot be the cause of the problem [14-Dec-2005 17:32:20] DB_Error Object ( [error_message_prefix] = [mode] = 1 [level] = 1024 [code] = -14 [message] = DB Error: no database selected [userinfo] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativecode=2013 ** Lost connection to MySQL server during query] [backtrace] = Array ( [0] = Array ( [file] = /usr/share/php5/PEAR/DB.php [line] = 888 [function] = PEAR_Error [class] = DB_Error [type] = - [args] = Array ( [0] = DB Error: no database selected [1] = -14 [2] = 1 [3] = 1024 [4] = SELECT * FROM buser Where mUserID='d86659dcee2cf9933d84ea337b1b9785' LIMIT 0,1 [nativec ode=2013 ** Lost connection to MySQL server during query] ) ) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Lost connection to MySQL server during query when calling stored procedure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Fri, 23 Sep 2005, Jasper Bryant-Greene wrote: Thing is, even though I get that error, the server keeps running and accepting other connections and responding to queries fine. Probably because the mysqld_safe wrapper script has restarted it right after the crash. Take a look at the server's log files. My server log shows absolutely nothing after server startup, no matter how many times that stored procedure fails. I'm about to recompile with the debug USE flag (I'm on Gentoo) to try to track down the problem; once I've done that I'll file a bug. Before you file a bug, please re-test it with 5.0.13 - several SP-releated bugs have been fixed since 5.0.12 was released. If it's still repeatable in 5.0.13, please file a bug report at http://bugs.mysql.com. Thanks! Bye, LenZ - -- Lenz Grimmer [EMAIL PROTECTED] Senior Production Engineer MySQL GmbH, http://www.mysql.de/ Hamburg, Germany Are you MySQL certified? http://www.mysql.com/certification/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFDOOvWSVDhKrJykfIRAh8uAJ4n1NLXykT3Ob65mTK/VT239cQTpACfZaW8 bym5rslnYYYrOeJTZOXvnjw= =0fJP -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Lost connection to MySQL server during query when calling stored procedure
On Thursday, 22 September 2005 at 17:06:32 +1200, Jasper Bryant-Greene wrote: Jasper Bryant-Greene wrote: I have a stored procedure defined as follows: ... Sometimes when I execute this stored procedure ... I get the error Lost connection to MySQL server during query. I am using MySQL 5.0.12-beta-log on Gentoo Linux x86. This only seems to happen when accessing MySQL from PHP's MySQLi API, not when accessing it using the mysql command-line client. Is this a bug I should report to MySQL or to PHP? I'm not able to test other APIs at the moment. If the server dies, that's a MySQL problem. Take a look at http://bugs.mysql.com/ for information on how to report it. In particular, the server logs should give some information. Greg -- Greg Lehey, Senior Software Engineer MySQL AB, http://www.mysql.com/ Echunga, South Australia See complete headers for address and phone numbers. Are you MySQL certified? http://www.mysql.com/certification/ pgpjYgw1PlK8L.pgp Description: PGP signature
Re: Lost connection to MySQL server during query when calling stored procedure
Greg 'groggy' Lehey wrote: On Thursday, 22 September 2005 at 17:06:32 +1200, Jasper Bryant-Greene wrote: Jasper Bryant-Greene wrote: Sometimes when I execute this stored procedure ... I get the error Lost connection to MySQL server during query. I am using MySQL 5.0.12-beta-log on Gentoo Linux x86. This only seems to happen when accessing MySQL from PHP's MySQLi API, not when accessing it using the mysql command-line client. Is this a bug I should report to MySQL or to PHP? I'm not able to test other APIs at the moment. If the server dies, that's a MySQL problem. Take a look at http://bugs.mysql.com/ for information on how to report it. In particular, the server logs should give some information. Thing is, even though I get that error, the server keeps running and accepting other connections and responding to queries fine. My server log shows absolutely nothing after server startup, no matter how many times that stored procedure fails. I'm about to recompile with the debug USE flag (I'm on Gentoo) to try to track down the problem; once I've done that I'll file a bug. -- Jasper Bryant-Greene Freelance web developer http://jasper.bryant-greene.name/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Lost connection to MySQL server during query when calling stored procedure
I have a stored procedure defined as follows: CREATE PROCEDURE `album`.`getUser`( IN userID INT ) READS SQL DATA DETERMINISTIC SQL SECURITY INVOKER SELECT * FROM users WHERE id=userID LIMIT 1; Sometimes when I execute this stored procedure with, for example: CALL getUser(7); I get the error Lost connection to MySQL server during query. This only ever happens with stored procedures, never with any normal kind of query. I am using MySQL 5.0.12-beta-log on Gentoo Linux x86. -- Jasper Bryant-Greene Freelance web developer http://jasper.bryant-greene.name/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Lost connection to MySQL server during query when calling stored procedure
I have a stored procedure defined as follows: CREATE PROCEDURE `album`.`getUser`( IN userID INT ) READS SQL DATA DETERMINISTIC SQL SECURITY INVOKER SELECT * FROM users WHERE id=userID LIMIT 1; Sometimes when I execute this stored procedure with, for example: CALL getUser(7); I get the error Lost connection to MySQL server during query. This only ever happens with stored procedures, never with any normal kind of query. I am using MySQL 5.0.12-beta-log on Gentoo Linux x86. And what is your question? ;-) Most probably, a server crash... With regards, Martijn Tonies Database Workbench - tool for InterBase, Firebird, MySQL, Oracle MS SQL Server Upscene Productions http://www.upscene.com Database development questions? Check the forum! http://www.databasedevelopmentforum.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Lost connection to MySQL server during query when calling stored procedure
Martijn Tonies wrote: I have a stored procedure defined as follows: CREATE PROCEDURE `album`.`getUser`( IN userID INT ) READS SQL DATA DETERMINISTIC SQL SECURITY INVOKER SELECT * FROM users WHERE id=userID LIMIT 1; Sometimes when I execute this stored procedure with, for example: CALL getUser(7); I get the error Lost connection to MySQL server during query. This only ever happens with stored procedures, never with any normal kind of query. I am using MySQL 5.0.12-beta-log on Gentoo Linux x86. And what is your question? Fairly obviously, how do I fix it!? ;) Most probably, a server crash... Can you be a little bit more specific please? The MySQL server is working absolutely fine for everything else and also continues to respond to connections and queries perfectly after getting that error. Thanks -- Jasper Bryant-Greene Freelance web developer http://jasper.bryant-greene.name/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Lost connection to MySQL server during query when calling stored procedure
Hi, 2005/9/21, Jasper Bryant-Greene [EMAIL PROTECTED]: Martijn Tonies wrote: I have a stored procedure defined as follows: CREATE PROCEDURE `album`.`getUser`( IN userID INT ) READS SQL DATA DETERMINISTIC SQL SECURITY INVOKER SELECT * FROM users WHERE id=userID LIMIT 1; Sometimes when I execute this stored procedure with, for example: CALL getUser(7); I get the error Lost connection to MySQL server during query. This only ever happens with stored procedures, never with any normal kind of query. I am using MySQL 5.0.12-beta-log on Gentoo Linux x86. And what is your question? Fairly obviously, how do I fix it!? ;) Most probably, a server crash... Can you be a little bit more specific please? The MySQL server is working absolutely fine for everything else and also continues to respond to connections and queries perfectly after getting that error. I think he means, that you should try the official binaries, and this still happens, file a bug report because 5.0 is still in Beta stage. -- Pooly Webzine Rock : http://www.w-fenec.org/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Lost connection to MySQL server during query when calling stored procedure
What API are you using to call the SP from--PHP mysqli, Perl DBD-mysql, etc.? -Daniel Jasper Bryant-Greene wrote: I have a stored procedure defined as follows: CREATE PROCEDURE `album`.`getUser`( IN userID INT ) READS SQL DATA DETERMINISTIC SQL SECURITY INVOKER SELECT * FROM users WHERE id=userID LIMIT 1; Sometimes when I execute this stored procedure with, for example: CALL getUser(7); I get the error Lost connection to MySQL server during query. This only ever happens with stored procedures, never with any normal kind of query. I am using MySQL 5.0.12-beta-log on Gentoo Linux x86. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Lost connection to MySQL server during query when calling stored procedure
Daniel wrote: What API are you using to call the SP from--PHP mysqli, Perl DBD-mysql, etc.? PHP MySQLi Jasper Bryant-Greene wrote: I have a stored procedure defined as follows: CREATE PROCEDURE `album`.`getUser`( IN userID INT ) READS SQL DATA DETERMINISTIC SQL SECURITY INVOKER SELECT * FROM users WHERE id=userID LIMIT 1; Sometimes when I execute this stored procedure with, for example: CALL getUser(7); I get the error Lost connection to MySQL server during query. This only ever happens with stored procedures, never with any normal kind of query. I am using MySQL 5.0.12-beta-log on Gentoo Linux x86. -- Jasper Bryant-Greene Freelance web developer http://jasper.bryant-greene.name/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Lost connection to MySQL server during query when calling stored procedure
Jasper Bryant-Greene wrote: I have a stored procedure defined as follows: CREATE PROCEDURE `album`.`getUser`( IN userID INT ) READS SQL DATA DETERMINISTIC SQL SECURITY INVOKER SELECT * FROM users WHERE id=userID LIMIT 1; Sometimes when I execute this stored procedure with, for example: CALL getUser(7); I get the error Lost connection to MySQL server during query. This only ever happens with stored procedures, never with any normal kind of query. I am using MySQL 5.0.12-beta-log on Gentoo Linux x86. This only seems to happen when accessing MySQL from PHP's MySQLi API, not when accessing it using the mysql command-line client. Is this a bug I should report to MySQL or to PHP? I'm not able to test other APIs at the moment. -- Jasper Bryant-Greene Freelance web developer http://jasper.bryant-greene.name/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Please I need inputs on Lost connection to MySQL server during query
On Thursday 01 September 2005 20:41, Pooly wrote: Hi, what is the error in your error log ? im using MySQL-client-4.1.12-1 binary from mysql website i got this.. 050901 14:50:44 [Warning] Asked for 196608 thread stack, but got 126976 -- im trying to fix this by adding set-variable thread_stack=192K but everytime I restart the server i still get the warning.. 050901 14:50:45 InnoDB: Started; log sequence number 0 43951 050901 14:50:45 [Warning] mysql.user table is not updated to new password format; Disabling new password usage until mysql_fix_privilege_tables is run if ill be doing what the log file says execute mysql_fix_privilege_tables .. would there be any draw backs or problems that ill be encountering.. Does your server crash for every query it makes ? Or only some ? the server doesnt crash i check the uptime for the DB and its up fror 12 days.. Are you using the official binary from MySQL or the one used for you distro vendor ? no i downloaded the binary from mysql website.. Are you using UDF ? no ... We need more inputs ;-) 2005/9/1, JM [EMAIL PROTECTED]: Hi all, Ive read this link http://dev.mysql.com/doc/mysql/en/gone-away.html; hoping this has something to do with the error... Ive already checked based on the page the list of roots of error to produce gone-away.. w/c i hope leads to Lost connection to MySQL server during query and non of it is present. One thing Ive noticed. When I tried connecting using mysql client from web server to my DB box its takes time before mysql console shows-up after giving the password. Client and Server are connected through a LAN. Based on ping an average of .1 ms reply.. tia, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- Pooly Webzine Rock : http://www.w-fenec.org/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Please I need inputs on Lost connection to MySQL server during query
On Thursday 01 September 2005 22:14, [EMAIL PROTECTED] wrote: JM [EMAIL PROTECTED] wrote on 09/01/2005 06:01:57 AM: Hi all, Ive read this link http://dev.mysql.com/doc/mysql/en/gone-away. html hoping this has something to do with the error... Ive already checked based on the page the list of roots of error to produce gone-away.. w/c i hope leads to Lost connection to MySQL server during query and non of it is present. One thing Ive noticed. When I tried connecting using mysql client from web server to my DB box its takes time before mysql console shows-up after giving the password. Client and Server are connected through a LAN. Based on ping an average of .1 ms reply.. tia, OK, we have the error message (good). We know what you have looked at to solve the error (also good). What we don't have is what you did to create the error in the first place. the error is somehow unpredictable.. sometimes when i access the first page.. its works.. trying refreshing it.. after sometime its works. trying to do it every once so often then i encounter the problem... Please describe what you are doing to create the error, the data you are doing it with, and the tools involved in both ends of the process. Then we can understand your problem. Thanks! Shawn Green Database Administrator Unimin Corporation - Spruce Pine -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Please I need inputs on Lost connection to MySQL server during query
Hi all, Ive read this link http://dev.mysql.com/doc/mysql/en/gone-away.html; hoping this has something to do with the error... Ive already checked based on the page the list of roots of error to produce gone-away.. w/c i hope leads to Lost connection to MySQL server during query and non of it is present. One thing Ive noticed. When I tried connecting using mysql client from web server to my DB box its takes time before mysql console shows-up after giving the password. Client and Server are connected through a LAN. Based on ping an average of .1 ms reply.. tia, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Please I need inputs on Lost connection to MySQL server during query
Hi, what is the error in your error log ? Does your server crash for every query it makes ? Or only some ? Are you using the official binary from MySQL or the one used for you distro vendor ? Are you using UDF ? ... We need more inputs ;-) 2005/9/1, JM [EMAIL PROTECTED]: Hi all, Ive read this link http://dev.mysql.com/doc/mysql/en/gone-away.html; hoping this has something to do with the error... Ive already checked based on the page the list of roots of error to produce gone-away.. w/c i hope leads to Lost connection to MySQL server during query and non of it is present. One thing Ive noticed. When I tried connecting using mysql client from web server to my DB box its takes time before mysql console shows-up after giving the password. Client and Server are connected through a LAN. Based on ping an average of .1 ms reply.. tia, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- Pooly Webzine Rock : http://www.w-fenec.org/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Please I need inputs on Lost connection to MySQL server during query
JM [EMAIL PROTECTED] wrote on 09/01/2005 06:01:57 AM: Hi all, Ive read this link http://dev.mysql.com/doc/mysql/en/gone-away. html hoping this has something to do with the error... Ive already checked based on the page the list of roots of error to produce gone-away.. w/c i hope leads to Lost connection to MySQL server during query and non of it is present. One thing Ive noticed. When I tried connecting using mysql client from web server to my DB box its takes time before mysql console shows-up after giving the password. Client and Server are connected through a LAN. Based on ping an average of .1 ms reply.. tia, OK, we have the error message (good). We know what you have looked at to solve the error (also good). What we don't have is what you did to create the error in the first place. Please describe what you are doing to create the error, the data you are doing it with, and the tools involved in both ends of the process. Then we can understand your problem. Thanks! Shawn Green Database Administrator Unimin Corporation - Spruce Pine
Lost connection to MySQL server during query - on long queries
Hello, Each time we run long queries (over around 5 seconds) the mySQL server fails and restarts (you can see it in the error log that starts with Database page corruption on disk or a fail.. and then there is a dump...) and the query return with Lost connection to MySQL server during query... Using Linux 9 with mySQL 4.1.11-standard the tables are InnoDB The error is happening from everywhere: mysql command line, Query browser, from local and remote computers, running selects, insert and even check table, EMS client . Java (see below the log) The problem is probably not in the network parameters, see list of the variables below The database is quit big around 5 GB After the error the server restart automatically and continue to run for the short queries We found one place where long queries work - when we run from the query browser the same select * from some big table. However running from the same place check table... reproduce the error !. Again running the same select * from some big table from all the other palaces cause the server to fall Amir Server parameters 'back_log', '50' 'basedir', '/' 'binlog_cache_size', '32768' 'bulk_insert_buffer_size', '8388608' 'character_set_client', 'utf8' 'character_set_connection', 'utf8' 'character_set_database', 'hebrew' 'character_set_results', 'utf8' 'character_set_server', 'hebrew' 'character_set_system', 'utf8' 'character_sets_dir', '/usr/share/mysql/charsets/' 'collation_connection', 'utf8_general_ci' 'collation_database', 'hebrew_general_ci' 'collation_server', 'hebrew_general_ci' 'concurrent_insert', 'ON' 'connect_timeout', '100' 'datadir', '/var/lib/mysql/' 'date_format', '%Y-%m-%d' 'datetime_format', '%Y-%m-%d %H:%i:%s' 'default_week_format', '0' 'delay_key_write', 'ON' 'delayed_insert_limit', '100' 'delayed_insert_timeout', '300' 'delayed_queue_size', '1000' 'expire_logs_days', '0' 'flush', 'OFF' 'flush_time', '0' 'ft_boolean_syntax', '+ -()~*:|' 'ft_max_word_len', '84' 'ft_min_word_len', '4' 'ft_query_expansion_limit', '20' 'ft_stopword_file', '(built-in)' 'group_concat_max_len', '1024' 'have_archive', 'NO' 'have_bdb', 'NO' 'have_blackhole_engine', 'NO' 'have_compress', 'YES' 'have_crypt', 'YES' 'have_csv', 'NO' 'have_example_engine', 'NO' 'have_geometry', 'YES' 'have_innodb', 'YES' 'have_isam', 'NO' 'have_ndbcluster', 'NO' 'have_openssl', 'NO' 'have_query_cache', 'YES' 'have_raid', 'NO' 'have_rtree_keys', 'YES' 'have_symlink', 'YES' 'init_connect', '' 'init_file', '' 'init_slave', '' 'innodb_additional_mem_pool_size', '14680064' 'innodb_autoextend_increment', '8' 'innodb_buffer_pool_awe_mem_mb', '0' 'innodb_buffer_pool_size', '1073741824' 'innodb_data_file_path', 'ibdata1:10M:autoextend' 'innodb_data_home_dir', '/var/lib/mysql' 'innodb_fast_shutdown', 'ON' 'innodb_file_io_threads', '4' 'innodb_file_per_table', 'OFF' 'innodb_flush_log_at_trx_commit', '1' 'innodb_flush_method', '' 'innodb_force_recovery', '0' 'innodb_lock_wait_timeout', '50' 'innodb_locks_unsafe_for_binlog', 'OFF' 'innodb_log_arch_dir', '' 'innodb_log_archive', 'OFF' 'innodb_log_buffer_size', '1048576' 'innodb_log_file_size', '5242880' 'innodb_log_files_in_group', '2' 'innodb_log_group_home_dir', './' 'innodb_max_dirty_pages_pct', '90' 'innodb_max_purge_lag', '0' 'innodb_mirrored_log_groups', '1' 'innodb_open_files', '300' 'innodb_table_locks', 'ON' 'innodb_thread_concurrency', '8' 'interactive_timeout', '100' 'join_buffer_size', '131072' 'key_buffer_size', '8388600' 'key_cache_age_threshold', '300' 'key_cache_block_size', '1024' 'key_cache_division_limit', '100' 'language', '/usr/share/mysql/english/' 'large_files_support', 'ON' 'license', 'GPL' 'local_infile', 'ON' 'locked_in_memory', 'OFF' 'long_query_time', '10' 'low_priority_updates', 'OFF' 'lower_case_file_system', 'OFF' 'lower_case_table_names', '1' 'max_allowed_packet', '1047552' 'max_binlog_cache_size', '4294967295' 'max_binlog_size', '1073741824' 'max_connect_errors', '10' 'max_connections', '100' 'max_delayed_threads', '20' 'max_error_count', '64' 'max_heap_table_size', '16777216' 'max_insert_delayed_threads', '20' 'max_join_size', '4294967295' 'max_length_for_sort_data', '1024' 'max_relay_log_size', '0' 'max_seeks_for_key', '4294967295' 'max_sort_length', '1024' 'max_tmp_tables', '32' 'max_user_connections', '0' 'max_write_lock_count', '4294967295' 'net_buffer_length', '16384' 'net_read_timeout', '30' 'net_retry_count', '10' 'net_write_timeout', '60' 'new', 'OFF' 'old_passwords', 'OFF' 'open_files_limit', '1024' 'pid_file', '/var/lib/mysql/mendelson.lotonet.local.pid' 'port', '3306' 'preload_buffer_size', '32768' 'protocol_version', '10' 'query_alloc_block_size', '8192' 'query_cache_limit', '67108864' 'query_cache_min_res_unit', '4096' 'query_cache_size', '67108864' 'query_cache_type', 'ON' 'query_cache_wlock_invalidate', 'OFF' 'query_prealloc_size', '8192' 'range_alloc_block_size', '2048' 'read_buffer_size', '131072' 'read_only', 'OFF' 'read_rnd_buffer_size', '262144' 'relay_log_purge
