The bot crash, restart mysql

Bug #1739523 reported by 邰翀 on 2017-12-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to

Bug Description

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 440470 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
You may download the Percona Server operations manual by visiting You may find information
in the manual which will help you identify the cause of the crash.
Writing a core file
Segmentation fault (core dumped)
2017-12-20T16:16:01.951934Z mysqld_safe mysqld from pid file /data/mysql/ ended

邰翀 (tceason) on 2017-12-21
tags: added: crash
tags: added: core dumped
removed: crash
邰翀 (tceason) on 2017-12-21
affects: percona-server → mysql-server
affects: mysql-server → percona-server
tags: added: tokudb
removed: core dumped
Sveta Smirnova (svetasmirnova) wrote :

Thank you for the report.

Please upload full error log file, containing crash information and inform us which version of Percona Server do you use.

If crashes are repeatable please share actions you use to repeat them.

Changed in percona-server:
status: New → Incomplete
邰翀 (tceason) wrote :

Thank you for your attention, to find out the reason, is my friend misoperation led to the loss of data files, leading to failure.

Sveta Smirnova (svetasmirnova) wrote :

Thank you for the update.

I will close the report as "Invalid", because corrupted data files supposedly lead to crash.

Changed in percona-server:
status: Incomplete → Invalid

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers