Moin,
habe die fliege Files, gestern lief noch alles gut.
Heute Morgen war der Metin2 Server down und MySQL wollte nicht mehr starten. Erst wollte er Rechte für Dateien, die hab ich ihm gegeben.
Ich habe nichts an der DB geändert außer das MySQL PW und Accounts / GM List.
Ich möchte MySQL nicht neu Installieren! Außer es bleibt mir wirklich keine andere Wahl.
Code
- 180309 08:49:48 mysqld_safe Logging to '/var/db/mysql/root602524.kms4.cc.err'.
- 180309 08:49:48 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
- 2018-03-09 08:49:49 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2018-03-09 08:49:49 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.39) starting as process 1437 ...
- 2018-03-09 08:49:49 1437 [Note] Plugin 'FEDERATED' is disabled.
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2018-03-09 08:49:49 1437 [Note] InnoDB: The InnoDB memory heap is disabled
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Memory barrier is not used
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Compressed tables use zlib 1.2.11
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Using CPU crc32 instructions
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Completed initialization of buffer pool
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Highest supported file format is Barracuda.
- 2018-03-09 08:49:49 1437 [Note] InnoDB: The log sequence numbers 1600637 and 1600637 in ibdata files do not match the log sequence number 1600647 in the ib_logfiles!
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Database was not shutdown normally!
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Starting crash recovery.
- 2018-03-09 08:49:49 1437 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2018-03-09 08:49:49 1437 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_worker_info uses space ID: 5 at filepath: ./mysql/slave_worker_info.ibd. Cannot open tablespace account/server_settings which uses space ID: 5 at filepath: ./account/server_settings.ibd
- 2018-03-09 08:49:49 803616000 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 ./account/server_settings.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.
- 180309 08:49:49 mysqld_safe mysqld from pid file /var/db/mysql/root602524.kms4.cc.pid ended
