Mea Culpa, Mea Culpa, Mea Maxima Culpa!
My fault, my fault, it’s all my fault! Why? Well because new versions = new bugs :) = wait till they are fixed, then use it!
As an ubuntu fan I just had to install 10.10 GA … and as a MySQL DBA I can’t run apt-get install mysql …. not even in my nightmares can I do that. Why? Well because if you are a car mechanic you don’t take your car for repairs to another mechanic and not ask what was done on it do you? You do it yourself right? That is what I did, I installed mysql 5.1.50, the same binaries I had downloaded and used on my 10.04 machine and loaded a dump. Woops, mysql crashed big time. I figured, lets install 5.1.51, load and … boom, again crashed.
The same dump, is loading fine on my 10.04 ubuntu server running both 5.1.50 and 5.1.51.
101018 12:48:26 - 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=8384512
read_buffer_size=131072
max_used_connections=6
max_threads=151
threads_connected=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337737 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0xa364a88
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_bottom = 0xb4162388 thread_stack 0x30000
/mysql/sandboxes/5.1.51/bin/mysqld(my_print_stacktrace+0x21)[0x84e5271]
/mysql/sandboxes/5.1.51/bin/mysqld(handle_segfault+0x381)[0x8206e71]
[0xb7785400]
/mysql/sandboxes/5.1.51/bin/mysqld(_Z23well_formed_copy_ncharsP15charset_info_stPcjS0_PKcjjPS3_S4_S4_+0x44)[0x8200a64]
/mysql/sandboxes/5.1.51/bin/mysqld(_ZN15Field_varstring5storeEPKcjP15charset_info_st+0x64)[0x81e0324]
/mysql/sandboxes/5.1.51/bin/mysqld(_ZN11Item_string13save_in_fieldEP5Fieldb+0x50)[0x8155f50]
/mysql/sandboxes/5.1.51/bin/mysqld(_Z36fill_record_n_invoke_before_triggersP3THDPP5FieldR4ListI4ItemEbP19Table_triggers_list14trg_event_type+0x4d)[0x825100d]
/mysql/sandboxes/5.1.51/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1089)[0x828da79]
/mysql/sandboxes/5.1.51/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1b37)[0x8218927]
/mysql/sandboxes/5.1.51/bin/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x3c4)[0x821e8c4]
/mysql/sandboxes/5.1.51/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x694)[0x821ef64]
/mysql/sandboxes/5.1.51/bin/mysqld(_Z10do_commandP3THD+0xe0)[0x8220480]
/mysql/sandboxes/5.1.51/bin/mysqld(handle_one_connection+0x253)[0x82109f3]
/lib/libpthread.so.0(+0x5cc9)[0xb7760cc9]
/lib/libc.so.6(clone+0x5e)[0xb76596ae]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
I have done several small things like creating databases, users, tables, stored proceudres etc, but on loading big chunks of data the above happens.
Anybody had the same problem on 10.10 by any chance? I don’t have time to test stuff out to be honest, but would appreciate your feedback on this.
Because Sharing is Caring
PlanetMySQL Voting: Vote UP / Vote DOWN