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

*** buffer overflow detected ***: /usr/sbin/mysqld terminated

    Details

    • Type: Bug
    • Status: Stalled (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 10.3.14
    • Fix Version/s: 10.3
    • Component/s: Server
    • Labels:
    • Environment:
      Linux wpmudev 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

      Server version: 10.3.14-MariaDB-1:10.3.14+maria~bionic-log mariadb.org binary distribution

      Description

      We are trying to perform search and replace on WordPress which make all 10.3.14 servers crashed but same database with 10.1 works perfectly fine.

      We tested on 10 servers which are running on 10.3.14 and 10.1 and all had same output crash on 10.3 and works on 10.1

      wpcli search-replace --network "www.example.com" "example.host" --skip-plugins --skip-themes
      PHP Warning:  mysqli_query(): MySQL server has gone away in /var/web/site/public_html/wp-includes/wp-db.php on line 2007
      Warning: mysqli_query(): MySQL server has gone away in /var/web/site/public_html/wp-includes/wp-db.php on line 2007
      PHP Warning:  mysqli_query(): Error reading result set's header in /var/web/site/public_html/wp-includes/wp-db.php on line 2007
      Warning: mysqli_query(): Error reading result set's header in /var/web/site/public_html/wp-includes/wp-db.php on line 2007
      Error: Error reconnecting to the database. This means that we lost contact with the database server at `127.0.0.1:3306`. This could mean your host’s database server is down.
      

      MySQL Logs

      190423  6:37:55 [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.3.14-MariaDB-1:10.3.14+maria~bionic-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=2
      max_threads=52
      thread_count=8
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 245361 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f9f34000c08
      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 = 0x7f9fa52a4dd8 thread_stack 0x49000
      *** buffer overflow detected ***: /usr/sbin/mysqld terminated
      Fatal signal 6 while backtracing
      2019-04-23  6:38:01 0 [Note] InnoDB: Using Linux native AIO
      2019-04-23  6:38:01 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2019-04-23  6:38:01 0 [Note] InnoDB: Uses event mutexes
      2019-04-23  6:38:01 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2019-04-23  6:38:01 0 [Note] InnoDB: Number of pools: 1
      2019-04-23  6:38:01 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2019-04-23  6:38:01 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
      2019-04-23  6:38:01 0 [Note] InnoDB: Completed initialization of buffer pool
      2019-04-23  6:38:01 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2019-04-23  6:38:01 0 [Warning] InnoDB: Failed to set O_DIRECT on file./ibdata1; OPEN: Invalid argument, continuing anyway. O_DIRECT is known to result in 'Invalid argument' on Linux on tmpfs, see MySQL Bug#26662.
      2019-04-23  6:38:01 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=8615017946
      2019-04-23  6:38:01 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2019-04-23  6:38:01 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2019-04-23  6:38:01 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2019-04-23  6:38:01 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2019-04-23  6:38:01 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2019-04-23  6:38:01 0 [Note] InnoDB: Waiting for purge to start
      2019-04-23  6:38:01 0 [Note] InnoDB: 10.3.14 started; log sequence number 8615017955; transaction id 1078715
      2019-04-23  6:38:01 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/site/ib_buffer_pool
      2019-04-23  6:38:01 0 [Note] Plugin 'FEEDBACK' is disabled.
      2019-04-23  6:38:01 0 [Note] Recovering after a crash using tc.log
      2019-04-23  6:38:01 0 [Note] Starting crash recovery...
      2019-04-23  6:38:01 0 [Note] Crash recovery finished.
      2019-04-23  6:38:01 0 [Note] Server socket created on IP: '::'.
      2019-04-23  6:38:01 0 [Warning] 'user' entry 'root@baseimage-wpmudev-hosting' ignored in --skip-name-resolve mode.
      2019-04-23  6:38:01 0 [Warning] 'user' entry '@baseimage-wpmudev-hosting' ignored in --skip-name-resolve mode.
      2019-04-23  6:38:01 0 [Warning] 'proxies_priv' entry '@% root@baseimage-wpmudev-hosting' ignored in --skip-name-resolve mode.
      2019-04-23  6:38:01 0 [Note] InnoDB: Buffer pool(s) load completed at 190423  6:38:01
      2019-04-23  6:38:01 0 [Note] Reading of all Master_info entries succeded
      2019-04-23  6:38:01 0 [Note] Added new Master_info '' to hash table
      2019-04-23  6:38:01 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.3.14-MariaDB-1:10.3.14+maria~bionic-log'  socket: '/var/run/mysqld/mysqld2.sock'  port: 3306  mariadb.org binary distribution
      

        Attachments

          Activity

            People

            • Assignee:
              sanja Oleksandr Byelkin
              Reporter:
              ShahMitesh Mitesh Shah
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: