Benötige eure Hilfe... Was ist wieder mit meinem MySQL Server los?
Folgender Error wird ausgespuckt:
ZitatAlles anzeigen150624 05:23:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql2015-06-24 05:23:54 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
2015-06-24 05:23:54 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-06-24 05:23:54 4726 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
2015-06-24 05:23:54 4726 [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)
2015-06-24 05:23:54 4726 [Note] Plugin 'FEDERATED' is disabled.
2015-06-24 05:23:54 4726 [ERROR] Function 'innodb' already exists
2015-06-24 05:23:54 4726 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'.
2015-06-24 05:23:54 4726 [ERROR] Function 'federated' already exists
2015-06-24 05:23:54 4726 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'.
2015-06-24 05:23:54 4726 [ERROR] Function 'blackhole' already exists
2015-06-24 05:23:54 4726 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'.
2015-06-24 05:23:54 4726 [ERROR] Function 'archive' already exists
2015-06-24 05:23:54 4726 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'.
2015-06-24 05:23:54 4726 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-24 05:23:54 4726 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-24 05:23:54 4726 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-06-24 05:23:54 4726 [Note] InnoDB: Memory barrier is not used
2015-06-24 05:23:54 4726 [Note] InnoDB: Compressed tables use zlib 1.2.7
2015-06-24 05:23:54 4726 [Note] InnoDB: Using Linux native AIO
2015-06-24 05:23:54 4726 [Note] InnoDB: Using CPU crc32 instructions
2015-06-24 05:23:54 4726 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-06-24 05:23:54 4726 [Note] InnoDB: Completed initialization of buffer pool
2015-06-24 05:23:54 4726 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-24 05:23:54 7f3bec426720 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2015-06-24 05:23:54 4726 [ERROR] InnoDB: Could not find a valid tablespace file for 'wphomepage/wp_options'. See http://dev.mysql.com/doc/refma…bleshooting-datadict.html for how to resolve the issue.
2015-06-24 05:23:54 4726 [ERROR] InnoDB: Tablespace open failed for '"wphomepage"."wp_options"', ignored.
2015-06-24 05:23:54 4726 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-24 05:23:54 4726 [Note] InnoDB: Waiting for purge to start
2015-06-24 05:23:54 4726 [ERROR] InnoDB: Failed to find tablespace for table '"wphomepage"."wp_options"' in the cache. Attempting to load the tablespace with space id 578.
2015-06-24 05:23:54 7f3bd2ce5700 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
2015-06-24 05:23:54 4726 [ERROR] InnoDB: Could not find a valid tablespace file for 'wphomepage/wp_options'. See http://dev.mysql.com/doc/refma…bleshooting-datadict.html for how to resolve the issue.
InnoDB: Error: tablespace id is 272 in the data dictionary
InnoDB: but in file ./mailjunky/bm60_file_cache.ibd it is 4051!
2015-06-24 05:23:54 7f3bd2ce5700 InnoDB: Assertion failure in thread 139894916536064 in file fil0fil.cc line 796
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/refma…cing-innodb-recovery.html
InnoDB: about forcing recovery.
03:23:54 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 = 76433 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+0x2e)[0x893b3e]
/usr/sbin/mysqld(handle_fatal_signal+0x35a)[0x65cc2a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f3bec0080a0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f3bea89a165]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f3bea89d3e0]
/usr/sbin/mysqld[0xa46b64]
/usr/sbin/mysqld[0xa46c75]
/usr/sbin/mysqld[0xa5100b]
/usr/sbin/mysqld[0xa18c9a]
/usr/sbin/mysqld[0xa194a0]
/usr/sbin/mysqld[0xa026f3]
/usr/sbin/mysqld[0x9e7bd9]
/usr/sbin/mysqld[0x995455]
/usr/sbin/mysqld[0x9922a8]
/usr/sbin/mysqld[0x993d89]
/usr/sbin/mysqld[0x9636eb]
/usr/sbin/mysqld[0x9b7de7]
/usr/sbin/mysqld[0x9aafdf]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f3bebfffb50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f3bea94395d]
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.
150624 05:23:54 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Vielen Dank für eure Hilfe
