[MDEV-26816] Galera cluster received "mariadbd[2354817]: segfault" Error Created: 2021-10-13 Updated: 2022-01-26 Resolved: 2021-11-29 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Aria |
| Affects Version/s: | 10.6.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Pon Suresh Pandian (Inactive) | Assignee: | Michael Widenius |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | Aria, need_feedback | ||
| Environment: |
Red Hat Linux 8 |
||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Description |
|
Hi Team, Customer got segfault error on db nodes. Here I have attached the backtrace report. It looks like two complex selects and one of them crashed while accessing some wrong memory area while in Aria temporary table related code. Please check the attached backtrace report.
|
| Comments |
| Comment by Pon Suresh Pandian (Inactive) [ 2021-11-30 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Julien, I have tested this issue in my environment, I cant able to re produce this issue. Here I have attached the DDL/DML file.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Ramesh Sivaraman [ 2021-12-07 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Roel Could not reproduce the issue using provided dummy data.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Michael Widenius [ 2022-01-10 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I have examined the stack trace in detail, but unfortunately this is an optimized build and some of the vital information is not available. A non optimized build would be more helpful as in this case we get more information in gdb traces that could show the issue. I am not sure that a ASAN/UBSAN build will help as it is not clear if this is a logical error in record length counting or if it stray write into another memory structure that causes the fault. It is very likely it will fail in exactly the same point without any additional information. One way to find out what is going on is to give me remote access to the computer with gdb, the core and server source. It would also help to get the mysqld.err file attached to the is ticket (or at least all information related to this failure) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Michael Widenius [ 2022-01-10 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
About optimized builds. Note that the customer ONLY needs a copy of the mariadbd executable that he can use to temporarily replace the failing one. There is no need to do a full rpm for him. In theory someone could even log into the customer machine and compile it there. This would be the fastest way to get a quick turn around for finding the problem (as there may be needed several compile + fix + test cycles needed to find this bug...) |