| 2014-10-18 04:36:55 |
Roel Van de Paar |
description |
On Percona Server 5.5.29:
141002 14:08:46 [Warning] Aborted connection 11233573 to db: 'unconnected' user: 'etluser' host: '10.0.20.65' (Got an error reading communication packets)
19:11:01 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=268435456
read_buffer_size=262144
max_used_connections=116
max_threads=1002
thread_count=57
connection_count=57
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 16947701 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+0x35)[0x7b07a5]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x68bec4]
/lib64/libpthread.so.0(+0xf500)[0x7f14c37da500]
/usr/sbin/mysqld(my_realpath+0x73)[0x7ad893]
/usr/sbin/mysqld(_Z19find_or_create_fileP10PFS_threadP14PFS_file_classPKcj+0x84)[0x80b184]
/usr/sbin/mysqld[0x8144a6]
/usr/sbin/mysqld[0x8e3f85]
/usr/sbin/mysqld[0x8e47b9]
/usr/sbin/mysqld[0x8e78dc]
/usr/sbin/mysqld[0x8b75bb]
/usr/sbin/mysqld[0x8b91f5]
/usr/sbin/mysqld[0x8b9bcd]
/usr/sbin/mysqld[0x861102]
/lib64/libpthread.so.0(+0x7851)[0x7f14c37d2851]
/lib64/libc.so.6(clone+0x6d)[0x7f14c2a5811d]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
Writing a core file
Will get resolved stack and possibly core dump and update here. |
On Percona Server 5.5.29:
141002 14:08:46 [Warning] Aborted connection 11233573 to db: 'unconnected' user: '<user>' host: '<ip>' (Got an error reading communication packets)
19:11:01 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=268435456
read_buffer_size=262144
max_used_connections=116
max_threads=1002
thread_count=57
connection_count=57
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 16947701 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+0x35)[0x7b07a5]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x68bec4]
/lib64/libpthread.so.0(+0xf500)[0x7f14c37da500]
/usr/sbin/mysqld(my_realpath+0x73)[0x7ad893]
/usr/sbin/mysqld(_Z19find_or_create_fileP10PFS_threadP14PFS_file_classPKcj+0x84)[0x80b184]
/usr/sbin/mysqld[0x8144a6]
/usr/sbin/mysqld[0x8e3f85]
/usr/sbin/mysqld[0x8e47b9]
/usr/sbin/mysqld[0x8e78dc]
/usr/sbin/mysqld[0x8b75bb]
/usr/sbin/mysqld[0x8b91f5]
/usr/sbin/mysqld[0x8b9bcd]
/usr/sbin/mysqld[0x861102]
/lib64/libpthread.so.0(+0x7851)[0x7f14c37d2851]
/lib64/libc.so.6(clone+0x6d)[0x7f14c2a5811d]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
Writing a core file
Will get resolved stack and possibly core dump and update here. |
|
