- 论坛徽章:
- 0
|
我是4.1.22的mysql+rhel 2.6.9-34.ELsmp,4G内存。
最近2个月我的mysql每天至少会重启1到2次,有时候是在访问高峰期,有时候却是在凌晨没什么负载的情况下重启。
以下是重启时.err报的错误:
--------------------------------------------------------------------------------------------------------------------------
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=16773120
max_used_connections=201
max_connections=200
threads_connected=34
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2620638 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x310cf398
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...
Cannot determine thread, fp=0xb, backtrace may not be correct.
Bogus stack limit or frame pointer, fp=0xb, stack_bottom=0x4860000, thread_stack=196608, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x18fdb6c8 is invalid pointer
thd->thread_id=13294
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
--------------------------------------------------------------------------------------------------------------------------
我调过key_buffer_size,read_buffer_size,sort_buffer_size等参数,调到很低也照样会死掉。
我也看过coredump出来的core文件,没看出每次死掉的时候有什么共同点,也看不到在执行什么语句。。
现在我怀疑是linux2.6的内核,不允许单个进程使用内存超过3G的原因。
以上这台出问题的mysql,是我7台作用相同的数据库中的一台,因为硬件条件比较好,所以分配给他的负载比较重
希望各位遇到过相同情况的,帮我看看,为什么这个数据库的占用内存一直会增大,就算在凌晨也不释放,或者是不是有别的原因导致它死掉? |
|