Percona Server moved to https://jira.percona.com/projects/PS

Bug #1259833
Comment #3

Comment 3 for bug 1259833

Revision history for this message

David Busby (d-busby) wrote on 2014-06-04: Re: mysqld got signal 8

Encountered same issue:

---
08:37:12 UTC - mysqld got signal 8 ;
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://bugs.percona.com/

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=2502
thread_count=2
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5483630 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xa35176b0
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 = 7f11a771bd78 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c9c65]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x69eac4]
/lib64/libpthread.so.0(+0xf710)[0x7f2a979c3710]
/usr/sbin/mysqld[0x541cd7]
/usr/sbin/mysqld[0x5423b0]
/usr/sbin/mysqld[0x542666]
/usr/sbin/mysqld[0x539ec9]
/usr/sbin/mysqld(_Z16acl_authenticateP3THDjj+0x930)[0x549770]
/usr/sbin/mysqld[0x639dd4]
/usr/sbin/mysqld(_Z16login_connectionP3THD+0x50)[0x63a020]
/usr/sbin/mysqld(_Z22thd_prepare_connectionP3THD+0x24)[0x63a244]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x11a)[0x63b68a]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x63b791]
/lib64/libpthread.so.0(+0x79d1)[0x7f2a979bb9d1]
/lib64/libc.so.6(clone+0x6d)[0x7f2a962eeb5d]

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): 42
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
...

Resolution:

mysql/users.MYD was 0 bytes in size, as this was a new install, removal of datadir contents and re-running of mysql_install_db (after fixing selinux contexts on the non standard datadir location) all was well.

Bug here imho is the poor handling of the empty users table; crashing instead of throwing an error.

Encountered same issue:

---
08:37:12 UTC - mysqld got signal 8 ;
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://bugs.percona.com/

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=2502
thread_count=2
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5483630 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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): 42
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
...

Resolution:

mysql/users.MYD was 0 bytes in size, as this was a new install, removal of datadir  contents and re-running of mysql_install_db (after fixing selinux contexts on the non standard datadir location) all was well.

Bug here imho is the poor handling of the empty users table; crashing instead of throwing an error.