MySQL Forums
Forum List  »  General

MYSQLD Got SIGNAL 11
Posted by: Lance Lugo
Date: January 20, 2016 11:31AM

Good day, I am going to post some of the output from my mysql log that was generated after we received an error MySQLD Got SIGNAL 11, the engine died and restarted shortly after.

2016-01-19 16:09:11 4111 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: update PATIENT set ACTIVE=1, ADDRESS1='934 Garden Walk Blvd', ADDRESS2='316', ADMISSION_DATE=null, ADMISSION_ID=null, CALL_STATUS=null, CALLED_BY=null, CALLED_DATE=null, CALLED_TIME=null, CITY='College Park', CLINICAL_RESEARCH=null, CONTACT_METHOD='', CREATED_BY='elishad', CREATED_DATE='2016-01-19 13:48:37', DATE_OF_BIRTH='1951-03-13', DECEASED=null, DIABETICS=null, DIALYSIS=null, DISCHARGE_DATE=null, DISCHARGE_FROM_PRACTISE=null, DOC_RECEIVED_DATE=null, DOC_RECEIVED_ENT_BY=null, DON_NOT_CALL=null, EMAIL_ADDRESS='conniebradford612@gmail.com', EMER_CONTACT_NAME='', EMER_PRIM_PHON_NO='', EMER_SEC_PHON_NO='', ETHNICITY=null, EXTRA_CUST_CA
2016-01-19 16:09:11 4111 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly. Statement: update VISIT_CHECKIN set ADHOC_VISIT=null, appointment_id=3327297, appointment_time='1970-01-01 15:10:00', APPT_COMMENTS='', DOC_SPECIALITY='OV', bin_time='1970-01-01 14:54:00', CHECK_OUT_TIME=null, checked_in_by_userid='marye', checked_in_by_username='Escalona Mary', COMMENTS='', consultation_end_time='2016-01-19 16:04:45.937', consultation_start_time='1970-01-01 15:48:21', IS_DELETED=0, discharge_ma=null, DISCHARGE_MA_CODE=null, doctor_code='DC1', doctor_id=71, DRUG_HISTORY_VIEWED=null, ELIGIB_STATUS=null, first_visit=0, HIGH_RISK=1, insurance_code='HG', insurance_id=1110, MEDICAL_ASST_CODE='mh', MA_ROOM_IN_TIME=null, medical_assistant=130, OFFICE_ID=10022, offsite_visit=null, patient_daily_no=105, PAT_FULL_NAME='Dupiton, Frantz', PATIENT_ID=8
2016-01-19 16:09:12 4111 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly. Statement: update VISIT_CHECKIN set ADHOC_VISIT=null, appointment_id=3377543, appointment_time='1970-01-01 15:30:00', APPT_COMMENTS='', DOC_SPECIALITY='PODIA', bin_time='1970-01-01 15:00:00', CHECK_OUT_TIME=null, checked_in_by_userid='CarmenS', checked_in_by_username='Stacel Carmen', COMMENTS='', consultation_end_time='1970-01-01 16:03:15', consultation_start_time='1970-01-01 15:57:28', IS_DELETED=0, discharge_ma=3077, DISCHARGE_MA_CODE='OC', doctor_code='MF', doctor_id=124549, DRUG_HISTORY_VIEWED=null, ELIGIB_STATUS=4, first_visit=0, HIGH_RISK=1, insurance_code='VM', insurance_id=427, MEDICAL_ASST_CODE='lmcm', MA_ROOM_IN_TIME='1970-01-01 16:05:10', medical_assistant=1015, OFFICE_ID=10002, offsite_visit=null, patient_daily_no=105, PAT_FULL_NAME='Mijares, T
21:09:13 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=33554432
read_buffer_size=131072
max_used_connections=901
max_threads=900
thread_count=504
connection_count=504
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 29651360 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x152bb240
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 = 7f158975ce18 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8fef65]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x691bd4]
/lib64/libpthread.so.0[0x37fd00f710]
/lib64/libc.so.6[0x37fcd34a3c]
/usr/sbin/mysqld(_Z15get_digest_textPcP18PSI_digest_storage+0x2d3)[0xab7a53]
/usr/sbin/mysqld(_ZN30table_events_statements_common8make_rowEP21PFS_events_statements+0x390)[0xacd090]
/usr/sbin/mysqld(_ZN31table_events_statements_current8rnd_nextEv+0x97)[0xacd547]
/usr/sbin/mysqld(_ZN13ha_perfschema8rnd_nextEPh+0x4f)[0xab5cdf]
/usr/sbin/mysqld(_ZN7handler11ha_rnd_nextEPh+0x9c)[0x5d495c]
/usr/sbin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x1e)[0x83ad2e]
/usr/sbin/mysqld(_ZN14JOIN_CACHE_BNL21join_matching_recordsEb+0xbd)[0x85280d]
/usr/sbin/mysqld(_ZN10JOIN_CACHE12join_recordsEb+0x1a1)[0x851471]
/usr/sbin/mysqld(_ZN10JOIN_CACHE12join_recordsEb+0x1dc)[0x8514ac]
/usr/sbin/mysqld(_ZN10JOIN_CACHE12join_recordsEb+0x1dc)[0x8514ac]
/usr/sbin/mysqld(_Z13sub_select_opP4JOINP13st_join_tableb+0x40)[0x6ec590]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x2c2)[0x6ecb22]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x250)[0x72d2c0]
/usr/sbin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x187)[0x72db37]
/usr/sbin/mysqld[0x709f1d]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0xb46)[0x70be76]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x32f)[0x71014f]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xe14)[0x711054]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xcf)[0x6debef]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6ded17]
/usr/sbin/mysqld(pfs_spawn_thread+0x139)[0xadfc29]
/lib64/libpthread.so.0[0x37fd0079d1]
/lib64/libc.so.6(clone+0x6d)[0x37fcce88fd]

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

The query above appeared to be the last piece that was picked up before it took a dump: any insights as to what the stack trace is calling?
I tried to find any information in the INNODB ENGINE status call from CLI, but we don't have the start up params set to allow for larger than 64K to be returned, so I don't see anything other than what is provided here in the logs. There were no hardware related issues from a memory/disk perspective either. Business as usual from SQL wait times and executions, so it appears that something in this queries caused the exception. anything would be great

Options: ReplyQuote


Subject
Written By
Posted
MYSQLD Got SIGNAL 11
January 20, 2016 11:31AM
January 20, 2016 02:21PM
January 21, 2016 10:51AM


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.