mysql - 如何发现MariaDB崩溃的原因？-6ren

mysql - 如何发现MariaDB崩溃的原因？

转载作者：行者123 更新时间：2023-12-02 19:18:31

我使用Nextcloud(当前为18)。直到今天，当我通过Web浏览器访问云时收到此消息时，一切工作正常。

Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log.

我使用Docker或更具体的Docker Compose已有近两年了。 Alpine fpm，分为5部分:mariadb，redis，app，web和cron。

version: '3'

services:
  nextcloud_db:
    image: mariadb
    command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW
    restart: always
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - nextcloud_db:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=
    env_file:
      - db.env

  nextcloud_redis:
    image: redis:alpine
    restart: always

  nextcloud_app:
    build: ./app
    restart: always
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - nextcloud:/var/www/html
    environment:
      - MYSQL_HOST=nextcloud_db
      - REDIS_HOST=nextcloud_redis
    env_file:
      - db.env
    depends_on:
      - nextcloud_db
      - nextcloud_redis

  nextcloud_web:
    build: ./web
    restart: always
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - nextcloud:/var/www/html:ro
    environment:
      - VIRTUAL_HOST=
      - LETSENCRYPT_HOST=
    depends_on:
      - nextcloud_app

  nextcloud_cron:
    image: nextcloud:fpm-alpine
    restart: always
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - nextcloud:/var/www/html
    entrypoint: /cron.sh
    depends_on:
      - nextcloud_db
      - nextcloud_redis

volumes:
  nextcloud_db:
  nextcloud:

mariadb文件当前有错误。

