ich versuche ein XAMPP mit PHP 7.3.1 zu starten, der Apache läuft, aber die MySQL Datenbank startet nicht:
von der Konsole über versuche ich es gerade mit
sudo /Applications/XAMPP/xamppfiles/sbin/mysqld
u.a. mit diesen Fehlern.
- Code: Select all
2019-02-19 9:32:16 4588156352 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.37-MariaDB) starting as process 52853 ...
2019-02-19 9:32:16 4588156352 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2019-02-19 9:32:16 4588156352 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-02-19 9:32:16 4588156352 [Note] InnoDB: The InnoDB memory heap is disabled
2019-02-19 9:32:16 4588156352 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-02-19 9:32:16 4588156352 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-02-19 9:32:16 4588156352 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-02-19 9:32:16 4588156352 [Note] InnoDB: Using SSE crc32 instructions
2019-02-19 9:32:16 4588156352 [Note] InnoDB: Initializing buffer pool, size = 32.0M
2019-02-19 9:32:16 4588156352 [Note] InnoDB: Completed initialization of buffer pool
2019-02-19 9:32:16 4588156352 [Note] InnoDB: Highest supported file format is Barracuda.
2019-02-19 9:32:16 4588156352 [Note] InnoDB: The log sequence number 1762733 in ibdata file do not match the log sequence number 1765988 in the ib_logfiles!
2019-02-19 9:32:16 4588156352 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace phpmyadmin/pma__column_info uses space ID: 5 at filepath: ./phpmyadmin/pma__column_info.ibd. Cannot open tablespace mysql/slave_worker_info which uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd
2019-02-19 09:32:16 11179b5c0 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.
InnoDB: Error: could not open single-table tablespace file ./mysql/slave_worker_info.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
190219 9:32:16 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 10.1.37-MariaDB
key_buffer_size=33554432
read_buffer_size=262144
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 153427 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 = 0x0 thread_stack 0x48400
0 mysqld 0x00000001067493cd my_print_stacktrace + 61
0 mysqld 0x00000001060abbed handle_fatal_signal + 685
0 libsystem_platform.dylib 0x00007fff7f4edb3d _sigtramp + 29
0 ??? 0x00000001117037c7 0x0 + 4587534279
0 libsystem_c.dylib 0x00007fff7f3ab1c9 abort + 127
0 mysqld 0x00000001065bc9d3 _Z33fil_load_single_table_tablespacesPFmPKcS0_E + 5987
0 mysqld 0x0000000106663abd _Z40recv_recovery_from_checkpoint_start_funcmyy + 3085
0 mysqld 0x00000001066ec2f1 _Z34innobase_start_or_create_for_mysqlv + 4721
0 mysqld 0x0000000106610596 _ZL13innobase_initPv + 3430
0 mysqld 0x00000001060acb0e _Z24ha_initialize_handlertonP13st_plugin_int + 94
0 mysqld 0x0000000106291f2f _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 335
0 mysqld 0x0000000106291be9 _Z11plugin_initPiPPci + 2857
0 mysqld 0x000000010619eb0c _ZL22init_server_componentsv + 1948
0 mysqld 0x000000010619ccdb _Z11mysqld_mainiPPc + 11355
0 libdyld.dylib 0x00007fff7f302ed9 start + 1
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.
Abort trap: 6
was kann ich hier tun?
Danke
Mark