- 积分
- 34
- 威望
-
- 金钱
-
- 注册时间
- 2012-7-4
- 在线时间
- 小时
- 最后登录
- 1970-1-1
|
机器配置:CPU:E7400 内存:2g 程序安装的是:Discuz 2.0 PV值:10W左右
==================================
my.cnf配置
[mysqld]
port
= 3306
socket
= /tmp/mysql.sock
skip-external-locking
#key_buffer_size = 16M
key_buffer_size = 128M
max_allowed_packet = 1M
table_open_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
#read_buffer_size = 256K
read_buffer_size = 1M
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
max_connections = 500
======================================
lnmp日志报错:
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query ((nil)): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED
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.
121012 05:25:44 mysqld_safe Number of processes running now: 0
121012 05:25:44 mysqld_safe mysqld restarted
121012 5:25:44 [Note] Event Scheduler: Loaded 0 events
121012 5:25:44 [Note] /usr/local/mysql/libexec/mysqld: ready for connections.
Version: '5.1.60-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution
121012 5:25:45 - 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=134217728
read_buffer_size=1048576
max_used_connections=2
max_threads=500
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 904239 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2d8d300
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 = 0x7f86c3a62cf0 thread_stack 0x40000
[0x6895a4]
[0x4bdd6b]
[0x62b440]
/lib/x86_64-linux-gnu/libc.so.6(get_nprocs+0x10d) [0x7f86d03215dd]
/lib/x86_64-linux-gnu/libc.so.6(+0x7f23a) [0x7f86d02ae23a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x1a9) [0x7f86d02b21e9]
/lib/x86_64-linux-gnu/libc.so.6(+0x6f30b) [0x7f86d029e30b]
/lib/x86_64-linux-gnu/libnss_files.so.2(_nss_files_gethostbyaddr_r+0x1bb) [0x7f86cbaed50b]
[0x7ab670]
[0x7ab3f6]
[0x4c49dc]
[0x4c5f00]
[0x4c670f]
[0x62763a]
[0x7a7ab9]
进入phpmyadmin后台,状态里面提示MYSQL无故重启;基本一个效果左右提示一次,
求教军哥,能否找出问题? |
|