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

Mariadb service stop and rolled back recovered InnoDB: Semaphore wait Error Code 6

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.4.17
    • Fix Version/s: 10.4
    • Labels:
    • Environment:
      DB: 16core vcpu, 40GB RAM, 6*100 LVM DISK/ 600GB, Centos7 2003,
      ZABBIX: 8core vcpu, 16GB RAM, 100GB DISK, Centos7 2003,

      Description

      Hello,

      We use Zabbix Monitoring. We separated the application and the db server.
      I think last month, the permanent mariadb service is restarting and I'm viewing the log file, Innodb has been rolled back.

      I don't understand why you are doing this. But we were struck by a huge problem.

      How can I find the solution of the error or the bug that occurred?

      END OF INNODB MONITOR OUTPUT
      ============================
      InnoDB: ###### Diagnostic info printed to the standard error stream
      2021-03-15 7:50:42 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the serv
      er because it appears to be hung.
      210315 7:50:42 [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.

      Server version: 10.4.17-MariaDB-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=139
      max_threads=258
      thread_count=145
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 698828 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x0

        Attachments

          Activity

            People

            Assignee:
            marko Marko Mäkelä
            Reporter:
            myakan MERT YAKAN
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration