# mysqld got signal 11 ;

**URL:** <https://forums.percona.com/t/mysqld-got-signal-11/5505>\
**Category:** Other MySQL® Questions\
**Created:** [March 23, 2017, 2:57am UTC](https://forums.percona.com/t/mysqld-got-signal-11/5505 "2017-03-23T02:57:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![xliu](https://avatars.discourse-cdn.com/v4/letter/x/ecccb3/32.png) [@xliu](https://forums.percona.com/u/xliu)\
**Post date:** [March 23, 2017, 2:57am UTC](https://forums.percona.com/t/mysqld-got-signal-11/5505/1 "2017-03-23T02:57:07Z")

</div>

Hi,  
I use Percona-Server-5.7.12-5-Linux.x86\_64.ssl101

In mysql.err file ，It throws the following error

。。。。。。  
09:05:03 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.  
Attempting to collect some information that could help diagnose the problem.  
As this is a crash and something is definitely wrong, the information  
collection process might 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=33554432  
read\_buffer\_size=1048576  
max\_used\_connections=40  
max\_threads=501  
thread\_count=9  
connection\_count=7  
It is possible that mysqld could use up to  
key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_threads = 1063797 K bytes of memory  
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f6a13016000  
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 = 7f6d7b906ce0 thread\_stack 0x30000  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(my\_print\_stacktrace+0x2c)[0xec366c]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(handle\_fatal\_signal+0x461)[0x79cb41]  
/lib64/libpthread.so.0[0x38c500f710]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld[0xc90635]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(\_ZN4JOIN14test\_skip\_sortEv+0x15d)[0xc913bd]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(\_ZN4JOIN8optimizeEv+0x1b53)[0xc9e483]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(\_ZN13st\_select\_lex8optimizeEP3THD+0x685)[0xce3965]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(\_Z12handle\_queryP3THDP3LEXP12Query\_resultyy+0x155)[0xce3b45]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld[0x75c26f]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(\_Z21mysql\_execute\_commandP3THDb+0x46ae)[0xca715e]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(\_Z11mysql\_parseP3THDP12Parser\_state+0x5b5)[0xcaa1b5]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(\_Z16dispatch\_commandP3THDPK8COM\_DATA19enum\_server\_command+0x92f)[0xcaab5f]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(\_Z10do\_commandP3THD+0x1b7)[0xcac4f7]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(handle\_connection+0x2a8)[0xd6d468]  
/usr/local/Percona-Server-5.7.12-5-Linux.x86\_64.ssl101/bin/mysqld(pfs\_spawn\_thread+0x1b4)[0xf39164]  
/lib64/libpthread.so.0[0x38c50079d1]  
/lib64/libc.so.6(clone+0x6d)[0x35636e8b6d]

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

You may download the Percona Server operations manual by visiting  
[url][http://www.percona.com/software/percona-server/[/url]](http://www.percona.com/software/percona-server/%5B/url%5D). You may find information  
in the manual which will help you identify the cause of the crash.  
2017-03-21T09:05:03.697135Z mysqld\_safe Number of processes running now: 0  
2017-03-21T09:05:03.698458Z mysqld\_safe mysqld restarted  
。。。。。。  
Why ?  
How to solve it ?  
thanks!

---

<div class="post-metadata">

**Author:** ![jrivera](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jrivera/32/13_2.png) [@jrivera](https://forums.percona.com/u/jrivera)\
**Post date:** [March 28, 2017, 2:21am UTC](https://forums.percona.com/t/mysqld-got-signal-11/5505/2 "2017-03-28T02:21:22Z")

</div>

Hi, you might want to check the answer provided here - [url][mysql - Percona crash after running for some time - Database Administrators Stack Exchange](https://dba.stackexchange.com/questions/159428/percona-crash-after-running-for-some-time%5B/url%5D). It’s really hard to pinpoint what could’ve caused this unless if you can reproduce the crash.

---

<div class="post-metadata">

**Author:** ![xliu](https://avatars.discourse-cdn.com/v4/letter/x/ecccb3/32.png) [@xliu](https://forums.percona.com/u/xliu)\
**Post date:** [March 29, 2017, 4:04am UTC](https://forums.percona.com/t/mysqld-got-signal-11/5505/3 "2017-03-29T04:04:39Z")

</div>

I have found the reason ,Our bad sql causes the crash! thanks!