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

Servidor dejó de funcionar después de actualización automática de WHM

    XMLWordPrintable

    Details

      Description

      2019-11-06 11:23:45 139963087685600 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2019-11-06 11:23:45 139963087685600 [Note] InnoDB: Uses event mutexes
      2019-11-06 11:23:45 139963087685600 [Note] InnoDB: Compressed tables use zlib 1.2.3
      2019-11-06 11:23:45 139963087685600 [Note] InnoDB: Using Linux native AIO
      2019-11-06 11:23:45 139963087685600 [Note] InnoDB: Number of pools: 1
      2019-11-06 11:23:45 139963087685600 [Note] InnoDB: Using generic crc32 instructions
      2019-11-06 11:23:45 139963087685600 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
      2019-11-06 11:23:45 139963087685600 [Note] InnoDB: Completed initialization of buffer pool
      2019-11-06 11:23:45 139962304194304 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2019-11-06 11:23:45 139963087685600 [Note] InnoDB: Highest supported file format is Barracuda.
      2019-11-06 11:23:45 0x7f4bb21f87e0 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.28/storage/innobase/dict/dict0dict.cc line 1467
      InnoDB: Failing assertion: table->can_be_evicted
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      191106 11:23:45 [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.28-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=153
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467243 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
      mysys/stacktrace.c:268(my_print_stacktrace)[0x7f4bb1aa27bb]
      sql/signal_handler.cc:209(handle_fatal_signal)[0x7f4bb156d4f5]
      sigaction.c:0(__restore_rt)[0x7f4bb0a7b7e0]
      /lib64/libc.so.6(gsignal+0x35)[0x7f4baf0d54f5]
      /lib64/libc.so.6(abort+0x175)[0x7f4baf0d6cd5]
      ut/ut0rbt.cc:458(rbt_eject_node)[0x7f4bb13325d5]
      dict/dict0dict.cc:1467(dict_table_move_from_lru_to_non_lru(dict_table_t*))[0x7f4bb18e54d7]
      dict/dict0load.cc:3128(dict_load_table_one)[0x7f4bb18fcaea]
      dict/dict0load.cc:2797(dict_load_table(char const*, dict_err_ignore_t))[0x7f4bb18fd32d]
      dict/dict0load.cc:3222(dict_load_table_on_id(unsigned long, dict_err_ignore_t))[0x7f4bb18fe8d8]
      dict/dict0dict.cc:1011(dict_table_open_on_id(unsigned long, unsigned long, dict_table_op_t))[0x7f4bb18e9910]
      fts/fts0fts.cc:6443(fts_valid_parent_table)[0x7f4bb195baf8]
      log/log0recv.cc:4037(recv_recovery_rollback_active())[0x7f4bb176e50a]
      srv/srv0start.cc:2521(innobase_start_or_create_for_mysql())[0x7f4bb1829ce5]
      handler/ha_innodb.cc:4372(innobase_init)[0x7f4bb1710431]
      sql/handler.cc:555(ha_initialize_handlerton(st_plugin_int*))[0x7f4bb156fe18]
      sql/sql_plugin.cc:1417(plugin_initialize)[0x7f4bb13f4c51]
      sql/sql_plugin.cc:1698(plugin_init(int*, char**, int))[0x7f4bb13f5bba]
      sql/mysqld.cc:5333(init_server_components)[0x7f4bb13568f9]
      sql/mysqld.cc:5929(mysqld_main(int, char**))[0x7f4bb135a323]
      /lib64/libc.so.6(__libc_start_main+0x100)[0x7f4baf0c1d20]
      /usr/sbin/mysqld(+0x4a2299)[0x7f4bb134e299]
      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.
      Writing a core file...
      Working directory at /var/lib/mysql
      Core pattern: core

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              fausto1389 Fausto Trujillo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: