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/31/2001 06:54:26 AM
List:	com.mysql.lists.bugs

On Wed, 31 Oct 2001, Martin MOKREJŠ wrote:

On Tue, 30 Oct 2001, Michael Widenius wrote:

Hi!

"mmokrejs" == mmokrejs <iso-8859-2> writes:

mmokrejs> On Mon, 29 Oct 2001, Sasha Pachev wrote:

How-To-Repeat:

I guess the files from Sep 6 are 3.23.41 with those patches you wrote for REPAIR TABLE and myisampack. The problem is, that extracting binaries from your
website gives mysqld located in bin/ instead of libexec/ as is the default case when I create custom-compiled binaries.

So, to solve the problem: shell$ /usr/local/mysql/libexec/mysqld --help /usr/local/mysql/libexec/mysqld Ver 3.23.41 for pc-linux-gnu on i686 Copyright (C) 2000 MySQL AB & MySQL Finland AB, by Monty and others This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license

[...] Does the output above show if /usr/local/mysql/libexec/mysqld is from the binary package supplied by mysql or is it compiled by me?

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

[...] I hope you can figure out if the 3.23.41 version from which is the crashdump is the one from your website or not. Is the filesize same as in the binary distrib.?

Sorry for confusion.

It looks it was the mysqld from distribution, i.e. 3.23.41, because it reports itself as /usr/local/mysql/bin/mysqld . We can forget almost everythong what's currently in /usr/local/mysql/bin/ , because it has been overwritten on Sep 8. One of the remnants is in /usr/local/mysql/libexec/ created Sep 6 22:00.

Here's the full log.

010906 22:00:14 mysqld ended

010906 22:01:06 mysqld started /usr/local/mysql/bin/mysqld: ready for connections 010906 22:11:16 Warning: Retrying repair of: './Mloti/blast_data' with keycache mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary

[...]

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

[...] 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

Successfully dumped variables, if you ran with --log, take a look at the details of what thread 103 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash

Number of processes running now: 0 010906 22:11:17 mysqld restarted /usr/local/mysql/bin/mysqld: ready for connections

It may just confuse you, because I think this isn't any usefull information (just in case), but if I extract symbols from /usr/local/mysql/libexec/mysqld and use the above stack trace, I get: 0x807b1b8 yyparse__Fv + 15800 0x812af8a on_exit + 26 0x81517df key_encryptsession + 19 0x8114a6c pthread_exit + 28 0x8109304 get_charsets_dir + 144 0x80c4768 mysqld_list_processes__FP3THDPCcb + 28 0x80c446e store_create_info__FP3THDP8st_tableP6String + 1870 0x80cb320 exec_event__FP3THDP6st_netP14st_master_infoi + 556 0x80ce076 mysql_binlog_send__FP3THDPcUlUs + 1598 0x8082641 send_fields__FP3THDRt4List1Z4ItemUi + 245 0x80856a6 setup_conds__FP3THDP13st_table_listPP4Item + 414 0x8080d2d yyparse__Fv + 39213 0x808022c yyparse__Fv + 36396

But, think the stack dump is from /usr/local/mysql/bin/mysqld , that is from the binary distribution 3.23.41, so I suggest you to take the symbols file from distribution and resolve the stack trace yourself. ;)