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

Dead-lock in MYSQL_BIN_LOG::reset_logs(..) ?

    XMLWordPrintable

Details

    Description

      I've installed MariaDB 10.3.7 and initialized with my own configs (from previous setups), set a root user.. etc, then I have executed

      /usr/bin/mysql -NAB -u'root' -p'!password$$' -e "RESET MASTER"

      And this command seems to be stuck since hours (actually it is almost half a day since now...).

      I have attached my mysqld config, logs and the backtrace of mysqld too, it seems to be waiting for a mutex ... possibly dead-lock internally?

      Actually there are two issues here:
      1) Server gets stuck in executing 'RESET MASTER'
      ( The GDB backtrace suggests it is waiting for a mutex, possible dead-lock? )
      2) Client never times out? how is that?
      ( I still have this running since yesterday ~15:16 or something like that... )

      Unfortunetely mariadb doesn't provide -dbg packages (or i just don't see them) so i couldn't provide better backtrace atm...

      Attachments

        1. backtrace.txt
          22 kB
        2. my.cnf
          2 kB
        3. mysqld.log
          8 kB
        4. packages.txt
          2 kB
        5. processlist.txt
          1 kB
        6. reproduced_again.txt
          23 kB
        7. bt.txt
          40 kB
        8. my.cnf.txt
          2 kB
        9. processlist.txt
          0.6 kB
        10. psaux.txt
          9 kB
        11. pstree.txt
          2 kB
        12. rpmqa.txt
          9 kB

        Issue Links

          Activity

            People

              sachin.setiya.007 Sachin Setiya (Inactive)
              kedazo David Kedves
              Votes:
              0 Vote for this issue
              Watchers:
              8 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.