nextcloud_db_1     | 2020-05-15 01:28:44+02:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.4.13+maria~bionic started.
nextcloud_db_1     | 2020-05-15 01:28:49+02:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
nextcloud_db_1     | 2020-05-15 01:28:49+02:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.4.13+maria~bionic started.
nextcloud_db_1     | 2020-05-15  1:28:50 0 [Note] mysqld (mysqld 10.4.13-MariaDB-1:10.4.13+maria~bionic) starting as process 1 ...
nextcloud_db_1     | 2020-05-15  1:28:50 0 [Warning] You need to use --log-bin to make --binlog-format work.
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: Using Linux native AIO
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: Uses event mutexes
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: Number of pools: 1
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: Using SSE2 crc32 instructions
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: Completed initialization of buffer pool
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
nextcloud_db_1     | 2020-05-15  1:28:51 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=8312011756
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] InnoDB: Creating shared tablespace for temporary tables
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] InnoDB: Waiting for purge to start
nextcloud_db_1     | 2020-05-15 01:28:52 0x7f010affd700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.4.13/storage/innobase/include/fut0lst.ic line 67
nextcloud_db_1     | InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
nextcloud_db_1     | InnoDB: We intentionally generate a memory trap.
nextcloud_db_1     | InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
nextcloud_db_1     | InnoDB: If you get repeated assertion failures or crashes, even
nextcloud_db_1     | InnoDB: immediately after the mysqld startup, there may be
nextcloud_db_1     | InnoDB: corruption in the InnoDB tablespace. Please refer to
nextcloud_db_1     | InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
nextcloud_db_1     | InnoDB: about forcing recovery.
nextcloud_db_1     | 200515  1:28:52 [ERROR] mysqld got signal 6 ;
nextcloud_db_1     | This could be because you hit a bug. It is also possible that this binary
nextcloud_db_1     | or one of the libraries it was linked against is corrupt, improperly built,
nextcloud_db_1     | or misconfigured. This error can also be caused by malfunctioning hardware.
nextcloud_db_1     |
nextcloud_db_1     | To report this bug, see https://mariadb.com/kb/en/reporting-bugs
nextcloud_db_1     |
nextcloud_db_1     | We will try our best to scrape up some info that will hopefully help
nextcloud_db_1     | diagnose the problem, but since we have already crashed,
nextcloud_db_1     | something is definitely wrong and this may fail.
nextcloud_db_1     |
nextcloud_db_1     | Server version: 10.4.13-MariaDB-1:10.4.13+maria~bionic
nextcloud_db_1     | key_buffer_size=134217728
nextcloud_db_1     | read_buffer_size=2097152
nextcloud_db_1     | max_used_connections=0
nextcloud_db_1     | max_threads=102
nextcloud_db_1     | thread_count=4
nextcloud_db_1     | It is possible that mysqld could use up to
nextcloud_db_1     | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 760255 K  bytes of memory
nextcloud_db_1     | Hope that's ok; if not, decrease some variables in the equation.
nextcloud_db_1     |
nextcloud_db_1     | Thread pointer: 0x7f00fc000c08
nextcloud_db_1     | Attempting backtrace. You can use the following information to find out
nextcloud_db_1     | where mysqld died. If you see no messages after this, something went
nextcloud_db_1     | terribly wrong...
nextcloud_db_1     | stack_bottom = 0x7f010affcc08 thread_stack 0x49000
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] InnoDB: 10.4.13 started; log sequence number 8312011765; transaction id 20582626
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] InnoDB: !!! innodb_force_recovery is set to 1 !!!
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
nextcloud_db_1     | 2020-05-15  1:28:52 0 [Note] Plugin 'FEEDBACK' is disabled.
nextcloud_db_1     | mysqld(my_print_stacktrace+0x2e)[0x561046981e8e]
nextcloud_db_1     | mysqld(handle_fatal_signal+0x515)[0x5610463fd915]
nextcloud_db_1     | /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f0148c84890]
nextcloud_db_1     | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f01475b8e97]
nextcloud_db_1     | /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f01475ba801]
nextcloud_db_1     | mysqld(+0x57c53c)[0x56104610a53c]
nextcloud_db_1     | mysqld(+0xb35506)[0x5610466c3506]
nextcloud_db_1     | mysqld(+0xb35d5d)[0x5610466c3d5d]
nextcloud_db_1     | mysqld(+0xb39a55)[0x5610466c7a55]
nextcloud_db_1     | mysqld(+0xb1c16e)[0x5610466aa16e]
nextcloud_db_1     | /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7f0148c796db]
nextcloud_db_1     | /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f014769b88f]
nextcloud_db_1     |
nextcloud_db_1     | Trying to get some variables.
nextcloud_db_1     | Some pointers may be invalid and cause the dump to abort.
nextcloud_db_1     | Query (0x0):
nextcloud_db_1     | Connection ID (thread ID): 2
nextcloud_db_1     | Status: NOT_KILLED
nextcloud_db_1     |
nextcloud_db_1     | Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on
nextcloud_db_1     |
nextcloud_db_1     | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
nextcloud_db_1     | information that should help you find out what is causing the crash.
nextcloud_db_1     | Writing a core file...
nextcloud_db_1     | Working directory at /var/lib/mysql
nextcloud_db_1     | Resource Limits:
nextcloud_db_1     | Limit                     Soft Limit           Hard Limit           Units
nextcloud_db_1     | Max cpu time              unlimited            unlimited            seconds
nextcloud_db_1     | Max file size             unlimited            unlimited            bytes
nextcloud_db_1     | Max data size             unlimited            unlimited            bytes
nextcloud_db_1     | Max stack size            8388608              unlimited            bytes
nextcloud_db_1     | Max core file size        unlimited            unlimited            bytes
nextcloud_db_1     | Max resident set          unlimited            unlimited            bytes
nextcloud_db_1     | Max processes             unlimited            unlimited            processes
nextcloud_db_1     | Max open files            1048576              1048576              files
nextcloud_db_1     | Max locked memory         16777216             16777216             bytes
nextcloud_db_1     | Max address space         unlimited            unlimited            bytes
nextcloud_db_1     | Max file locks            unlimited            unlimited            locks
nextcloud_db_1     | Max pending signals       1545098              1545098              signals
nextcloud_db_1     | Max msgqueue size         819200               819200               bytes
nextcloud_db_1     | Max nice priority         0                    0
nextcloud_db_1     | Max realtime priority     0                    0
nextcloud_db_1     | Max realtime timeout      unlimited            unlimited            us
nextcloud_db_1     | Core pattern: co...
nextcloud_db_1     | Fatal signal 11 while backtracing
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.13-MariaDB-1:10.4.13+maria~bionic
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=102
thread_count=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 760255 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fa650000c08
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 = 0x7fa674ff0c08 thread_stack 0x49000
2020-05-15  0:01:32 0 [Note] InnoDB: 10.4.13 started; log sequence number 8312011765; transaction id 20582626
2020-05-15  0:01:32 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysqld(my_print_stacktrace+0x2e)[0x55e945e98e8e]
mysqld(handle_fatal_signal+0x515)[0x55e945914915]
2020-05-15  0:01:32 0 [Note] Plugin 'FEEDBACK' is disabled.
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fa6aeddc890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa6ad710e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa6ad712801]
mysqld(+0x57c53c)[0x55e94562153c]
mysqld(+0xb35506)[0x55e945bda506]
mysqld(+0xb35d5d)[0x55e945bdad5d]
mysqld(+0xb39a55)[0x55e945bdea55]
mysqld(+0xb1c16e)[0x55e945bc116e]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7fa6aedd16db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fa6ad7f388f]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0):
Connection ID (thread ID): 4
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on

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        unlimited            unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             unlimited            unlimited            processes
Max open files            1048576              1048576              files
Max locked memory         16777216             16777216             bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       1545098              1545098              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: co...
Fatal signal 11 while backtracing

