[SOLVED] New mysql 5.7 doesn't start

nbd · 2016-02-19 13:32:13

I just upgraded mysql to version 5.7 and it doesn't start. mysql_error.log contains the following:

2016-02-19T13:33:26.793402Z 0 [ERROR] Plugin keyring_file reported: 'keyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets provided'
2016-02-19T13:33:26.794998Z 0 [Note] InnoDB: PUNCH HOLE support available
2016-02-19T13:33:26.795085Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-02-19T13:33:26.795112Z 0 [Note] InnoDB: Uses event mutexes
2016-02-19T13:33:26.795136Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2016-02-19T13:33:26.795158Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-02-19T13:33:26.795180Z 0 [Note] InnoDB: Using Linux native AIO
2016-02-19T13:33:26.795877Z 0 [Note] InnoDB: Number of pools: 1
2016-02-19T13:33:26.796223Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2016-02-19T13:33:26.860832Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2016-02-19T13:33:26.890268Z 0 [Note] InnoDB: Completed initialization of buffer pool
2016-02-19T13:33:26.894951Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2016-02-19T13:33:26.913614Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2016-02-19T13:33:27.008700Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2016-02-19T13:33:27.008792Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2016-02-19T13:33:27.008836Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2016-02-19T13:33:27.008868Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './RCorp/block_lexem.ibd' OS error: 71

What can this mean? The previous version has been starting flawlessly.

EDIT:

The cause of the problem was this:

2016-02-19T13:33:27.667146Z 0 [ERROR] unknown variable 'myisam-recover=BACKUP'

Last edited by nbd (2016-02-19 14:00:53)

WorMzy · 2016-02-19 13:36:49

Mod note: moving to AUR issues.

Arch Linux

#1 2016-02-19 13:32:13

[SOLVED] New mysql 5.7 doesn't start

#2 2016-02-19 13:36:49

Re: [SOLVED] New mysql 5.7 doesn't start

Board footer