[FAIL... Failed! MYSQL szerver indítása meghiúsul?

Sziasztok!

FAILED hibaüzenettel meghiúsul a mysql szerver indítása.

Köszönöm előre is a válaszokat.

MYSQL log:

"Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 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.

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 0 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --slow-query-log is not set

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5010)

Nov 1 20:32:44 mysqld:

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5010)

Nov 1 20:32:44 mysqld:

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Warning] Buffered warning: Changed limits: max_connections: 214 (requested 1000)

Nov 1 20:32:44 mysqld:

Nov 1 20:32:44 mysqld:

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Warning] Buffered warning: Changed limits: table_cache: 400 (requested 2000)

Nov 1 20:32:44 mysqld:

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Warning] Buffered warning: Changed limits: max_connections: 214 (requested 1000)

Nov 1 20:32:44 mysqld:

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Warning] Buffered warning: Changed limits: table_cache: 400 (requested 2000)

Nov 1 20:32:44 mysqld:

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] Plugin 'FEDERATED' is disabled.

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] Plugin 'FEDERATED' is disabled.

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Using atomics to ref count buffer pool pages

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: The InnoDB memory heap is disabled

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Using atomics to ref count buffer pool pages

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: The InnoDB memory heap is disabled

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Compressed tables use zlib 1.2.7

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Using Linux native AIO

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Compressed tables use zlib 1.2.7

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Using Linux native AIO

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Using CPU crc32 instructions

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Using CPU crc32 instructions

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Initializing buffer pool, size = 8.0G

Nov 1 20:32:44 mysqld: 2016-11-01 20:32:44 6189 [Note] InnoDB: Initializing buffer pool, size = 8.0G

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Completed initialization of buffer pool

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Completed initialization of buffer pool

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Highest supported file format is Barracuda.

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Highest supported file format is Barracuda.

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Log scan progressed past the checkpoint lsn 193635872268

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Database was not shutdown normally!

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Log scan progressed past the checkpoint lsn 193635872268

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Database was not shutdown normally!

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Starting crash recovery.

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Reading tablespace information from the .ibd files...

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Starting crash recovery.

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [Note] InnoDB: Reading tablespace information from the .ibd files...

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace teszt2/lineo_sessions uses space ID: 73 at filepath: ./teszt2/lineo_sessions.ibd. Cannot open tablespace oldal/ratings which uses space ID: 73 at filepath: ./oldal/rating

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 32d4a764720 InnoDB: Operating system error number 2 in a file operation.

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 6189 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace teszt2/lineo_sessions uses space ID: 73 at filepath: ./teszt2/lineo_sessions.ibd. Cannot open tablespace oldal/ratings which uses space ID: 73 at filepath: ./oldal/rating

Nov 1 20:32:45 mysqld: 2016-11-01 20:32:45 32d4a764720 InnoDB: Operating system error number 2 in a file operation.

Nov 1 20:32:45 mysqld: InnoDB: The error means the system cannot find the path specified.

Nov 1 20:32:45 mysqld: InnoDB: If you are installing InnoDB, remember that you must create

Nov 1 20:32:45 mysqld: InnoDB: directories yourself, InnoDB does not create them.

Nov 1 20:32:45 mysqld: InnoDB: Error: could not open single-table tablespace file ./oldal/ratings.ibd

Nov 1 20:32:45 mysqld: InnoDB: We do not continue the crash recovery, because the table may become

Nov 1 20:32:45 mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.

Nov 1 20:32:45 mysqld: InnoDB: To fix the problem and start mysqld:

Nov 1 20:32:45 mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot

Nov 1 20:32:45 mysqld: InnoDB: open the file, you should modify the permissions.

Nov 1 20:32:45 mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,

Nov 1 20:32:45 mysqld: InnoDB: The error means the system cannot find the path specified.

Nov 1 20:32:45 mysqld: InnoDB: If you are installing InnoDB, remember that you must create

Nov 1 20:32:45 mysqld: InnoDB: directories yourself, InnoDB does not create them.

Nov 1 20:32:45 mysqld: InnoDB: Error: could not open single-table tablespace file ./oldal/ratings.ibd

Nov 1 20:32:45 mysqld: InnoDB: We do not continue the crash recovery, because the table may become

Nov 1 20:32:45 mysqld: InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.

Nov 1 20:32:45 mysqld: InnoDB: To fix the problem and start mysqld:

Nov 1 20:32:45 mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot

Nov 1 20:32:45 mysqld: InnoDB: open the file, you should modify the permissions.

Nov 1 20:32:45 mysqld: InnoDB: 2) If the table is not needed, or you can restore it from a backup,

Nov 1 20:32:45 mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal

Nov 1 20:32:45 mysqld: InnoDB: crash recovery and ignore that table.

Nov 1 20:32:45 mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove

Nov 1 20:32:45 mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf

Nov 1 20:32:45 mysqld: InnoDB: and force InnoDB to continue crash recovery here.

Nov 1 20:32:45 mysqld: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal

Nov 1 20:32:45 mysqld: InnoDB: crash recovery and ignore that table.

Nov 1 20:32:45 mysqld: InnoDB: 3) If the file system or the disk is broken, and you cannot remove

Nov 1 20:32:45 mysqld: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf

Nov 1 20:32:45 mysqld: InnoDB: and force InnoDB to continue crash recovery here.

Nov 1 20:32:45 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended

Nov 1 20:32:45 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended

Nov 1 20:32:58 /etc/init.d/mysql[6383]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in

Nov 1 20:32:58 /etc/init.d/mysql[6383]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed

Nov 1 20:32:58 /etc/init.d/mysql[6383]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in

Nov 1 20:32:58 /etc/init.d/mysql[6383]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed

Nov 1 20:32:58 /etc/init.d/mysql[6383]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'

Nov 1 20:32:58 /etc/init.d/mysql[6383]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

Nov 1 20:32:58 /etc/init.d/mysql[6383]:

Nov 1 20:32:58 /etc/init.d/mysql[6383]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'

Nov 1 20:32:58 /etc/init.d/mysql[6383]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!"