这在Docker日志中。这听起来对我来说太复杂了，我一点也不知道。

我尚未对设置进行任何更改。正如我所说的那样，我使用docker已有近2年的时间，随着时间的推移，对docker-compose.yml文件进行了一些更改。但是这个问题刚刚出现，并且大约3到4个月我都没有做任何更改。

它可能与大型数据库有关吗？我正在使用Nextcloud News，不清除任何项目，因为我将它们用于机器学习数据处理。因此数据库可能有点大。

经过amysqldump之后，oc_news_items表的大小约为170MB，上一次自动转储(今天上午)似乎没有损坏或类似的东西，但是它有99991行。因此，也许数据库中有99999行以上的nextcloud新闻项有问题？也许只是巧合。

最佳答案

这是MariaDB服务器问题。将其报告为错误https://mariadb.com/kb/en/reporting-bugs。

同时，将mariadb固定在以前的版本上:

image: mariadb:10.4.12

关于mysql - 如何发现MariaDB崩溃的原因？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/61809270/

文章推荐： powershell - Dockerfile 和 MSI 安装

文章推荐： node.js - 从容器内服务网格的网站

文章推荐： docker - 在 Bitnami Docker 容器中设置用户 UID

hadoop - Cassandra:原因:InvalidRequestException(原因:无效的限制)
我对cassandra并使用1.2.10非常陌生。我有一个时间戳数据类型的主键列。现在，我正在尝试检索日期范围的数据。由于我们知道不能在cassandra中使用，因此我使用的是大于()来获取日期范围。
objective-c - 以编程方式调用 segue 原因 NSInvalidArgumentException，原因 : 'UILabel length' unrecognized selector
我正在尝试进行有条件的转场。但我得到: Terminating app due to uncaught exception 'NSInvalidArgumentException', reas
iphone - 构建用新的应用程序版本替换旧版本的应用程序会导致应用程序崩溃!原因？
我有一个游戏项目，在调试和发布模式下在设备上运行得非常好。我有两个版本。旧版本和新版本具有更多(后来我添加了)功能，并且两者的 bundle ID、版本相同。当我构建旧版本时，之前没有安装“myGam
java - ClassCastException 原因
这个问题已经有答案了: 奥 git _a (2 个回答) 已关闭 5 年前。我正在获取 ClassCastException 。这两个类来自不同的 jar，但是JettyContinuationPr
java - 如何获取外部包中的异常原因/原因
以下代码行抛出异常: HttpResponse response = client.execute(request); // actual HTTP request 我能够捕获它并打印: Log
java - ClassNotFoundException 原因
就目前情况而言，这个问题不太适合我们的问答形式。我们希望答案得到事实、引用资料或专业知识的支持，但这个问题可能会引发辩论、争论、民意调查或扩展讨论。如果您觉得这个问题可以改进并可能重新开放，visit
java - 为什么这里抛出中断异常...原因？
public class TwoThreads { private static Object resource = new Object(); private static void
C程序-段错误，原因
当我输入 6 (int) 作为值时，运行此命令会出现段错误 (gcc filename.c -lm)。请帮助我解决这个问题。预期的功能尚未实现，但我需要知道为什么我已经陷入段错误。谢谢! #incl
c++ - 不良顶点数据的常见陷阱/原因？
所以，过去一周半我一直在研究这个 .OBJ/.MTL 网格解析器。在这段时间里，我一直在追踪/修复很多错误、清理代码、记录代码等等。问题是，每修复一个错误，仍然会出现这个问题，而且一张图片胜过一千个
为什么某些元素以数组和标量形式出现的 Python 原因
我正在运行一个代码，它基本上围绕 3 个维度旋转一个大数据数组(5000 万行)。但是，我遇到了一个奇怪的问题，我已将其缩小到如何评估旋转矩阵。基本上，对于除绕 x 轴以外的任何旋转，python 代
更改包名称大小写约定的 Java 原因
就在你说这是重复之前，我已经看到了其他问题，但我仍然想发布这个。所以我正在阅读 Thinking in Java -Bruce Eckel 这篇文章是关于小写命名约定的: In Java 1.0 a
Android SocketTimeoutException 原因
我想在我的应用程序中使用 REST API。它为我从这个应用程序发出的所有请求抛出 SocketTimeoutException。 Logcat 输出:(您也可以在此处看到带有漂亮格式的输出:http
python - 如何抑制显示后续异常的父异常(原因)
我知道 raise ... from None 并已阅读 How can I more easily suppress previous exceptions when I raise my own
gcc - 生成coreutils时发生MinGW错误(Windows和Linux上均发生一致错误)-原因？
在未能找到各种Unix工具(例如xargs和whatnot)的最新独立二进制文件(this version很好，但需要外部DLL)后，我承担了自己进行编译的挑战。 ...这是痛苦的。最终，尽管如此，
php - stream_socket_accept()失败时如何查找错误代码/原因
我有一个用PHP编写的流套接字服务器。为了查看一次可以处理多少个连接，我用C语言编写了一个模拟器来创建1000个不同的客户端以连接到服务器。 stream_socket_accept几次返回fals
android - 构建失败，原因:读取zip文件时出错
我的Android Studio昨天运行良好，但是今天当我启动Android Studio并想在移动设备上运行应用程序时，发生了以下错误，我在互联网和stackoverflow上进行了搜索，但没有解
grails - Grails Java域类中的toString()原因
默认情况下，grails似乎为Java域对象的toString()返回:。那当然不是我想要的，所以我尝试@Override toString()返回我想要的。当我尝试grails generate-a
spring - 原因:在Spring Security中无法将空值或空值传递给构造函数
尝试通过LDAP通过LDAP对用户进行身份验证时，出现以下错误。 Reason: Cannot pass null or empty values to constructor. 谁能告诉我做错了什么
Python模块无法加载共享库，原因: image not found
我正在尝试使用应用程序附带的 Houdini Python 模块，该模块是 Houdini 安装文件夹的一部分，位于标准 Python 路径之外。按照安装说明操作后，运行 Houdini Termin
c - 在非常小的代码片段中寻找 SEGFAULT 原因
简单地说，我正在为基本数据库编写单链表的原始实现。当用户请求打印索引下列出的元素高于数据库中当前记录数量时，我不断出现段错误，但仅当差值为 1 时。对于更高的数字，它只会触发我在那里编写的错误系统。

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

mysql - 如何发现MariaDB崩溃的原因？