Portál AbcLinuxu, 14. května 2025 06:10

Dotaz: mysqld got signal 11;

11.8.2009 15:47 Vláďa
mysqld got signal 11;
Přečteno: 256×
Odpovědět | Admin

Dobry den,

Mam problem s MySQL na Debianu:

Cas od casu zahlasi do syslogu toto a spadne:

Aug 11 15:00:23 z142 mysqld[14995]: 090811 15:00:23 - mysqld got signal 11;
Aug 11 15:00:23 z142 mysqld[14995]: This could be because you hit a bug. It is also possible that this binary
Aug 11 15:00:23 z142 mysqld[14995]: or one of the libraries it was linked against is corrupt, improperly built,
Aug 11 15:00:23 z142 mysqld[14995]: or misconfigured. This error can also be caused by malfunctioning hardware.
Aug 11 15:00:23 z142 mysqld[14995]: We will try our best to scrape up some info that will hopefully help diagnose
Aug 11 15:00:23 z142 mysqld[14995]: the problem, but since we have already crashed, something is definitely wrong
Aug 11 15:00:23 z142 mysqld[14995]: and this may fail.
Aug 11 15:00:23 z142 mysqld[14995]:
Aug 11 15:00:23 z142 mysqld[14995]: key_buffer_size=50331648
Aug 11 15:00:23 z142 mysqld[14995]: read_buffer_size=131072
Aug 11 15:00:23 z142 mysqld[14995]: max_used_connections=32
Aug 11 15:00:23 z142 mysqld[14995]: max_connections=600
Aug 11 15:00:23 z142 mysqld[14995]: threads_connected=32
Aug 11 15:00:23 z142 mysqld[14995]: It is possible that mysqld could use up to
Aug 11 15:00:23 z142 mysqld[14995]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1354747 K
Aug 11 15:00:23 z142 mysqld[14995]: bytes of memory
Aug 11 15:00:23 z142 mysqld[14995]: Hope that's ok; if not, decrease some variables in the equation.
Aug 11 15:00:23 z142 mysqld[14995]:
Aug 11 15:00:23 z142 mysqld[14995]: thd=0x1e5fe50
Aug 11 15:00:23 z142 mysqld[14995]: Attempting backtrace. You can use the following information to find out
Aug 11 15:00:23 z142 mysqld[14995]: where mysqld died. If you see no messages after this, something went
Aug 11 15:00:23 z142 mysqld[14995]: terribly wrong...
Aug 11 15:00:23 z142 mysqld[14995]: Cannot determine thread, fp=0x1e5fe50, backtrace may not be correct.
Aug 11 15:00:23 z142 mysqld[14995]: Bogus stack limit or frame pointer, fp=0x1e5fe50, stack_bottom=0x44450000, thread_stack=131072, aborting backtrace.
Aug 11 15:00:23 z142 mysqld[14995]: Trying to get some variables.
Aug 11 15:00:23 z142 mysqld[14995]: Some pointers may be invalid and cause the dump to abort...
Aug 11 15:00:23 z142 mysqld[14995]: thd->query at 0x1f851c8 =      

 

Nesetkali jste se s necim podobnym?

dekuji

 

 

Nástroje: Začni sledovat (0) ?Zašle upozornění na váš email při vložení nového komentáře.

Odpovědi

11.8.2009 16:56 cronin | skóre: 49
Rozbalit Rozbalit vše Re: mysqld got signal 11;
Odpovědět | | Sbalit | Link | Blokovat | Admin
11 je SIGSEGV. Staci sa riadit tym, co sa pise v opise toho chyboveho hlasenia: vylucit chybu v hardveri, najma ak "pada" aj nieco ine. Obcastne padanie by mohlo naznacovat problemy s prehrievanim. Ak je to zalezitost iba MySQL, pride na rad otazka, ako je nainstalovana, ci su v poriadku zavislosti, ci nebola "osidena" nejaka verzia kniznice a pod.; reinstalovat/rebuildovat aplikaciu a jej zavislosti.

Nesetkali jste se s necim podobnym?
Ano, tisice ludi sa s tym uz stetlo.
12.8.2009 11:48 Vláďa
Rozbalit Rozbalit vše Re: mysqld got signal 11;

Diky,

Odstranil jsem jednu podezrelou databazi (hlasila chyby v phpmyadminu) a provedl upgrade databaze, zatim to bezi 12 hodin bez vypadku, tak uvidime.

 

Založit nové vláknoNahoru

Tiskni Sdílej: Linkuj Jaggni to Vybrali.sme.sk Google Del.icio.us Facebook

ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.