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

innodb.table_flags failed in buildbot with Operating system error number 2

Details

    Description

      Logs are not available at the time

      innodb.table_flags '32k,xtradb'          w2 [ fail ]
      		 
              Test ended at 2017-10-06 14:25:35
      		 
       
      		 
      CURRENT_TEST: innodb.table_flags
      		 
       
      		 
       
      		 
      Server [mysqld.1 - pid: 28825, winpid: 28825, exit: 256] failed during test run
      		 
      Server log from this test:
      		 
      ----------SERVER LOG START-----------
      		 
      2017-10-06 14:24:28 140198879734016 [Note] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld (mysqld 10.1.29-MariaDB) starting as process 26834 ...
      		 
      2017-10-06 14:24:28 140198879734016 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4162)
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'SEQUENCE' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'partition' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB:  innodb-page-size has been changed from the default value 16384 to 32768 .
      		 
      innodb_open_files should not be greater than the open_files_limit.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
      		 
       
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: The InnoDB memory heap is disabled
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: Compressed tables use zlib 1.2.3
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: Using Linux native AIO
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: Using generic crc32 instructions
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: Initializing buffer pool, size = 24.0M
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: Completed initialization of buffer pool
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: Highest supported file format is Barracuda.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: 128 rollback segment(s) are active.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB: Waiting for purge to start
      		 
      2017-10-06 14:24:28 140198879734016 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 3111409
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_SYS_INDEXES' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'XTRADB_RSEG' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'CHANGED_PAGE_BITMAPS' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_LOCK_WAITS' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_TABLESPACES_ENCRYPTION' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'XTRADB_INTERNAL_HASH_TABLES' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_SYS_FIELDS' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'FEEDBACK' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_CMP' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_MUTEXES' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_CMP_RESET' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_SYS_COLUMNS' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_FT_CONFIG' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'XTRADB_READ_VIEW' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_SYS_SEMAPHORE_WAITS' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_CHANGED_PAGES' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_FT_DELETED' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Plugin 'INNODB_TABLESPACES_SCRUBBING' is disabled.
      		 
      2017-10-06 14:24:28 140198879734016 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown variable 'loose-feedback-debug-startup-interval=20'
      		 
      2017-10-06 14:24:28 140198879734016 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown variable 'loose-feedback-debug-first-interval=60'
      		 
      2017-10-06 14:24:28 140198879734016 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown variable 'loose-feedback-debug-interval=60'
      		 
      2017-10-06 14:24:28 140198879734016 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown option '--loose-pam-debug'
      		 
      2017-10-06 14:24:28 140198879734016 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown variable 'loose-debug-sync-timeout=300'
      		 
      2017-10-06 14:24:28 140198478345984 [Note] InnoDB: Dumping buffer pool(s) not yet started
      		 
      2017-10-06 14:24:28 140198879734016 [Note] Server socket created on IP: '127.0.0.1'.
      		 
      2017-10-06 14:24:28 140198879734016 [Note] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: ready for connections.
      		 
      Version: '10.1.29-MariaDB'  socket: '/mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/tmp/2/mysqld.1.sock'  port: 16000  MariaDB Server
      		 
      2017-10-06 14:24:28 140198878706432 [Note] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: Normal shutdown
      		 
       
      		 
      2017-10-06 14:24:28 140198878706432 [Note] Event Scheduler: Purging the queue. 0 events
      		 
      2017-10-06 14:24:28 140198541256448 [Note] InnoDB: FTS optimize thread exiting.
      		 
      2017-10-06 14:24:28 140198878706432 [Note] InnoDB: Starting shutdown...
      		 
      2017-10-06 14:24:29 140198878706432 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
      		 
      2017-10-06 14:24:31 140198878706432 [Note] InnoDB: Shutdown completed; log sequence number 3111419
      		 
      2017-10-06 14:24:31 140198878706432 [Note] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: Shutdown complete
      		 
       
      		 
      2017-10-06 14:24:32 139922942531840 [Note] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld (mysqld 10.1.29-MariaDB) starting as process 26926 ...
      		 
      2017-10-06 14:24:32 139922942531840 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4162)
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'SEQUENCE' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'partition' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB:  innodb-page-size has been changed from the default value 16384 to 32768 .
      		 
      innodb_open_files should not be greater than the open_files_limit.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
      		 
       
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: The InnoDB memory heap is disabled
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Compressed tables use zlib 1.2.3
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Using Linux native AIO
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Using generic crc32 instructions
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Initializing buffer pool, size = 24.0M
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Completed initialization of buffer pool
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: The first specified data file /mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/2/tmp/table_flags/ibdata1 did not exist: a new database to be created!
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Setting file /mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/2/tmp/table_flags/ibdata1 size to 10 MB
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Setting log file /mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/2/tmp/table_flags/ib_logfile101 size to 5 MB
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Setting log file /mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/2/tmp/table_flags/ib_logfile1 size to 5 MB
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Renaming log file /mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/2/tmp/table_flags/ib_logfile101 to /mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/2/tmp/table_flags/ib_logfile0
      		 
      2017-10-06 14:24:32 139922942531840 [Warning] InnoDB: New log files created, LSN=74143
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Doublewrite buffer not found: creating new
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Doublewrite buffer created
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: 128 rollback segment(s) are active.
      		 
      2017-10-06 14:24:32 139922942531840 [Warning] InnoDB: Creating foreign key constraint system tables.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Foreign key constraint system tables created
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Creating tablespace and datafile system tables.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Tablespace and datafile system tables created.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB: Waiting for purge to start
      		 
      2017-10-06 14:24:32 139922942531840 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 0
      		 
      2017-10-06 14:24:32 139922543474432 [Note] InnoDB: Dumping buffer pool(s) not yet started
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_SYS_INDEXES' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'XTRADB_RSEG' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'CHANGED_PAGE_BITMAPS' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_LOCK_WAITS' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_TABLESPACES_ENCRYPTION' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'XTRADB_INTERNAL_HASH_TABLES' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_SYS_FIELDS' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'FEEDBACK' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_CMP' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_MUTEXES' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_CMP_RESET' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_SYS_COLUMNS' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_FT_CONFIG' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'XTRADB_READ_VIEW' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_SYS_SEMAPHORE_WAITS' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_CHANGED_PAGES' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_FT_DELETED' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Plugin 'INNODB_TABLESPACES_SCRUBBING' is disabled.
      		 
      2017-10-06 14:24:32 139922942531840 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown variable 'loose-feedback-debug-startup-interval=20'
      		 
      2017-10-06 14:24:32 139922942531840 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown variable 'loose-feedback-debug-first-interval=60'
      		 
      2017-10-06 14:24:32 139922942531840 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown variable 'loose-feedback-debug-interval=60'
      		 
      2017-10-06 14:24:32 139922942531840 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown option '--loose-pam-debug'
      		 
      2017-10-06 14:24:32 139922942531840 [Warning] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: unknown variable 'loose-debug-sync-timeout=300'
      		 
      2017-10-06 14:24:32 139922942531840 [Note] Server socket created on IP: '127.0.0.1'.
      		 
      2017-10-06 14:24:32 139922942531840 [Note] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: ready for connections.
      		 
      Version: '10.1.29-MariaDB'  socket: '/mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/tmp/2/mysqld.1.sock'  port: 16000  MariaDB Server
      		 
      2017-10-06 14:24:32 139922941504256 [Note] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld: Normal shutdown
      		 
       
      		 
      2017-10-06 14:24:32 139922941504256 [Note] Event Scheduler: Purging the queue. 0 events
      		 
      2017-10-06 14:24:32 139922614757120 [Note] InnoDB: FTS optimize thread exiting.
      		 
      2017-10-06 14:24:32 139922941504256 [Note] InnoDB: Starting shutdown...
      		 
      2017-10-06 14:24:33 139922941504256 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
      		 
      2017-10-06 14:25:33 140182751852800 [Note] /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld (mysqld 10.1.29-MariaDB) starting as process 28826 ...
      		 
      2017-10-06 14:25:33 140182751852800 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4162)
      		 
      2017-10-06 14:25:33 140182751852800 [Note] Plugin 'SEQUENCE' is disabled.
      		 
      2017-10-06 14:25:33 140182751852800 [Note] Plugin 'partition' is disabled.
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB:  innodb-page-size has been changed from the default value 16384 to 32768 .
      		 
      innodb_open_files should not be greater than the open_files_limit.
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
      		 
       
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: The InnoDB memory heap is disabled
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: Compressed tables use zlib 1.2.3
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: Using Linux native AIO
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: Using generic crc32 instructions
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: Initializing buffer pool, size = 24.0M
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: Completed initialization of buffer pool
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: Highest supported file format is Barracuda.
      		 
      2017-10-06 14:25:33 140182751852800 [Note] InnoDB: The log sequence number 0 in ibdata file do not match the log sequence number 3103469 in the ib_logfiles!
      		 
      2017-10-06 14:25:33 140182751852800 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace test/tc uses space ID: 2 at filepath: ./test/tc.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd
      		 
      2017-10-06 14:25:33 7f7ed720b900  InnoDB: Operating system error number 2 in a file operation.
      		 
      InnoDB: The error means the system cannot find the path specified.
      		 
      InnoDB: If you are installing InnoDB, remember that you must create
      		 
      InnoDB: directories yourself, InnoDB does not create them.
      		 
      InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_index_stats.ibd
      		 
      InnoDB: We do not continue the crash recovery, because the table may become
      		 
      InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
      		 
      InnoDB: To fix the problem and start mysqld:
      		 
      InnoDB: 1) If there is a permission problem in the file and mysqld cannot
      		 
      InnoDB: open the file, you should modify the permissions.
      		 
      InnoDB: 2) If the table is not needed, or you can restore it from a backup,
      		 
      InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
      		 
      InnoDB: crash recovery and ignore that table.
      		 
      InnoDB: 3) If the file system or the disk is broken, and you cannot remove
      		 
      InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
      		 
      InnoDB: and force InnoDB to continue crash recovery here.
      		 
      171006 14:25:33 [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.1.29-MariaDB
      		 
      key_buffer_size=1048576
      		 
      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 = 62911 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 0x48400
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(my_print_stacktrace+0x2e)[0x5586ef31443e]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(handle_fatal_signal+0x2f5)[0x5586eee5cf35]
      		 
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f7ed5ad0390]
      		 
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f7ed50a0428]
      		 
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f7ed50a202a]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(+0x96edfe)[0x5586ef22bdfe]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(+0x8172df)[0x5586ef0d42df]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(+0x8a4c9d)[0x5586ef161c9d]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(+0x7bc8b2)[0x5586ef0798b2]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x5586eee5f6e4]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(+0x41f5d5)[0x5586eecdc5d5]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(_Z11plugin_initPiPPci+0x7ca)[0x5586eecdcf6a]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(+0x3774d0)[0x5586eec344d0]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(_Z11mysqld_mainiPPc+0x1b09)[0x5586eec37fb9]
      		 
      /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f7ed508b830]
      		 
      /mnt/buildbot/build/mariadb-10.1.29/sql/mysqld(_start+0x29)[0x5586eec2bb99]
      		 
      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
      		 
      ----------SERVER LOG END-------------
      		 
      mysqltest failed but provided no output

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          alice Alice Sherepa added a comment -

          another kind of failure http://buildbot.askmonty.org/buildbot/builders/kvm-deb-xenial-x86/builds/4422/steps/mtr/logs/stdio

          innodb.table_flags '4k,xtradb'           w4 [ fail ]
          		 
                  Test ended at 2017-11-23 22:02:45
          		 
           
          		 
          CURRENT_TEST: innodb.table_flags
          		 
          mysqltest: In included file "./include/wait_until_connected_again.inc": 
          included from ./include/start_mysqld.inc at line 18:
          		 
          included from /usr/share/mysql/mysql-test/suite/innodb/t/table_flags.test at line 118:
          		 
          At line 26: Server failed to restart
          		 
           
          		 
          The result from queries just before the failure was:
          		 
          < snip >
          		 
           DB_TRX_ID=0x000000000302,
          		 
           DB_ROLL_PTR=0x820000032a0110,
          		 
           ID=0x000000000000000f,
          		 
           N_COLS=0x00000001,
          		 
           TYPE=0x00000001,
          		 
           MIX_ID=0x0000000000000000,
          		 
           MIX_LEN=0x00000050,
          		 
           CLUSTER_NAME=NULL(0 bytes),
          		 
           SPACE=0x00000001)
          		 
          header=0x000048150074 (NAME='test/tz',
          		 
           DB_TRX_ID=0x000000000305,
          		 
           DB_ROLL_PTR=0x850000032d0110,
          		 
           ID=0x0000000000000012,
          		 
           N_COLS=0x80000001,
          		 
           TYPE=0x00000023,
          		 
           MIX_ID=0x0000000000000000,
          		 
           MIX_LEN=0x00000050,
          		 
           CLUSTER_NAME=NULL(0 bytes),
          		 
           SPACE=0x00000004)
          		 
          header=0x060008030000 (NAME=0x73757072656d756d00)
          		 
           
          		 
          More results from queries before failure can be found in /dev/shm/var/4/log/table_flags,4k.log

          http://buildbot.askmonty.org/buildbot/builders/kvm-deb-xenial-x86/builds/4422/steps/mtr/logs/mysqld.1.err.4

          2017-11-23 21:46:24 3068471296 [Note] Server socket created on IP: '127.0.0.1'.
          		 
          2017-11-23 21:46:24 3068471296 [Note] /usr/sbin/mysqld: ready for connections.
          		 
          Version: '10.1.30-MariaDB-1~xenial'  socket: '/dev/shm/var/tmp/4/mysqld.1.sock'  port: 16040  mariadb.org binary distribution
          		 
          2017-11-23 21:46:24 b6d9af40  InnoDB: Error: table 'test/tc'
          		 
          InnoDB: in InnoDB data dictionary has unknown type 81.
          		 
          2017-11-23 21:46:24 b6d9af40  InnoDB: incorrect flags in SYS_TABLES
          		 
          2017-11-23 21:46:24 3067719488 [Warning] InnoDB: Cannot open table test/tc from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
          		 
          2017-11-23 21:46:24 b6d9af40  InnoDB: Error: table 'test/td'
          		 
          InnoDB: in InnoDB data dictionary has unknown type f21.
          		 
          2017-11-23 21:46:24 b6d9af40  InnoDB: incorrect flags in SYS_TABLES
          		 
          2017-11-23 21:46:24 3067719488 [Warning] InnoDB: Cannot open table test/td from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
          		 
          2017-11-23 21:46:24 b6d9af40  InnoDB: Error: table 'test/tz'
          		 
          InnoDB: in InnoDB data dictionary has unknown type 3023.
          		 
          2017-11-23 21:46:24 b6d9af40  InnoDB: incorrect flags in SYS_TABLES
          		 
          2017-11-23 21:46:24 3067719488 [Warning] InnoDB: Cannot open table test/tz from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
          		 
          2017-11-23 21:46:24 b6d9af40  InnoDB: Error: table 'test/tp'
          		 
          InnoDB: in InnoDB data dictionary has unknown type 121.
          		 
          2017-11-23 21:46:24 b6d9af40  InnoDB: incorrect flags in SYS_TABLES
          		 
          2017-11-23 21:46:24 3067719488 [Warning] InnoDB: Cannot open table test/tp from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
          		 
          2017-11-23 21:46:24 3067719488 [Note] /usr/sbin/mysqld: Normal shutdown

          alice Alice Sherepa added a comment - another kind of failure http://buildbot.askmonty.org/buildbot/builders/kvm-deb-xenial-x86/builds/4422/steps/mtr/logs/stdio innodb.table_flags '4k,xtradb' w4 [ fail ] Test ended at 2017-11-23 22:02:45   CURRENT_TEST: innodb.table_flags mysqltest: In included file "./include/wait_until_connected_again.inc": included from ./include/start_mysqld.inc at line 18: included from /usr/share/mysql/mysql-test/suite/innodb/t/table_flags.test at line 118: At line 26: Server failed to restart   The result from queries just before the failure was: < snip > DB_TRX_ID=0x000000000302, DB_ROLL_PTR=0x820000032a0110, ID=0x000000000000000f, N_COLS=0x00000001, TYPE=0x00000001, MIX_ID=0x0000000000000000, MIX_LEN=0x00000050, CLUSTER_NAME=NULL(0 bytes), SPACE=0x00000001) header=0x000048150074 (NAME='test/tz', DB_TRX_ID=0x000000000305, DB_ROLL_PTR=0x850000032d0110, ID=0x0000000000000012, N_COLS=0x80000001, TYPE=0x00000023, MIX_ID=0x0000000000000000, MIX_LEN=0x00000050, CLUSTER_NAME=NULL(0 bytes), SPACE=0x00000004) header=0x060008030000 (NAME=0x73757072656d756d00)   More results from queries before failure can be found in /dev/shm/var/4/log/table_flags,4k.log http://buildbot.askmonty.org/buildbot/builders/kvm-deb-xenial-x86/builds/4422/steps/mtr/logs/mysqld.1.err.4 2017-11-23 21:46:24 3068471296 [Note] Server socket created on IP: '127.0.0.1'. 2017-11-23 21:46:24 3068471296 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.1.30-MariaDB-1~xenial' socket: '/dev/shm/var/tmp/4/mysqld.1.sock' port: 16040 mariadb.org binary distribution 2017-11-23 21:46:24 b6d9af40 InnoDB: Error: table 'test/tc' InnoDB: in InnoDB data dictionary has unknown type 81. 2017-11-23 21:46:24 b6d9af40 InnoDB: incorrect flags in SYS_TABLES 2017-11-23 21:46:24 3067719488 [Warning] InnoDB: Cannot open table test/tc from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem. 2017-11-23 21:46:24 b6d9af40 InnoDB: Error: table 'test/td' InnoDB: in InnoDB data dictionary has unknown type f21. 2017-11-23 21:46:24 b6d9af40 InnoDB: incorrect flags in SYS_TABLES 2017-11-23 21:46:24 3067719488 [Warning] InnoDB: Cannot open table test/td from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem. 2017-11-23 21:46:24 b6d9af40 InnoDB: Error: table 'test/tz' InnoDB: in InnoDB data dictionary has unknown type 3023. 2017-11-23 21:46:24 b6d9af40 InnoDB: incorrect flags in SYS_TABLES 2017-11-23 21:46:24 3067719488 [Warning] InnoDB: Cannot open table test/tz from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem. 2017-11-23 21:46:24 b6d9af40 InnoDB: Error: table 'test/tp' InnoDB: in InnoDB data dictionary has unknown type 121. 2017-11-23 21:46:24 b6d9af40 InnoDB: incorrect flags in SYS_TABLES 2017-11-23 21:46:24 3067719488 [Warning] InnoDB: Cannot open table test/tp from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem. 2017-11-23 21:46:24 3067719488 [Note] /usr/sbin/mysqld: Normal shutdown
          marko Marko Mäkelä added a comment -

          Did this ever occur on MariaDB Server 10.2 or later?

          2017-10-06 14:25:33 140182751852800 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace test/tc uses space ID: 2 at filepath: ./test/tc.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd

          I think that this should be prevented by the MLOG_FILE_NAME records that I introduced in WL#7142 in MySQL 5.7.4. These changes were included in MariaDB 10.2.2.

          I remember that during the 5.5 and 5.6 development, there were some "duplicate tablespace ID" bugs, especially when the server was killed soon after restarting. I introduced the DICT_HDR_MAX_SPACE_ID, and it seemed to help.

          marko Marko Mäkelä added a comment - Did this ever occur on MariaDB Server 10.2 or later? 2017-10-06 14:25:33 140182751852800 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace test/tc uses space ID: 2 at filepath: ./test/tc.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd I think that this should be prevented by the MLOG_FILE_NAME records that I introduced in WL#7142 in MySQL 5.7.4. These changes were included in MariaDB 10.2.2. I remember that during the 5.5 and 5.6 development, there were some "duplicate tablespace ID" bugs, especially when the server was killed soon after restarting. I introduced the DICT_HDR_MAX_SPACE_ID , and it seemed to help.
          elenst Elena Stepanova added a comment -

          marko,

          Did this ever occur on MariaDB Server 10.2 or later?

          Your cross-reference search is as good as mine. If you haven't found any occurrences on 10.2+, as your email suggests, I won't find them either.

          elenst Elena Stepanova added a comment - marko , Did this ever occur on MariaDB Server 10.2 or later? Your cross-reference search is as good as mine. If you haven't found any occurrences on 10.2+, as your email suggests, I won't find them either.
          marko Marko Mäkelä added a comment -

          I believe that this problem was fixed by me in WL#7142 (MySQL 5.7 and MariaDB Server 10.2.2).
          It does not seem fixable in earlier versions.

          The test case innodb.table_flags is a rather recent addition by me. The problem that the test case occasionally triggers is duplicate tablespace ID assignment when the server is killed and restarted.

          marko Marko Mäkelä added a comment - I believe that this problem was fixed by me in WL#7142 (MySQL 5.7 and MariaDB Server 10.2.2). It does not seem fixable in earlier versions. The test case innodb.table_flags is a rather recent addition by me. The problem that the test case occasionally triggers is duplicate tablespace ID assignment when the server is killed and restarted.

          People

            marko Marko Mäkelä
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.