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

InnoDB: Semaphore wait has lasted > 600 seconds

    XMLWordPrintable

    Details

      Description

      Last time write locked in file dict0stats.cc line 1969
      2022-02-10 13:50:56 0 [Note] InnoDB: A semaphore wait:
      --Thread 140328382174976 has waited at btr0cur.cc line 1480 for 611.00 seconds the semaphore:
      SX-lock on RW-latch at 0x7fa0b8add830 created in file dict0dict.cc line 2161
      a writer (thread id 140324852700928) has reserved it in mode SX
      number of readers 0, waiters flag 1, lock_word: 10000000
      Last time write locked in file dict0stats.cc line 1969
      InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info:
      InnoDB: Pending reads 1, writes 0
      InnoDB: ###### Diagnostic info printed to the standard error stream
      2022-02-10 13:50:56 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
      220210 13:50:56 [ERROR] mysqld got signal 6 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            roszaimi roszaimi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

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