Valerii,

This server is a slave and does not have any direct queries (or should
not).  What would be the best means to track down what was running just
prior the crash?

Thanks



On Fri, Jun 7, 2013 at 3:38 AM, Valerii Kravchuk <
<email address hidden>> wrote:

> Are you able to identify crashing statement? I wonder if it accesses any
> tables in the INFORMATION_SCHEMA.
>
> ** Changed in: percona-server
>        Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1188447
>
> Title:
>   mysqld crash
>
> Status in Percona Server with XtraDB:
>   Incomplete
>
> Bug description:
>   mysqld  Ver 5.5.31-30.3-log for Linux on x86_64 (Percona Server (GPL),
>   Release rel30.3, Revision 520)
>
>   uname -a
>   Linux db02.domain.com 3.4.37-40.44.amzn1.x86_64 #1 SMP Thu Mar 21
> 01:17:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
>   Here is the detail from error.log
>
>   02:05:02 UTC - 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.
>   Please help us make Percona Server better by reporting any
>   bugs at http://bugs.percona.com/
>
>   key_buffer_size=524288000
>   read_buffer_size=2097152
>   max_used_connections=4
>   max_threads=353
>   thread_count=1
>   connection_count=1
>   It is possible that mysqld could use up to
>   key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
> 1962208 K  bytes of memory
>   Hope that's ok; if not, decrease some variables in the equation.
>
>   Thread pointer: 0x13f887a0
>   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 = 7f905e992da8 thread_stack 0x40000
>   /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7b4965]
>   /usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x68f704]
>   /lib64/libpthread.so.0(+0xf8e0)[0x7f905e6c08e0]
>   /usr/sbin/mysqld[0x7e0774]
>   /usr/sbin/mysqld[0x5d0854]
>   /usr/sbin/mysqld[0x5e1a4b]
>
> /usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x25e)[0x5cff6e]
>   /usr/sbin/mysqld(_ZN4JOIN4execEv+0x4dd)[0x5caa4d]
>
> /usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x12c)[0x5cc95c]
>
> /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1cd)[0x5cd40d]
>   /usr/sbin/mysqld[0x5895d2]
>   /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1553)[0x58e2d3]
>   /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x33b)[0x591adb]
>
> /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x163d)[0x5931bd]
>   /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x13f)[0x62e4cf]
>   /usr/sbin/mysqld(handle_one_connection+0x51)[0x62e5b1]
>   /lib64/libpthread.so.0(+0x7c6b)[0x7f905e6b8c6b]
>   /lib64/libc.so.6(clone+0x6d)[0x7f905d3175ed]
>
>   Trying to get some variables.
>   Some pointers may be invalid and cause the dump to abort.
>   Query (7f8d480009a0): is an invalid pointer
>   Connection ID (thread ID): 67752
>   Status: NOT_KILLED
>
>   You may download the Percona Server operations manual by visiting
>   http://www.percona.com/software/percona-server/. You may find
> information
>   in the manual which will help you identify the cause of the crash.
>   130607 02:05:04 mysqld_safe Number of processes running now: 0
>   130607 02:05:04 mysqld_safe mysqld restarted
>   130607  2:05:04 [Note] Plugin 'FEDERATED' is disabled.
>   130607  2:05:04 [Warning] option 'innodb-autoextend-increment': unsigned
> value 262144 adjusted to 1000
>   130607  2:05:04 InnoDB: The InnoDB memory heap is disabled
>   130607  2:05:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
>   130607  2:05:04 InnoDB: Compressed tables use zlib 1.2.3
>   130607  2:05:04 InnoDB: Using Linux native AIO
>   130607  2:05:04 InnoDB: Initializing buffer pool, size = 10.0G
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-server/+bug/1188447/+subscriptions
>



-- 

*Philip Kubat*
*VP Technology,* Ziftr.com <http://www.ziftr.com>
Phone: (603) 575-9003 x 714