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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x76231e]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x65659a]
/lib64/libpthread.so.0[0x3ab8e0f7e0]
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.
170220 03:36:45 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
170220 03:40:30 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170220 3:40:30 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
170220 3:40:30 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 4061 ...
170220 3:40:30 [Note] Plugin 'FEDERATED' is disabled.
170220 3:40:30 InnoDB: The InnoDB memory heap is disabled
170220 3:40:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170220 3:40:30 InnoDB: Compressed tables use zlib 1.2.3
170220 3:40:30 InnoDB: Using Linux native AIO
170220 3:40:30 InnoDB: Initializing buffer pool, size = 1.0G
170220 3:40:30 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file /www/server/data/ib_logfile0 is of different size 0 0 bytes
InnoDB: than specified in the .cnf file 0 268435456 bytes!
170220 3:40:30 [ERROR] Plugin 'InnoDB' init function returned error.
170220 3:40:30 [ERROR]170220 03:40:30 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
170220 03:44:34 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170220 3:44:34 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
170220 3:44:34 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 2230 ...
170220 03:47:08 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170220 3:47:09 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
170220 3:47:09 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 2223 ...
170220 3:47:09 [Note] Plugin 'FEDERATED' is disabled.
170220 3:47:09 InnoDB: The InnoDB memory heap is disabled
170220 3:47:09 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170220 3:47:09 InnoDB: Compressed tables use zlib 1.2.3
170220 3:47:09 InnoDB: Using Linux native AIO
170220 3:47:09 InnoDB: Initializing buffer pool, size = 1.0G
170220 3:47:09 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file /www/server/data/ib_logfile0 is of different size 0 0 bytes
InnoDB: than specified in the .cnf file 0 268435456 bytes!
170220 3:47:09 [ERROR] Plugin 'InnoDB' init function returned error.
170220 3:47:09 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
02:47:09 UTC - 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.
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=268435456
read_buffer_size=4194304
max_used_connections=0
max_threads=500
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 = 4363909 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
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x76231e]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x65659a]
/lib64/libpthread.so.0[0x3ab8e0f7e0]
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.
170220 03:47:09 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
170220 04:00:56 mysqld_safe Starting mysqld daemon with databases from /www/server/data
170220 4:00:56 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
170220 4:00:56 [Note] /www/server/mysql/bin/mysqld (mysqld 5.5.53-log) starting as process 3205 ...
170220 4:00:56 [Note] Plugin 'FEDERATED' is disabled.
170220 4:00:56 InnoDB: The InnoDB memory heap is disabled
170220 4:00:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170220 4:00:56 InnoDB: Compressed tables use zlib 1.2.3
170220 4:00:56 InnoDB: Using Linux native AIO
170220 4:00:56 InnoDB: Initializing buffer pool, size = 1.0G
170220 4:00:56 InnoDB: Completed initialization of buffer pool
170220 4:00:56 InnoDB: Log file /www/server/data/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /www/server/data/ib_logfile0 size to 256 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB:170220 4:00:56 InnoDB: Error: Write to file /www/server/data/ib_logfile0 failed at offset 0 0.
InnoDB: 1048576 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 28.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk 170220 04:00:56 mysqld_safe mysqld from pid file /www/server/data/btcn.pid ended
[root@btcn ~]#
|