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

MariaDB crashes with Xen PVH - mysqld got signal 11



    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.0.23, 10.0.25, 10.0
    • N/A
    • None


      after upgrading our Gentoo Linux systems to latest stable versions, one of our MariaDB instance started to crash. The crashes seems to be random at times like:

      160527 9:34:05 [ERROR] mysqld got signal 11 ;
      160527 13:52:37 [ERROR] mysqld got signal 11 ;
      160530 20:46:51 [ERROR] mysqld got signal 11 ;
      160602 5:32:48 [ERROR] mysqld got signal 11 ;

      We have a master-slave replication. We first upgraded the slave to 10.0.25, had it running for 2 weeks without problems. Then we did a master failover, it worked for a week and then it started to crash. First it crashed on MariaDB 10.0.25, then again on 10.0.25. We downgraded to MariaDB 10.0.23 (that version worked before the system update), but it crashed again. Then we switched back to the old master instance (failover) with MariaDB 10.0.23, but it crashed again.

      The MariaDB instances are running virtualized as Xen DomU (in pvh mode) on Linux Kernel 4.1.24 with 230GB RAM / 24 vcpus. MariaDB was compiled with the following Gentoo USE flags: "extraengine jemalloc openssl pam server".

      The database is mostly used for selects (1000-3000 qps).


        1. 01-crash-mariadb-10.0.25-1.log
          41 kB
        2. 02-crash-mariadb-10.0.25-2.log
          1 kB
        3. 03-crash-mariadb-10.0.23-1.log
          20 kB
        4. 04-crash-mariadb-10.0.23-2.log
          23 kB
        5. my.cnf
          2 kB
        6. mysqld.err
          23 kB

        Issue Links



              jplindst Jan Lindström (Inactive)
              hydrapolic Tomas Mozes
              0 Vote for this issue
              4 Start watching this issue



                Git Integration

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