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

Mariabackup crashed with non privileged user

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 10.4.7
    • Fix Version/s: N/A
    • Component/s: mariabackup
    • Labels:
      None
    • Environment:
      CentOS 7, MariaDB 10.4 Repository

      Description

      [user1@localhost ~]$ cd /usr/bin/
      [user1@localhost bin]$ ./mariabackup --user=root --backup --target-dir=/tmp
      [00] 2019-08-19 17:48:22 Connecting to MySQL server host: localhost, user: root, password: not set, port: not set, socket: not set
      [00] 2019-08-19 17:48:22 Using server version 10.4.7-MariaDB-log
      ./mariabackup based on MariaDB server 10.4.7-MariaDB Linux (x86_64)
      [00] 2019-08-19 17:48:22 uses posix_fadvise().
      [00] 2019-08-19 17:48:22 cd to /var/lib/mysql/
      [00] 2019-08-19 17:48:22 open files limit requested 0, set to 1024
      [00] 2019-08-19 17:48:22 mariabackup: using the following InnoDB configuration:
      [00] 2019-08-19 17:48:22 innodb_data_home_dir =
      [00] 2019-08-19 17:48:22 innodb_data_file_path = ibdata1:12M:autoextend
      [00] 2019-08-19 17:48:22 innodb_log_group_home_dir = ./
      [00] 2019-08-19 17:48:22 InnoDB: Using Linux native AIO
      2019-08-19 17:48:22 0 [Note] InnoDB: Number of pools: 1
      2019-08-19 17:48:22 0 [Warning] InnoDB: Unable to open "./ib_logfile0" to check native AIO read support.
      2019-08-19 17:48:22 0 [Warning] InnoDB: Linux Native AIO disabled.
      2019-08-19 17:48:22 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
      2019-08-19 17:48:22 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
      2019-08-19 17:48:22 0x7f0d82f5d8c0 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.7/storage/innobase/fil/fil0fil.cc line 576
      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.
      190819 17:48:22 [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.4.7-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 = 5913 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)[0x55ef4485c82e]
      ./mariabackup(handle_fatal_signal+0x30f)[0x55ef4434fb4f]
      sigaction.c:0(__restore_rt)[0x7f0d82b555d0]
      :0(__GI_raise)[0x7f0d80e282c7]
      :0(__GI_abort)[0x7f0d80e299b8]
      addr2line: './mariabackup': No such file
      ./mariabackup(+0x5a7bc6)[0x55ef43fb8bc6]
      ./mariabackup(+0xad1bb1)[0x55ef444e2bb1]
      ./mariabackup(+0xad1d1b)[0x55ef444e2d1b]
      ./mariabackup(+0xad9ee3)[0x55ef444eaee3]
      ./mariabackup(+0xb87dd1)[0x55ef44598dd1]
      ./mariabackup(+0xb8d5d4)[0x55ef4459e5d4]
      ./mariabackup(+0x5dc96f)[0x55ef43fed96f]
      ./mariabackup(main+0x185)[0x55ef43fbbcd5]
      /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f0d80e14495]
      addr2line: './mariabackup': No such file
      ./mariabackup(+0x5d3914)[0x55ef43fe4914]
      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.
      Writing a core file...
      Working directory at /var/lib/mysql
      Resource Limits:
      Limit Soft Limit Hard Limit Units
      Max cpu time unlimited unlimited seconds
      Max file size unlimited unlimited bytes
      Max data size unlimited unlimited bytes
      Max stack size 8388608 unlimited bytes
      Max core file size 0 unlimited bytes
      Max resident set unlimited unlimited bytes
      Max processes 4096 127477 processes
      Max open files 1024 4096 files
      Max locked memory 65536 65536 bytes
      Max address space unlimited unlimited bytes
      Max file locks unlimited unlimited locks
      Max pending signals 127477 127477 signals
      Max msgqueue size 819200 819200 bytes
      Max nice priority 0 0
      Max realtime priority 0 0
      Max realtime timeout unlimited unlimited us
      Core pattern: |/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e %P %I %h

      Aborted (core dumped)
      [user1@localhost bin]$

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                oli Oli Sennhauser
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: