UBUNTU server. Last version.
And this is the error log
07:56:30 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=2000
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 = 4383238 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+0x20)[0x7f61a2d04f20]
/usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7f61a2bef8d5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f61a1981340]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7f61a0fd7f89]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f61a0fdb398]
/usr/sbin/mysqld(+0x62e540)[0x7f61a2e44540]
/usr/sbin/mysqld(+0x5f58e8)[0x7f61a2e0b8e8]
/usr/sbin/mysqld(+0x5977f9)[0x7f61a2dad7f9]
/usr/sbin/mysqld(+0x6258ec)[0x7f61a2e3b8ec]
/usr/sbin/mysqld(+0x626423)[0x7f61a2e3c423]
/usr/sbin/mysqld(+0x58595b)[0x7f61a2d9b95b]
/usr/sbin/mysqld(+0x554fb8)[0x7f61a2d6afb8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7f61a2bf1901]
/usr/sbin/mysqld(+0x3011f1)[0x7f61a2b171f1]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x8ea)[0x7f61a2b1af2a]
/usr/sbin/mysqld(+0x28a86b)[0x7f61a2aa086b]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7f61a2aa501b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f61a0fc2ec5]
/usr/sbin/mysqld(+0x286758)[0x7f61a2a9c758]
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.
140809 10:56:31 [Note] Plugin 'FEDERATED' is disabled.
140809 10:56:31 InnoDB: The InnoDB memory heap is disabled
140809 10:56:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140809 10:56:31 InnoDB: Compressed tables use zlib 1.2.8
140809 10:56:31 InnoDB: Using Linux native AIO
140809 10:56:31 InnoDB: Initializing buffer pool, size = 22.0G
140809 10:56:33 InnoDB: Completed initialization of buffer pool
140809 10:56:33 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 933438560304
140809 10:56:33 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: tried to read 1048576 bytes at offset 0 1048576.
InnoDB: Was only able to read 651264.
InnoDB: Fatal error: cannot read from file. OS error number 17.
140809 10:56:36 InnoDB: Assertion failure in thread 139822320605056 in file os0file.c line 2538
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.5/en/ ... overy.html
InnoDB: about forcing recovery.