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

sys_vars.log_slow_admin_statements_func failed in buildbot (server crashed)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.1
    • Fix Version/s: 10.1
    • Component/s: Server, Tests
    • Labels:
      None

      Description

      http://askmonty.org/buildbot/builders/kvm-deb-jessie-x86/builds/1864

      sys_vars.log_slow_admin_statements_func 'xtradb' w1 [ fail ]
              Test ended at 2017-03-01 12:17:44
       
      CURRENT_TEST: sys_vars.log_slow_admin_statements_func
      mysqltest: At line 50: query 'DROP TABLE log_slow_admin_statements' failed: 2013: Lost connection to MySQL server during query
       
      The result from queries just before the failure was:
      < snip >
      CREATE PROCEDURE add_rows()
      BEGIN
      DECLARE count INT;
      SET count = 1;
      INSERT INTO log_slow_admin_statements(j) values (REPEAT('A', 255));
      WHILE count <= 15 DO
      INSERT INTO log_slow_admin_statements(j) SELECT j FROM log_slow_admin_statements;
      SET count = count + 1;
      END WHILE;
      END
      $
      CALL add_rows();
      OPTIMIZE TABLE log_slow_admin_statements;
      Table	Op	Msg_type	Msg_text
      test.log_slow_admin_statements	optimize	note	Table does not support optimize, doing recreate + analyze instead
      test.log_slow_admin_statements	optimize	status	OK
      CHECK TABLE log_slow_admin_statements EXTENDED;
      Table	Op	Msg_type	Msg_text
      test.log_slow_admin_statements	check	status	OK
      DROP TABLE log_slow_admin_statements;
       
      More results from queries before failure can be found in /dev/shm/var/1/log/log_slow_admin_statements_func.log
       
       
      Server [mysqld.1 - pid: 20449, winpid: 20449, exit: 256] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      2017-03-01 12:17:38 3054567232 [Note] InnoDB: Online DDL : Start
      2017-03-01 12:17:38 3054567232 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files
      2017-03-01 12:17:38 3054567232 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files
      2017-03-01 12:17:38 3054567232 [Note] InnoDB: Online DDL : Completed
      2017-03-01 12:17:42 3054567232 [Note] InnoDB: Online DDL : Start
      2017-03-01 12:17:42 3054567232 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files
      2017-03-01 12:17:42 3054567232 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files
      2017-03-01 12:17:42 3054567232 [Note] InnoDB: Online DDL : Start merge-sorting index `PRIMARY` (1 / 1), estimated cost : 20.0000
      2017-03-01 12:17:42 3054567232 [Note] InnoDB: Online DDL : merge-sorting has estimated 9 runs
      2017-03-01 12:17:42 3054567232 [Note] InnoDB: Online DDL : End of  merge-sorting index `PRIMARY` (1 / 1)
      2017-03-01 12:17:42 3054567232 [Note] InnoDB: Online DDL : Start building index `PRIMARY` (1 / 1), estimated cost : 30.0000
      2017-03-01 12:17:43 3054567232 [Note] InnoDB: Online DDL : End of building index `PRIMARY` (1 / 1)
      2017-03-01 12:17:43 3054567232 [Note] InnoDB: Online DDL : Completed
      170301 12:17:43 [ERROR] mysqld got signal 11 ;
      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.22-MariaDB-1~jessie
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=3
      max_threads=153
      thread_count=1
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61771 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
      /usr/sbin/mysqld(my_print_stacktrace+0x28)[0xb72c6b88]
      /usr/sbin/mysqld(handle_fatal_signal+0x2f7)[0xb6dde9a7]
      linux-gate.so.1(__kernel_sigreturn+0x0)[0xb69a2d18]
      /usr/sbin/mysqld(+0x7c7eb7)[0xb718deb7]
      /usr/sbin/mysqld(+0x7cd108)[0xb7193108]
      /usr/sbin/mysqld(+0x8236e3)[0xb71e96e3]
      /usr/sbin/mysqld(+0x758e64)[0xb711ee64]
      /lib/i386-linux-gnu/i686/cmov/libpthread.so.0(+0x6ecb)[0xb6983ecb]
      /lib/i386-linux-gnu/i686/cmov/libc.so.6(clone+0x5e)[0xb642fd0e]
      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-------------
       
       
       - saving '/dev/shm/var/1/log/sys_vars.log_slow_admin_statements_func-xtradb/' to '/dev/shm/var/log/sys_vars.log_slow_admin_statements_func-xtradb/'
       
      Retrying test sys_vars.log_slow_admin_statements_func, attempt(2/3)...
       
      worker[1] > Restart  - not started
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: