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

MariaDB crashes with Xen PVH - mysqld got signal 11

Details

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

    Description

      Hello,
      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).

      Attachments

        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

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-10020 InnoDB NOT IN Query Crash When One Item Is NULL

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            hydrapolic Tomáš Mózes created issue -
            hydrapolic Tomáš Mózes made changes -
            Field Original Value New Value
            Attachment 01-crash-mariadb-10.0.25-1.log [ 42084 ]
            Attachment 02-crash-mariadb-10.0.25-2.log [ 42085 ]
            Attachment 03-crash-mariadb-10.0.23-1.log [ 42086 ]
            Attachment 04-crash-mariadb-10.0.23-2.log [ 42087 ]
            Attachment my.cnf [ 42088 ]
            hydrapolic Tomáš Mózes made changes -
            Environment Gentoo Linux, latest stable

            Linux Kernel 4.1.24
            Glibc-2.22-r4
            Jemalloc-3.6.0
            Openssl-1.0.2h
            Libaio-0.3.110
            Zlib-1.2.8-r1             		Gentoo Linux, latest stable

            Linux Kernel 4.1.24
            Glibc-2.22-r4
            Jemalloc-3.6.0
            Openssl-1.0.2h
            Libaio-0.3.110
            Zlib-1.2.8-r1
            Xen 4.6.1-r3
            hydrapolic Tomáš Mózes made changes -
            Description Hello,
            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, 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".             		Hello,
            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".
            hydrapolic Tomáš Mózes made changes -
            Summary MariaDB crashes MariaDB crashes - mysqld got signal 11
            hydrapolic Tomáš Mózes made changes -
            Affects Version/s 10.0 [ 16000 ]
            hydrapolic Tomáš Mózes made changes -
            Environment Gentoo Linux, latest stable

            Linux Kernel 4.1.24
            Glibc-2.22-r4
            Jemalloc-3.6.0
            Openssl-1.0.2h
            Libaio-0.3.110
            Zlib-1.2.8-r1
            Xen 4.6.1-r3             		Gentoo Linux, latest stable

            Hardware:
            HP Proliant DL360p Gen8, 2x CPU Intel Xeon CPU E5-2640 0 @ 2.50GHz, 256GB RAM, HW RAID 1 with 300-600GB disks 10.000/15.000 rpm

            Software:
            Linux Kernel 4.1.24
            Glibc-2.22-r4
            Gcc 4.9.3
            Jemalloc-3.6.0
            Openssl-1.0.2h
            Libaio-0.3.110
            Zlib-1.2.8-r1
            Xen 4.6.1-r3
            hydrapolic Tomáš Mózes made changes -
            Description Hello,
            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".             		Hello,
            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).
            elenst Elena Stepanova made changes -
            Labels need_feedback
            hydrapolic Tomáš Mózes made changes -
            Attachment mysqld.err [ 42092 ]
            elenst Elena Stepanova made changes -
            Labels need_feedback
            elenst Elena Stepanova made changes -
            Labels need_feedback
            elenst Elena Stepanova made changes -
            Labels need_feedback
            elenst Elena Stepanova made changes -
            elenst Elena Stepanova made changes -
            Fix Version/s 10.0 [ 16000 ]
            Assignee Jan Lindström [ jplindst ]
            hydrapolic Tomáš Mózes made changes -
            Summary MariaDB crashes - mysqld got signal 11 MariaDB crashes with Xen PVH - mysqld got signal 11
            jplindst Jan Lindström (Inactive) made changes -
            Component/s Storage Engine - InnoDB [ 10129 ]
            Fix Version/s N/A [ 14700 ]
            Fix Version/s 10.0 [ 16000 ]
            Resolution Not a Bug [ 6 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 75869 ] MariaDB v4 [ 150477 ]

            People

              jplindst Jan Lindström (Inactive)
              hydrapolic Tomáš Mózes
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.