Kommando zurück. MySQL Server hat sich wieder verabschiedet.
2014-09-04 16:26:37 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
2014-09-04 16:26:38 0 Warning The syntax 'pre-4.1 password hash' is deprecated and will be removed in a future release. Please use post-4.1 password hash instead.
2014-09-04 16:26:38 0 Warning TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-09-04 16:26:38 2449 Warning Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive
2014-09-04 16:26:38 2449 Note Plugin 'FEDERATED' is disabled.
2014-09-04 16:26:38 2449 Note InnoDB: The InnoDB memory heap is disabled
2014-09-04 16:26:38 2449 Note InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-09-04 16:26:38 2449 Note InnoDB: Compressed tables use zlib 1.2.3
2014-09-04 16:26:38 2449 Note InnoDB: Using CPU crc32 instructions
2014-09-04 16:26:38 2449 Note InnoDB: Initializing buffer pool, size = 128.0M
2014-09-04 16:26:38 2449 Note InnoDB: Completed initialization of buffer pool
2014-09-04 16:26:38 2449 Note InnoDB: Highest supported file format is Barracuda.
2014-09-04 16:26:38 2449 Note InnoDB: 128 rollback segment(s) are active.
2014-09-04 16:26:38 2449 Note InnoDB: Waiting for purge to start
InnoDB: Error: tablespace id is 315 in the data dictionary
InnoDB: but in file ./wordpress/wp_posts.ibd it is 419!
2014-09-04 16:26:38 1296a7000 InnoDB: Assertion failure in thread 4989808640 in file fil0fil.cc line 794
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.
14:26: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=8388608
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 = 68218 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 0x40000
0 mysqld 0x0000000104fb77d6 my_print_stacktrace + 61
1 mysqld 0x0000000104e132a0 handle_fatal_signal + 705
2 libsystem_platform.dylib 0x00007fff8c4ad5aa _sigtramp + 26
3 ??? 0x747265737341203a 0x0 + 8390880602273947706
4 libsystem_c.dylib 0x00007fff86cbfb1a abort + 125
5 mysqld 0x000000010502ce9f _ZL18fil_node_open_fileP10fil_node_tP12fil_system_tP11fil_space_t + 1886
6 mysqld 0x0000000105034655 _ZL23fil_node_prepare_for_ioP10fil_node_tP12fil_system_tP11fil_space_t + 116
7 mysqld 0x0000000105034e5e _Z6fil_iombmmmmmPvS_ + 679
8 mysqld 0x000000010500ab35 _ZL17buf_read_page_lowP7dberr_tbmmmmxm + 427
9 mysqld 0x000000010500af13 _Z13buf_read_pagemmm + 69
10 mysqld 0x0000000104ff7dc3 _Z16buf_page_get_genmmmmP11buf_block_tmPKcmP5mtr_t + 2773
11 mysqld 0x0000000104fe4db7 _Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_tmmP9btr_cur_tmPKcmP5mtr_t + 2671
12 mysqld 0x00000001050e3807 _Z22row_search_index_entryP12dict_index_tPK8dtuple_tmP10btr_pcur_tP5mtr_t + 140
13 mysqld 0x00000001050e1b13 _ZL28row_purge_remove_sec_if_possP12purge_node_tP12dict_index_tPK8dtuple_t + 377
14 mysqld 0x00000001050e10a1 _Z14row_purge_stepP9que_thr_t + 786
15 mysqld 0x00000001050bb285 _Z15que_run_threadsP9que_thr_t + 1401
16 mysqld 0x00000001051049ed _Z9trx_purgemmb + 2793
17 mysqld 0x00000001050fa054 srv_purge_coordinator_thread + 2156
18 libsystem_pthread.dylib 0x00007fff87e49899 _pthread_body + 138
19 libsystem_pthread.dylib 0x00007fff87e4972a _pthread_struct_init + 0
20 libsystem_pthread.dylib 0x00007fff87e4dfc9 thread_start + 13
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.