Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 2015-07-21 03:23:18 2354 [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.
- 2015-07-21 03:23:18 2354 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:23:18 2354 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:23:18 2354 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:23:18 2354 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Database physically writes the file full: wait...
- 2015-07-21 03:23:18 2354 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
- 2015-07-21 03:23:19 2354 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
- 2015-07-21 03:23:20 2354 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
- 2015-07-21 03:23:20 2354 [Warning] InnoDB: New log files created, LSN=45781
- 2015-07-21 03:23:20 2354 [Note] InnoDB: Doublewrite buffer not found: creating new
- 2015-07-21 03:23:20 2354 [Note] InnoDB: Doublewrite buffer created
- 2015-07-21 03:23:20 2354 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:23:20 2354 [Warning] InnoDB: Creating foreign key constraint system tables.
- 2015-07-21 03:23:21 2354 [Note] InnoDB: Foreign key constraint system tables created
- 2015-07-21 03:23:21 2354 [Note] InnoDB: Creating tablespace and datafile system tables.
- 2015-07-21 03:23:21 2354 [Note] InnoDB: Tablespace and datafile system tables created.
- 2015-07-21 03:23:21 2354 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:23:21 2354 [Note] InnoDB: 5.6.24 started; log sequence number 0
- 2015-07-21 03:23:22 3ff751cf1d0 InnoDB: Assertion failure in thread 4395716374992 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:23:22 UTC - mysqld got signal 6 ;
- 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=1
- connection_count=0
- It is possible that mysqld could use up to
- key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 2015-07-21 03:23:24 2391 [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.
- 2015-07-21 03:23:24 2391 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:23:24 2391 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:23:24 2391 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:23:24 2391 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600607
- 2015-07-21 03:23:24 2391 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2015-07-21 03:23:24 3ff91bef1d0 InnoDB: Assertion failure in thread 4396196753872 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:23:24 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 2015-07-21 03:23:26 2405 [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.
- 2015-07-21 03:23:26 2405 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:23:26 2405 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:23:26 2405 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:23:26 2405 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600607
- 2015-07-21 03:23:26 2405 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2015-07-21 03:23:26 3ff8174f1d0 InnoDB: Assertion failure in thread 4395923468752 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:23:26 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 2015-07-21 03:23:28 2419 [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.
- 2015-07-21 03:23:28 2419 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:23:28 2419 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:23:28 2419 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:23:28 2419 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600607
- 2015-07-21 03:23:28 2419 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2015-07-21 03:23:28 3ff7c18f1d0 InnoDB: Assertion failure in thread 4395833553360 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:23:28 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:23:36 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
- 2015-07-21 03:23:36 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:23:36 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 2848 ...
- 2015-07-21 03:23:36 2848 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:23:36 2848 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:23:36 2848 [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.
- 2015-07-21 03:23:36 2848 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:23:36 2848 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:23:36 2848 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:23:36 2848 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:23:36 2848 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600607
- 2015-07-21 03:23:37 2848 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:23:37 2848 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:23:37 2848 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:23:37 2848 [Note] InnoDB: 5.6.24 started; log sequence number 1600607
- 2015-07-21 03:23:37 2848 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: e05beb3c-2f57-11e5-823e-6a84a5abbbc9.
- 2015-07-21 03:23:37 2848 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:23:37 2848 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:23:37 2848 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:23:37 2848 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:23:37 2848 [ERROR] Cannot open mysql.event
- 2015-07-21 03:23:37 2848 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:23:37 2848 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:23:38 3ff968df1d0 InnoDB: Assertion failure in thread 4396277428688 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:23:38 UTC - mysqld got signal 6 ;
- 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=1
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:23:40 mysqld_safe Number of processes running now: 0
- 150721 03:23:40 mysqld_safe mysqld restarted
- 2015-07-21 03:23:40 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:23:40 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 2898 ...
- 2015-07-21 03:23:40 2898 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:23:40 2898 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:23:40 2898 [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.
- 2015-07-21 03:23:40 2898 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:23:40 2898 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:23:40 2898 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:23:40 2898 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:23:40 2898 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600617
- 2015-07-21 03:23:41 2898 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:23:41 2898 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:23:41 2898 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:23:41 2898 [Note] InnoDB: 5.6.24 started; log sequence number 1600617
- 2015-07-21 03:23:41 2898 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:23:41 2898 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:23:41 2898 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:23:41 2898 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:23:41 2898 [ERROR] Cannot open mysql.event
- 2015-07-21 03:23:41 2898 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:23:41 2898 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:23:42 3ff7639f1d0 InnoDB: Assertion failure in thread 4395735052752 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:23:42 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:23:45 mysqld_safe Number of processes running now: 0
- 150721 03:23:45 mysqld_safe mysqld restarted
- 2015-07-21 03:23:45 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:23:45 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 2937 ...
- 2015-07-21 03:23:45 2937 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:23:45 2937 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:23:45 2937 [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.
- 2015-07-21 03:23:45 2937 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:23:45 2937 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:23:45 2937 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:23:45 2937 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600627
- 2015-07-21 03:23:45 2937 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:23:46 2937 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:23:46 2937 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:23:46 2937 [Note] InnoDB: 5.6.24 started; log sequence number 1600627
- 2015-07-21 03:23:46 2937 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:23:46 2937 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:23:46 2937 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:23:46 2937 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:23:46 2937 [ERROR] Cannot open mysql.event
- 2015-07-21 03:23:46 2937 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:23:46 2937 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:23:47 3ff7011f1d0 InnoDB: Assertion failure in thread 4395631768016 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:23:47 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:23:49 mysqld_safe Number of processes running now: 0
- 150721 03:23:49 mysqld_safe mysqld restarted
- 2015-07-21 03:23:49 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:23:49 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 2975 ...
- 2015-07-21 03:23:49 2975 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:23:49 2975 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:23:49 2975 [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.
- 2015-07-21 03:23:49 2975 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:23:49 2975 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:23:49 2975 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:23:49 2975 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600637
- 2015-07-21 03:23:49 2975 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2015-07-21 03:23:49 3ff8895f1d0 InnoDB: Assertion failure in thread 4396043071952 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:23:49 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:23:51 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
- 2015-07-21 03:27:38 3392 [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.
- 2015-07-21 03:27:38 3392 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:27:38 3392 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:27:38 3392 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:27:38 3392 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600637
- 2015-07-21 03:27:38 3392 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2015-07-21 03:27:38 3ff862cf1d0 InnoDB: Assertion failure in thread 4396002636240 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:27:38 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 2015-07-21 03:27:40 3420 [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.
- 2015-07-21 03:27:40 3420 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:27:40 3420 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:27:40 3420 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:27:40 3420 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600637
- 2015-07-21 03:27:40 3420 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2015-07-21 03:27:40 3ffa744f1d0 InnoDB: Assertion failure in thread 4396557857232 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:27:40 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 2015-07-21 03:27:42 3434 [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.
- 2015-07-21 03:27:42 3434 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:27:42 3434 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:27:42 3434 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:27:42 3434 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600637
- 2015-07-21 03:27:42 3434 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:27:43 3434 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:27:43 3434 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:27:43 3434 [Note] InnoDB: 5.6.24 started; log sequence number 1600637
- 2015-07-21 03:27:43 3434 [Note] Binlog end
- 2015-07-21 03:27:43 3434 [Note] InnoDB: FTS optimize thread exiting.
- 2015-07-21 03:27:43 3434 [Note] InnoDB: Starting shutdown...
- 2015-07-21 03:27:44 3ff9e60f1d0 InnoDB: Assertion failure in thread 4396408697296 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:27:44 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:27:49 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
- 2015-07-21 03:27:49 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:27:49 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 3866 ...
- 2015-07-21 03:27:49 3866 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:27:49 3866 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:27:49 3866 [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.
- 2015-07-21 03:27:49 3866 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:27:49 3866 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:27:49 3866 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:27:49 3866 [ERROR] Function 'federated' already exists
- 2015-07-21 03:27:49 3866 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:27:49 3866 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:27:49 3866 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:27:49 3866 [ERROR] Function 'archive' already exists
- 2015-07-21 03:27:49 3866 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:27:49 3866 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:27:49 3866 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:27:49 3866 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600647
- 2015-07-21 03:27:49 3866 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:27:50 3866 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:27:50 3866 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:27:50 3866 [Note] InnoDB: 5.6.24 started; log sequence number 1600647
- 2015-07-21 03:27:50 3866 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:27:50 3866 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:27:50 3866 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:27:50 3866 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:27:50 3866 [ERROR] Cannot open mysql.event
- 2015-07-21 03:27:50 3866 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:27:50 3866 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:27:51 3ff96e7f1d0 InnoDB: Assertion failure in thread 4396283326928 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:27:51 UTC - mysqld got signal 6 ;
- 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=1
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:27:53 mysqld_safe Number of processes running now: 0
- 150721 03:27:53 mysqld_safe mysqld restarted
- 2015-07-21 03:27:53 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:27:53 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 3914 ...
- 2015-07-21 03:27:53 3914 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:27:53 3914 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:27:53 3914 [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.
- 2015-07-21 03:27:53 3914 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:27:53 3914 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:27:53 3914 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:27:53 3914 [ERROR] Function 'federated' already exists
- 2015-07-21 03:27:53 3914 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:27:53 3914 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:27:53 3914 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:27:53 3914 [ERROR] Function 'archive' already exists
- 2015-07-21 03:27:53 3914 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:27:53 3914 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:27:53 3914 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:27:53 3914 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600657
- 2015-07-21 03:27:53 3914 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:27:54 3914 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:27:54 3914 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:27:54 3914 [Note] InnoDB: 5.6.24 started; log sequence number 1600657
- 2015-07-21 03:27:54 3914 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:27:54 3914 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:27:54 3914 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:27:54 3914 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:27:54 3914 [ERROR] Cannot open mysql.event
- 2015-07-21 03:27:54 3914 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:27:54 3914 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:27:55 3ffa1fff1d0 InnoDB: Assertion failure in thread 4396469449168 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:27:55 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:27:57 mysqld_safe Number of processes running now: 0
- 150721 03:27:57 mysqld_safe mysqld restarted
- 2015-07-21 03:27:57 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:27:57 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 3952 ...
- 2015-07-21 03:27:57 3952 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:27:57 3952 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:27:57 3952 [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.
- 2015-07-21 03:27:57 3952 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:27:57 3952 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:27:57 3952 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:27:57 3952 [ERROR] Function 'federated' already exists
- 2015-07-21 03:27:57 3952 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:27:57 3952 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:27:57 3952 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:27:57 3952 [ERROR] Function 'archive' already exists
- 2015-07-21 03:27:57 3952 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:27:57 3952 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:27:57 3952 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:27:57 3952 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600667
- 2015-07-21 03:27:57 3952 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:27:58 3952 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:27:58 3952 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:27:58 3952 [Note] InnoDB: 5.6.24 started; log sequence number 1600667
- 2015-07-21 03:27:58 3952 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:27:58 3952 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:27:58 3952 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:27:58 3952 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:27:58 3952 [ERROR] Cannot open mysql.event
- 2015-07-21 03:27:58 3952 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:27:58 3952 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:27:59 3ffa175f1d0 InnoDB: Assertion failure in thread 4396460405200 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:27:59 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:28:01 mysqld_safe Number of processes running now: 0
- 150721 03:28:01 mysqld_safe mysqld restarted
- 2015-07-21 03:28:01 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:28:01 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 3988 ...
- 2015-07-21 03:28:01 3988 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:28:01 3988 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:28:01 3988 [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.
- 2015-07-21 03:28:01 3988 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:28:01 3988 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:28:01 3988 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:28:01 3988 [ERROR] Function 'federated' already exists
- 2015-07-21 03:28:01 3988 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:28:01 3988 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:28:01 3988 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:28:01 3988 [ERROR] Function 'archive' already exists
- 2015-07-21 03:28:01 3988 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:28:01 3988 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:28:01 3988 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:28:01 3988 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600677
- 2015-07-21 03:28:01 3988 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:28:02 3988 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:28:02 3988 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:28:02 3988 [Note] InnoDB: 5.6.24 started; log sequence number 1600677
- 2015-07-21 03:28:02 3988 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:28:02 3988 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:28:02 3988 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:28:02 3988 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:28:02 3988 [ERROR] Cannot open mysql.event
- 2015-07-21 03:28:02 3988 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:28:02 3988 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:28:03 3ff6467f1d0 InnoDB: Assertion failure in thread 4395436077520 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:28:03 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:28:05 mysqld_safe Number of processes running now: 0
- 150721 03:28:05 mysqld_safe mysqld restarted
- 2015-07-21 03:28:05 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:28:05 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 4024 ...
- 2015-07-21 03:28:05 4024 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:28:05 4024 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:28:05 4024 [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.
- 2015-07-21 03:28:05 4024 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:28:05 4024 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:28:05 4024 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:28:05 4024 [ERROR] Function 'federated' already exists
- 2015-07-21 03:28:05 4024 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:28:05 4024 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:28:05 4024 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:28:05 4024 [ERROR] Function 'archive' already exists
- 2015-07-21 03:28:05 4024 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:28:05 4024 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:28:05 4024 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:28:05 4024 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600687
- 2015-07-21 03:28:05 4024 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2015-07-21 03:28:05 3ff7377f1d0 InnoDB: Assertion failure in thread 4395688784336 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:28:05 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:28:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
- 150721 03:29:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
- 2015-07-21 03:29:15 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:29:15 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 4443 ...
- 2015-07-21 03:29:15 4443 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:29:15 4443 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:29:15 4443 [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.
- 2015-07-21 03:29:15 4443 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:29:15 4443 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:29:15 4443 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:29:15 4443 [ERROR] Function 'federated' already exists
- 2015-07-21 03:29:15 4443 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:29:15 4443 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:29:15 4443 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:29:15 4443 [ERROR] Function 'archive' already exists
- 2015-07-21 03:29:15 4443 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:29:15 4443 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:29:15 4443 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:29:15 4443 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600687
- 2015-07-21 03:29:15 4443 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2015-07-21 03:29:15 3ff9015f1d0 InnoDB: Assertion failure in thread 4396168901072 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:29:15 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:29:17 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
- 150721 03:39:16 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
- 2015-07-21 03:39:16 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:16 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 6747 ...
- 2015-07-21 03:39:16 6747 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:16 6747 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:16 6747 [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.
- 2015-07-21 03:39:16 6747 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:16 6747 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:16 6747 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:16 6747 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:16 6747 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:16 6747 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:16 6747 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:16 6747 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:16 6747 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:16 6747 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:16 6747 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:16 6747 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600687
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:16 6747 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:16 6747 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:16 6747 [Note] InnoDB: 5.6.24 started; log sequence number 1600687
- 2015-07-21 03:39:16 6747 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:16 6747 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:16 6747 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:16 6747 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:16 6747 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:16 6747 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:16 6747 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:17 3ff8c3ff1d0 InnoDB: Assertion failure in thread 4396104544720 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:17 UTC - mysqld got signal 6 ;
- 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=1
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:20 mysqld_safe Number of processes running now: 0
- 150721 03:39:20 mysqld_safe mysqld restarted
- 2015-07-21 03:39:20 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:20 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 6790 ...
- 2015-07-21 03:39:20 6790 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:20 6790 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:20 6790 [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.
- 2015-07-21 03:39:20 6790 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:20 6790 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:20 6790 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:20 6790 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:20 6790 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:20 6790 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:20 6790 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:20 6790 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:20 6790 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:20 6790 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:20 6790 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:20 6790 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600697
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:20 6790 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:20 6790 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:21 6790 [Note] InnoDB: 5.6.24 started; log sequence number 1600697
- 2015-07-21 03:39:21 6790 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:21 6790 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:21 6790 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:21 6790 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:21 6790 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:21 6790 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:21 6790 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:22 3ffa35ff1d0 InnoDB: Assertion failure in thread 4396492517840 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:22 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:24 mysqld_safe Number of processes running now: 0
- 150721 03:39:24 mysqld_safe mysqld restarted
- 2015-07-21 03:39:24 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:24 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 6828 ...
- 2015-07-21 03:39:24 6828 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:24 6828 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:24 6828 [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.
- 2015-07-21 03:39:24 6828 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:24 6828 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:24 6828 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:24 6828 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:24 6828 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:24 6828 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:24 6828 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:24 6828 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:24 6828 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:24 6828 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:24 6828 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:24 6828 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600707
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:24 6828 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:24 6828 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:24 6828 [Note] InnoDB: 5.6.24 started; log sequence number 1600707
- 2015-07-21 03:39:24 6828 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:24 6828 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:24 6828 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:24 6828 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:24 6828 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:24 6828 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:24 6828 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:26 3ff74d3f1d0 InnoDB: Assertion failure in thread 4395711590864 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:26 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:28 mysqld_safe Number of processes running now: 0
- 150721 03:39:28 mysqld_safe mysqld restarted
- 2015-07-21 03:39:28 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:28 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 6864 ...
- 2015-07-21 03:39:28 6864 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:28 6864 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:28 6864 [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.
- 2015-07-21 03:39:28 6864 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:28 6864 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:28 6864 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:28 6864 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:28 6864 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:28 6864 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:28 6864 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:28 6864 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:28 6864 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:28 6864 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:28 6864 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:28 6864 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600717
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:28 6864 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:28 6864 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:28 6864 [Note] InnoDB: 5.6.24 started; log sequence number 1600717
- 2015-07-21 03:39:28 6864 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:28 6864 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:28 6864 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:28 6864 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:28 6864 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:28 6864 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:28 6864 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:30 3ff79b5f1d0 InnoDB: Assertion failure in thread 4395793510864 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:30 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:32 mysqld_safe Number of processes running now: 0
- 150721 03:39:32 mysqld_safe mysqld restarted
- 2015-07-21 03:39:32 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:32 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 6900 ...
- 2015-07-21 03:39:32 6900 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:32 6900 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:32 6900 [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.
- 2015-07-21 03:39:32 6900 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:32 6900 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:32 6900 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:32 6900 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:32 6900 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:32 6900 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:32 6900 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:32 6900 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:32 6900 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:32 6900 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:32 6900 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:32 6900 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600727
- 2015-07-21 03:39:32 6900 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:33 6900 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:33 6900 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:33 6900 [Note] InnoDB: 5.6.24 started; log sequence number 1600727
- 2015-07-21 03:39:33 6900 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:33 6900 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:33 6900 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:33 6900 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:33 6900 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:33 6900 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:33 6900 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:34 3ff7d29f1d0 InnoDB: Assertion failure in thread 4395851444688 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:34 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:36 mysqld_safe Number of processes running now: 0
- 150721 03:39:36 mysqld_safe mysqld restarted
- 2015-07-21 03:39:36 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:36 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 6938 ...
- 2015-07-21 03:39:36 6938 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:36 6938 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:36 6938 [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.
- 2015-07-21 03:39:36 6938 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:36 6938 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:36 6938 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:36 6938 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:36 6938 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:36 6938 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:36 6938 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:36 6938 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:36 6938 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:36 6938 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:36 6938 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:36 6938 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600737
- 2015-07-21 03:39:36 6938 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:37 6938 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:37 6938 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:37 6938 [Note] InnoDB: 5.6.24 started; log sequence number 1600737
- 2015-07-21 03:39:37 6938 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:37 6938 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:37 6938 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:37 6938 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:37 6938 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:37 6938 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:37 6938 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:38 3ff6d95f1d0 InnoDB: Assertion failure in thread 4395590087120 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:38 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:40 mysqld_safe Number of processes running now: 0
- 150721 03:39:40 mysqld_safe mysqld restarted
- 2015-07-21 03:39:40 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:40 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 6974 ...
- 2015-07-21 03:39:40 6974 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:40 6974 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:40 6974 [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.
- 2015-07-21 03:39:40 6974 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:40 6974 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:40 6974 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:40 6974 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:40 6974 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:40 6974 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:40 6974 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:40 6974 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:40 6974 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:40 6974 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:40 6974 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:40 6974 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600747
- 2015-07-21 03:39:40 6974 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:41 6974 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:41 6974 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:41 6974 [Note] InnoDB: 5.6.24 started; log sequence number 1600747
- 2015-07-21 03:39:41 6974 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:41 6974 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:41 6974 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:41 6974 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:41 6974 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:41 6974 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:41 6974 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:42 3ff735df1d0 InnoDB: Assertion failure in thread 4395687080400 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:42 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:44 mysqld_safe Number of processes running now: 0
- 150721 03:39:44 mysqld_safe mysqld restarted
- 2015-07-21 03:39:44 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:44 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 7013 ...
- 2015-07-21 03:39:44 7013 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:44 7013 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:44 7013 [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.
- 2015-07-21 03:39:44 7013 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:44 7013 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:44 7013 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:44 7013 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:44 7013 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:44 7013 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:44 7013 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:44 7013 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:44 7013 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:44 7013 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:44 7013 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:44 7013 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600757
- 2015-07-21 03:39:44 7013 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:45 7013 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:45 7013 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:45 7013 [Note] InnoDB: 5.6.24 started; log sequence number 1600757
- 2015-07-21 03:39:45 7013 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:45 7013 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:45 7013 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:45 7013 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:45 7013 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:45 7013 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:45 7013 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:46 3ff84f5f1d0 InnoDB: Assertion failure in thread 4395982254544 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:46 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:48 mysqld_safe Number of processes running now: 0
- 150721 03:39:48 mysqld_safe mysqld restarted
- 2015-07-21 03:39:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:48 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 7049 ...
- 2015-07-21 03:39:48 7049 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:48 7049 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:48 7049 [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.
- 2015-07-21 03:39:48 7049 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:48 7049 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:48 7049 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:48 7049 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:48 7049 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:48 7049 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:48 7049 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:48 7049 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:48 7049 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:48 7049 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:48 7049 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:48 7049 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:48 7049 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600767
- 2015-07-21 03:39:49 7049 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:49 7049 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:49 7049 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:49 7049 [Note] InnoDB: 5.6.24 started; log sequence number 1600767
- 2015-07-21 03:39:49 7049 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:49 7049 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:49 7049 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:49 7049 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:49 7049 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:49 7049 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:49 7049 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:50 3ff86cdf1d0 InnoDB: Assertion failure in thread 4396013187536 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:50 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:53 mysqld_safe Number of processes running now: 0
- 150721 03:39:53 mysqld_safe mysqld restarted
- 2015-07-21 03:39:53 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:53 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 7085 ...
- 2015-07-21 03:39:53 7085 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:53 7085 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:53 7085 [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.
- 2015-07-21 03:39:53 7085 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:53 7085 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:53 7085 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:53 7085 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:53 7085 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:53 7085 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:53 7085 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:53 7085 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:53 7085 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:53 7085 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:53 7085 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:53 7085 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600777
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:53 7085 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:53 7085 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:53 7085 [Note] InnoDB: 5.6.24 started; log sequence number 1600777
- 2015-07-21 03:39:53 7085 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:53 7085 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:53 7085 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:53 7085 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:53 7085 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:53 7085 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:53 7085 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:55 3ff992ff1d0 InnoDB: Assertion failure in thread 4396321599952 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:55 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:39:57 mysqld_safe Number of processes running now: 0
- 150721 03:39:57 mysqld_safe mysqld restarted
- 2015-07-21 03:39:57 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:39:57 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 7123 ...
- 2015-07-21 03:39:57 7123 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:39:57 7123 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:39:57 7123 [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.
- 2015-07-21 03:39:57 7123 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:39:57 7123 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:39:57 7123 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:39:57 7123 [ERROR] Function 'federated' already exists
- 2015-07-21 03:39:57 7123 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:39:57 7123 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:39:57 7123 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:39:57 7123 [ERROR] Function 'archive' already exists
- 2015-07-21 03:39:57 7123 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:39:57 7123 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:39:57 7123 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:39:57 7123 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600787
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
- InnoDB: Apply batch completed
- 2015-07-21 03:39:57 7123 [Note] InnoDB: 128 rollback segment(s) are active.
- 2015-07-21 03:39:57 7123 [Note] InnoDB: Waiting for purge to start
- 2015-07-21 03:39:57 7123 [Note] InnoDB: 5.6.24 started; log sequence number 1600787
- 2015-07-21 03:39:57 7123 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 2015-07-21 03:39:57 7123 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 2015-07-21 03:39:57 7123 [Note] Server socket created on IP: '127.0.0.1'.
- 2015-07-21 03:39:57 7123 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
- 2015-07-21 03:39:57 7123 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
- 2015-07-21 03:39:58 7123 [ERROR] Cannot open mysql.event
- 2015-07-21 03:39:58 7123 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- 2015-07-21 03:39:58 7123 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.6.24-0ubuntu2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- 2015-07-21 03:39:59 3ff7b5df1d0 InnoDB: Assertion failure in thread 4395821298128 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:39:59 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:40:01 mysqld_safe Number of processes running now: 0
- 150721 03:40:01 mysqld_safe mysqld restarted
- 2015-07-21 03:40:01 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2015-07-21 03:40:01 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 7159 ...
- 2015-07-21 03:40:01 7159 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
- 2015-07-21 03:40:01 7159 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
- 2015-07-21 03:40:01 7159 [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.
- 2015-07-21 03:40:01 7159 [Note] Plugin 'FEDERATED' is disabled.
- 2015-07-21 03:40:01 7159 [ERROR] Function 'innodb' already exists
- 2015-07-21 03:40:01 7159 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
- 2015-07-21 03:40:01 7159 [ERROR] Function 'federated' already exists
- 2015-07-21 03:40:01 7159 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
- 2015-07-21 03:40:01 7159 [ERROR] Function 'blackhole' already exists
- 2015-07-21 03:40:01 7159 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
- 2015-07-21 03:40:01 7159 [ERROR] Function 'archive' already exists
- 2015-07-21 03:40:01 7159 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2015-07-21 03:40:01 7159 [Note] InnoDB: The InnoDB memory heap is disabled
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2015-07-21 03:40:01 7159 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Compressed tables use zlib 1.2.8
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Using Linux native AIO
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Not using CPU crc32 instructions
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Completed initialization of buffer pool
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Highest supported file format is Barracuda.
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49961
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Database was not shutdown normally!
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Starting crash recovery.
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Restoring possible half-written data pages
- 2015-07-21 03:40:01 7159 [Note] InnoDB: from the doublewrite buffer...
- InnoDB: Doing recovery: scanned up to log sequence number 1600797
- 2015-07-21 03:40:01 7159 [Note] InnoDB: Starting an apply batch of log records to the database...
- InnoDB: Progress in percent: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2015-07-21 03:40:01 3ffa48ff1d0 InnoDB: Assertion failure in thread 4396512440784 in file fil0fil.cc line 5413
- InnoDB: Failing assertion: node->n_pending > 0
- InnoDB: We intentionally generate a memory trap.
- InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- InnoDB: If you get repeated assertion failures or crashes, even
- InnoDB: immediately after the mysqld startup, there may be
- InnoDB: corruption in the InnoDB tablespace. Please refer to
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 03:40:01 UTC - mysqld got signal 6 ;
- 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 = 76297 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- 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 = 0 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x44)[0x896dac]
- 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.
- 150721 03:40:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement