[MDEV-19742] Signal 11 querying information_schema tables Created: 2019-06-12  Updated: 2019-06-12  Resolved: 2019-06-12

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.3.15
Fix Version/s: 10.3.16

Type: Bug Priority: Major
Reporter: Thomas Boyd (Inactive) Assignee: Anel Husakovic
Resolution: Fixed Votes: 0
Labels: None

Attachments: File mariadb-log.out    
Issue Links:
Duplicate
is duplicated by MDEV-19490 show tables fails when selecting the ... Closed

 Description   

I am getting regular signal 11 errors when interacting with INFORMATION_SCHEMA in 10.3.15. Have now crashed using homebrew install on my Mac, docker contianer on my mac, and Centos repo install on AWS (to rule out hardware issue). Once I crashed simply when I issuesd "use information_schema" via mysql command line. More often I crash doing simple selects against the column table.

Most recent crash on AWS Centos repo install simply involved starting the mariadb service via systemctl, starting mysql command line and then issuing.

mysql -uroot
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 8
Server version: 10.3.15-MariaDB MariaDB Server
 
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
 
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
MariaDB [(none)]> use information_schema
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
 
Database changed
MariaDB [information_schema]> select column_name from columns;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:    8
Current database: information_schema
 
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)
ERROR: Can't connect to the server
 
unknown [information_schema]>

Log output via journalctl is attached and includes at least a couple signal 11s.

Running on m5.xlarge (4 core 16 GB memory).
Let me know what other info you would like. Crash has been easy for me to reproduce (3 environments out of 3 so far).



 Comments   
Comment by Anel Husakovic [ 2019-06-12 ]

This bug is already solved in 10.3.16. with patch `ef04a7123a7beed5bf20736`

Generated at Thu Feb 08 08:54:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.