在Mac OSX上使用Docker Toolbox部署mysql容器时遇到权限问题，启动过程中报错，显示无法访问数据文件目录。错误信息涉及InnoDB内存堆、初始化缓冲池及日志文件设置。建议检查Docker挂载卷的权限配置，确保与主机文件系统的兼容性。
好像是权限问题。有没有人碰到过类似问题？
Installing MySQL system tables...2015-11-16 01:33:36 0 /usr/sbin/mysqld (mysqld 5.6.25) starting as process 33 ...
2015-11-16 01:33:36 33 InnoDB: Using atomics to ref count buffer pool pages
2015-11-16 01:33:36 33 InnoDB: The InnoDB memory heap is disabled
2015-11-16 01:33:36 33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-11-16 01:33:36 33 InnoDB: Memory barrier is not used
2015-11-16 01:33:36 33 InnoDB: Compressed tables use zlib 1.2.7
2015-11-16 01:33:36 33 InnoDB: Using Linux native AIO
2015-11-16 01:33:36 33 InnoDB: Using CPU crc32 instructions
2015-11-16 01:33:36 33 InnoDB: Initializing buffer pool, size = 128.0M
2015-11-16 01:33:36 33 InnoDB: Completed initialization of buffer pool
2015-11-16 01:33:36 33 InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2015-11-16 01:33:36 33 InnoDB: Setting file ./ibdata1 size to 12 MB
2015-11-16 01:33:36 33 InnoDB: Database physically writes the file full: wait...
2015-11-16 01:33:36 33 InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2015-11-16 01:33:37 33 InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2015-11-16 01:33:38 7f1307465720 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
2015-11-16 01:33:38 7f1307465720 InnoDB: Assertion failure in thread 139719703156512 in file fil0fil.cc line 875
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
01:33:38 UTC - 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.
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.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68105 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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)
/usr/sbin/mysqld(handle_fatal_signal+0x471)
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)
/usr/sbin/mysqld
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x7b0)
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x7bd)
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)
/usr/sbin/mysqld
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.
mysql_install_dbInstalling MySQL system tables...2015-11-16 01:33:58 0 /usr/sbin/mysqld (mysqld 5.6.25) starting as process 49 ...
2015-11-16 01:33:58 49 InnoDB: Using atomics to ref count buffer pool pages
2015-11-16 01:33:58 49 InnoDB: The InnoDB memory heap is disabled
2015-11-16 01:33:58 49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-11-16 01:33:58 49 InnoDB: Memory barrier is not used
2015-11-16 01:33:58 49 InnoDB: Compressed tables use zlib 1.2.7
2015-11-16 01:33:58 49 InnoDB: Using Linux native AIO
2015-11-16 01:33:58 49 InnoDB: Using CPU crc32 instructions
2015-11-16 01:33:58 49 InnoDB: Initializing buffer pool, size = 128.0M
2015-11-16 01:33:58 49 InnoDB: Completed initialization of buffer pool
2015-11-16 01:33:58 49 InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2015-11-16 01:33:58 49 InnoDB: Setting file ./ibdata1 size to 12 MB
2015-11-16 01:33:58 49 InnoDB: Database physically writes the file full: wait...
2015-11-16 01:33:58 49 InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2015-11-16 01:33:58 49 InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2015-11-16 01:33:59 7f5914eab720 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
2015-11-16 01:33:59 7f5914eab720 InnoDB: Assertion failure in thread 140020579743520 in file fil0fil.cc line 875
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
01:33:59 UTC - 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.
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.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68105 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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)
/usr/sbin/mysqld(handle_fatal_signal+0x471)
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)
/usr/sbin/mysqld
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x7b0)
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x7bd)
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)
/usr/sbin/mysqld
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.
扫一扫
5481
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
