image-2019-12-20-14-39-32-713.png
image-2019-12-20-14-40-15-452.png
[MDEV-21366] Server Crash on MariaDB 10.3.13 Created: 2019-12-20 Updated: 2020-10-02 Resolved: 2020-10-02 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | N/A |
| Affects Version/s: | 10.3 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Critical |
| Reporter: | Yeongin JUNG | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | crash, need_verification | ||
| Environment: |
CentOS7 |
||
| Attachments: |
image-2019-12-20-14-39-32-713.png
image-2019-12-20-14-40-15-452.png
|
| Description |
|
Hi, I am using MariaDB 10.3.13 version. And one day server suddenly crashed with those logs although I didnt do any operation, and I wanna know is there any the possible reason for this. |
| Comments |
| Comment by Daniel Black [ 2020-10-02 ] |
|
I'm sorry, the latest 10.3.13 version (http://ftp.hosteurope.de/mirror/archive.mariadb.org/mariadb-10.3.13/yum/centos7-amd64/rpms/) doesn't include the the MariaDB-server-debuginfo package that I need to decode the address locations in your images. Can you please try a newer version as see if anything happens? For bug reports it would be significantly easier if the stack traces where provided as text rather than images. If a core is generated, install MariaDB-server-debuginfo from the same respository and run gdb /usr/sbin/mysqld core and then thread apply all bt full to show the result. https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/#analyzing-a-core-file-with-gdb-on-linux for more information. Thanks for reporting an issue, however with the provided information I can't do anything with it. |
