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

Mariadb initialize a shut down just after starting

    XMLWordPrintable

Details

    Description

      Hello,

      I've just encountered an issue with my setup and don't understand what happen...

      I've made a fresh install some days ago, tweak some settings, restart mariadb, and started to import thousands of tables through ssh because I had a problem with xtrabackup.

      My import process finished, i decided to shutdown mariadb to change the bind-adress et try to restart it ..... CRASH

      My first doubt was when i was watching the log and seen it hang on the message :"Highest supported file format is Barracuda."

      After 5min, the process has continued but starts a shutdown just after the message : "/usr/sbin/mysqld: ready for connections."

      I've tried to restart it multiple times with the same result.....

      See bellow the log:

      2016-05-23 18:31:14 131118867564480 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
      2016-05-23 18:31:14 131118867564480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2016-05-23 18:31:14 131118867564480 [Note] InnoDB: The InnoDB memory heap is disabled
      2016-05-23 18:31:14 131118867564480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2016-05-23 18:31:14 131118867564480 [Note] InnoDB: Memory barrier is not used
      2016-05-23 18:31:14 131118867564480 [Note] InnoDB: Compressed tables use zlib 1.2.8
      2016-05-23 18:31:14 131118867564480 [Note] InnoDB: Using Linux native AIO
      2016-05-23 18:31:14 131118867564480 [Note] InnoDB: Using SSE crc32 instructions
      2016-05-23 18:31:14 131118867564480 [Note] InnoDB: Initializing buffer pool, size = 80.0G
      2016-05-23 18:31:18 131118867564480 [Note] InnoDB: Completed initialization of buffer pool
      2016-05-23 18:31:18 131118867564480 [Note] InnoDB: Highest supported file format is Barracuda.
      2016-05-23 18:37:03 131118867564480 [Note] InnoDB: 128 rollback segment(s) are active.
      2016-05-23 18:37:03 131118867564480 [Note] InnoDB: Waiting for purge to start
      2016-05-23 18:37:03 131118867564480 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.29-76.2 started; log sequence number 5149822398415
      2016-05-23 18:37:03 131024369362688 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2016-05-23 18:37:03 131118867564480 [Note] Plugin 'FEEDBACK' is disabled.
      2016-05-23 18:37:04 131118867564480 [Note] Server socket created on IP: '127.0.0.1'.
      2016-05-23 18:37:04 131118865778432 [Note] /usr/sbin/mysqld: Normal shutdown
       
      2016-05-23 18:37:04 131118867564480 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.1.14-MariaDB-1~jessie'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
      2016-05-23 18:37:04 131118865778432 [Note] Event Scheduler: Purging the queue. 0 events
      2016-05-23 18:37:04 131024351069952 [Note] InnoDB: FTS optimize thread exiting.
      2016-05-23 18:37:04 131118865778432 [Note] InnoDB: Starting shutdown...
      2016-05-23 18:37:10 131118865778432 [Note] InnoDB: Shutdown completed; log sequence number 5149822398425
      2016-05-23 18:37:10 131118865778432 [Note] /usr/sbin/mysqld: Shutdown complete
      

      And this is my.cnf:

      sudo egrep -v "^#" /etc/mysql/my.cnf
       
      [client]
      port		= 3306
      socket		= /var/run/mysqld/mysqld.sock
       
       
      [mysqld_safe]
      socket		= /var/run/mysqld/mysqld.sock
      nice		= 0
       
      [mysqld]
      user		= mysql
      pid-file	= /var/run/mysqld/mysqld.pid
      socket		= /var/run/mysqld/mysqld.sock
      port		= 3306
      basedir		= /usr
      datadir		= /var/lib/mysql
      tmpdir		= /tmp
      datadir         = /home/mysql/db
      tmpdir          = /home/mysql/tmp
      lc-messages-dir	= /usr/share/mysql
      skip-external-locking
      bind-address		= 127.0.0.1
      key_buffer		= 16M
      max_allowed_packet	= 16M
      thread_stack		= 192K
      thread_cache_size       = 128
      bulk_insert_buffer_size = 16M
      tmp_table_size          = 32M
      max_heap_table_size     = 32M
       
      myisam-recover         = BACKUP
      max_connections        = 200
      connect_timeout         = 5
      wait_timeout            = 600
      query_cache_limit	= 1M
      query_cache_size        = 64M
      log_error = /var/log/mysql/error.log
      server-id		= 1
      log_bin			= /home/mysql/log/mysql-bin.log
      expire_logs_days	= 5
      max_binlog_size         = 100M
      default_storage_engine  = InnoDB
      innodb_log_file_size    = 1G
      innodb_log_files_in_group       = 8
      innodb_buffer_pool_size = 80G
      innodb_log_buffer_size  = 16M
      innodb_file_per_table   = 1
      innodb_open_files       = 400
      innodb_io_capacity      = 400
      innodb_flush_method     = O_DIRECT
       
      innodb_thread_concurrency       = 32
      innodb_log_group_home_dir       = /home/mysql/redo
      innodb_file_format      = Barracuda
       
       
       
       
      [mysqldump]
      quick
      quote-names
      max_allowed_packet	= 16M
       
      [mysql]
       
      [isamchk]
      key_buffer		= 16M
       
      !includedir /etc/mysql/conf.d/
      

      I hope you will have good news for me because I've spent many hours for this migration :-/

      Best regards,

      Attachments

        Issue Links

          Activity

            People

              jplindst Jan Lindström (Inactive)
              rockandska Yoann PANIER
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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