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

mariabackup crashes with Too many open files

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.2.36
    • Fix Version/s: 10.2
    • Component/s: mariabackup
    • Labels:
      None
    • Environment:
      Linux, n.a.

      Description

      mariabackup crashes with Too many open files

      mariabackup --backup --user=root --datadir=${DATADIR} --target-dir=${BACKUPDIR}
      [00] 2020-11-16 17:48:55 Connecting to MySQL server host: localhost, user: root, password: not set, port: 3312, socket: /var/run/mysqld/mysql-3312.sock
      [00] 2020-11-16 17:48:55 Using server version 10.2.36-MariaDB-log
      mariabackup based on MariaDB server 10.2.36-MariaDB Linux (x86_64)
      [00] 2020-11-16 17:48:55 uses posix_fadvise().
      [00] 2020-11-16 17:48:55 cd to /home/mysql/database_slow/mariadb-102/data/
      [00] 2020-11-16 17:48:55 open files limit requested 0, set to 1024
      [00] 2020-11-16 17:48:55 mariabackup: using the following InnoDB configuration:
      [00] 2020-11-16 17:48:55 innodb_data_home_dir =
      [00] 2020-11-16 17:48:55 innodb_data_file_path = ibdata1:12M:autoextend
      [00] 2020-11-16 17:48:55 innodb_log_group_home_dir = ./
      [00] 2020-11-16 17:48:55 InnoDB: Using Linux native AIO
      2020-11-16 17:48:55 139794920362560 [Note] InnoDB: Number of pools: 1
      [00] 2020-11-16 17:48:55 mariabackup: Generating a list of tablespaces
      2020-11-16 17:48:55 139794920362560 [Warning] InnoDB: Allocated tablespace ID 5713 for wp/wp_postmeta, old maximum was 0
      2020-11-16 17:49:02 139794920362560 [ERROR] InnoDB: Operating system error number 24 in a file operation.
      2020-11-16 17:49:02 139794920362560 [ERROR] InnoDB: Error number 24 means 'Too many open files'
      2020-11-16 17:49:02 139794920362560 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
      2020-11-16 17:49:02 139794920362560 [ERROR] InnoDB: File ./hybris1/solrsortlp.ibd: 'open' returned OS error 224.
      2020-11-16 17:49:02 0x7f248a91d240 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/fil/fil0fil.cc line 702
      InnoDB: Failing assertion: success
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      201116 17:49:02 [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.2.36-MariaDB
      key_buffer_size=0
      read_buffer_size=131072
      max_used_connections=0
      max_threads=1
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5419 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
      mariabackup(my_print_stacktrace+0x2e)[0x56073374761e]
      mariabackup(handle_fatal_signal+0x30d)[0x560733203bfd]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f248ae62730]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f248a96f7bb]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f248a95a535]
      mariabackup(+0x4ad414)[0x560732f17414]
      mariabackup(+0x9248a6)[0x56073338e8a6]
      mariabackup(+0x925d27)[0x56073338fd27]
      mariabackup(+0x4cfaff)[0x560732f39aff]
      mariabackup(+0x4cf18d)[0x560732f3918d]
      mariabackup(+0x4cf5b0)[0x560732f395b0]
      mariabackup(+0x4d2473)[0x560732f3c473]
      mariabackup(main+0x185)[0x560732f19975]
      /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f248a95c09b]
      mariabackup(+0x4c7c51)[0x560732f31c51]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...

        Attachments

          Activity

            People

            Assignee:
            marko Marko Mäkelä
            Reporter:
            oli Oli Sennhauser
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.