>From log: 03:57:49 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=131072 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 = 76296 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7ffdc26f0350 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 = 7ffdc26efdf0 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x8dc04b] /usr/sbin/mysqld(handle_fatal_signal+0x37b)[0x63c6ab] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10)[0x7fb636f5bd10] /usr/sbin/mysqld(_Z18ha_resolve_by_nameP3THDPK19st_mysql_lex_stringb+0x60)[0x57cbd0] /usr/sbin/mysqld(_Z14open_table_defP3THDP11TABLE_SHAREj+0x1641)[0x74bde1] /usr/sbin/mysqld(_Z15get_table_shareP3THDP10TABLE_LISTPKcjjPij+0x1a0)[0x66ca60] /usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0x272)[0x66f122] /usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x923)[0x6781a3] /usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x42)[0x678ab2] /usr/sbin/mysqld[0x54dc14] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x649)[0x6d6d79] /usr/sbin/mysqld[0x574879] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x55e)[0x57589e] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fb636300a40] /usr/sbin/mysqld(_start+0x29)[0x56a059] 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. 160131 22:57:49 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 160131 23:07:49 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2016-01-31 23:07:49 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2016-01-31 23:07:49 0 [Note] /usr/sbin/mysqld (mysqld 5.6.28-0ubuntu0.15.10.1) starting as process 6819 ... 2016-01-31 23:07:49 6819 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000) 2016-01-31 23:07:49 6819 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000) 2016-01-31 23:07:49 6819 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 2016-01-31 23:07:49 6819 [Note] Plugin 'FEDERATED' is disabled. 04:07:49 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=131072 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 = 76296 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7ffda1bad4e0 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 = 7ffda1bacf80 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x8dc04b] /usr/sbin/mysqld(handle_fatal_signal+0x37b)[0x63c6ab] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10)[0x7fdfe6de0d10] /usr/sbin/mysqld(_Z18ha_resolve_by_nameP3THDPK19st_mysql_lex_stringb+0x60)[0x57cbd0] /usr/sbin/mysqld(_Z14open_table_defP3THDP11TABLE_SHAREj+0x1641)[0x74bde1] /usr/sbin/mysqld(_Z15get_table_shareP3THDP10TABLE_LISTPKcjjPij+0x1a0)[0x66ca60] /usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0x272)[0x66f122] /usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x923)[0x6781a3] /usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x42)[0x678ab2] /usr/sbin/mysqld[0x54dc14] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x649)[0x6d6d79] /usr/sbin/mysqld[0x574879] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x55e)[0x57589e] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fdfe6185a40] /usr/sbin/mysqld(_start+0x29)[0x56a059] 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. 160131 23:07:49 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended ** Summary changed: - package mysql-server-5.6 5.6.28-0ubuntu0.15.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 + mysqld from 5.6.28-0ubuntu0.15.10.1 segfaults -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1540214 Title: mysqld from 5.6.28-0ubuntu0.15.10.1 segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1540214/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
