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

MariaDB Assert Crash Using mysqlbackup

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.8.3
    • N/A
    • Storage Engine - InnoDB
    • None
    • Running in Docker

    Description

      My main MariaDB container has started crashing, sometimes, during nightly backups. It does not always crash which makes me think it's not a data issue. When it does crash, it is not at the same point.

      The backup script (bash) has not changed in 2 years and this just started recently, I'm not sure why. After this crash occurs the server responds with "Too many connections".

      The part of the script running the backup issues this command:

      sudo docker exec $CONTAINER_NAME mysqldump --user=$MARIADB_USER --lock-tables --all-databases > $BACKUP_TARGET_HOST

      MariaDB Log (minus the bug reporting advice)

      2022-06-15 13:49:12 0x7f956a7fc640  InnoDB: Assertion failure in file ./storage/innobase/os/os0file.cc line 3540
      		 
      InnoDB: Failing assertion: cb->m_err == DB_SUCCESS
      		 
      220615 13:49:12 [ERROR] mysqld got signal 6 
      Server version: 10.8.3-MariaDB-1:10.8.3+maria~jammy
      		 
      key_buffer_size=134217728
      		 
      read_buffer_size=131072
      		 
      max_used_connections=3
      		 
      max_threads=153
      		 
      thread_count=3
      		 
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467997 K  bytes of memory
      		 
      Hope that's ok; if not, decrease some variables in the equation.
      		 
      Thread pointer: 0x0
      		 
      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 = 0x0 thread_stack 0x49000
      		 
      mariadbd(my_print_stacktrace+0x32)[0x7f95a4905212]
      		 
      mariadbd(handle_fatal_signal+0x478)[0x7f95a43da7e8]

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27593 Crashing on I/O error is unhelpful

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28857 innodb assertion cb->m_err == DB_SUCCESS during shutdown (Windows)

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 13 older comments
            danblack Daniel Black added a comment -

            add-apt-repository if you use 10.8 instead of 10.5 and jammy instead of focal this should work as a repository directly.

            danblack Daniel Black added a comment - add-apt-repository if you use 10.8 instead of 10.5 and jammy instead of focal this should work as a repository directly.
            leethompson Lee Thompson added a comment -

            @Daniel Black, Having trouble with the container building, the Synology Diskstation DS1817+ has it's own Docker UI which is somewhat limited. I've now got Portainer working and should be able to use that.

            I have never built my own container image myself so this may take some time.

            leethompson Lee Thompson added a comment - @Daniel Black, Having trouble with the container building, the Synology Diskstation DS1817+ has it's own Docker UI which is somewhat limited. I've now got Portainer working and should be able to use that. I have never built my own container image myself so this may take some time.
            danblack Daniel Black added a comment -

            with MDEV-27593 resolve the code path around this assertion and all stacks above have significantly improved.

            Is this still an issue?

            danblack Daniel Black added a comment - with MDEV-27593 resolve the code path around this assertion and all stacks above have significantly improved. Is this still an issue?
            ashishcyrus ashish added a comment -

            yes, this issue is happening every month

            ashishcyrus ashish added a comment - yes, this issue is happening every month
            marko Marko Mäkelä added a comment -

            ashishcyrus, which version are you using? Note that the 10.8 series was a short-term support release and is no longer supported. Can you post some fresh logs?

            marko Marko Mäkelä added a comment - ashishcyrus , which version are you using? Note that the 10.8 series was a short-term support release and is no longer supported. Can you post some fresh logs?

            People

              danblack Daniel Black
              leethompson Lee Thompson
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.