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

InnoDB: Assertion failure in file /home/buildbot/buildbot





      MariaDB has stopped responding suddenly. MariaDB service status shows as it is running but we could not login to the MySQL. each login attempt got hanged and the service restart attempt was also got hanged. We had to kill the MySQL process manually and start the service again,

      Following is what we found in the log

      2021-09-10 07:45:16 0x7f4b447ad700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.34/storage/innobase/sync/sync0rw.cc line 259
      InnoDB: Failing assertion: lock->lock_word == X_LOCK_DECR
      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.
      210910 7:45:16 [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.34-MariaDB-log


      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2772248 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f4a800009a8
      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 = 0x7f4b447acd30 thread_stack 0x49000
      2021-09-10 8:21:36 139949292594944 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Uses event mutexes
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Compressed tables use zlib 1.2.7
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Using Linux native AIO
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Number of pools: 1
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Using SSE2 crc32 instructions
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Completed initialization of buffer pool
      2021-09-10 8:34:52 139668705941248 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Highest supported file format is Barracuda.
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Starting crash recovery from checkpoint LSN=4889588424546
      2021-09-10 8:34:52 139671396681920 [Note] InnoDB: Last binlog file '/data/mysqllogs/bin-log.001943', position 677839642
      2021-09-10 8:34:54 139671396681920 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2021-09-10 8:34:54 139671396681920 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2021-09-10 8:34:54 139671396681920 [Note] InnoDB: Creating shared tablespace for temporary tables
      2021-09-10 8:34:54 139671396681920 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2021-09-10 8:34:54 139671396681920 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2021-09-10 8:34:54 139671396681920 [Note] InnoDB: Waiting for purge to start
      2021-09-10 8:34:54 139671396681920 [Note] InnoDB: 5.7.31 started; log sequence number 4889588424555
      2021-09-10 8:34:54 139668267968256 [Note] InnoDB: Loading buffer pool(s) from /data/mysql/ib_buffer_pool
      2021-09-10 8:34:54 139671396681920 [Note] Plugin 'FEEDBACK' is disabled.
      2021-09-10 8:34:54 139671396681920 [Note] Recovering after a crash using /data/mysqllogs/bin-log
      2021-09-10 8:34:54 139671396681920 [Note] Starting crash recovery...
      2021-09-10 8:34:54 139671396681920 [Note] Crash recovery finished.
      2021-09-10 8:34:54 139671396681920 [Note] Server socket created on IP: '::'.
      2021-09-10 8:34:54 139668652697344 [Note] Event Scheduler: scheduler thread started with id 7
      2021-09-10 8:34:54 139671396681920 [Note] Reading of all Master_info entries succeeded
      2021-09-10 8:34:54 139671396681920 [Note] Added new Master_info '' to hash table
      2021-09-10 8:34:54 139671396681920 [Warning] Neither -relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use 'log-basename=#' or '-relay-log=<SERVER>-relay-bin' to avoid this problem.
      2021-09-10 8:34:54 139671396681920 [Note] /usr/sbin/mysqld: ready for connections.




            Unassigned Unassigned
            chanakar Chanaka Rathnayaka
            0 Vote for this issue
            2 Start watching this issue



                Git Integration

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