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

MariaDB server crashed and can not start up

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major
        • Resolution: Cannot Reproduce
        • Affects Version/s: None
        • Fix Version/s: N/A
        • Component/s: OTHER
        • Labels:
          None

          Description

          Thread pointer: 0x0x0
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 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7f51a77feead]
/usr/libexec/mysqld(handle_fatal_signal+0x345)[0x7f51a7367b55]
/lib64/libpthread.so.0(+0x100d0)[0x7f51a6a010d0]
/lib64/libc.so.6(gsignal+0x37)[0x7f51a4f368c7]
/lib64/libc.so.6(abort+0x16a)[0x7f51a4f3852a]
/usr/libexec/mysqld(+0x8089c7)[0x7f51a76399c7]
/usr/libexec/mysqld(+0x808a9c)[0x7f51a7639a9c]
/usr/libexec/mysqld(+0x810bad)[0x7f51a7641bad]
/usr/libexec/mysqld(+0x7d6c86)[0x7f51a7607c86]
/usr/libexec/mysqld(+0x7b8da4)[0x7f51a75e9da4]
/usr/libexec/mysqld(+0x799f01)[0x7f51a75caf01]
/usr/libexec/mysqld(+0x7398d3)[0x7f51a756a8d3]
/usr/libexec/mysqld(+0x736521)[0x7f51a7567521]
/usr/libexec/mysqld(+0x738197)[0x7f51a7569197]
/usr/libexec/mysqld(+0x702c0e)[0x7f51a7533c0e]
/usr/libexec/mysqld(+0x76115f)[0x7f51a759215f]
/usr/libexec/mysqld(+0x7526f4)[0x7f51a75836f4]
/lib64/libpthread.so.0(+0x752a)[0x7f51a69f852a]
/lib64/libc.so.6(clone+0x6d)[0x7f51a500279d]
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.

            Gliffy Diagrams

              Attachments

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                elenst Elena Stepanova added a comment -

                Hi,

                Unfortunately, we can't get far with this description. The stack trace is useless (not your fault, it just is). But would you be able to

                • specify what the server was doing at the moment of the crash (provide as many details as you can, of course the query it crashed on would be the best);
                • provide the whole error log from the server startup and up to the end of the crash, not just the stack trace, and if it cannot start anymore – also the error log from the restart attempts;
                • specify the server version and then environment you are using;
                • attach the cnf file(s).

                If the server cannot start after a crash, most likely it means that the data is corrupted. Is it a production instance? How big and how confidential the data is? Would you be able to upload the whole data directory (compressed) to our ftp.askmonty.org/private?

                If you cannot upload the data, could you maybe run a debug binary to see more information on why the server cannot start? (If you can, we'll send you the debug binary after you say which OS, architecture and server version you are on, or you can build it yourself if you normally build from source).

                Thanks.

                Show
                elenst Elena Stepanova added a comment - Hi, Unfortunately, we can't get far with this description. The stack trace is useless (not your fault, it just is). But would you be able to specify what the server was doing at the moment of the crash (provide as many details as you can, of course the query it crashed on would be the best); provide the whole error log from the server startup and up to the end of the crash, not just the stack trace, and if it cannot start anymore – also the error log from the restart attempts; specify the server version and then environment you are using; attach the cnf file(s). If the server cannot start after a crash, most likely it means that the data is corrupted. Is it a production instance? How big and how confidential the data is? Would you be able to upload the whole data directory (compressed) to our ftp.askmonty.org/private? If you cannot upload the data, could you maybe run a debug binary to see more information on why the server cannot start? (If you can, we'll send you the debug binary after you say which OS, architecture and server version you are on, or you can build it yourself if you normally build from source). Thanks.
                Hide
                Permalink
                netroby zhifeng hu added a comment -

                It is not data corrupted. I move the data to a new clean mysql server . it working normally.

                I am using the latest 10.0.17 rpm for fedora 21 x64. Once a normal yum update. mariadb can not start anymore.

                The all thing useful i can got from log was what i post.

                I am not sure what happened , and could not resolve the problem by my self.

                Show
                netroby zhifeng hu added a comment - It is not data corrupted. I move the data to a new clean mysql server . it working normally. I am using the latest 10.0.17 rpm for fedora 21 x64. Once a normal yum update. mariadb can not start anymore. The all thing useful i can got from log was what i post. I am not sure what happened , and could not resolve the problem by my self.
                Hide
                Permalink
                netroby zhifeng hu added a comment -

                Please close this issue. i am sorry i can not reproduce it after new fresh reinstall with mariadb.

                Show
                netroby zhifeng hu added a comment - Please close this issue. i am sorry i can not reproduce it after new fresh reinstall with mariadb.

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    netroby zhifeng hu
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Due:
                      Created:
                      Updated:
                      Resolved: