Hello,
please help.
please help.
PS: I speak CzechQuote:
140501 11:01:48 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2014-05-01 11:01:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-05-01 11:01:48 11832 [Note] Plugin 'FEDERATED' is disabled.
2014-05-01 11:01:48 11832 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-05-01 11:01:48 11832 [Note] InnoDB: The InnoDB memory heap is disabled
2014-05-01 11:01:48 11832 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-05-01 11:01:48 11832 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-05-01 11:01:48 11832 [Note] InnoDB: Using CPU crc32 instructions
2014-05-01 11:01:49 11832 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-05-01 11:01:49 11832 [Note] InnoDB: Completed initialization of buffer pool
2014-05-01 11:01:49 11832 [Note] InnoDB: Highest supported file format is Barracuda.
2014-05-01 11:01:49 11832 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2014-05-01 11:01:49 11832 [Note] InnoDB: Database was not shutdown normally!
2014-05-01 11:01:49 11832 [Note] InnoDB: Starting crash recovery.
2014-05-01 11:01:49 11832 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-05-01 11:01:49 802807400 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_index_stats.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.
140501 11:01:49 mysqld_safe mysqld from pid file /var/db/mysql/freya.pid ended