mysql.log.gz
[MDEV-10434] segfault in mariadb Created: 2016-07-25 Updated: 2020-10-20 Resolved: 2020-10-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 5.5.50-galera |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Evan Jardine-Skinner | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Ubuntu 14.04 mariadb-5.5.50 and galera-3.25.16 |
||
| Attachments: |
mysql.log.gz
|
| Description |
|
See the following in syslog. Attaching the general log as that was running at the time of the failure
|
| Comments |
| Comment by Evan Jardine-Skinner [ 2016-07-25 ] |
|
mysql.log.gz uploaded (the last 200000 lines anyway, due the the 10mb upload limit) The last query in there is nothicng special though and doesn't cause the server to crash normally. |
| Comment by Elena Stepanova [ 2016-07-30 ] |
|
Was it a one-time crash, or does it keep happening? Unfortunately, there is literally nothing to work with – the stack trace is unreadable, and according to the general log (thanks for providing it), there were no queries at all at the time of the crash, all connections that recently performed queries were already closed or closing. My best guess is that the crash is somehow related to the Galera node activity, but it's just a speculation. For a note, big files can be uploaded to ftp.askmonty.org/private (better to give them specific names though, optimally mentioning the JIRA issue number). |
| Comment by Evan Jardine-Skinner [ 2016-08-01 ] |
|
I've seen segfault crashes every now and then (not all the time, but not a one time thing either). The stack trace is always different. Since adding the code to restart a Hung mysql I've not seen a segfault though, so it's possible the 2 are related. The bug concerning the hung mysql https://jira.mariadb.org/browse/MDEV-10400 is really the biggest problem for me at the moment. |
| Comment by Evan Jardine-Skinner [ 2016-08-01 ] |
|
Closing this one because., as you say, it is diffcult to make any progress if I can't reproduce it. Thanks for looking into it. |
| Comment by Evan Jardine-Skinner [ 2016-08-01 ] |
|
Hmm I must be being dumb but I can't find a way to close this. Please feel free to close it |
| Comment by Elena Stepanova [ 2016-08-01 ] |
|
Ev, you said "the stack trace is always different" – does it mean that sometimes it looks more meaningful than the one in the description? If so, could you maybe paste it? |
| Comment by Evan Jardine-Skinner [ 2016-08-01 ] |
|
The nodes have been re-installed since I saw more of the stack traces but I did find one interesting one: Jul 29 09:30:18 advancedportalnode-test-20160725-10-137-105-48 mysqld: InnoDB: Error: trying to free a corrupt |
| Comment by Elena Stepanova [ 2020-10-20 ] |
|
We have never been able to reproduce it, the stack trace is not distinctive enough to match it with other open or fixed bugs, and 5.5-galera is long gone now; so I'm closing it as incomplete. The issue can be re-opened if it gets fresh information related to active versions. |
