Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 395054 Details for
Bug 538046
dev-db/mysql-5.6.22: crashed - mysqld got signal 11 on /usr/sbin/mysqld(_Z9get_fieldP11st_mem_rootP5Field+0x30)
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
mysql.err crash log
mysqld-crash.txt (text/plain), 2.59 KB, created by
cilly
on 2015-01-28 14:38:21 UTC
(
hide
)
Description:
mysql.err crash log
Filename:
MIME Type:
Creator:
cilly
Created:
2015-01-28 14:38:21 UTC
Size:
2.59 KB
patch
obsolete
>tail -n 50 /var/log/mysql/mysqld.err >2015-01-28 15:17:03 18829 [Note] InnoDB: 5.6.22 started; log sequence number 1982988 >2015-01-28 15:17:03 18829 [Note] Recovering after a crash using mysqld-bin >2015-01-28 15:17:03 18829 [Note] Starting crash recovery... >2015-01-28 15:17:03 18829 [Note] Crash recovery finished. >2015-01-28 15:17:03 18829 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work. >2015-01-28 15:17:03 18829 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work. >2015-01-28 15:17:03 18829 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 >2015-01-28 15:17:03 18829 [Note] - '127.0.0.1' resolves to '127.0.0.1'; >2015-01-28 15:17:03 18829 [Note] Server socket created on IP: '127.0.0.1'. >14:17:03 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. > >key_buffer_size=16777216 >read_buffer_size=262144 >max_used_connections=0 >max_threads=151 >thread_count=0 >connection_count=0 >It is possible that mysqld could use up to >key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134417 K bytes of memory >Hope that's ok; if not, decrease some variables in the equation. > >Thread pointer: 0x1a57f80790 >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 = 3e2e4490a80 thread_stack 0x40000 >/usr/sbin/mysqld(my_print_stacktrace+0x47)[0x1a560c9aa7] >/usr/sbin/mysqld(handle_fatal_signal+0x3e0)[0x1a55e2c920] >/lib64/libpthread.so.0(+0x10e00)[0x329ce6d6e00] >/usr/sbin/mysqld(_Z9get_fieldP11st_mem_rootP5Field+0x30)[0x1a55f39ee0] >/usr/sbin/mysqld(_Z10acl_reloadP3THD+0x1393)[0x1a55e460a3] >/usr/sbin/mysqld(_Z8acl_initb+0x147)[0x1a55e470a7] >/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1472)[0x1a55d357e2] >/lib64/libc.so.6(__libc_start_main+0x11b)[0x329cdd0ee5b] >/usr/sbin/mysqld(+0x368123)[0x1a55d28123] > >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): 0 >Status: NOT_KILLED > >The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains >information that should help you find out what is causing the crash.
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 538046
:
395052
| 395054