Отвалилась база данных

[zharinov]

Пару недель назад перенес сюда на стартовый тариф VDS Старт штук 6 сайтов на Друпале,
Все работало нормально, внезапно вчера на всех перестала грузится база данных,
и смена тарифа вообще никак не помогла.

Что подсказывает гугл - не помогает.

Как найти причину, что делать?

---------------------------

PDOException: SQLSTATE[HY000] [2002] Connection refused in lock_may_be_available() (line 167 of /home/admin/web/MYDOMEN.ru/public_html/includes/lock.inc).

[Art.i]

Что говорит база при запуске? Какие ошибки?
команды

Код: выделить все

service mysql restart
service mysqld restart
systemctl restart mariadb

Что в логах базы?

Проверьте свободное место и инноды на сервере
команды

Код: выделить все

df -h
df -i

UP: поправил команду

[zharinov]

Что говорит база при запуске? Какие ошибки?
команды

Код: выделить все

service mysql restart
service mysqld restart
systemctl mariadb restart

Что в логах базы?

Проверьте свободное место и инноды на сервере
команды

Код: выделить все

df -h
df -i

2017-06-02_09-31-51.png (13.55 KiB) Просмотров: 12274

[Art.i]

Пришлите вывод команды

Код: выделить все

/usr/bin/mysqld_safe

[zharinov]

Пришлите вывод команды

Код: выделить все

/usr/bin/mysqld_safe

2017-06-02_12-43-14.png (5.78 KiB) Просмотров: 12265

170602 5:33:09 [ERROR] Cannot find or open table admin_zerkal/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:09 [ERROR] Cannot find or open table admin_zerkal/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:09 [ERROR] Cannot find or open table admin_zerkal/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:09 [ERROR] Cannot find or open table admin_zerkal/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:09 [ERROR] Cannot find or open table admin_zerkal/cache from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:09 [ERROR] Cannot find or open table admin_zerkal/system from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:09 [ERROR] Cannot find or open table admin_zerkal/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:09 [ERROR] Cannot find or open table admin_zerkal/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:41 [ERROR] Cannot find or open table admin_terror/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:41 [ERROR] Cannot find or open table admin_terror/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:41 [ERROR] Cannot find or open table admin_terror/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:41 [ERROR] Cannot find or open table admin_terror/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:41 [ERROR] Cannot find or open table admin_terror/cache from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:41 [ERROR] Cannot find or open table admin_terror/system from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:41 [ERROR] Cannot find or open table admin_terror/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:33:41 [ERROR] Cannot find or open table admin_terror/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:34:19 InnoDB: Error creating file './admin_terror/access.ibd'.
170602 5:34:19 InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... codes.html
InnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file './admin_terror/access.ibd'
InnoDB: under the 'datadir' of MySQL.
170602 5:34:32 [ERROR] Cannot find or open table admin_terror/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:34:32 [ERROR] Cannot find or open table admin_terror/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:34:32 [ERROR] Cannot find or open table admin_terror/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:34:32 [ERROR] Cannot find or open table admin_terror/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:34:32 [ERROR] Cannot find or open table admin_terror/cache from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:34:32 [ERROR] Cannot find or open table admin_terror/system from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:34:32 [ERROR] Cannot find or open table admin_terror/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:34:32 [ERROR] Cannot find or open table admin_terror/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:34:48 InnoDB: Error creating file './admin_terror/access.ibd'.
170602 5:34:48 InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... codes.html
InnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file './admin_terror/access.ibd'
InnoDB: under the 'datadir' of MySQL.
170602 5:35:47 InnoDB: Error: table 'admin_terror/access'
InnoDB: in InnoDB data dictionary has tablespace id 809,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./admin_terror/access.ibd and id 811, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... adict.html
InnoDB: for how to resolve the issue.
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table `admin_terror`.`access`.
170602 5:36:28 InnoDB: Warning: trying to init to the tablespace memory cache
InnoDB: a tablespace 816 of name './admin_terror/access.ibd',
InnoDB: but a tablespace 811 of the same name
InnoDB: already exists in the tablespace memory cache!
InnoDB: We assume that InnoDB did a crash recovery, and you had
InnoDB: an .ibd file for which the table did not exist in the
InnoDB: InnoDB internal data dictionary in the ibdata files.
InnoDB: We assume that you later removed the .ibd and .frm files,
InnoDB: and are now trying to recreate the table. We now remove the
InnoDB: conflicting tablespace object from the memory cache and try
InnoDB: the init again.
170602 5:36:43 [ERROR] Cannot find or open table admin_terror/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:36:43 [ERROR] Cannot find or open table admin_terror/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:37:15 InnoDB: Error: table `admin_unoduo`.`actions` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
170602 5:37:15 InnoDB: Error creating file './admin_unoduo/actions.ibd'.
170602 5:37:15 InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... codes.html
InnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file './admin_unoduo/actions.ibd'
InnoDB: under the 'datadir' of MySQL.
170602 5:37:50 [ERROR] Cannot find or open table admin_zerkal/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:37:50 [ERROR] Cannot find or open table admin_zerkal/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:37:50 [ERROR] Cannot find or open table admin_zerkal/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:37:50 [ERROR] Cannot find or open table admin_zerkal/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:37:50 [ERROR] Cannot find or open table admin_zerkal/cache from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:37:50 [ERROR] Cannot find or open table admin_zerkal/system from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:37:50 [ERROR] Cannot find or open table admin_zerkal/cache_bootstrap from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:37:50 [ERROR] Cannot find or open table admin_zerkal/semaphore from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
how you can resolve the problem.

