Trying to figure out what went wrong here. Any advice would be appreciated. This server is running a new installation of Percona Server 5.6.19 on CentOS 6.5

16:05:46 UTC - mysqld got signal 11 ;
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/

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 7228203 K  bytes  of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x17e85e60
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 = 7f7c813f8d40 thread_stack 0x30000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7c380009a0): is an invalid pointer
Connection ID (thread ID): 71

It seems an invalid pointer was caught when doing a full table scan on the Archive engine. I recommend you to post the trace on Percona Server bug tracker. Developers are very friendly even if you are not a client. They will be able to tell you if it is a Percona specific problem or an upstream problem (if they have changed anything on the Archive stored engine).

My own experience with the Archive engine is that, while it is a nice theoretical engine for some workloads, it is currently mostly unmaintained and not ready for production, having astounding bugs. Percona does not recommend it, and if you are concerned about stability, you are probably better served by InnoDB compressed or TokuDB (no matter if you are running PS or stock MySQL).

  • Thanks for pointing me in the right direction. I filed a bug report with Percona and they say it's not a bug in their software. They did point me to an old upstream bug, but I don't think it applies in this case as archive tables in the 20G range are the norm with this application. bugs.mysql.com/bug.php?id=15787 – tcoker Jul 15 '14 at 20:33

I have run percona-server-5.6.19-67.0.tar.gz from source without a hitch. No heavy workload my end - just wanted to test. You don't say what you were doing - I could try and run it if you like.

Did you install over an old install of MySQL? Did you jump a couple of versions? Your problem could be related to this.

  • Thanks, I did look at that first. However it appears to be related to the archive engine and there have not been any re-installations, upgrades or imports recently. – tcoker Jul 15 '14 at 20:37
  • I know that you cannot migrate now, but ARCHIVE not only is incredible buggy, it is unmaintained (by Oracle and 3rd party vendors). You should contemplate a future migration to the alternatives InnoDB compressed, TokuDB, ... – jynus Jul 16 '14 at 19:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.