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

Server crashes, perfschema.hostcache_ipv4_addrinfo_again_allow failed in buildbot with ps-protocol

    XMLWordPrintable

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/8065/steps/test_3/logs/stdio
      (ps-protocol)

      perfschema.hostcache_ipv4_addrinfo_again_allow w2 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-05-09 03:31:14
      line
      170509  3:31:14 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
      ^ Found warnings in /mnt/buildbot/build/mariadb-10.2.6/mysql-test/var/2/log/mysqld.1.err
      

      CURRENT_TEST: perfschema.hostcache_ipv4_addrinfo_again_allow
      2017-05-09  3:31:14 2972105536 [Warning] Host name 'santa.claus.ipv4.example.com' could not be resolved: Temporary failure in name resolution
      2017-05-09  3:31:14 2965371712 [Warning] Host name 'santa.claus.ipv4.example.com' could not be resolved: Temporary failure in name resolution
      170509  3:31:14 [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.2.6-MariaDB-debug-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=3
      max_threads=153
      thread_count=4
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61863 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0xb08005d0
      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 = 0xb0bff2a0 thread_stack 0x49000
      /mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(my_print_stacktrace+0x32)[0x8cebcee]
      /mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(handle_fatal_signal+0x3c1)[0x859c60d]
      [0xb76f6400]
      /lib/i386-linux-gnu/libc.so.6(+0xbd4a5)[0xb72614a5]
      /lib/i386-linux-gnu/libc.so.6(fnmatch+0x69)[0xb7262af9]
      /mnt/buildbot/build/mariadb-10.2.6/sql/mysqld[0x8d0dc82]
      /mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_db_keyword_+0x79)[0x8d0e15a]
      /mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_db_pargs_+0x65)[0x8d0d570]
      /mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(sf_malloc_usable_size+0x6e)[0x8cf77b7]
      /mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(my_free+0x81)[0x8ce5a10]
      /mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_ZN16Security_context7destroyEv+0xc6)[0x82f9a0e]
      /mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_ZN3THD15free_connectionEv+0xf6)[0x82f1e12]
      mysys/stacktrace.c:267(my_print_stacktrace)[0x8260149]
      dbug/dbug.c:1515(InList)[0x8260601]
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.