170602 5:38:06 InnoDB: Error: table `admin_zerkal`.`actions` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... oting.html
170602 5:38:06 InnoDB: Error creating file './admin_zerkal/actions.ibd'.
170602 5:38:06 InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... codes.html
InnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file './admin_zerkal/actions.ibd'
InnoDB: under the 'datadir' of MySQL.
170602 06:20:35 mysqld_safe Number of processes running now: 0
170602 06:20:35 mysqld_safe mysqld restarted
170602 6:20:36 [Note] /usr/libexec/mysqld (mysqld 5.5.52-MariaDB) starting as process 19223 ...
170602 6:20:36 InnoDB: The InnoDB memory heap is disabled
170602 6:20:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170602 6:20:36 InnoDB: Compressed tables use zlib 1.2.7
170602 6:20:36 InnoDB: Using Linux native AIO
170602 6:20:36 InnoDB: Initializing buffer pool, size = 128.0M
170602 6:20:36 InnoDB: Completed initialization of buffer pool
170602 6:20:36 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
170602 6:20:36 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: trying to add tablespace 14 of name './roundcube/cache_index.ibd'
InnoDB: to the tablespace memory cache, but tablespace
InnoDB: 14 of name './admin_dom74/block.ibd' already exists in the tablespace
InnoDB: memory cache!
170602 06:20:37 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
170602 07:07:42 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170602 7:07:42 [Note] /usr/libexec/mysqld (mysqld 5.5.52-MariaDB) starting as process 21567 ...
170602 7:07:42 InnoDB: The InnoDB memory heap is disabled
170602 7:07:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170602 7:07:42 InnoDB: Compressed tables use zlib 1.2.7
170602 7:07:42 InnoDB: Using Linux native AIO
170602 7:07:42 InnoDB: Initializing buffer pool, size = 128.0M
170602 7:07:42 InnoDB: Completed initialization of buffer pool
170602 7:07:42 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
170602 7:07:42 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: trying to add tablespace 14 of name './roundcube/cache_index.ibd'
InnoDB: to the tablespace memory cache, but tablespace
InnoDB: 14 of name './admin_dom74/block.ibd' already exists in the tablespace
InnoDB: memory cache!
170602 07:07:46 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
170602 07:18:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170602 7:18:01 [Note] /usr/libexec/mysqld (mysqld 5.5.52-MariaDB) starting as process 22456 ...
170602 7:18:01 InnoDB: The InnoDB memory heap is disabled
170602 7:18:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170602 7:18:01 InnoDB: Compressed tables use zlib 1.2.7
170602 7:18:01 InnoDB: Using Linux native AIO
170602 7:18:01 InnoDB: Initializing buffer pool, size = 128.0M
170602 7:18:01 InnoDB: Completed initialization of buffer pool
170602 7:18:01 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
170602 7:18:01 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: trying to add tablespace 14 of name './roundcube/cache_index.ibd'
InnoDB: to the tablespace memory cache, but tablespace
InnoDB: 14 of name './admin_dom74/block.ibd' already exists in the tablespace
InnoDB: memory cache!
170602 07:18:01 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended

[Art.i]

У вас побились таблицы формата Innodb.
Вот хорошая инструкция как восстановить такие таблицы:
https://habrahabr.ru/company/kingservers/blog/257627/

Если у вас есть бэкапы баз и потеря последних данных вам не критична, то можно просто удалить/перенести файлы
/var/lib/mysql/ibdata1
/var/lib/mysql/ib_logfile0
/var/lib/mysql/ib_logfile1
Запустить MySQL и восстановить базы из бэкапов.