Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
5.5.43
-
None
-
Ubuntu 14.04 x64_64
Description
mysqld segfaults on startup.
Stack trace below.
It then restarts through mysqld_safe, and after that appears to be ok-ish with clients able to connect. But it's not in good shape. There may be InnoDB tables with corruption in this installation, which could be a possible trigger for the crash - however, a segfault is always a bug. An specific assert from InnoDB would be (although still annoying) more useful as then more context is shown.
150506 13:41:19 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
|
150506 13:41:19 [Note] /usr/sbin/mysqld (mysqld 5.5.43-MariaDB-1~trusty) starting as process 19351 ...
|
150506 13:41:19 InnoDB: The InnoDB memory heap is disabled
|
150506 13:41:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
150506 13:41:19 InnoDB: Compressed tables use zlib 1.2.8
|
150506 13:41:19 InnoDB: Using Linux native AIO
|
150506 13:41:19 InnoDB: Initializing buffer pool, size = 16.0G
|
150506 13:41:19 InnoDB: Completed initialization of buffer pool
|
150506 13:41:19 InnoDB: highest supported file format is Barracuda.
|
150506 13:41:19 InnoDB: Waiting for the background threads to start
|
150506 13:41:20 Percona XtraDB (http://www.percona.com) 5.5.42-MariaDB-37.1 started; log sequence number 74624717726974
|
150506 13:41:20 [Note] Plugin 'FEEDBACK' is disabled.
|
150506 13:41:20 [Note] Server socket created on IP: '0.0.0.0'.
|
150506 13:41:20 [Note] Event Scheduler: Loaded 0 events
|
150506 13:41:20 [Note] /usr/sbin/mysqld: ready for connections.
|
Version: '5.5.43-MariaDB-1~trusty' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
|
150506 13:41:20 [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: 5.5.43-MariaDB-1~trusty
|
key_buffer_size=16777216
|
read_buffer_size=131072
|
max_used_connections=1
|
max_threads=153
|
thread_count=1
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352025 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x0x7f0661bce000
|
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 = 0x7f0ab8ec9e40 thread_stack 0x30000
|
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f0ab981dcee]
|
/usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7f0ab940ed77]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f0ab84bc340]
|
/usr/sbin/mysqld(+0x66888d)[0x7f0ab95ad88d]
|
/usr/sbin/mysqld(+0x675c6d)[0x7f0ab95bac6d]
|
/usr/sbin/mysqld(+0x4560df)[0x7f0ab939b0df]
|
/usr/sbin/mysqld(_ZN22Repair_table_statement7executeEP3THD+0xcc)[0x7f0ab939b9fc]
|
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1970)[0x7f0ab92c85e0]
|
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11a)[0x7f0ab92cd8ba]
|
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1896)[0x7f0ab92cf9e6]
|
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c3)[0x7f0ab938dd13]
|
/usr/sbin/mysqld(handle_one_connection+0x4a)[0x7f0ab938de0a]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f0ab84b4182]
|
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0ab759e47d]
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x7f064841d018): is an invalid pointer
|
Connection ID (thread ID): 6
|
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=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.
|
150506 13:41:20 mysqld_safe Number of processes running now: 0
|
150506 13:41:20 mysqld_safe mysqld restarted
|
Attachments
Issue Links
- is duplicated by
-
MDEV-8115 mysql_upgrade crashes the server with REPAIR VIEW
- Closed