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

new server crashed




      Server crashed at the starting time, just after is has been installed.

      error log:

      151119 17:18:34 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      151119 17:18:34 [Note] InnoDB: The InnoDB memory heap is disabled
      151119 17:18:34 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      151119 17:18:34 [Note] InnoDB: Compressed tables use zlib 1.2.3
      151119 17:18:34 [Note] InnoDB: Using CPU crc32 instructions
      151119 17:18:34 [Note] InnoDB: Initializing buffer pool, size = 600.0M
      151119 17:18:34 [Note] InnoDB: Completed initialization of buffer pool
      151119 17:18:34 [Note] InnoDB: Highest supported file format is Barracuda.
      151119 17:18:34 [Note] InnoDB: 128 rollback segment(s) are active.
      151119 17:18:34 [Note] InnoDB: Waiting for purge to start
      151119 17:18:34 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.17-65.0 started; log sequence number 1616718
      151119 17:18:34 [Note] Semi-sync replication initialized for transactions.
      151119 17:18:34 [Note] Semi-sync replication enabled on the master.
      151119 17:18:34 server_audit: MariaDB Audit Plugin version 1.1.7 STARTED.
      151119 17:18:34 [Note] Server socket created on IP: ''.
      Status information:
      Current dir: /home/maria76/data/data/
      Running threads: 0  Stack size: 294912
      Current locks:
      lock: 0x7f5472c60d88:
      lock: 0x7f53c8018508:
      lock: 0x18f1760:
      lock: 0x18f1680:
      lock: 0x18f06c0:
      lock: 0x18f05e0:
      lock: 0x18f0500:
      lock: 0x18f0880:
      lock: 0x18eeac0:
      lock: 0x18f15a0:
      lock: 0x18ef1c0:
      lock: 0x18ef460:
      lock: 0x18ef0e0:
      lock: 0x18ef380:
      lock: 0x18ef000:
      lock: 0x18ef2a0:
      lock: 0x18ef9a0:
      lock: 0x18ef8c0:
      lock: 0x18ef7e0:
      lock: 0x18eef20:
      lock: 0x18eec80:
      lock: 0x18eee40:
      lock: 0x18eeba0:
      lock: 0x18eed60:
      lock: 0x18ef700:
      lock: 0x18ef620:
      lock: 0x18ef540:
      lock: 0x18f1220:
      lock: 0x18f14c0:
      lock: 0x18f13e0:
      lock: 0x18f1300:
      lock: 0x18f0ea0:
      lock: 0x18f0dc0:
      lock: 0x18f0ce0:
      lock: 0x18f0c00:
      lock: 0x18f0b20:
      lock: 0x18f1060:
      lock: 0x18f0a40:
      lock: 0x18f0960:
      lock: 0x18f0f80:
      lock: 0x18f07a0:
      lock: 0x18f0340:
      lock: 0x18f0420:
      lock: 0x18f0260:
      lock: 0x18f0180:
      lock: 0x18efe00:
      lock: 0x18f00a0:
      lock: 0x18effc0:
      lock: 0x18efd20:
      lock: 0x18efee0:
      lock: 0x18efc40:
      lock: 0x18efb60:
      lock: 0x18efa80:
      lock: 0x18f1140:
      151119 17:18:34 [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.12-MariaDB-log
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137032 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x0x0
      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 = 0x0 thread_stack 0x48000
      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.




            serg Sergei Golubchik
            linzhoukai Zhoukai Lin
            0 Vote for this issue
            3 Start watching this issue



              Git Integration

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