As I can't provide steps to reproduce the crash, I decided to mail my
problem to this list. If this isn't the correct list, sorry. And sorry if
this message comes twice as for some reason the mail bounced back twice
already.
Anywho, I'm running mysql-standard-4.1.12-pc-linux-gnu-i686 (statically
linked version) to which I upgraded to just today from 4.0.2 because 4.0.2
seemed to be crashing randomly during some queries. The problem, however,
was not fixed with the update.
I'm running MySQL on a virtual server running Xen with 2.6.10-kernel. When
using for example Coppermine, the database server crashes sometimes (about
one time in six) when uploading images to the server. The same problem
occurs with TikiWiki when adding images. The server gets about 7-8
queries/second but runs fast without any other problems even though the
virtual server is limited to 128M of memory.
The crash causes the following error log:
--- clip ---
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
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=8388600
read_buffer_size=131072
max_used_connections=20
max_connections=100
threads_connected=12
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8964d48
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...
Cannot determine thread, fp=0xbfddec78, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x808b7a3
0x82e0a48
0x80c1baf
0x80bf91e
0x80bc1d1
0x80be77f
0x80bb916
0x809b78a
0x809fdef
0x809a2ce
0x8099c98
0x8099367
0x82de1fc
0x8307b8a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/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 0x8a16bb0 = select * from bcategorylist where parent=1
thd->thread_id=58
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.
--- clip ---
The query that is reported in the crash varies, and is actually never a
query to any of the image gallery applications but a high-traffic website
that uses the same MySQL database although the crash occurs immediately
after some operation is performed by the image gallery software.
resolve_stack_dump on the backtrace gives the following info:
--- clip ---
0x808b7a3 handle_segfault + 423
0x82e0a48 pthread_sighandler + 184
0x80c1baf get_best_combination__FP4JOIN + 163
0x80bf91e
make_join_statistics__FP4JOINP13st_table_listP4ItemP16st_dynamic_array +
4206
0x80bc1d1 optimize__4JOIN + 385
0x80be77f
mysql_select__FP3THDPPP4ItemP13st_table_listUiRt4List1Z4ItemP4ItemUiP8st_ord
erT7T5T7UlP13select_resultP18st_select_lex_unitP13s + 711
0x80bb916 handle_select__FP3THDP6st_lexP13select_result + 150
0x809b78a mysql_execute_command__FP3THD + 1414
0x809fdef mysql_parse__FP3THDPcUi + 207
0x809a2ce dispatch_command__F19enum_server_commandP3THDPcUi + 1578
0x8099c98 do_command__FP3THD + 188
0x8099367 handle_one_connection + 615
0x82de1fc pthread_start_thread + 220
0x8307b8a thread_start + 4
--- clip ---
My first instinct was that MySQL was running out of memory but decreasing
the memory used by MySQL did not help and the crashes continued.
I have ran myisamcheck on the tables and it seems to complain about some of
the tables not being closed, but can this be the source of the problem?
Any tips, pointers, rtfms are appreciated.
Tuomas Rinta
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
