[MDEV-20678] MariaDB 10.3.15 Crash "[ERROR] mysqld got signal 11 ;" Created: 2019-09-26  Updated: 2019-09-27  Resolved: 2019-09-26

Status: Closed
Project: MariaDB Server
Component/s: Platform RedHat, Server, Storage Engine - InnoDB
Affects Version/s: 10.3.15
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Jan Petrzilka Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: crash, innodb
Environment:

RedHat 7.6,


Attachments: Text File Print_defaults.txt     Text File list_variables.log     File my.cnf     Text File mysqld.log    
Issue Links:
Duplicate
duplicates MDEV-19490 show tables fails when selecting the ... Closed

 Description   

MariaDB crash many times with 190926 15:59:48 [ERROR] mysqld got signal 11 ;
Example:
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]> show tables;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 13
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 '/usr/local/dba/tmp/.mysql.QOCP.sock' (111)
ERROR: Can't connect to the server

unknown [information_schema]>

MariaDB crashed, process mysqld was restarted.

 Comments   
Comment by Alice Sherepa [ 2019-09-26 ]

It seems to be the same bug as MDEV-19490, please upgrade to the latest release

Comment by Jan Petrzilka [ 2019-09-27 ]

Hi Alice,
we updated to 10.3.18 and db works OK. It's possible to use information_schema.

Thanks a lot and Best Regards.
Jan

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