I'm running Mariadb 10.0.11 on linux/64.
Connected to my DB, executing similar queries, one succeeds, the next
fails @ error
"ERROR 2013 (HY000): Lost connection to MySQL server during
query"
There's a backtrace included below. I'm not sure what it tells me about
the problem, or what to do about. Any help or suggestions would be
appreciated.
Here are the queries
MariaDB [dTEST]> UPDATE system SET status='0' WHERE
name='tagclouds';
Query OK, 0 rows affected (0.00 sec)
Rows matched: 1 Changed: 0 Warnings: 0
MariaDB [dTEST]> UPDATE system SET status='0' WHERE
name='tagclouds';
Query OK, 0 rows affected (0.00 sec)
Rows matched: 1 Changed: 0 Warnings: 0
MariaDB [dTEST]> UPDATE system SET status='0' WHERE
name='system_charts';
ERROR 2013 (HY000): Lost connection to MySQL server during query
MariaDB [dTEST]> UPDATE system SET status='0' WHERE
name='system_charts';
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 3
Current database: dTEST
ERROR 2013 (HY000): Lost connection to MySQL server during query
MariaDB [dTEST]> UPDATE system SET status='0' WHERE
name='system_charts';
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 3
Current database: dTEST
ERROR 2013 (HY000): Lost connection to MySQL server during query
MariaDB [dTEST]> UPDATE system SET status='0' WHERE
name='tagclouds';
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 3
Current database: dTEST
Query OK, 0 rows affected (0.09 sec)
Rows matched: 1 Changed: 0 Warnings: 0
MariaDB [dTEST]>
Here's the -err log on failed exec of
UPDATE system SET status='0' WHERE name='system_charts';
tail -f /var/log/mariadb/mariadb-err.log
140612 22:34:39 [ERROR] 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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.
Server version: 10.0.11-MariaDB-log
key_buffer_size=268435456
read_buffer_size=1048576
max_used_connections=1
max_threads=66
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_threads = 601410 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x7f2de93f1008
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...
stack_bottom = 0x7f2e11fe5e78 thread_stack 0x100000
/usr/local/mariadb/bin/mysqld(my_print_stacktrace+0x2e)[0xacb60e]
/usr/local/mariadb/bin/mysqld(handle_fatal_signal+0x390)[0x6f5a10]
/lib64/libpthread.so.0(+0xf9f0)[0x7f2e177f79f0]
/usr/local/mariadb/bin/mysqld[0x915cba]
/usr/local/mariadb/bin/mysqld[0x909e27]
/usr/local/mariadb/bin/mysqld[0x90a35b]
/usr/local/mariadb/bin/mysqld[0x916853]
/usr/local/mariadb/bin/mysqld[0x8a9aa6]
/usr/local/mariadb/bin/mysqld[0x8ab639]
/usr/local/mariadb/bin/mysqld[0x8cd5a7]
/usr/local/mariadb/bin/mysqld[0x8d0cfc]
/usr/local/mariadb/bin/mysqld[0x8b5777]
/usr/local/mariadb/bin/mysqld[0x82ef43]
/usr/local/mariadb/bin/mysqld(_ZN7handler13ha_update_rowEPKhPh+0xe5)[0x6fedc5]
/usr/local/mariadb/bin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x10e2)[0x641922]
/usr/local/mariadb/bin/mysqld(_Z21mysql_execute_commandP3THD+0x191b)[0x5b923b]
/usr/local/mariadb/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1d7)[0x5bf4f7]
/usr/local/mariadb/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x15d7)[0x5c1057]
/usr/local/mariadb/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x20c)[0x66f0ec]
/usr/local/mariadb/bin/mysqld(handle_one_connection+0x38)[0x66f138]
/usr/local/mariadb/bin/mysqld[0x9d5184]
/lib64/libpthread.so.0(+0x80db)[0x7f2e177f00db]
/lib64/libc.so.6(clone+0x6d)[0x7f2e164a090d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f2dd8c3e020): UPDATE system SET status='0' WHERE
name='system_charts'
Connection ID (thread ID): 3
Status: NOT_KILLED
Optimizer switch:
index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=off
The manual page at
http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the
crash.
140612 22:34:39 mysqld_safe Number of processes running now: 0
140612 22:34:39 mysqld_safe mysqld restarted
2014-06-12 22:34:39 7f025c6d9780 InnoDB: Warning: Using
innodb_additional_mem_pool_size is DEPRECATED. This option may
be removed in future releases, together with the option
innodb_use_sys_malloc and with the InnoDB's internal memory
allocator.
140612 22:34:39 [Note] InnoDB: Using mutexes to ref count buffer
pool pages
140612 22:34:39 [Note] InnoDB: The InnoDB memory heap is
disabled
140612 22:34:39 [Note] InnoDB: Mutexes and rw_locks use GCC
atomic builtins
140612 22:34:39 [Note] InnoDB: Compressed tables use zlib 1.2.8
140612 22:34:39 [Note] InnoDB: Using Linux native AIO
140612 22:34:39 [Note] InnoDB: Not using CPU crc32 instructions
140612 22:34:39 [Note] InnoDB: Initializing buffer pool, size =
256.0M
140612 22:34:39 [Note] InnoDB: Completed initialization of
buffer pool
140612 22:34:39 [Note] InnoDB: Highest supported file format is
Barracuda.
140612 22:34:39 [Note] InnoDB: The log sequence numbers
736578572 and 736578572 in ibdata files do not match the log
sequence number 736659958 in the ib_logfiles!
140612 22:34:39 [Note] InnoDB: Database was not shutdown
normally!
140612 22:34:39 [Note] InnoDB: Starting crash recovery.
140612 22:34:39 [Note] InnoDB: Reading tablespace information
from the .ibd files...
140612 22:34:39 [Note] InnoDB: Restoring possible half-written
data pages
140612 22:34:39 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 6422, file name
/var/log/mariadb/mariadb-bin.000270
140612 22:34:39 [Note] InnoDB: 128 rollback segment(s) are
active.
140612 22:34:39 [Note] InnoDB: Waiting for purge to start
140612 22:34:39 [Note] InnoDB: Percona XtraDB
(http://www.percona.com) 5.6.17-65.0 started; log sequence
number 736659958
140612 22:34:39 [Note] Recovering after a crash using
/var/log/mariadb/mariadb-bin
140612 22:34:39 [Note] Starting crash recovery...
140612 22:34:39 [Note] Crash recovery finished.
140612 22:34:39 [Note] Server socket created on IP: '127.0.0.1'.
140612 22:34:39 [Note] Event Scheduler: Loaded 0 events
140612 22:34:39 [Note] /usr/local/mariadb/bin/mysqld: ready for
connections.
Version: '10.0.11-MariaDB-log' socket:
'/var/cache/mariadb/mariadb.sock' port: 3306 Source
distribution
_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp
