Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.5, 10.2.6
-
linux, x86-64
Description
MariaDB 10.2.5 is constantly crashing.
with the message
2017-05-19 13:33:00 0x7f97f67fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.5/storage/innobase/handler/ha_innodb.cc line 2780 |
InnoDB: Failing assertion: block > 0
|
InnoDB: We intentionally generate a memory trap. |
InnoDB: Submit a detailed bug report to http://bugs.mysql.com. |
InnoDB: If you get repeated assertion failures or crashes, even
|
InnoDB: immediately after the mysqld startup, there may be
|
InnoDB: corruption in the InnoDB tablespace. Please refer to |
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html |
InnoDB: about forcing recovery.
|
170519 13:33:00 [ERROR] mysqld got signal 6 ;
|
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.
|
|
To report this bug, see https://mariadb.com/kb/en/reporting-bugs |
|
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.
|
|
Server version: 10.2.5-MariaDB-10.2.5+maria~jessie
|
key_buffer_size=134217728
|
read_buffer_size=2097152
|
max_used_connections=2
|
max_threads=102
|
thread_count=9
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759886 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation. |
|
Thread pointer: 0x7f97880008c8
|
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 = 0x7f97f67fde38 thread_stack 0x49000
|
mysqld(my_print_stacktrace+0x2e)[0x55dafb3c9d4e]
|
mysqld(handle_fatal_signal+0x305)[0x55dafae10205]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f981c996890] |
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f981acbe067] |
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f981acbf448] |
mysqld(+0x4178b2)[0x55dafabb68b2]
|
mysqld(+0x7f08b8)[0x55dafaf8f8b8]
|
mysqld(+0x808879)[0x55dafafa7879]
|
mysqld(_ZN7handler21update_auto_incrementEv+0x2dd)[0x55dafae1637d]
|
mysqld(+0x807699)[0x55dafafa6699]
|
mysqld(_ZN7handler12ha_write_rowEPh+0x1af)[0x55dafae1a62f]
|
mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6f)[0x55dafac4fc6f]
|
mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1234)[0x55dafac58e84]
|
mysqld(_Z21mysql_execute_commandP3THD+0x2372)[0x55dafac6d962]
|
mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x28a)[0x55dafac735ca]
|
mysqld(+0x4d4d87)[0x55dafac73d87]
|
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xfdd)[0x55dafac752bd]
|
mysqld(_Z10do_commandP3THD+0x164)[0x55dafac76874]
|
mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x55dafad48a62]
|
mysqld(handle_one_connection+0x3d)[0x55dafad48bfd]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f981c98f064] |
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f981ad7162d] |
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x7f978800eed0): INSERT INTO `user` ( id, `first_name`,`last_name`,`email`,`password`,`token`,`who_id` ) VALUES ( NULL, 'John','Doe','john.doe@vblpso.click','64d09d9930c8ecf79e513167a588cb75439b762ce8f9b22ea59765f32aa74ca19d2f1e97dc922a3d4954594a05062917fb24d1f8e72f2ed02a58ed7534f94d27',NULL,1 ) |
Connection ID (thread ID): 65
|
Status: NOT_KILLED
|
|
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
|
|
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. |
Running from Dockerfile:
FROM vonbraunlabs/mariadb:10.2
|
|
RUN apt-get update -y
|
RUN apt-get install -y \
|
dnsutils \
|
file \
|
htop \
|
procps \
|
psmisc \
|
redis-tools \
|
sudo \
|
vim
|
|
|
USER mysql
|
COPY galera.cnf /etc/mysql/conf.d/galera.cnf
|
WORKDIR /opt
|
|
COPY start.sh ./
|
COPY recreateall.sql /docker-entrypoint-initdb.d/
|
|
EXPOSE 3306 4444 4567 4567/udp 4568
|
|
USER root
|
|
ENTRYPOINT ["./start.sh"]
|
The galera.cnf have the content:
[galera]
|
# Mandatory settings
|
wsrep_on=ON
|
wsrep_provider=/usr/lib/galera/libgalera_smm.so
|
wsrep_cluster_name=vblpso
|
wsrep_cluster_address=GCOMM
|
wsrep_sst_method=rsync
|
binlog_format=row
|
default_storage_engine=InnoDB
|
innodb_autoinc_lock_mode=2
|
|
wsrep_node_address=NODEADDRESS
|
#
|
# Allow server to accept connections on all interfaces.
|
#
|
bind-address=0.0.0.0
|
Attachments
Issue Links
- relates to
-
MDEV-6076 Persistent AUTO_INCREMENT for InnoDB
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Description |
MariaDB 10.2.5 is constantly crashing.
with the message {{2017-05-19 13:33:00 0x7f97f67fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.5/storage/innobase/handler/ha_innodb.cc line 2780 InnoDB: Failing assertion: block > 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170519 13:33:00 [ERROR] mysqld got signal 6 ; 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. To report this bug, see https://mariadb.com/kb/en/reporting-bugs 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. Server version: 10.2.5-MariaDB-10.2.5+maria~jessie key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=2 max_threads=102 thread_count=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759886 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f97880008c8 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 = 0x7f97f67fde38 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55dafb3c9d4e] mysqld(handle_fatal_signal+0x305)[0x55dafae10205] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f981c996890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f981acbe067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f981acbf448] mysqld(+0x4178b2)[0x55dafabb68b2] mysqld(+0x7f08b8)[0x55dafaf8f8b8] mysqld(+0x808879)[0x55dafafa7879] mysqld(_ZN7handler21update_auto_incrementEv+0x2dd)[0x55dafae1637d] mysqld(+0x807699)[0x55dafafa6699] mysqld(_ZN7handler12ha_write_rowEPh+0x1af)[0x55dafae1a62f] mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6f)[0x55dafac4fc6f] mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1234)[0x55dafac58e84] mysqld(_Z21mysql_execute_commandP3THD+0x2372)[0x55dafac6d962] mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x28a)[0x55dafac735ca] mysqld(+0x4d4d87)[0x55dafac73d87] mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xfdd)[0x55dafac752bd] mysqld(_Z10do_commandP3THD+0x164)[0x55dafac76874] mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x55dafad48a62] mysqld(handle_one_connection+0x3d)[0x55dafad48bfd] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f981c98f064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f981ad7162d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f978800eed0): INSERT INTO `user` ( id, `first_name`,`last_name`,`email`,`password`,`token`,`who_id` ) VALUES ( NULL, 'John','Doe','john.doe@vblpso.click','64d09d9930c8ecf79e513167a588cb75439b762ce8f9b22ea59765f32aa74ca19d2f1e97dc922a3d4954594a05062917fb24d1f8e72f2ed02a58ed7534f94d27',NULL,1 ) Connection ID (thread ID): 65 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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.}} Running from Dockerfile: {{ FROM vonbraunlabs/mariadb:10.2 RUN apt-get update -y RUN apt-get install -y \ dnsutils \ file \ htop \ procps \ psmisc \ redis-tools \ sudo \ vim USER mysql COPY galera.cnf /etc/mysql/conf.d/galera.cnf WORKDIR /opt COPY start.sh ./ COPY recreateall.sql /docker-entrypoint-initdb.d/ EXPOSE 3306 4444 4567 4567/udp 4568 USER root ENTRYPOINT ["./start.sh"] }} The galera.cnf have the content: {{ [galera] # Mandatory settings wsrep_on=ON wsrep_provider=/usr/lib/galera/libgalera_smm.so wsrep_cluster_name=vblpso wsrep_cluster_address=GCOMM wsrep_sst_method=rsync binlog_format=row default_storage_engine=InnoDB innodb_autoinc_lock_mode=2 wsrep_node_address=NODEADDRESS # # Allow server to accept connections on all interfaces. # bind-address=0.0.0.0 }} |
MariaDB 10.2.5 is constantly crashing.
with the message {code:bash} 2017-05-19 13:33:00 0x7f97f67fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.5/storage/innobase/handler/ha_innodb.cc line 2780 InnoDB: Failing assertion: block > 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170519 13:33:00 [ERROR] mysqld got signal 6 ; 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. To report this bug, see https://mariadb.com/kb/en/reporting-bugs 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. Server version: 10.2.5-MariaDB-10.2.5+maria~jessie key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=2 max_threads=102 thread_count=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759886 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f97880008c8 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 = 0x7f97f67fde38 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55dafb3c9d4e] mysqld(handle_fatal_signal+0x305)[0x55dafae10205] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f981c996890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f981acbe067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f981acbf448] mysqld(+0x4178b2)[0x55dafabb68b2] mysqld(+0x7f08b8)[0x55dafaf8f8b8] mysqld(+0x808879)[0x55dafafa7879] mysqld(_ZN7handler21update_auto_incrementEv+0x2dd)[0x55dafae1637d] mysqld(+0x807699)[0x55dafafa6699] mysqld(_ZN7handler12ha_write_rowEPh+0x1af)[0x55dafae1a62f] mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6f)[0x55dafac4fc6f] mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1234)[0x55dafac58e84] mysqld(_Z21mysql_execute_commandP3THD+0x2372)[0x55dafac6d962] mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x28a)[0x55dafac735ca] mysqld(+0x4d4d87)[0x55dafac73d87] mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xfdd)[0x55dafac752bd] mysqld(_Z10do_commandP3THD+0x164)[0x55dafac76874] mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x55dafad48a62] mysqld(handle_one_connection+0x3d)[0x55dafad48bfd] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f981c98f064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f981ad7162d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f978800eed0): INSERT INTO `user` ( id, `first_name`,`last_name`,`email`,`password`,`token`,`who_id` ) VALUES ( NULL, 'John','Doe','john.doe@vblpso.click','64d09d9930c8ecf79e513167a588cb75439b762ce8f9b22ea59765f32aa74ca19d2f1e97dc922a3d4954594a05062917fb24d1f8e72f2ed02a58ed7534f94d27',NULL,1 ) Connection ID (thread ID): 65 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. {code} Running from Dockerfile: {{ FROM vonbraunlabs/mariadb:10.2 RUN apt-get update -y RUN apt-get install -y \ dnsutils \ file \ htop \ procps \ psmisc \ redis-tools \ sudo \ vim USER mysql COPY galera.cnf /etc/mysql/conf.d/galera.cnf WORKDIR /opt COPY start.sh ./ COPY recreateall.sql /docker-entrypoint-initdb.d/ EXPOSE 3306 4444 4567 4567/udp 4568 USER root ENTRYPOINT ["./start.sh"] }} The galera.cnf have the content: {{ [galera] # Mandatory settings wsrep_on=ON wsrep_provider=/usr/lib/galera/libgalera_smm.so wsrep_cluster_name=vblpso wsrep_cluster_address=GCOMM wsrep_sst_method=rsync binlog_format=row default_storage_engine=InnoDB innodb_autoinc_lock_mode=2 wsrep_node_address=NODEADDRESS # # Allow server to accept connections on all interfaces. # bind-address=0.0.0.0 }} |
Description |
MariaDB 10.2.5 is constantly crashing.
with the message {code:bash} 2017-05-19 13:33:00 0x7f97f67fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.5/storage/innobase/handler/ha_innodb.cc line 2780 InnoDB: Failing assertion: block > 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170519 13:33:00 [ERROR] mysqld got signal 6 ; 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. To report this bug, see https://mariadb.com/kb/en/reporting-bugs 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. Server version: 10.2.5-MariaDB-10.2.5+maria~jessie key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=2 max_threads=102 thread_count=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759886 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f97880008c8 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 = 0x7f97f67fde38 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55dafb3c9d4e] mysqld(handle_fatal_signal+0x305)[0x55dafae10205] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f981c996890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f981acbe067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f981acbf448] mysqld(+0x4178b2)[0x55dafabb68b2] mysqld(+0x7f08b8)[0x55dafaf8f8b8] mysqld(+0x808879)[0x55dafafa7879] mysqld(_ZN7handler21update_auto_incrementEv+0x2dd)[0x55dafae1637d] mysqld(+0x807699)[0x55dafafa6699] mysqld(_ZN7handler12ha_write_rowEPh+0x1af)[0x55dafae1a62f] mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6f)[0x55dafac4fc6f] mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1234)[0x55dafac58e84] mysqld(_Z21mysql_execute_commandP3THD+0x2372)[0x55dafac6d962] mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x28a)[0x55dafac735ca] mysqld(+0x4d4d87)[0x55dafac73d87] mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xfdd)[0x55dafac752bd] mysqld(_Z10do_commandP3THD+0x164)[0x55dafac76874] mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x55dafad48a62] mysqld(handle_one_connection+0x3d)[0x55dafad48bfd] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f981c98f064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f981ad7162d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f978800eed0): INSERT INTO `user` ( id, `first_name`,`last_name`,`email`,`password`,`token`,`who_id` ) VALUES ( NULL, 'John','Doe','john.doe@vblpso.click','64d09d9930c8ecf79e513167a588cb75439b762ce8f9b22ea59765f32aa74ca19d2f1e97dc922a3d4954594a05062917fb24d1f8e72f2ed02a58ed7534f94d27',NULL,1 ) Connection ID (thread ID): 65 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. {code} Running from Dockerfile: {{ FROM vonbraunlabs/mariadb:10.2 RUN apt-get update -y RUN apt-get install -y \ dnsutils \ file \ htop \ procps \ psmisc \ redis-tools \ sudo \ vim USER mysql COPY galera.cnf /etc/mysql/conf.d/galera.cnf WORKDIR /opt COPY start.sh ./ COPY recreateall.sql /docker-entrypoint-initdb.d/ EXPOSE 3306 4444 4567 4567/udp 4568 USER root ENTRYPOINT ["./start.sh"] }} The galera.cnf have the content: {{ [galera] # Mandatory settings wsrep_on=ON wsrep_provider=/usr/lib/galera/libgalera_smm.so wsrep_cluster_name=vblpso wsrep_cluster_address=GCOMM wsrep_sst_method=rsync binlog_format=row default_storage_engine=InnoDB innodb_autoinc_lock_mode=2 wsrep_node_address=NODEADDRESS # # Allow server to accept connections on all interfaces. # bind-address=0.0.0.0 }} |
MariaDB 10.2.5 is constantly crashing.
with the message {noformat} 2017-05-19 13:33:00 0x7f97f67fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.5/storage/innobase/handler/ha_innodb.cc line 2780 InnoDB: Failing assertion: block > 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170519 13:33:00 [ERROR] mysqld got signal 6 ; 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. To report this bug, see https://mariadb.com/kb/en/reporting-bugs 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. Server version: 10.2.5-MariaDB-10.2.5+maria~jessie key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=2 max_threads=102 thread_count=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759886 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f97880008c8 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 = 0x7f97f67fde38 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55dafb3c9d4e] mysqld(handle_fatal_signal+0x305)[0x55dafae10205] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f981c996890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f981acbe067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f981acbf448] mysqld(+0x4178b2)[0x55dafabb68b2] mysqld(+0x7f08b8)[0x55dafaf8f8b8] mysqld(+0x808879)[0x55dafafa7879] mysqld(_ZN7handler21update_auto_incrementEv+0x2dd)[0x55dafae1637d] mysqld(+0x807699)[0x55dafafa6699] mysqld(_ZN7handler12ha_write_rowEPh+0x1af)[0x55dafae1a62f] mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6f)[0x55dafac4fc6f] mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1234)[0x55dafac58e84] mysqld(_Z21mysql_execute_commandP3THD+0x2372)[0x55dafac6d962] mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x28a)[0x55dafac735ca] mysqld(+0x4d4d87)[0x55dafac73d87] mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xfdd)[0x55dafac752bd] mysqld(_Z10do_commandP3THD+0x164)[0x55dafac76874] mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x55dafad48a62] mysqld(handle_one_connection+0x3d)[0x55dafad48bfd] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f981c98f064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f981ad7162d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f978800eed0): INSERT INTO `user` ( id, `first_name`,`last_name`,`email`,`password`,`token`,`who_id` ) VALUES ( NULL, 'John','Doe','john.doe@vblpso.click','64d09d9930c8ecf79e513167a588cb75439b762ce8f9b22ea59765f32aa74ca19d2f1e97dc922a3d4954594a05062917fb24d1f8e72f2ed02a58ed7534f94d27',NULL,1 ) Connection ID (thread ID): 65 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. {noformat} Running from Dockerfile: {noformat} FROM vonbraunlabs/mariadb:10.2 RUN apt-get update -y RUN apt-get install -y \ dnsutils \ file \ htop \ procps \ psmisc \ redis-tools \ sudo \ vim USER mysql COPY galera.cnf /etc/mysql/conf.d/galera.cnf WORKDIR /opt COPY start.sh ./ COPY recreateall.sql /docker-entrypoint-initdb.d/ EXPOSE 3306 4444 4567 4567/udp 4568 USER root ENTRYPOINT ["./start.sh"] {noformat} The galera.cnf have the content: {noformat} [galera] # Mandatory settings wsrep_on=ON wsrep_provider=/usr/lib/galera/libgalera_smm.so wsrep_cluster_name=vblpso wsrep_cluster_address=GCOMM wsrep_sst_method=rsync binlog_format=row default_storage_engine=InnoDB innodb_autoinc_lock_mode=2 wsrep_node_address=NODEADDRESS # # Allow server to accept connections on all interfaces. # bind-address=0.0.0.0 {noformat} |
Description |
MariaDB 10.2.5 is constantly crashing.
with the message {noformat} 2017-05-19 13:33:00 0x7f97f67fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.5/storage/innobase/handler/ha_innodb.cc line 2780 InnoDB: Failing assertion: block > 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170519 13:33:00 [ERROR] mysqld got signal 6 ; 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. To report this bug, see https://mariadb.com/kb/en/reporting-bugs 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. Server version: 10.2.5-MariaDB-10.2.5+maria~jessie key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=2 max_threads=102 thread_count=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759886 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f97880008c8 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 = 0x7f97f67fde38 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55dafb3c9d4e] mysqld(handle_fatal_signal+0x305)[0x55dafae10205] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f981c996890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f981acbe067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f981acbf448] mysqld(+0x4178b2)[0x55dafabb68b2] mysqld(+0x7f08b8)[0x55dafaf8f8b8] mysqld(+0x808879)[0x55dafafa7879] mysqld(_ZN7handler21update_auto_incrementEv+0x2dd)[0x55dafae1637d] mysqld(+0x807699)[0x55dafafa6699] mysqld(_ZN7handler12ha_write_rowEPh+0x1af)[0x55dafae1a62f] mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6f)[0x55dafac4fc6f] mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1234)[0x55dafac58e84] mysqld(_Z21mysql_execute_commandP3THD+0x2372)[0x55dafac6d962] mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x28a)[0x55dafac735ca] mysqld(+0x4d4d87)[0x55dafac73d87] mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xfdd)[0x55dafac752bd] mysqld(_Z10do_commandP3THD+0x164)[0x55dafac76874] mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x55dafad48a62] mysqld(handle_one_connection+0x3d)[0x55dafad48bfd] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f981c98f064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f981ad7162d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f978800eed0): INSERT INTO `user` ( id, `first_name`,`last_name`,`email`,`password`,`token`,`who_id` ) VALUES ( NULL, 'John','Doe','john.doe@vblpso.click','64d09d9930c8ecf79e513167a588cb75439b762ce8f9b22ea59765f32aa74ca19d2f1e97dc922a3d4954594a05062917fb24d1f8e72f2ed02a58ed7534f94d27',NULL,1 ) Connection ID (thread ID): 65 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. {noformat} Running from Dockerfile: {noformat} FROM vonbraunlabs/mariadb:10.2 RUN apt-get update -y RUN apt-get install -y \ dnsutils \ file \ htop \ procps \ psmisc \ redis-tools \ sudo \ vim USER mysql COPY galera.cnf /etc/mysql/conf.d/galera.cnf WORKDIR /opt COPY start.sh ./ COPY recreateall.sql /docker-entrypoint-initdb.d/ EXPOSE 3306 4444 4567 4567/udp 4568 USER root ENTRYPOINT ["./start.sh"] {noformat} The galera.cnf have the content: {noformat} [galera] # Mandatory settings wsrep_on=ON wsrep_provider=/usr/lib/galera/libgalera_smm.so wsrep_cluster_name=vblpso wsrep_cluster_address=GCOMM wsrep_sst_method=rsync binlog_format=row default_storage_engine=InnoDB innodb_autoinc_lock_mode=2 wsrep_node_address=NODEADDRESS # # Allow server to accept connections on all interfaces. # bind-address=0.0.0.0 {noformat} |
MariaDB 10.2.5 is constantly crashing.
with the message {code:bash} 2017-05-19 13:33:00 0x7f97f67fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.5/storage/innobase/handler/ha_innodb.cc line 2780 InnoDB: Failing assertion: block > 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170519 13:33:00 [ERROR] mysqld got signal 6 ; 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. To report this bug, see https://mariadb.com/kb/en/reporting-bugs 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. Server version: 10.2.5-MariaDB-10.2.5+maria~jessie key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=2 max_threads=102 thread_count=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759886 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f97880008c8 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 = 0x7f97f67fde38 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55dafb3c9d4e] mysqld(handle_fatal_signal+0x305)[0x55dafae10205] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f981c996890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f981acbe067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f981acbf448] mysqld(+0x4178b2)[0x55dafabb68b2] mysqld(+0x7f08b8)[0x55dafaf8f8b8] mysqld(+0x808879)[0x55dafafa7879] mysqld(_ZN7handler21update_auto_incrementEv+0x2dd)[0x55dafae1637d] mysqld(+0x807699)[0x55dafafa6699] mysqld(_ZN7handler12ha_write_rowEPh+0x1af)[0x55dafae1a62f] mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6f)[0x55dafac4fc6f] mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1234)[0x55dafac58e84] mysqld(_Z21mysql_execute_commandP3THD+0x2372)[0x55dafac6d962] mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x28a)[0x55dafac735ca] mysqld(+0x4d4d87)[0x55dafac73d87] mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xfdd)[0x55dafac752bd] mysqld(_Z10do_commandP3THD+0x164)[0x55dafac76874] mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x55dafad48a62] mysqld(handle_one_connection+0x3d)[0x55dafad48bfd] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f981c98f064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f981ad7162d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f978800eed0): INSERT INTO `user` ( id, `first_name`,`last_name`,`email`,`password`,`token`,`who_id` ) VALUES ( NULL, 'John','Doe','john.doe@vblpso.click','64d09d9930c8ecf79e513167a588cb75439b762ce8f9b22ea59765f32aa74ca19d2f1e97dc922a3d4954594a05062917fb24d1f8e72f2ed02a58ed7534f94d27',NULL,1 ) Connection ID (thread ID): 65 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. {code} Running from Dockerfile: {code:Dockerfile} FROM vonbraunlabs/mariadb:10.2 RUN apt-get update -y RUN apt-get install -y \ dnsutils \ file \ htop \ procps \ psmisc \ redis-tools \ sudo \ vim USER mysql COPY galera.cnf /etc/mysql/conf.d/galera.cnf WORKDIR /opt COPY start.sh ./ COPY recreateall.sql /docker-entrypoint-initdb.d/ EXPOSE 3306 4444 4567 4567/udp 4568 USER root ENTRYPOINT ["./start.sh"] {code} The galera.cnf have the content: {code:cnf} [galera] # Mandatory settings wsrep_on=ON wsrep_provider=/usr/lib/galera/libgalera_smm.so wsrep_cluster_name=vblpso wsrep_cluster_address=GCOMM wsrep_sst_method=rsync binlog_format=row default_storage_engine=InnoDB innodb_autoinc_lock_mode=2 wsrep_node_address=NODEADDRESS # # Allow server to accept connections on all interfaces. # bind-address=0.0.0.0 {code} |
Fix Version/s | 10.2 [ 14601 ] | |
Assignee | Marko Mäkelä [ marko ] |
Affects Version/s | 10.2.6 [ 22527 ] |
Assignee | Marko Mäkelä [ marko ] | Jan Lindström [ jplindst ] |
Fix Version/s | 10.2.7 [ 22543 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 80855 ] | MariaDB v4 [ 152179 ] |
Problem is also affecting version 10.2.6+mariadb~jessie
2017-05-23 19:52:53 0x7f7865954700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.6/storage/innobase/handler/ha_innodb.cc line 2784
InnoDB: Failing assertion: block > 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
170523 19:52:53 [ERROR] mysqld got signal 6 ;
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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 10.2.6-MariaDB-10.2.6+maria~jessie
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=1
max_threads=102
thread_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759887 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f77f00008c8
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 = 0x7f7865953e38 thread_stack 0x49000
mysqld(my_print_stacktrace+0x2e)[0x5568fda85a5e]
mysqld(handle_fatal_signal+0x305)[0x5568fd4c64f5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f7883b18890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f7881e40067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f7881e41448]
mysqld(+0x41c0a0)[0x5568fd26b0a0]
mysqld(+0x7f7dd8)[0x5568fd646dd8]
mysqld(+0x80cbf9)[0x5568fd65bbf9]
mysqld(_ZN7handler21update_auto_incrementEv+0x2dd)[0x5568fd4cc66d]
mysqld(+0x80ec49)[0x5568fd65dc49]
mysqld(_ZN7handler12ha_write_rowEPh+0x1af)[0x5568fd4d091f]
mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6f)[0x5568fd304b1f]
mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1234)[0x5568fd30dd44]
mysqld(_Z21mysql_execute_commandP3THD+0x24ca)[0x5568fd32297a]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x28a)[0x5568fd32844a]
mysqld(+0x4d9c07)[0x5568fd328c07]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xfdd)[0x5568fd32a13d]
mysqld(_Z10do_commandP3THD+0x164)[0x5568fd32b6f4]
mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x5568fd3fde72]
mysqld(handle_one_connection+0x3d)[0x5568fd3fe00d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f7883b11064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f7881ef362d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f77f000eed0): INSERT INTO `user` ( id, `first_name`,`last_name`,`email`,`password`,`token`,`who_id` ) VALUES ( NULL, 'John','Doe','john.doe@vblpso.click','64d09d9930c8ecf79e513167a588cb75439b762ce8f9b22ea59765f32aa74ca19d2f1e97dc922a3d4954594a05062917fb24d1f8e72f2ed02a58ed7534f94d27',NULL,1 )
Connection ID (thread ID): 72
Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
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.