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

Server Crash on MariaDB 10.3.13

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Cannot Reproduce
    • 10.3(EOL)
    • N/A
    • N/A
    • CentOS7

    Description

      Hi, I am using MariaDB 10.3.13 version.

      And one day server suddenly crashed with those logs although I didnt do any operation, and I wanna know is there any the possible reason for this.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          duddls2054 Yeongin JUNG created issue -
          julien.fritsch Julien Fritsch made changes -
          Field Original Value New Value
          Labels crash crash need_verification
          danblack Daniel Black added a comment -

          I'm sorry, the latest 10.3.13 version (http://ftp.hosteurope.de/mirror/archive.mariadb.org/mariadb-10.3.13/yum/centos7-amd64/rpms/) doesn't include the the MariaDB-server-debuginfo package that I need to decode the address locations in your images.

          Can you please try a newer version as see if anything happens?

          For bug reports it would be significantly easier if the stack traces where provided as text rather than images. If a core is generated, install MariaDB-server-debuginfo from the same respository and run gdb /usr/sbin/mysqld core and then thread apply all bt full to show the result.

          https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/#analyzing-a-core-file-with-gdb-on-linux for more information.

          Thanks for reporting an issue, however with the provided information I can't do anything with it.

          danblack Daniel Black added a comment - I'm sorry, the latest 10.3.13 version ( http://ftp.hosteurope.de/mirror/archive.mariadb.org/mariadb-10.3.13/yum/centos7-amd64/rpms/ ) doesn't include the the MariaDB-server-debuginfo package that I need to decode the address locations in your images. Can you please try a newer version as see if anything happens? For bug reports it would be significantly easier if the stack traces where provided as text rather than images. If a core is generated, install MariaDB-server-debuginfo from the same respository and run gdb /usr/sbin/mysqld core and then thread apply all bt full to show the result. https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/#analyzing-a-core-file-with-gdb-on-linux for more information. Thanks for reporting an issue, however with the provided information I can't do anything with it.
          danblack Daniel Black made changes -
          Fix Version/s N/A [ 14700 ]
          Resolution Cannot Reproduce [ 5 ]
          Status Open [ 1 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 102602 ] MariaDB v4 [ 157132 ]

          People

            Unassigned Unassigned
            duddls2054 Yeongin JUNG
            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.