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

MariaDB Server is Suddenly down

    XMLWordPrintable

Details

    Description

      I had Error As Below When i finished Job about configuration.
      (heap size, tmp size, bin_log, path for tmp dir)

      190825 7:46:24 [ERROR] mysqld got signal 11 ;
      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.2.21-MariaDB-log
      key_buffer_size=134217728
      read_buffer_size=2097152
      max_used_connections=167
      max_threads=2001
      thread_count=38
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8369814 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f9418b86008
      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 = 0x7f9927d35c38 thread_stack 0x49000

      I want to know How i can avoid this Error, and why this problem was occured.

      Attachments

        Activity

          People

            Unassigned Unassigned
            90son Songuyoung
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.