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

changing a field by mistake to a table linked via the connect engine, crashes mariadb

    XMLWordPrintable

Details

    Description

      I forgot that a table was linked via de Connecte engine, and tried to change the default value for a column, ending in crash. Twice.

      220914  0:10:36 [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.7.5-MariaDB-1:10.7.5+maria~ubu2204
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=2
      max_threads=65546
      thread_count=3
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 25314143 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fd5d0000d48
      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...

      Attachments

        Activity

          People

            Unassigned Unassigned
            philip_38 Philip orleans
            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.