Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-8108

MariaDB 5.5.43 segfaults on startup




      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: ''.
      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
      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
      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


        Issue Links



              serg Sergei Golubchik
              arjen Arjen Lentz
              1 Vote for this issue
              5 Start watching this issue



                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.