数据库错误。军哥帮忙看下

yang2610278

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/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x760ede]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x654dba]
/lib64/libpthread.so.0(+0xf7e0)[0x7f9c157b77e0]
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.
160824 00:56:04 mysqld_safe mysqld from pid file /usr/local/mysql/var/t11592160327.pid ended
160824 01:01:32 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160824  1:01:32 InnoDB: The InnoDB memory heap is disabled
160824  1:01:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160824  1:01:32 InnoDB: Compressed tables use zlib 1.2.3
160824  1:01:32 InnoDB: Initializing buffer pool, size = 16.0M
160824  1:01:32 InnoDB: Completed initialization of buffer pool
160824  1:01:32 InnoDB: highest supported file format is Barracuda.
160824  1:01:32  InnoDB: Waiting for the background threads to start
160824  1:01:33 InnoDB: 5.5.42 started; log sequence number 1595695
17:01:33 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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1000
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 = 795907 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/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x760ede]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x654dba]
/lib64/libpthread.so.0(+0xf7e0)[0x7fbc78d067e0]
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.
160824 01:01:33 mysqld_safe mysqld from pid file /usr/local/mysql/var/t11592160327.pid ended
160824 01:06:22 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160824  1:06:22 InnoDB: The InnoDB memory heap is disabled
160824  1:06:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160824  1:06:22 InnoDB: Compressed tables use zlib 1.2.3
160824  1:06:22 InnoDB: Initializing buffer pool, size = 16.0M
160824  1:06:22 InnoDB: Completed initialization of buffer pool
160824  1:06:22 InnoDB: highest supported file format is Barracuda.
160824  1:06:22  InnoDB: Waiting for the background threads to start
160824  1:06:23 InnoDB: 5.5.42 started; log sequence number 1595695
17:06:23 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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1000
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 = 795907 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/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x760ede]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x654dba]
/lib64/libpthread.so.0(+0xf7e0)[0x7f48db4957e0]
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.
160824 01:06:23 mysqld_safe mysqld from pid file /usr/local/mysql/var/t11592160327.pid ended
160824 01:11:59 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160824  1:11:59 InnoDB: The InnoDB memory heap is disabled
160824  1:11:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160824  1:11:59 InnoDB: Compressed tables use zlib 1.2.3
160824  1:11:59 InnoDB: Initializing buffer pool, size = 16.0M
160824  1:11:59 InnoDB: Completed initialization of buffer pool
160824  1:11:59 InnoDB: highest supported file format is Barracuda.
160824  1:11:59  InnoDB: Waiting for the background threads to start
160824  1:12:00 InnoDB: 5.5.42 started; log sequence number 1595695
17:12:00 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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1000
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 = 795907 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/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x760ede]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x654dba]
/lib64/libpthread.so.0(+0xf7e0)[0x7f1535a4a7e0]
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.
160824 01:12:00 mysqld_safe mysqld from pid file /usr/local/mysql/var/t11592160327.pid ended

licess

首先检查硬盘或分区占用情况看看是不是满了，占用没问题的话再看https://bbs.vpser.net/thread-13040-1-1.html

yang2610278

lv_root 满了。。100%

yang2610278

LV_root     100%    怎么解决

licess

自己看有什么能删的就删除
可以按 https://www.vpser.net/manage/ncdu.html 挨个目录确认哪个目录文件占用的多

yang2610278

嗯。。好的。。有分区教程吗？

licess

论坛里有，用关键词 分区 搜索一下就行，选择所有开放版块