Bitnami MariaDB 重启失败记录

自动部署的 Magento 附带的 MariaDB 镜像第一次启动能够成功,但 stop 之后就无法再次启动。启动命令 docker-compose up -d,重启命令 docker-compose restart

关键 log:

1
2
3
InnoDB: Assertion failure in file /bitnami/blacksmith-sandox/mariadb-10.2.28/storage/innobase/dict/dict0dict.cc line 1467
InnoDB: Failing assertion: table->can_be_evicted
[ERROR] mysqld got signal 6 ;

详细的 stdout 如下——

第一次启动

docker log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
 03:20:42.43 Welcome to the Bitnami mariadb container
03:20:42.43 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mariadb
03:20:42.43 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mariadb/issues
03:20:42.44 Send us your feedback at containers@bitnami.com
03:20:42.44
03:20:42.44 INFO ==> ** Starting MariaDB setup **
03:20:42.48 INFO ==> Validating settings in MYSQL_*/MARIADB_* env vars
03:20:42.48 WARN ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
03:20:42.49 INFO ==> Initializing mariadb database
03:20:42.50 INFO ==> Installing database
03:20:47.95 INFO ==> Starting mariadb in background
03:20:48.97 INFO ==> Configuring authentication
03:20:49.12 INFO ==> Running mysql_upgrade
03:20:49.65 INFO ==> Stopping mariadb
03:20:53.69 INFO ==> ** MariaDB setup finished! **

03:20:53.77 INFO ==> ** Starting MariaDB **
2019-11-08 3:20:53 140200746645312 [Note] /opt/bitnami/mariadb/sbin/mysqld (mysqld 10.2.28-MariaDB) starting as process 1 ...
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Uses event mutexes
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Using Linux native AIO
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Number of pools: 1
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Using SSE2 crc32 instructions
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Completed initialization of buffer pool
2019-11-08 3:20:53 140200228304640 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Highest supported file format is Barracuda.
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-11-08 3:20:53 140200746645312 [Note] InnoDB: Waiting for purge to start
2019-11-08 3:20:54 140200746645312 [Note] InnoDB: 5.7.28 started; log sequence number 1620006
2019-11-08 3:20:54 140199854065408 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mariadb/data/ib_buffer_pool
2019-11-08 3:20:54 140199854065408 [Note] InnoDB: Buffer pool(s) load completed at 191108 3:20:54
2019-11-08 3:20:54 140200746645312 [Note] Plugin 'FEEDBACK' is disabled.
2019-11-08 3:20:54 140200746645312 [Note] Server socket created on IP: '0.0.0.0'.
2019-11-08 3:20:54 140200746645312 [Warning] 'proxies_priv' entry '@% root@58577f4b0595' ignored in --skip-name-resolve mode.
2019-11-08 3:20:54 140200746645312 [Note] Reading of all Master_info entries succeeded
2019-11-08 3:20:54 140200746645312 [Note] Added new Master_info '' to hash table
2019-11-08 3:20:54 140200746645312 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections.
Version: '10.2.28-MariaDB' socket: '/opt/bitnami/mariadb/tmp/mysql.sock' port: 3306 Source distribution

停止

1
2
3
4
5
6
7
8
9
10
2019-11-15 15:08:01 140200219911936 [Note] /opt/bitnami/mariadb/sbin/mysqld (initiated by: unknown): Normal shutdown
2019-11-15 15:08:01 140200219911936 [Note] Event Scheduler: Purging the queue. 0 events
2019-11-15 15:08:01 140200105715456 [Note] InnoDB: FTS optimize thread exiting.
2019-11-15 15:08:01 140200219911936 [Note] InnoDB: Starting shutdown...
2019-11-15 15:08:01 140199854065408 [Note] InnoDB: Dumping buffer pool(s) to /bitnami/mariadb/data/ib_buffer_pool
2019-11-15 15:08:01 140199854065408 [Note] InnoDB: Instance 0, restricted to 2047 pages due to innodb_buf_pool_dump_pct=25
2019-11-15 15:08:01 140199854065408 [Note] InnoDB: Buffer pool(s) dump completed at 191115 15:08:01
2019-11-15 15:08:02 140200219911936 [Note] InnoDB: Shutdown completed; log sequence number 482295338
2019-11-15 15:08:02 140200219911936 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-11-15 15:08:02 140200219911936 [Note] /opt/bitnami/mariadb/sbin/mysqld: Shutdown complete

重启后

