• Type: Bug
    • Status: Confirmed (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.1.22, 5.5, 10.1, 10.2, 10.3, 10.4, 10.1.30
    • Fix Version/s: 10.1, 10.2, 10.3, 10.4
    • Component/s: Storage Engine - Aria
    • Labels:
    • Environment:
      CentOS Linux release 7.4.1708


      We have copied part of our environment to a virtual server and since then we have experienced random crashes (4 times in a couple of weeks). As soon as the crash happens the dbms won't restart, since it crashes again while recovering. The latest crash, tonight, shows this stacktrace:

      stack_bottom = 0x0 thread_stack 0x48400

      Using 'addr2line' I deduced that the crash happens while doing a pagecache flush:

      flush_cached_blocks .../mariadb-10.1.30/storage/maria/ma_pagecache.c:4431
      flush_pagecache_blocks_int .../mariadb-10.1.30/storage/maria/ma_pagecache.c:4727
      flush_pagecache_blocks_with_filter .../mariadb-10.1.30/storage/maria/ma_pagecache.c:4844
      ma_checkpoint_background .../mariadb-10.1.30/storage/maria/ma_checkpoint.c:674

      As said, when the dbms restarts, the recovery fails:

      recovered pages: 0% 10% 20% 30% 40% 50%180208 21:55:00 [ERROR] mysqld got signal 11 ;

      which happens here:

      stack_bottom = 0x0 thread_stack 0x48400
      sql/*, st_plugin_int*, int*, char**, bool))[0x563768f6601a]

      The four mysqld addresses translate to:

      exec_REDO_LOGREC_CLR_END .../mariadb-10.1.30/storage/maria/ma_recovery.c:2139
      display_and_apply_record .../mariadb-10.1.30/storage/maria/ma_recovery.c:588
      run_redo_phase .../mariadb-10.1.30/storage/maria/ma_recovery.c:2730
      maria_apply_log .../mariadb-10.1.30/storage/maria/ma_recovery.c:350
      maria_recovery_from_log .../mariadb-10.1.30/storage/maria/ma_recovery.c:242

      We can get the dbms running by removing a the table in which the redo log crashes (as determined by using aria_read_log) and moving the table back in after the restart.

      Then everything runs fine, for a few days, for a week, even for two weeks and then it crashes again.

      We haven't got the faintest idea of what goes wrong. I checked the open bugs and found some vague resemblance, but nothing that stood out. There is no oom-error or other malfunction visible on the system that can be pinpointed to the problem. I tried to investigate (at least) the aria_log file, but could not find tools to find out what is causing the crash in the restart. I know that the record which causes the crash is not the last record in the logfile, so it seems the two crashes are not related.

      But we are a bit at a dead end. Any help is appreciated. We can enable logs (if someone tells us how), we can run a debug version, we can even try to update to 10.2 (but there are some issues in de Perl DBD::mysql module at the moment that keep us from doing so). Bear in mind that updating from 10.1.22 to 10.1.30 did not solve the issue. Help is appreciated...


          Issue Links



              • Assignee:
                vlad.lesin Vladislav Lesin
                Frank_VID Frank Maas
              • Votes:
                0 Vote for this issue
                3 Start watching this issue


                • Created: