Portál AbcLinuxu, 14. května 2025 11:36
mysqld got signal 11; key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=15 max_connections=150 threads_connected=10 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 73982 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8430120 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... Bogus stack limit or frame pointer, fp=0x4129b1e4, stack_bottom=0x362, \\ thread_stack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x840d120 = Č P..B. thd->thread_id=11445 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash.Prosel jsem dokumentaci, zkousel sem prohledavat google, menit parametry (key_buffer_size, read_buffer_size a dalsi), downgradnout na nizsi verzi (4.0.18), ale situace se porad opakuje. MySQL mam kompilovane ze zdrojaku, distribuce je Redhat9. Poradi nekdo, kde muze byt zakopany pes? Diky
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.