[MDEV-20736] MariaDB 10.3.18 Crash "[ERROR] mysqld got signal 11 ;" Created: 2019-10-03 Updated: 2019-10-22 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.3.18 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Martin Mørch | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | crash | ||
| Environment: |
CentOS Linux release 7.7.1908 (Core) |
||
| Description |
|
We recently ran into a crash with a user performing a query causing MariaDB to crash. Crash log:
The query in question:
When the query is run statement by statement, in 4 separate queries, is succeeds with no issue, like this:
However, when run as a single query with multiple statements, it causes the entire server to crash. This is the query log when a crash occurs:
Steps to re-produce:
|
| Comments |
| Comment by Alice Sherepa [ 2019-10-04 ] | ||||||||||||||||||||||||||||||||||||
|
Could you please describe how exactly you run the queries, does it crash every time for you? Please add your
| ||||||||||||||||||||||||||||||||||||
| Comment by Martin Mørch [ 2019-10-04 ] | ||||||||||||||||||||||||||||||||||||
|
This is an example of a session that caused a crash. Doing the exact same set of queries can re-produce a crash every single time:
Server config: https://pastebin.com/RbbuDdMM | ||||||||||||||||||||||||||||||||||||
| Comment by Elena Stepanova [ 2019-10-06 ] | ||||||||||||||||||||||||||||||||||||
|
I can't reproduce it either, although I don't have CentOS 7.7 handy, so I'm trying 7.5, and smaller buffer pool size.
I would think that it is somehow something specific to the database, for example there are corrupt tables which make information schema misbehave, or the queries values are such that they trigger a failure, but it doesn't explain why it wouldn't fail when the statements are executed one by one. martinmorch, would you be able to enable the coredump and see if you can acquire a stack trace? You might need to additionally install MariaDB-server-debuginfo-10.3.18-1.el7.centos.x86_64.rpm to make the stack trace meaningful. | ||||||||||||||||||||||||||||||||||||
| Comment by Martin Mørch [ 2019-10-08 ] | ||||||||||||||||||||||||||||||||||||
|
I was messing with getting mysqld-debug up and running and had to stop halfway. Remove *-debuginfo packages and did a yum reinstall on MariaDB-server. After reinstall, I cannot re-produce the issue. Had a small PHP script using PDO that was able to make mysqld crash every single time. After the reinstall, it simply throws an error:
Before, this same script would simply hang and never produce an error.
Weird part is, this statement works just fine using the MariaDB mysql CLI tool. Anyway, I think you can park this as "user error" or similar. Something obviously happened when reinstalling RPM's, unfortunately I do not know what | ||||||||||||||||||||||||||||||||||||
| Comment by Martin Mørch [ 2019-10-22 ] | ||||||||||||||||||||||||||||||||||||
|
Our DBA mentioned today that he was missing MariaDB-connect-engine on the server that previously had issues. Did 'yum install MariaDB-connect-engine' (specifically MariaDB-connect-engine-10.3.18-1.el7.centos.x86_64), verified MariaDB had restarted correctly and out of curiosity tried running the above statement again and VOILA! MariaDB crashed! So, something related to MariaDB-connect-engine-10.3.18-1.el7.centos.x86_64 seems to cause this issue. Can anyone else verify? |