Mysqld crashing after upgrade from 8.0.22 to 8.0.23 (mysqld got signal 11)

After a regular package update, my server started crashing as soon as it receives traffic.

here is what I see in the logs:

2021-05-15T06:12:54.515778Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: ‘8.0.23-14’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 Percona Server (GPL), Release ‘14’, Revision ‘3558242’.
06:12:57 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.

Build ID: ed5f68b550fd501799d6aa2fd13a87fb062cedd0
Server Version: 8.0.23-14 Percona Server (GPL), Release ‘14’, Revision ‘3558242’

Thread pointer: 0x7fcf9c010ac0
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 = 7fd2ac5f7d10 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x55aeeeed5231]
/usr/sbin/mysqld(handle_fatal_signal+0x38b) [0x55aeedef72bb]
/lib/x86_64-linux-gnu/ [0x7fd2bc4453c0]
/usr/sbin/mysqld(+0x243845f) [0x55aeeef9b45f]
/usr/sbin/mysqld(Item_func_match::val_real()+0xa4) [0x55aeedb25f84]
/usr/sbin/mysqld(Item_ref::val_real()+0x23) [0x55aeedaa7e43]
/usr/sbin/mysqld(Arg_comparator::compare_real()+0x1f) [0x55aeedac705f]
/usr/sbin/mysqld(Item_func_gt::val_int()+0x2f) [0x55aeedac77df]
/usr/sbin/mysqld(FilterIterator::Read()+0x2c) [0x55aeedfbd15c]
/usr/sbin/mysqld(SELECT_LEX_UNIT::ExecuteIteratorQuery(THD*)+0x30e) [0x55aeede74d3e]
/usr/sbin/mysqld(SELECT_LEX_UNIT::execute(THD*)+0x33) [0x55aeede75063]
/usr/sbin/mysqld(Sql_cmd_dml::execute_inner(THD*)+0x32b) [0x55aeeddf83cb]
/usr/sbin/mysqld(Sql_cmd_dml::execute(THD*)+0x535) [0x55aeede02135]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0x9fd) [0x55aeedd9fe2d]
/usr/sbin/mysqld(dispatch_sql_command(THD*, Parser_state*, bool)+0x52b) [0x55aeedda4fab]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x1f05) [0x55aeedda7375]
/usr/sbin/mysqld(do_command(THD*)+0x218) [0x55aeedda8268]
/usr/sbin/mysqld(+0x1384ff8) [0x55aeedee7ff8]
/usr/sbin/mysqld(+0x28ef272) [0x55aeef452272]
/lib/x86_64-linux-gnu/ [0x7fd2bc439609]
/lib/x86_64-linux-gnu/ [0x7fd2bbbfb293]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fcf9d1182e8): SELECT COUNT(*) AS count, MATCH (content_search.titles, content_search.keywords, content_search.descriptions) AGAINST (‘busty’ IN BOOLEAN MODE) AS score FROM content JOIN content_search ON content_search.content = content.record_num WHERE content.enabled = 1 AND = 0 AND MATCH (content_search.titles, content_search.keywords, content_search.descriptions) AGAINST (‘busty’ IN BOOLEAN MODE) HAVING score > 0
Connection ID (thread ID): 16

Please help us make Percona Server better by reporting any
bugs at

You may download the Percona Server operations manual by visiting You may find information
in the manual which will help you identify the cause of the crash.
2021-05-15T06:12:58.387232Z 0 [Warning] [MY-010915] [Server] ‘NO_ZERO_DATE’, ‘NO_ZERO_IN_DATE’ and ‘ERROR_FOR_DIVISION_BY_ZERO’ sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2021-05-15T06:12:58.388578Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.23-14) starting as process 884846

I have no clue what the reason could be… I already tried a:

mysqlcheck --all-databases -a #analyze
mysqlcheck --all-databases -r #repair
mysqlcheck --all-databases -o #optimize

any help would be much appreciated

Reported here: MySQL Bugs: #103712: innodb fulltext search with nonaggregated columns crashes mysqld

1 Like

Please delete the thread as the bug is classified as S1 critical and it allows any unprivileged user to cause a segfault and put out of service the whole server

1 Like