MySQL Forums
Forum List  »  InnoDB

service crashed while executing UDF
Posted by: Erika Samantaray
Date: July 22, 2014 01:06AM

Every time one of the UDF functionality is been executed , mysql crash with the follwing the error log
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=151
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 = 68245 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x355dc60
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 = 7f720e6f1e18 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8d63f5]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x663094]
/lib64/libpthread.so.0[0x3d8420f500]
/lib64/libc.so.6[0x3d83e779dd]
/usr/sbin/mysqld(free_root+0x117)[0x8cd727]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x7b2)[0x669a22]
/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x6d7)[0x66aee7]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0xcaa)[0x6de8ca]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x32f)[0x6e2b3f]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x140b)[0x6e403b]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xcf)[0x6b0f4f]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6b1077]
/usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xafc0ca]
/lib64/libpthread.so.0[0x3d84207851]
/lib64/libc.so.6(clone+0x6d)[0x3d83ee767d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7208006c90): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
140722 12:26:35 mysqld_safe Number of processes running now: 0
140722 12:26:35 mysqld_safe mysqld restarted
2014-07-22 12:26:35 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-07-22 12:26:35 14424 [Note] Plugin 'FEDERATED' is disabled.
2014-07-22 12:26:35 14424 [Note] InnoDB: Started in read only mode
2014-07-22 12:26:35 14424 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-22 12:26:35 14424 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-22 12:26:35 14424 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-07-22 12:26:35 14424 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-22 12:26:35 14424 [Note] InnoDB: Using Linux native AIO
2014-07-22 12:26:35 14424 [Note] InnoDB: Using CPU crc32 instructions
2014-07-22 12:26:35 14424 [Note] InnoDB: Disabling background IO write threads.
2014-07-22 12:26:35 14424 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-07-22 12:26:35 14424 [Note] InnoDB: Completed initialization of buffer pool
2014-07-22 12:26:35 14424 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-22 12:26:35 14424 [Note] InnoDB: 5.6.17 started; log sequence number 2710964
2014-07-22 12:26:35 14424 [Note] InnoDB: !!! innodb_force_recovery is set to 4 !!!
2014-07-22 12:26:35 14424 [Note] Server hostname (bind-address): '*'; port: 3306
2014-07-22 12:26:35 14424 [Note] IPv6 is available.
2014-07-22 12:26:35 14424 [Note] - '::' resolves to '::';
2014-07-22 12:26:35 14424 [Note] Server socket created on IP: '::'.
2014-07-22 12:26:35 14424 [Note] Event Scheduler: Loaded 2 events
2014-07-22 12:26:35 14424 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.17' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)

I have tried restarting the service with proper backup but no changes have been found.

Options: ReplyQuote


Subject
Views
Written By
Posted
service crashed while executing UDF
1727
July 22, 2014 01:06AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.