Bug #77348 | "mysqld got signal 11" at startup | ||
---|---|---|---|
Submitted: | 14 Jun 2015 12:03 | Modified: | 24 May 2017 16:06 |
Reporter: | db db | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.6.24 | OS: | FreeBSD (10.1-RELEASE-p12) |
Assigned to: | CPU Architecture: | Any |
[14 Jun 2015 12:03]
db db
[14 Jun 2016 7:02]
Hartmut Holzgraefe
Can't reproduce this, I did the following steps: * created a /foobar directory * moved over the datadir of an existing mysql to /foobar/data * set datadir=/foobar/data in my.cnf * changed /foobar permissions to --x--x--x * started mysqld, as "root" and as "mysql" * started mysqld after deleting ibdata and iblog files Never ran into a crash with this ...
[14 Jun 2016 7:06]
MySQL Verification Team
re http://bugs.mysql.com/bug.php?id=81827 and sadly there is no stack trace on freebsd to point us in right direction. gdb or corefile would be needed..
[14 Jun 2016 7:57]
Hartmut Holzgraefe
Ah, I totally overlooked the OS information, I tested on Linux ...
[25 May 2017 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".