# \[ERROR\] Got an error from unknown thread...any help??

**URL:** <https://forums.percona.com/t/error-got-an-error-from-unknown-thread-any-help/4459>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [October 19, 2015, 2:22am UTC](https://forums.percona.com/t/error-got-an-error-from-unknown-thread-any-help/4459 "2015-10-19T02:22:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![edudril](https://avatars.discourse-cdn.com/v4/letter/e/3da27b/32.png) [@edudril](https://forums.percona.com/u/edudril)\
**Post date:** [October 19, 2015, 2:22am UTC](https://forums.percona.com/t/error-got-an-error-from-unknown-thread-any-help/4459/1 "2015-10-19T02:22:03Z")

</div>

Hi everybody,

This morning I had an error in my PerconaCluster.this is the log, but i don’t know which is the ‘hit a bug’.  
Any idea please?

2015-10-19 08:41:40 48172 [ERROR] /usr/local/mysql/bin/mysqld: Incorrect key file for table ‘/tmp/#sql\_bc2c\_0.MYI’; try to repair it  
2015-10-19 08:41:40 48172 [ERROR] Got an error from unknown thread, /root/Galera\_Installation/Packages/Percona-XtraDB-Cluster-5.6.19-67.0/storage/myisam/mi\_write.c:223  
06:41:40 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 XtraDB Cluster better by reporting any  
bugs at [url][https://bugs.launchpad.net/percona-xtradb-cluster[/url]](https://bugs.launchpad.net/percona-xtradb-cluster%5B/url%5D)

key\_buffer\_size=33554432  
read\_buffer\_size=131072  
max\_used\_connections=501  
max\_threads=502  
thread\_count=46  
connection\_count=29  
It is possible that mysqld could use up to  
key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_threads = 233156 K bytes of memory  
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0xdbb28560  
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 = 7fa57fb2bdf8 thread\_stack 0x40000  
/usr/local/mysql/bin/mysqld(my\_print\_stacktrace+0x35)[0x904ac5]  
/usr/local/mysql/bin/mysqld(handle\_fatal\_signal+0x4c4)[0x680b74]  
/lib64/libpthread.so.0[0x31a7a0f500]  
/usr/local/mysql/bin/mysqld(\_ZNK7handler22ha\_statistic\_incrementEM17system\_status\_vary+0x8)[0x5bec28]  
/usr/local/mysql/bin/mysqld(\_ZN9ha\_myisam9write\_rowEPh+0x20)[0x957df0]  
/usr/local/mysql/bin/mysqld(\_ZN7handler12ha\_write\_rowEPh+0xff)[0x5c7b1f]  
/usr/local/mysql/bin/mysqld[0x6dd7f9]  
/usr/local/mysql/bin/mysqld[0x6e1731]  
/usr/local/mysql/bin/mysqld(\_Z10sub\_selectP4JOINP13st\_join\_tableb+0x1c1)[0x6e1c61]  
/usr/local/mysql/bin/mysqld[0x6e1731]  
/usr/local/mysql/bin/mysqld(\_Z10sub\_selectP4JOINP13st\_join\_tableb+0x1c1)[0x6e1c61]  
/usr/local/mysql/bin/mysqld[0x6e1731]  
/usr/local/mysql/bin/mysqld(\_Z10sub\_selectP4JOINP13st\_join\_tableb+0x1c1)[0x6e1c61]  
/usr/local/mysql/bin/mysqld[0x6e1731]  
/usr/local/mysql/bin/mysqld(\_Z10sub\_selectP4JOINP13st\_join\_tableb+0x1c1)[0x6e1c61]  
/usr/local/mysql/bin/mysqld[0x6e1731]  
/usr/local/mysql/bin/mysqld(\_Z10sub\_selectP4JOINP13st\_join\_tableb+0x1c1)[0x6e1c61]  
/usr/local/mysql/bin/mysqld[0x6e1731]  
/usr/local/mysql/bin/mysqld(\_Z10sub\_selectP4JOINP13st\_join\_tableb+0x1c1)[0x6e1c61]  
/usr/local/mysql/bin/mysqld[0x6e1731]  
/usr/local/m151019 08:41:48 mysqld\_safe Number of processes running now: 0  
151019 08:41:48 mysqld\_safe WSREP: not restarting wsrep node automatically  
151019 08:41:48 mysqld\_safe mysqld from pid file /DATAMYSQL/data1/mysql.pid ended