docker log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
 16:16:36.31 Welcome to the Bitnami mariadb container
16:16:36.31 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mariadb
16:16:36.32 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mariadb/issues
16:16:36.32 Send us your feedback at containers@bitnami.com
16:16:36.32
16:16:36.32 INFO ==> ** Starting MariaDB setup **
16:16:36.35 INFO ==> Validating settings in MYSQL_*/MARIADB_* env vars
16:16:36.35 WARN ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
16:16:36.35 INFO ==> Initializing mariadb database
16:16:36.36 INFO ==> Using persisted data
16:16:36.37 INFO ==> Running mysql_upgrade
16:16:36.37 INFO ==> Starting mariadb in background
2019-11-15 16:16:36 140149675591488 [Note] /opt/bitnami/mariadb/sbin/mysqld (mysqld 10.2.28-MariaDB) starting as process 109 ...
2019-11-15 16:16:36 140149675591488 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-11-15 16:16:36 140149675591488 [Note] InnoDB: Uses event mutexes
2019-11-15 16:16:36 140149675591488 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-11-15 16:16:36 140149675591488 [Note] InnoDB: Using Linux native AIO
2019-11-15 16:16:36 140149675591488 [Note] InnoDB: Number of pools: 1
2019-11-15 16:16:36 140149675591488 [Note] InnoDB: Using SSE2 crc32 instructions
2019-11-15 16:16:36 140149675591488 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-11-15 16:16:36 140149675591488 [Note] InnoDB: Completed initialization of buffer pool
2019-11-15 16:16:36 140149158459136 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-11-15 16:16:36 140149675591488 [Note] InnoDB: Highest supported file format is Barracuda.
2019-11-15 16:16:36 0x7f7723a10740 InnoDB: Assertion failure in file /bitnami/blacksmith-sandox/mariadb-10.2.28/storage/innobase/dict/dict0dict.cc line 1467
InnoDB: Failing assertion: table->can_be_evicted
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.
191115 16:16:36 [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.28-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467243 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
/opt/bitnami/mariadb/sbin/mysqld(my_print_stacktrace+0x29)[0x55bc847d6809]
/opt/bitnami/mariadb/sbin/mysqld(handle_fatal_signal+0x39d)[0x55bc84306bcd]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f77235ed0e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f7721aaafff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f7721aac42a]
/opt/bitnami/mariadb/sbin/mysqld(+0x413e3a)[0x55bc840d8e3a]
/opt/bitnami/mariadb/sbin/mysqld(+0x966940)[0x55bc8462b940]
/opt/bitnami/mariadb/sbin/mysqld(+0x973ff7)[0x55bc84638ff7]
/opt/bitnami/mariadb/sbin/mysqld(+0x974750)[0x55bc84639750]
/opt/bitnami/mariadb/sbin/mysqld(+0x975bc0)[0x55bc8463abc0]
/opt/bitnami/mariadb/sbin/mysqld(+0x966870)[0x55bc8462b870]
/opt/bitnami/mariadb/sbin/mysqld(+0x9b6fb0)[0x55bc8467bfb0]
/opt/bitnami/mariadb/sbin/mysqld(+0x9bd2bd)[0x55bc846822bd]
/opt/bitnami/mariadb/sbin/mysqld(+0x80a7fa)[0x55bc844cf7fa]
/opt/bitnami/mariadb/sbin/mysqld(+0x8affd1)[0x55bc84574fd1]
/opt/bitnami/mariadb/sbin/mysqld(+0x7b2820)[0x55bc84477820]
/opt/bitnami/mariadb/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x65)[0x55bc84309115]
/opt/bitnami/mariadb/sbin/mysqld(+0x4c9d88)[0x55bc8418ed88]
/opt/bitnami/mariadb/sbin/mysqld(_Z11plugin_initPiPPci+0x7fa)[0x55bc8418fd2a]
/opt/bitnami/mariadb/sbin/mysqld(+0x431825)[0x55bc840f6825]
/opt/bitnami/mariadb/sbin/mysqld(_Z11mysqld_mainiPPc+0x1bd3)[0x55bc840fc3b3]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f7721a982e1]
/opt/bitnami/mariadb/sbin/mysqld(_start+0x2a)[0x55bc840eff5a]
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 /bitnami/mariadb/data
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 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 31861 31861 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/share/apport/apport %p %s %c %d %P

/libos.sh: line 103: 109 Aborted (core dumped) "$@"

Comments

Your browser is out-of-date!

Update your browser to view this website correctly. Update my browser now

×