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

rpl.rpl_insert_id_pk failed in buildbot with Failing assertion: ret == 0 (pthread_create failed)





      rpl.rpl_insert_id_pk 'innodb,stmt'       w4 [ fail ]
              Test ended at 2018-06-12 11:44:28
      CURRENT_TEST: rpl.rpl_insert_id_pk
      Failed to start mysqld.2
      mysqltest failed but provided no output

      10.2 8f5f0575ab41bd03369ab1dc31425ef7ab1c6b10

      CURRENT_TEST: rpl.rpl_insert_id_pk
      2018-06-12 11:44:10 139640564107520 [Note] /usr/sbin/mysqld (mysqld 10.2.16-MariaDB-log) starting as process 853 ...
      2018-06-12 11:44:10 139640564107520 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4182)
      2018-06-12 11:44:10 139640564107520 [Warning] Changed limits: max_open_files: 1024  max_connections: 151 (was 151)  table_cache: 421 (was 2000)
      2018-06-12 11:44:10 139640564107520 [Note] Plugin 'SEQUENCE' is disabled.
      2018-06-12 11:44:10 139640564107520 [Note] Plugin 'partition' is disabled.
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Uses event mutexes
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Using Linux native AIO
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Number of pools: 1
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Using generic crc32 instructions
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Completed initialization of buffer pool
      2018-06-12 11:44:10 139640283571968 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Highest supported file format is Barracuda.
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Creating shared tablespace for temporary tables
      2018-06-12 11:44:10 139640564107520 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2018-06-12 11:44:11 139640564107520 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2018-06-12 11:44:11 0x7f009a384900  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.16/storage/innobase/os/os0thread.cc line 139
      InnoDB: Failing assertion: ret == 0
      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/xtradbinnodb-recovery-modes/
      InnoDB: about forcing recovery.
      180612 11:44:12 [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.16-MariaDB-log
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63014 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
      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 at /dev/shm/var/4/mysqld.2/data/
      CURRENT_TEST: rpl.rpl_insert_id_pk


        Issue Links



              Unassigned Unassigned
              elenst Elena Stepanova
              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.