We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

MySQL - mysqld got signal 11


gtomek
18-06-2008, 23:15
Na 2 maszynach otrzymuje:

Jun 18 22:59:08 mysqld[23175]: mysqld got signal 11;
Jun 18 22:59:08 mysqld[23175]: This could be because you hit a bug. It is also possible that this binary
Jun 18 22:59:08 mysqld[23175]: or one of the libraries it was linked against is corrupt, improperly built,
Jun 18 22:59:08 mysqld[23175]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jun 18 22:59:08 mysqld[23175]: We will try our best to scrape up some info that will hopefully help diagnose
Jun 18 22:59:08 mysqld[23175]: the problem, but since we have already crashed, something is definitely wrong
Jun 18 22:59:08 mysqld[23175]: and this may fail.
Jun 18 22:59:08 mysqld[23175]:
Jun 18 22:59:08 mysqld[23175]: key_buffer_size=5242880
Jun 18 22:59:08 mysqld[23175]: read_buffer_size=131072
Jun 18 22:59:08 mysqld[23175]: max_used_connections=15
Jun 18 22:59:08 mysqld[23175]: max_connections=160
Jun 18 22:59:08 mysqld[23175]: threads_connected=6
Jun 18 22:59:08 mysqld[23175]: It is possible that mysqld could use up to
Jun 18 22:59:08 mysqld[23175]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 353278 K
Jun 18 22:59:08 mysqld[23175]: bytes of memory
Jun 18 22:59:08 mysqld[23175]: Hope that's ok; if not, decrease some variables in the equation.
Jun 18 22:59:08 mysqld[23175]:
Jun 18 22:59:08 mysqld[23175]: thd=0x2ac37b6008d0
Jun 18 22:59:08 mysqld[23175]: Attempting backtrace. You can use the following information to find out
Jun 18 22:59:08 mysqld[23175]: where mysqld died. If you see no messages after this, something went
Jun 18 22:59:08 mysqld[23175]: terribly wrong...
Jun 18 22:59:08 mysqld[23175]: Cannot determine thread, fp=0x403ce190, backtrace may not be correct.
Jun 18 22:59:08 mysqld[23175]: Stack range sanity check OK, backtrace follows:
Jun 18 22:59:08 mysqld[23175]: (nil)
Jun 18 22:59:08 mysqld[23175]: Stack trace seems successful - bottom reached
Jun 18 22:59:08 mysqld[23175]: Please read http://dev.mysql.com/doc/mysql/en/us...ack-trace.html and follow instructions on how to resolve the stack trace. Resolved
Jun 18 22:59:08 mysqld[23175]: stack trace is much more helpful in diagnosing the problem, so please do
Jun 18 22:59:08 mysqld[23175]: resolve it
Jun 18 22:59:08 mysqld[23175]: Trying to get some variables.
Jun 18 22:59:08 mysqld[23175]: Some pointers may be invalid and cause the dump to abort...
Jun 18 22:59:08 mysqld[23175]: thd->query at (nil) is invalid pointer
Jun 18 22:59:08 mysqld[23175]: thd->thread_id=11064
Jun 18 22:59:08 mysqld[23175]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Jun 18 22:59:08 mysqld[23175]: information that should help you find out what is causing the crash.
Jun 18 22:59:08 mysqld_safe[8758]: ended
Kompilacje wykluczam bo to mysql jest z paczki debianowskich 64 bit (nic nie kombinowałem).

Uszkodzenie hardware raczej takze, poniewaz podobny blad wystapil nagle na podobnej (trzeciej) maszynie ktora miala uptime od 300 dni - a te dwie to świeżaki po kilka dni.

Nie kiedy potrafie miec restart co 1 sekunde :/

It is possible that mysqld could use up to ...
takze wykluczam bo wszystko bylo ok przy znacznie wiekszych parametrach (te podane wyżej są specjalne zaniżone, tak jak proponuje komunikat)

Blad zaczyna wystepowac, gdy Queries per second avg przekroczy 30 - (normalnie obslugiwalem bez problemu nawet 300 / s )

Rece mi opadaja - jakies rady?