MySQL Forums
Forum List  »  InnoDB

UTC - mysqld got signal 11
Posted by: Ajay Gupta
Date: October 31, 2017 04:55AM

I am getting below error in a month at fix time,I m new to mysql.
This is a Mysql cluster and error is at SQL node.

Mysql version = 5.6.37-ndb-7.4.16-cluster-gpl-log MySQL Cluster Community Server (GPL)

Please let me know any other info required.

2017-10-24 22:20:02 23763 [ERROR] NDB: Query 'DELETE FROM mysql.ndb_binlog_index WHERE File='/var/lib/mysql/binlogs/mysql-bin.005818'' failed, error: 1205: Lock wait timeout exceeded; try restarting transaction
2017-10-24 22:25:02 23763 [ERROR] NDB: Query 'DELETE FROM mysql.ndb_binlog_index WHERE File='/var/lib/mysql/binlogs/mysql-bin.005819'' failed, error: 1205: Lock wait timeout exceeded; try restarting transaction
2017-10-24 22:30:02 23763 [ERROR] NDB: Query 'DELETE FROM mysql.ndb_binlog_index WHERE File='/var/lib/mysql/binlogs/mysql-bin.005820'' failed, error: 1205: Lock wait timeout exceeded; try restarting transaction
2017-10-24 22:35:02 23763 [ERROR] NDB: Query 'DELETE FROM mysql.ndb_binlog_index WHERE File='/var/lib/mysql/binlogs/mysql-bin.005821'' failed, error: 1205: Lock wait timeout exceeded; try restarting transaction
2017-10-24 22:40:02 23763 [ERROR] NDB: Query 'DELETE FROM mysql.ndb_binlog_index WHERE File='/var/lib/mysql/binlogs/mysql-bin.005822'' failed, error: 1205: Lock wait timeout exceeded; try restarting transaction
2017-10-24 22:45:02 23763 [ERROR] NDB: Query 'DELETE FROM mysql.ndb_binlog_index WHERE File='/var/lib/mysql/binlogs/mysql-bin.005823'' failed, error: 1205: Lock wait timeout exceeded; try restarting transaction
20:45: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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=34
max_threads=151
thread_count=17
connection_count=16
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68108 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f18800009b0
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 = 7f18b4d59910 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x963a2b]
/usr/sbin/mysqld(handle_fatal_signal+0x491)[0x6efd01]
/lib64/libpthread.so.0(+0xf370)[0x7f18de022370]
/lib64/libc.so.6(+0x86b71)[0x7f18dcc6fb71]
/usr/sbin/mysqld[0xbc0748]
/usr/sbin/mysqld(_ZN17Ndb_binlog_thread6do_runEv+0x364c)[0xbc8f5c]
/usr/sbin/mysqld(_ZN13Ndb_component8run_implEv+0x74)[0xbde474]
/usr/sbin/mysqld(Ndb_component_run_C+0x19)[0xbde499]
/lib64/libpthread.so.0(+0x7dc5)[0x7f18de01adc5]
/lib64/libc.so.6(clone+0x6d)[0x7f18dcce076d]

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

Thanks,
Ajay Gupta

Options: ReplyQuote


Subject
Views
Written By
Posted
UTC - mysqld got signal 11
90
October 31, 2017 04:55AM


Sorry, only registered users may post in this forum.

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.