mysqld crash when config not readable
# ls -l /etc/mysql/
-rw-r----- 1 root root 5616 okt 31 16:23 /etc/mysql/
mysql> slave start;
Could not open required defaults file: /etc/mysql/
Fatal error in defaults handling. Program aborted
*** glibc detected *** /usr/sbin/mysqld: free(): invalid pointer: 0x00007fa1500085e0 ***
121031 16:23:59 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './slave-
Query OK, 0 rows affected (0.00 sec)
mysql> ======= Backtrace: =========
======= Memory map: ========
14:23:59 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona Server better by reporting any
bugs at http://
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fa150000990
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
stack_bottom = 7fa164139c90 thread_stack 0x40000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 4
You may download the Percona Server operations manual by visiting
in the manual which will help you identify the cause of the crash.
this simple fix makes it not to crash:
# chgrp mysql /etc/mysql/