# Segmentation faults Percona Server 5.6.19

**URL:** <https://forums.percona.com/t/segmentation-faults-percona-server-5-6-19/3607>\
**Category:** Percona Server for MySQL 5.6\
**Created:** [July 10, 2014, 10:13am UTC](https://forums.percona.com/t/segmentation-faults-percona-server-5-6-19/3607 "2014-07-10T10:13:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tcoker](https://avatars.discourse-cdn.com/v4/letter/t/ecc23a/32.png) [@tcoker](https://forums.percona.com/u/tcoker)\
**Post date:** [July 10, 2014, 10:13am UTC](https://forums.percona.com/t/segmentation-faults-percona-server-5-6-19/3607/1 "2014-07-10T10:13:05Z")

</div>

Hi, I’m hoping for a little guidance with this. I have had two of these crashes now on a recent installation of Percona Server 5.6.19 on CentOS 6.5. The problem happens when accessing ARCHIVE tables. Does this look like a bug?

16:05:46 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 [url][System Dashboard - Percona JIRA](http://bugs.percona.com/%5B/url%5D)

key\_buffer\_size=1073741824  
read\_buffer\_size=1048576  
max\_used\_connections=188  
max\_threads=2002  
thread\_count=177  
connection\_count=176  
It is possible that mysqld could use up to  
key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_threads = 7228203 K bytes of memory  
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x17e85e60  
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 = 7f7c813f8d40 thread\_stack 0x30000  
/usr/sbin/mysqld(my\_print\_stacktrace+0x2c)[0x8bb80c]  
/usr/sbin/mysqld(handle\_fatal\_signal+0x479)[0x6504b9]  
/lib64/libpthread.so.0[0x3af3a0f710]  
/usr/sbin/mysqld(\_ZN10ha\_archive10unpack\_rowEP11azio\_streamPh+0xf5)[0xadb385]  
/usr/sbin/mysqld(\_ZN10ha\_archive8rnd\_nextEPh+0x7a)[0xadb8ba]  
/usr/sbin/mysqld(\_ZN7handler11ha\_rnd\_nextEPh+0x5d)[0x597c5d]  
/usr/sbin/mysqld(\_Z13rr\_sequentialP11READ\_RECORD+0x20)[0x7f5780]  
/usr/sbin/mysqld(\_Z10sub\_selectP4JOINP13st\_join\_tableb+0x101)[0x6adbf1]  
/usr/sbin/mysqld(\_ZN4JOIN4execEv+0x2b8)[0x6ace68]  
/usr/sbin/mysqld(\_Z12mysql\_selectP3THDP10TABLE\_LISTjR4ListI4ItemEPS4\_P10SQL\_I\_ListI8st\_orderESB\_S7\_yP13select\_resultP18st\_select\_lex\_unitP13st\_select\_lex+0x275)[0x6f56b5]  
/usr/sbin/mysqld(\_Z13handle\_selectP3THDP13select\_resultm+0x165)[0x6f5f15]  
/usr/sbin/mysqld[0x559ee0]  
/usr/sbin/mysqld(\_Z21mysql\_execute\_commandP3THD+0x1cec)[0x6cfe3c]  
/usr/sbin/mysqld(\_Z11mysql\_parseP3THDPcjP12Parser\_state+0x5c8)[0x6d5078]  
/usr/sbin/mysqld(\_Z16dispatch\_command19enum\_server\_commandP3THDPcj+0xfa7)[0x6d6807]  
/usr/sbin/mysqld(\_Z24do\_handle\_one\_connectionP3THD+0x162)[0x6a4882]  
/usr/sbin/mysqld(handle\_one\_connection+0x40)[0x6a4970]  
/usr/sbin/mysqld(pfs\_spawn\_thread+0x143)[0xb0dc13]  
/lib64/libpthread.so.0[0x3af3a079d1]  
/lib64/libc.so.6(clone+0x6d)[0x3af36e8b5d]

Trying to get some variables.  
Some pointers may be invalid and cause the dump to abort.  
Query (7f7c380009a0): is an invalid pointer  
Connection ID (thread ID): 71  
Status: NOT\_KILLED

================================================================

08:11:21 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 [url][System Dashboard - Percona JIRA](http://bugs.percona.com/%5B/url%5D)

key\_buffer\_size=1073741824  
read\_buffer\_size=1048576  
max\_used\_connections=111  
max\_threads=2002  
thread\_count=31  
connection\_count=30  
It is possible that mysqld could use up to  
key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_threads = 7228203 K bytes of memory  
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x17ede490  
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 = 7fe1fcd8dd40 thread\_stack 0x30000  
/usr/sbin/mysqld(my\_print\_stacktrace+0x2c)[0x8bb80c]  
/usr/sbin/mysqld(handle\_fatal\_signal+0x479)[0x6504b9]  
/lib64/libpthread.so.0[0x3af3a0f710]  
/usr/sbin/mysqld(\_ZN10ha\_archive10unpack\_rowEP11azio\_streamPh+0xf5)[0xadb385]  
/usr/sbin/mysqld(\_ZN10ha\_archive8optimizeEP3THDP15st\_ha\_check\_opt+0x2a7)[0xadbbf7]  
/usr/sbin/mysqld(\_ZN10ha\_archive6repairEP3THDP15st\_ha\_check\_opt+0x15)[0xad9145]  
/usr/sbin/mysqld(\_ZN10ha\_archive16check\_and\_repairEP3THD+0x31)[0xad92f1]  
/usr/sbin/mysqld(\_ZN18Open\_table\_context24recover\_from\_failed\_openEv+0x431)[0x68b941]  
/usr/sbin/mysqld(\_Z11open\_tablesP3THDPP10TABLE\_LISTPjjP19Prelocking\_strategy+0x4fe)[0x68c14e]  
/usr/sbin/mysqld(\_Z30open\_normal\_and\_derived\_tablesP3THDP10TABLE\_LISTj+0x51)[0x68cc51]  
/usr/sbin/mysqld[0x6fcd02]  
/usr/sbin/mysqld(\_Z14get\_all\_tablesP3THDP10TABLE\_LISTP4Item+0x191)[0x70f121]  
/usr/sbin/mysqld(\_Z24get\_schema\_tables\_resultP4JOIN23enum\_schema\_table\_state+0x2d2)[0x7100d2]  
/usr/sbin/mysqld(\_ZN4JOIN14prepare\_resultEPP4ListI4ItemE+0xa5)[0x6f0f15]  
/usr/sbin/mysqld(\_ZN4JOIN4execEv+0xac)[0x6acc5c]  
/usr/sbin/mysqld(\_Z12mysql\_selectP3THDP10TABLE\_LISTjR4ListI4ItemEPS4\_P10SQL\_I\_ListI8st\_orderESB\_S7\_yP13select\_resultP18st\_select\_lex\_unitP13st\_select\_lex+0x275)[0x6f56b5]  
/usr/sbin/mysqld(\_Z13handle\_selectP3THDP13select\_resultm+0x165)[0x6f5f15]  
/usr/sbin/mysqld[0x559ee0]  
/usr/sbin/mysqld(\_Z21mysql\_execute\_commandP3THD+0x1cec)[0x6cfe3c]  
/usr/sbin/mysqld(\_Z11mysql\_parseP3THDPcjP12Parser\_state+0x5c8)[0x6d5078]  
/usr/sbin/mysqld(\_Z16dispatch\_command19enum\_server\_commandP3THDPcj+0xfa7)[0x6d6807]  
/usr/sbin/mysqld(\_Z24do\_handle\_one\_connectionP3THD+0x162)[0x6a4882]  
/usr/sbin/mysqld(handle\_one\_connection+0x40)[0x6a4970]  
/usr/sbin/mysqld(pfs\_spawn\_thread+0x143)[0xb0dc13]  
/lib64/libpthread.so.0[0x3af3a079d1]  
/lib64/libc.so.6(clone+0x6d)[0x3af36e8b5d]

Trying to get some variables.  
Some pointers may be invalid and cause the dump to abort.  
Query (7fe0f8004af0): is an invalid pointer  
Connection ID (thread ID): 5310  
Status: NOT\_KILLED
