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

mysqld got signal 6

    XMLWordPrintable

    Details

      Description

      Mysql 8.0.13 in Macbook 10.14.1 failed to start and keeps restarting after a shutdown due to battery short.

      The following is the error log:
      *************************************
      InnoDB: End of page dump
      InnoDB: Page may be an index page where index id is 2018
      2020-10-30T15:52:45.615429Z 1 [ERROR] [MY-011825] [InnoDB] [FATAL] The page in the doublewrite buffer is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6
      2020-10-30T15:52:45.615446Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:620 thread 123145364848640
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      15:52:45 UTC - 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.
      Attempting to collect some information that could help diagnose the problem.
      As this is a crash and something is definitely wrong, the information
      collection process might fail.

      key_buffer_size=8388608
      read_buffer_size=131072
      max_used_connections=0
      max_threads=200
      thread_count=1
      connection_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 87232 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7fae30000000
      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 = 700003ba3ea0 thread_stack 0x46000
      0 mysqld 0x000000010edf0d4c my_print_stacktrace(unsigned char*, unsigned long) + 60
      1 mysqld 0x000000010e21e456 handle_fatal_signal + 678
      2 libsystem_platform.dylib 0x00007fff7a607b3d _sigtramp + 29
      3 ??? 0x0000700003b9ada0 0x0 + 123145364811168
      4 libsystem_c.dylib 0x00007fff7a4c61c9 abort + 127
      5 mysqld 0x000000010f199e99 ut_dbg_assertion_failed(char const*, char const*, unsigned long) + 329
      6 mysqld 0x000000010f19c8ca ib::fatal::~fatal() + 314
      7 mysqld 0x000000010f19c939 ib::fatal::~fatal() + 9
      8 mysqld 0x000000010ef102c9 buf_dblwr_recover_page(unsigned int, fil_space_t*, unsigned int, unsigned char const*) + 1513
      9 mysqld 0x000000010ef105bb buf_dblwr_recover_pages(fil_space_t*) + 107
      10 mysqld 0x000000010ef9ff05 Fil_system::open_for_recovery(unsigned int) + 789
      11 mysqld 0x000000010f0b3558 recv_apply_hashed_log_recs(log_t&, bool) + 520
      12 mysqld 0x000000010f15ac41 srv_start(bool, std::_1::basic_string<char, std::1::char_traits<char>, std::_1::allocator<char> > const&) + 6225
      13 mysqld 0x000000010f0248bd innobase_ddse_dict_init(dict_init_mode_t, unsigned int, List<dd::Object_table const>, List<Plugin_tablespace const>) + 525
      14 mysqld 0x000000010ebd2309 dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int) + 137
      15 mysqld 0x000000010edcd016 dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*) + 1830
      16 mysqld 0x000000010ddb691e bootstrap::handle_bootstrap(void*) + 222
      17 mysqld 0x000000010f1feadc pfs_spawn_thread(void*) + 316
      18 libsystem_pthread.dylib 0x00007fff7a610339 _pthread_body + 126
      19 libsystem_pthread.dylib 0x00007fff7a6132a7 _pthread_start + 70
      20 libsystem_pthread.dylib 0x00007fff7a60f445 thread_start + 13

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0): is an invalid pointer
      Connection ID (thread ID): 1
      Status: NOT_KILLED

      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.
      ^C

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              tsinyi JustinTsin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration