Hallo, ich habe die Files gedownloadet und installiert. Alles klappte bis ich den mysql.tar.gz entpackt habe. seitdem bekomme ich eine große error liste und ich kann die mysql nicht mehr starten. wenn ich sie Starte, beendet sie sich automatisch wieder
Code
- 170519 16:41:16 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
- 2017-05-19 16:41:18 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2017-05-19 16:41:18 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
- 2017-05-19 16:41:18 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.34) starting as process 953 ...
- 2017-05-19 16:41:18 953 [Note] Plugin 'FEDERATED' is disabled.
- 2017-05-19 16:41:18 953 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2017-05-19 16:41:18 953 [Note] InnoDB: The InnoDB memory heap is disabled
- 2017-05-19 16:41:18 953 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2017-05-19 16:41:18 953 [Note] InnoDB: Memory barrier is not used
- 2017-05-19 16:41:18 953 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2017-05-19 16:41:18 953 [Note] InnoDB: Using CPU crc32 instructions
- 2017-05-19 16:41:18 953 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2017-05-19 16:41:18 953 [Note] InnoDB: Completed initialization of buffer pool
- 2017-05-19 16:41:18 953 [Note] InnoDB: Highest supported file format is Barracuda.
- 2017-05-19 16:41:18 953 [Note] InnoDB: The log sequence numbers 1669497 and 1669497 in ibdata files do not match the log sequence number 1669507 in the ib_logfiles!
- 2017-05-19 16:41:18 953 [Note] InnoDB: Database was not shutdown normally!
- 2017-05-19 16:41:18 953 [Note] InnoDB: Starting crash recovery.
- 2017-05-19 16:41:18 953 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2017-05-19 16:41:18 953 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace log/okay_event uses space ID: 5 at filepath: ./log/okay_event.ibd. Cannot open tablespace mysql/slave_worker_info which uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd
- 2017-05-19 16:41:18 802807400 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.
- 170519 16:41:18 mysqld_safe mysqld from pid file /var/db/mysql/syserr.pid ended
