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

Running mariabackup with insufficient system privileges cause crash / coredump

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.2.14, 10.3.5
    • Fix Version/s: 10.2, 10.3, 10.4
    • Component/s: Backup
    • Labels:
      None
    • Environment:
      Linux CentOS 7.2

      Description

      As an ordinary user, run:

      $ mariabackup -backup
      

      This is an error, but shouldn't cause a core dump like this:

      180409 17:26:16 Connecting to MySQL server host: localhost, user: not set, password: not set, port: not set, socket: not set
      Using server version 10.2.14-MariaDB-log
      mariabackup based on MariaDB server 10.2.14-MariaDB Linux (x86_64)
      mariabackup: uses posix_fadvise().
      mariabackup: cd to /var/lib/mysql/
      mariabackup: open files limit requested 0, set to 1024
      mariabackup: using the following InnoDB configuration:
      mariabackup:   innodb_data_home_dir = .
      mariabackup:   innodb_data_file_path = ibdata1:12M:autoextend
      mariabackup:   innodb_log_group_home_dir = ./
      2018-04-09 17:26:16 139746500786304 [Note] InnoDB: Number of pools: 1
      2018-04-09 17:26:16 139746500786304 [ERROR] InnoDB: Operating system error number 13 in a file operation.
      2018-04-09 17:26:16 139746500786304 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
      2018-04-09 17:26:16 0x7f194489b880  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.14/storage/innobase/fil/fil0fil.cc line 761
      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/xtradbinnodb-recovery-modes/
      InnoDB: about forcing recovery.
      180409 17:26:16 [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.14-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 = 5421 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
      addr2line: 'mariabackup': No such file
      mariabackup(my_print_stacktrace+0x2e)[0x7f19454f552e]
      mariabackup(handle_fatal_signal+0x355)[0x7f1944fe3835]
      sigaction.c:0(__restore_rt)[0x7f19444ac100]
      :0(__GI_raise)[0x7f1942a395f7]
      :0(__GI_abort)[0x7f1942a3ace8]
      addr2line: 'mariabackup': No such file
      mariabackup(+0x434b1e)[0x7f1944d11b1e]
      mariabackup(+0x8d40f5)[0x7f19451b10f5]
      mariabackup(+0x8d432b)[0x7f19451b132b]
      mariabackup(+0x8debe2)[0x7f19451bbbe2]
      mariabackup(+0x989aa6)[0x7f1945266aa6]
      mariabackup(+0x992245)[0x7f194526f245]
      mariabackup(+0x457e22)[0x7f1944d34e22]
      mariabackup(main+0x185)[0x7f1944d13b05]
      /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f1942a25b15]
      addr2line: 'mariabackup': No such file
      mariabackup(+0x45016d)[0x7f1944d2d16d]
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      Aborted
      

      Note that the dump says that "mysqld got signal 6", but actually mysqld per se didn't crash at all. In addition, there is a pointer at the end to a page in the MySQL manual that is unliekly to help (http://dev.mysql.com/doc/mysql/en/crashing.html) .

      The workaround is to run mariabackup with sudo, obviously.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                vlad.lesin Vladislav Lesin
                Reporter:
                karlsson Anders Karlsson
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: