When i tried to import Product mysql crash on step 7
In mysql log i got this
15:23:33 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=9437184000
read_buffer_size=131072
max_used_connections=2
max_threads=500
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 9414679 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f0564000b30
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...
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7cf8011a80): INSERT INTO tmp_pimgento_entities_product (sku, _entity_id, description_es-en_US) SELECT p.sku, p._entity_id AS entity_id, GROUP_CONCAT(c1.entity_id SEPARATOR ",") AS description_es-en_US FROM tmp_pimgento_entities_product AS p INNER JOIN (SELECT SUBSTRING(c.code,16) AS code, c.entity_id FROM pimgento_entities AS c WHERE (c.code like 'descriptiones%' ) AND (c.import = 'option')) AS c1 ON IF ( locate(',', description_es-en_US) > 0 , p.description_es-en_US like CONCAT('%', c1.code, '%'), p.description_es-en_US = c1.code ) GROUP BY p.sku ON DUPLICATE KEY UPDATE sku = VALUES(sku), _entity_id = VALUES(_entity_id), description_es-en_US = VALUES(description_es-en_US)
Connection ID (thread ID): 24
Status: NOT_KILLED
I try to increase key_buffer_size but it didn't work
When i tried to import Product mysql crash on step 7
In mysql log i got this
15:23:33 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail.
key_buffer_size=9437184000 read_buffer_size=131072 max_used_connections=2 max_threads=500 thread_count=2 connection_count=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 9414679 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f0564000b30 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 = 7f7d3c0d7e80 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x5569a57f615c] /usr/sbin/mysqld(handle_fatal_signal+0x479)[0x5569a5127029] /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f7f8ad130c0] /usr/sbin/mysqld(_ZN10Field_blob15copy_blob_valueEP11st_mem_root+0x25)[0x5569a5154fe5] /usr/sbin/mysqld(_Z25mysql_prepare_blob_valuesP3THDR4ListI4ItemEP11st_mem_root+0x370)[0x5569a57396d0] /usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP9COPYINFOS4+0x9b2)[0x5569a573bca2] /usr/sbin/mysqld(_ZN19Query_result_insert9send_dataER4ListI4ItemE+0xb3)[0x5569a573d023] /usr/sbin/mysqld(_Z14end_send_groupP4JOINP7QEP_TABb+0x418)[0x5569a559cba8] /usr/sbin/mysqld(+0xab97ea)[0x5569a55987ea] /usr/sbin/mysqld(_ZN13QEP_tmp_table8end_sendEv+0x10c)[0x5569a559dadc] /usr/sbin/mysqld(_Z13sub_select_opP4JOINP7QEP_TABb+0x35)[0x5569a559e1e5] /usr/sbin/mysqld(_ZN4JOIN4execEv+0x388)[0x5569a5596b48] /usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x233)[0x5569a5604e13] /usr/sbin/mysqld(_ZN21Sql_cmd_insert_select7executeEP3THD+0x399)[0x5569a573ac59] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x1ac1)[0x5569a55c6861] /usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3dd)[0x5569a55cbced] /usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xfe9)[0x5569a55ccd29] /usr/sbin/mysqld(_Z10do_commandP3THD+0x197)[0x5569a55ce107] /usr/sbin/mysqld(handle_connection+0x270)[0x5569a56884e0] /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x5569a5b5b0d4] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7f7f8ad09494] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f7f89555aff]
Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f7cf8011a80): INSERT INTO
tmp_pimgento_entities_product
(sku
,_entity_id
,description_es-en_US
) SELECTp
.sku
,p
._entity_id
ASentity_id
, GROUP_CONCAT(c1
.entity_id
SEPARATOR ",") ASdescription_es-en_US
FROMtmp_pimgento_entities_product
ASp
INNER JOIN (SELECT SUBSTRING(c
.code
,16) AScode
,c
.entity_id
FROMpimgento_entities
ASc
WHERE (c.code like 'descriptiones%' ) AND (c.import = 'option')) ASc1
ON IF ( locate(',',description_es-en_US
) > 0 ,p
.description_es-en_US
like CONCAT('%',c1
.code
, '%'),p
.description_es-en_US
=c1
.code
) GROUP BYp
.sku
ON DUPLICATE KEY UPDATEsku
= VALUES(sku
),_entity_id
= VALUES(_entity_id
),description_es-en_US
= VALUES(description_es-en_US
) Connection ID (thread ID): 24 Status: NOT_KILLEDI try to increase key_buffer_size but it didn't work
Mysql config : [mysqld] pid-file = /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock datadir = /var/lib/mysql log-error = /var/log/mysql/error.log
Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0 local_infile=1 max_connections = 500 secure_file_priv="" sql_mode = NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES key_buffer_size=9000M query_cache_size=32M
Can anyone know how to fix this ?