Re: Bug in 3.23.42 on Linux - Martin MOKREJŠ - com.mysql.lists.bugs

10 messages in com.mysql.lists.bugsRe: Bug in 3.23.42 on Linux

From	Sent On	Attachments
Martin MOKREJŠ	29 Oct 2001 13:38
Sasha Pachev	29 Oct 2001 16:47
Martin MOKREJŠ	30 Oct 2001 02:05
Michael Widenius	30 Oct 2001 04:34
Martin MOKREJŠ	31 Oct 2001 06:35
Martin MOKREJŠ	31 Oct 2001 06:54
Michael Widenius	31 Oct 2001 11:39
Michael Widenius	31 Oct 2001 11:43
Martin MOKREJŠ	01 Nov 2001 04:55
Michael Widenius	01 Nov 2001 11:12

Subject:	Re: Bug in 3.23.42 on Linux
From:	Martin MOKREJŠ (mmok...@natur.cuni.cz)
Date:	10/30/2001 02:05:45 AM
List:	com.mysql.lists.bugs

On Mon, 29 Oct 2001, Sasha Pachev wrote:

How-To-Repeat:

This looks like some page corruption or a nasty buffer overrun, assuming you have used the correct .sym file to resolve it. The stack strace you have is impossible - there are way too many inconsistencies in the call hierarchy. Are you sure you used the right mysqld.sym file?

Hmm, I'm retrying again:

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

key_buffer_size=268431360 record_buffer=1044480 sort_buffer=1048568 max_used_connections=3 max_connections=100 threads_connected=3 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 466539 K bytes of memory Hope that's ok, if not, decrease some variables in the equation

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 range sanity check OK, backtrace follows: 0x807b1b8 0x812af8a 0x81517df 0x8114a6c 0x8109304 0x80c4768 0x80c446e 0x80cb320 0x80ce076 0x8082641 0x80856a6 0x8080d2d 0x808022c Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow
instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x50518d28 is invalid pointer thd->thread_id=103

shell$ /usr/local/mysql/bin/mysqladmin version /usr/local/mysql/bin/mysqladmin Ver 8.21 Distrib 3.23.42, for pc-linux-gnu on
i686 Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license

Server version 3.23.42-log Protocol version 10 Connection Localhost via UNIX socket UNIX socket /tmp/mysql.sock Uptime: 19 hours 30 min 51 sec

Threads: 5 Questions: 1163039 Slow queries: 39 Opens: 927 Flush tables: 1
Open tables: 785 Queries per second avg: 16.555 shell$

shell$ gzip -dc /usr/local/mysql/bin/mysqld.sym.gz > symbols shell$ /usr/local/mysql/bin/resolve_stack_dump ./symbols ./stack 0x807b1b8 server_init__Fv + 136 0x812af8a __pthread_initialize_manager + 354 0x81517df mem2chunk_check + 187 0x8114a6c flush_key_blocks + 788 0x8109304 chk_data_link + 6244 0x80c4768 check__9ha_myisamP3THDP15st_ha_check_opt + 592 0x80c446e dump__9ha_myisamP3THDi + 122 0x80cb320 prepare_for_restore__FP3THDP13st_table_list + 24 0x80ce076
mysql_alter_table__FP3THDPcT1P24st_ha_create_informationP13st_table_listRt4List1Z12create_fieldRt4List1Z3KeyRt4List1Z10Alter_dr
+ 9198 0x8082641 mysql_execute_command__Fv + 2709 0x80856a6
add_table_to_list__FP11Table_identP10lex_stringb13thr_lock_typePt4List1Z6StringT4
+ 370 0x8080d2d mysql_table_dump__FP3THDPcT1i + 225 0x808022c check_connections__FP3THD + 56 shell$ ps -ef | grep mysql pedant 28026 1 0 Oct29 ? 00:00:00 sh /usr/local/mysql/bin/safe_mys pedant 28065 28026 0 Oct29 ? 00:00:00 /usr/local/mysql/bin/mysqld --de pedant 28067 28065 0 Oct29 ? 00:00:01 /usr/local/mysql/bin/mysqld --de [...]