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

MariaDB Start AND Crash Loop

    XMLWordPrintable

Details

    Description

      A Server Xtrabackup And B Server Data Restore
      MariaDB start And Crash!!

      mairadb.log

      2019-03-05 20:24:41 140315674646400 [Note] CONNECT: Version 1.06.0007 August 06, 2018
      2019-03-05 20:24:41 140315674646400 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2019-03-05 20:24:41 140315674646400 [Note] InnoDB: Uses event mutexes
      2019-03-05 20:24:41 140315674646400 [Note] InnoDB: Compressed tables use zlib 1.2.3
      2019-03-05 20:24:41 140315674646400 [Note] InnoDB: Using Linux native AIO
      2019-03-05 20:24:41 140315674646400 [Note] InnoDB: Number of pools: 1
      2019-03-05 20:24:41 140315674646400 [Note] InnoDB: Using SSE2 crc32 instructions
      2019-03-05 20:24:41 140315674646400 [Note] InnoDB: Initializing buffer pool, total size = 88G, instances = 64, chunk size = 128M
      2019-03-05 20:24:44 140315674646400 [Note] InnoDB: Completed initialization of buffer pool
      2019-03-05 20:24:45 140210880632576 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2019-03-05 20:24:45 140315674646400 [Note] InnoDB: Highest supported file format is Barracuda.
      2019-03-05 20:24:47 140315674646400 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2019-03-05 20:24:47 140315674646400 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2019-03-05 20:24:47 140315674646400 [Note] InnoDB: Creating shared tablespace for temporary tables
      2019-03-05 20:24:47 140315674646400 [Note] InnoDB: Setting file '/data/mariadata/data/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2019-03-05 20:24:47 140315674646400 [Note] InnoDB: File '/data/mariadata/data/ibtmp1' size is now 12 MB.
      2019-03-05 20:24:47 140315674646400 [Note] InnoDB: Waiting for purge to start
      2019-03-05 20:24:47 140315674646400 [Note] InnoDB: 5.7.23 started; log sequence number 8426277837864
      2019-03-05 20:24:47 140210360768256 [Note] InnoDB: Loading buffer pool(s) from /data/mariadata/data/ib_buffer_pool
      2019-03-05 20:24:47 140315674646400 [Note] Plugin 'FEEDBACK' is disabled.
      190305 20:24:47 server_audit: MariaDB Audit Plugin version 1.4.4 STARTED.
      2019-03-05 20:24:47 140315674646400 [Note] Semi-sync replication initialized for transactions.
      2019-03-05 20:24:47 140315674646400 [Note] Semi-sync replication enabled on the master.
      2019-03-05 20:24:47 140315674646400 [Note] Server socket created on IP: '0.0.0.0'.
      2019-03-05 20:24:47 140315673286400 [Note] Event Scheduler: scheduler thread started with id 7
      2019-03-05 20:24:47 140315674646400 [Note] Reading of all Master_info entries succeded
      2019-03-05 20:24:47 140315674646400 [Note] Added new Master_info '' to hash table
      2019-03-05 20:24:47 140315674646400 [Note] /data/mariadb/bin/mysqld: ready for connections.
      Version: '10.2.17-MariaDB-log' socket: '/tmp/mysql.sock' port: 3306 MariaDB Server
      2019-03-05 20:24:48 140210360768256 [ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.
      190305 20:24:48 [ERROR] mysqld got signal 6 ;
      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 https://mariadb.com/kb/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.2.17-MariaDB-log
      key_buffer_size=67108864
      read_buffer_size=4194304
      max_used_connections=0
      max_threads=1025
      thread_count=8
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 12682629 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0
      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 0x49000
      /data/mariadb/bin/mysqld(my_print_stacktrace+0x2b)[0x55bad786f4fb]
      /data/mariadb/bin/mysqld(handle_fatal_signal+0x535)[0x55bad7339ca5]
      /lib64/libpthread.so.0(+0xf5e0)[0x7f9dc8e815e0]
      /lib64/libc.so.6(gsignal+0x37)[0x7f9dc84da1f7]
      :0(__GI_raise)[0x7f9dc84db8e8]
      /data/mariadb/bin/mysqld(+0x99ae7a)[0x55bad763ce7a]
      /data/mariadb/bin/mysqld(+0x9dffe1)[0x55bad7681fe1]
      /data/mariadb/bin/mysqld(+0xa02510)[0x55bad76a4510]
      ut/ut0ut.cc:792(ib::fatal::~fatal())[0x55bad76a5b48]
      include/sync0rw.ic:455(buf_page_io_complete(buf_page_t*, bool, bool))[0x55bad7690464]
      buf/buf0rea.cc:227(buf_read_page_low(dberr_t*, bool, unsigned long, unsigned long, page_id_t const&, page_size_t const&, bool, bool))[0x55bad769085b]
      /lib64/libpthread.so.0(+0x7e25)[0x7f9dc8e79e25]
      /lib64/libc.so.6(clone+0x6d)[0x7f9dc859d34d]
      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.
      2019-03-05 20:24:52 140449149761408 [Note] CONNECT: Version 1.06.0007 August 06, 2018
      2019-03-05 20:24:52 140449149761408 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2019-03-05 20:24:52 140449149761408 [Note] InnoDB: Uses event mutexes
      2019-03-05 20:24:52 140449149761408 [Note] InnoDB: Compressed tables use zlib 1.2.3
      2019-03-05 20:24:52 140449149761408 [Note] InnoDB: Using Linux native AIO
      2019-03-05 20:24:52 140449149761408 [Note] InnoDB: Number of pools: 1
      2019-03-05 20:24:52 140449149761408 [Note] InnoDB: Using SSE2 crc32 instructions
      2019-03-05 20:24:52 140449149761408 [Note] InnoDB: Initializing buffer pool, total size = 88G, instances = 64, chunk size = 128M
      2019-03-05 20:24:56 140449149761408 [Note] InnoDB: Completed initialization of buffer pool
      2019-03-05 20:24:57 140344355968768 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2019-03-05 20:24:57 140449149761408 [Note] InnoDB: Highest supported file format is Barracuda.
      2019-03-05 20:24:57 140449149761408 [Note] InnoDB: Starting crash recovery from checkpoint LSN=8426277837883
      2019-03-05 20:24:59 140449149761408 [Note] InnoDB: Last binlog file '/log/mariadb_log/mysql-bin.000013', position 299283542
      2019-03-05 20:25:00 140449149761408 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2019-03-05 20:25:00 140449149761408 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2019-03-05 20:25:00 140449149761408 [Note] InnoDB: Creating shared tablespace for temporary tables
      2019-03-05 20:25:00 140449149761408 [Note] InnoDB: Setting file '/data/mariadata/data/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2019-03-05 20:25:00 140449149761408 [Note] InnoDB: File '/data/mariadata/data/ibtmp1' size is now 12 MB.
      2019-03-05 20:25:00 140449149761408 [Note] InnoDB: Waiting for purge to start
      2019-03-05 20:25:00 140449149761408 [Note] InnoDB: 5.7.23 started; log sequence number 8426277837892
      2019-03-05 20:25:00 140343827719936 [Note] InnoDB: Loading buffer pool(s) from /data/mariadata/data/ib_buffer_pool
      2019-03-05 20:25:00 140449149761408 [Note] Plugin 'FEEDBACK' is disabled.
      190305 20:25:00 server_audit: MariaDB Audit Plugin version 1.4.4 STARTED.
      2019-03-05 20:25:00 140449149761408 [Note] Semi-sync replication initialized for transactions.
      2019-03-05 20:25:00 140449149761408 [Note] Semi-sync replication enabled on the master.
      2019-03-05 20:25:00 140449149761408 [Note] Recovering after a crash using /log/mariadb_log/mysql-bin
      2019-03-05 20:25:00 140449149761408 [Note] Starting crash recovery...
      2019-03-05 20:25:00 140449149761408 [Note] Crash recovery finished.
      2019-03-05 20:25:00 140449149761408 [Note] Server socket created on IP: '0.0.0.0'.
      2019-03-05 20:25:00 140449148401408 [Note] Event Scheduler: scheduler thread started with id 7
      2019-03-05 20:25:00 140449149761408 [Note] Reading of all Master_info entries succeded
      2019-03-05 20:25:00 140449149761408 [Note] Added new Master_info '' to hash table
      2019-03-05 20:25:00 140449149761408 [Note] /data/mariadb/bin/mysqld: ready for connections.
      Version: '10.2.17-MariaDB-log' socket: '/tmp/mysql.sock' port: 3306 MariaDB Server
      2019-03-05 20:25:01 140343827719936 [ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page.
      190305 20:25:01 [ERROR] mysqld got signal 6 ;
      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 https://mariadb.com/kb/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.2.17-MariaDB-log
      key_buffer_size=67108864
      read_buffer_size=4194304
      max_used_connections=0
      max_threads=1025
      thread_count=8
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 12682629 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0
      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 0x49000
      /data/mariadb/bin/mysqld(my_print_stacktrace+0x2b)[0x55dfa27a24fb]
      /data/mariadb/bin/mysqld(handle_fatal_signal+0x535)[0x55dfa226cca5]
      /lib64/libpthread.so.0(+0xf5e0)[0x7fbcdca4b5e0]
      /lib64/libc.so.6(gsignal+0x37)[0x7fbcdc0a41f7]
      :0(__GI_raise)[0x7fbcdc0a58e8]
      /data/mariadb/bin/mysqld(+0x99ae7a)[0x55dfa256fe7a]
      ut/ut0ut.cc:792(ib::fatal::~fatal())[0x55dfa25b4fe1]
      include/sync0rw.ic:455(buf_page_io_complete(buf_page_t*, bool, bool))[0x55dfa25d7510]
      buf/buf0rea.cc:227(buf_read_page_low(dberr_t*, bool, unsigned long, unsigned long, page_id_t const&, page_size_t const&, bool, bool))[0x55dfa25d8b48]
      :0(buf_read_page_background(page_id_t const&, page_size_t const&, bool))[0x55dfa25c3464]
      buf/buf0dump.cc:720(buf_load())[0x55dfa25c385b]
      /lib64/libpthread.so.0(+0x7e25)[0x7fbcdca43e25]
      /lib64/libc.so.6(clone+0x6d)[0x7fbcdc16734d]
      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.
      2019-03-05 20:25:04 140103609575296 [Note] CONNECT: Version 1.06.0007 August 06, 2018
      2019-03-05 20:25:04 140103609575296 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2019-03-05 20:25:04 140103609575296 [Note] InnoDB: Uses event mutexes
      2019-03-05 20:25:04 140103609575296 [Note] InnoDB: Compressed tables use zlib 1.2.3
      2019-03-05 20:25:04 140103609575296 [Note] InnoDB: Using Linux native AIO
      2019-03-05 20:25:04 140103609575296 [Note] InnoDB: Number of pools: 1
      2019-03-05 20:25:04 140103609575296 [Note] InnoDB: Using SSE2 crc32 instructions
      2019-03-05 20:25:04 140103609575296 [Note] InnoDB: Initializing buffer pool, total size = 88G, instances = 64, chunk size = 128M
      2019-03-05 20:25:07 140103609575296 [Note] InnoDB: Completed initialization of buffer pool
      2019-03-05 20:25:08 139998816622336 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2019-03-05 20:25:08 140103609575296 [Note] InnoDB: Highest supported file format is Barracuda.
      2019-03-05 20:25:09 140103609575296 [Note] InnoDB: Starting crash recovery from checkpoint LSN=8426277837920
      2019-03-05 20:25:11 140103609575296 [Note] InnoDB: Last binlog file '/log/mariadb_log/mysql-bin.000013', position 299283542
      2019-03-05 20:25:11 140103609575296 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2019-03-05 20:25:11 140103609575296 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2019-03-05 20:25:11 140103609575296 [Note] InnoDB: Creating shared tablespace for temporary tables
      2019-03-05 20:25:11 140103609575296 [Note] InnoDB: Setting file '/data/mariadata/data/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2019-03-05 20:25:11 140103609575296 [Note] InnoDB: File '/data/mariadata/data/ibtmp1' size is now 12 MB.
      2019-03-05 20:25:11 140103609575296 [Note] InnoDB: Waiting for purge to start
      2019-03-05 20:25:11 140103609575296 [Note] InnoDB: 5.7.23 started; log sequence number 8426277837929
      2019-03-05 20:25:11 139998288373504 [Note] InnoDB: Loading buffer pool(s) from /data/mariadata/data/ib_buffer_pool
      2019-03-05 20:25:11 140103609575296 [Note] Plugin 'FEEDBACK' is disabled.
      190305 20:25:11 server_audit: MariaDB Audit Plugin version 1.4.4 STARTED.
      2019-03-05 20:25:11 140103609575296 [Note] Semi-sync replication initialized for transactions.
      2019-03-05 20:25:11 140103609575296 [Note] Semi-sync replication enabled on the master.
      2019-03-05 20:25:11 140103609575296 [Note] Recovering after a crash using /log/mariadb_log/mysql-bin
      2019-03-05 20:25:11 140103609575296 [Note] Starting crash recovery...
      2019-03-05 20:25:11 140103609575296 [Note] Crash recovery finished.
      2019-03-05 20:25:11 140103609575296 [Note] Server socket created on IP: '0.0.0.0'.
      2019-03-05 20:25:11 140103608215296 [Note] Event Scheduler: scheduler thread started with id 7
      2019-03-05 20:25:11 140103609575296 [Note] Reading of all Master_info entries succeded
      2019-03-05 20:25:11 140103609575296 [Note] Added new Master_info '' to hash table
      2019-03-05 20:25:11 140103609575296 [Note] /data/mariadb/bin/mysqld: ready for connections.
      Version: '10.2.17-MariaDB-log' socket: '/tmp/mysql.sock' port: 3306 MariaDB Server

      Attachments

        Activity

          People

            Unassigned Unassigned
            nyxneuf Na Yun Ho
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.