[MDEV-24108] Our server crashed and there was no possibility to restart it - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Incomplete
Affects Version/s: 10.3.11
Fix Version/s: N/A
Component/s: Storage Engine - InnoDB
Labels:
- need_feedback
Environment:

Hide
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-514.el7.x86_64
Architecture: x86-64

Show
Operating System: CentOS Linux 7 (Core) CPE OS Name: cpe:/o:centos:centos:7 Kernel: Linux 3.10.0-514.el7.x86_64 Architecture: x86-64

Description

Suddenly we started receiving the next errors:
Error Code: 2013 Lost connection to MySQL server at 'reading initial communication packet', system error: 0
Error Code: 2003 Can't connect to MySQL server on '185.156.42.233' (10061)

After checking the log we found out that MariaDB is not able to restart after some fatal crash. Please investigate the log, I've attached the whole day trace, you may find a crash starting at about 12:55.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

mariadb-for-jira.log
2.63 MB
2020-11-03 13:17

Issue Links

relates to

MDEV-19916 Corruption after instant ADD/DROP and shrinking the index tree

Closed

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Sergii

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2020-11-03 13:17

Updated:: 2021-04-25 15:25

Resolved:: 2021-04-25 15:25

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.