From: Date: July 2 2009 6:54pm
Subject: FW: 5.1.30 crashes (sig 11)
List-Archive: http://lists.mysql.com/internals/37068
Message-Id: <82624B02DA0A3C4691069A83007F651D03C2FD2F@SNV-EXVS08.ds.corp.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable



=20
Rick James
MySQL Geeks - Consulting & Review

=20
> I've received two of these mysqld crashes on two different servers =20
> (within about 14 hours) in our new 5.1.30 production domain:
>=20
> 090604 20:30:39 - mysqld got signal 11 ;
> This could be because you hit a bug. It is also possible that this =20
> binary
> or one of the libraries it was linked against is corrupt, improperly =20
> built,
> or misconfigured. This error can also be caused by malfunctioning =20
> hardware.
> We will try our best to scrape up some info that will hopefully help =20
> diagnose
> the problem, but since we have already crashed, something is =20
> definitely wrong
> and this may fail.
>=20
> key_buffer_size=3D2097152000
> read_buffer_size=3D131072
> max_used_connections=3D6
> max_threads=3D600
> threads_connected=3D2
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size +=20
> sort_buffer_size)*max_threads =3D =20
> 41452503 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
>=20
> thd: 0x7e26210
> Attempting backtrace. You can use the following information=20
> to find out
> where mysqld died. If you see no messages after this, something went
> terribly wrong...
> stack_bottom =3D 0x45250138 thread_stack 0x40000
> /home/y/libexec64/mysqld(my_print_stacktrace+0x26) [0x9c33c6]
> /home/y/libexec64/mysqld(handle_segfault+0x253) [0x62dd63]
> /lib64/tls/libpthread.so.0 [0x313320c5b0]
> /lib64/tls/libc.so.6(strlen+0x30) [0x3132570be0]
> /home/y/libexec64/mysqld(strdup_root+0x33) [0x9b14c3]
> /home/y/libexec64/mysqld(Query_arena::strdup(char const*)+0x21) =20
> [0x57ff9f]
> /home/y/libexec64/mysqld(mysqld_list_processes(THD*, char=20
> const*, bool)=20
> +0x535) [0x761247]
> /home/y/libexec64/mysqld(mysql_execute_command(THD*)+0x2909)=20
> [0x63d439]
> /home/y/libexec64/mysqld(mysql_parse(THD*, char const*,=20
> unsigned int, =20
> char const**)+0x17f) [0x6430ab]
> /home/y/libexec64/mysqld(dispatch_command(enum_server_command, THD*, =20
> char*, unsigned int)+0x90d) [0x639669]
> /home/y/libexec64/mysqld(do_command(THD*)+0x13c) [0x638bd4]
> /home/y/libexec64/mysqld(handle_one_connection+0x128) [0x63767e]
> /lib64/tls/libpthread.so.0 [0x3133206137]
> /lib64/tls/libc.so.6(__clone+0x73) [0x31325c9883]
> Trying to get some variables.
> Some pointers may be invalid and cause the dump to abort...
> thd->query at 0x2bdff02940 is an invalid pointer
> thd->thread_id=3D678342
> thd->killed=3DNOT_KILLED
> The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html =20
> contains
> information that should help you find out what is causing the crash.
>=20
> Any idea what might be going on?  Looks like it might be occurring =20
> during simultaneous invocations of SHOW PROCESSLIST.
>=20
> --Michael
>=20
>=20