Je n'arrive pas à relancer le service MySQL sur le serveur Debian

stefaan77 · 13-06-2018 10:54:37

Bonjour,

Ce matin j'ai la mauvaise surprise de trouver mon serveur Debian sans accès aux bases de données. Si je relance le service mySql il m'indique une erreur et je n'arrive pas à relancer. (petit détail supplémentaire, il semble que j'ai eu la visite de quelques IP chinoises que j'ai bloquée avant que cela ne fonctionne plus).

Voici les informations:

service mysql start

Job for mariadb.service failed. See 'systemctl status mariadb.service' and 'journalctl -xn' for details.

systemctl status mariadb.service

● mariadb.service - MariaDB database server

   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled)

  Drop-In: /run/systemd/generator/mysql.service.d

           └─50-mariadb-$database.conf

   Active: failed (Result: exit-code) since mer. 2018-06-13 10:47:20 CEST; 2min 34s ago

  Process: 2201 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)

  Process: 2119 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)

  Process: 2114 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)

  Process: 2113 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)

 Main PID: 2201 (code=exited, status=1/FAILURE)

   Status: "MariaDB server is down"

juin 13 10:47:14 monserver systemd[1]: Starting MariaDB database server...

juin 13 10:47:14 monserver mysqld[2201]: 2018-06-13 10:47:14 139821878537280 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name '...size' instead.

juin 13 10:47:14 monserver mysqld[2201]: 2018-06-13 10:47:14 139821878537280 [Note] /usr/sbin/mysqld (mysqld 10.1.26-MariaDB-0+deb9u1) starting as process 2201 ...

juin 13 10:47:20 monserver systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE

juin 13 10:47:20 monserver systemd[1]: Failed to start MariaDB database server.

juin 13 10:47:20 monserver systemd[1]: Unit mariadb.service entered failed state.

Hint: Some lines were ellipsized, use -l to show in full.

journalctl -xn

-- Logs begin at mer. 2018-06-13 09:25:21 CEST, end at mer. 2018-06-13 10:51:21 CEST. --

juin 13 10:51:17 monserver sshd[2242]: Failed password for root from 182.100.67.82 port 49620 ssh2

juin 13 10:51:20 monserver sshd[2242]: Failed password for root from 182.100.67.82 port 49620 ssh2

juin 13 10:51:20 monserver sshd[2242]: error: maximum authentication attempts exceeded for root from 182.100.67.82 port 49620 ssh2 [preauth]

juin 13 10:51:20 monserver sshd[2242]: Disconnecting: Too many authentication failures [preauth]

juin 13 10:51:20 monserver sshd[2242]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.100.67.82  user=root

juin 13 10:51:20 monserver sshd[2242]: PAM service(sshd) ignoring max retries; 6 > 3

juin 13 10:51:21 monserver sshd[2244]: rexec line 19: Deprecated option KeyRegenerationInterval

juin 13 10:51:21 monserver sshd[2244]: rexec line 20: Deprecated option ServerKeyBits

juin 13 10:51:21 monserver sshd[2244]: rexec line 31: Deprecated option RSAAuthentication

juin 13 10:51:21 monserver sshd[2244]: rexec line 38: Deprecated option RhostsRSAAuthentication

vdir /var/lib/mysql/

total 305588

drwxrwxrwx 2 mysql mysql     12288 juin   7 21:09 EB0077

-rwxrwxrwx 1 mysql mysql     16384 juin  13 11:00 aria_log.00000001

-rwxrwxrwx 1 mysql mysql        52 juin  13 11:00 aria_log_control

-rwxrwxrwx 1 root  root          0 avril 20 22:12 debian-10.1.flag

drwxrwxrwx 2 mysql mysql      4096 avril  3 11:31 onahf

-rwxrwxrwx 1 mysql mysql 211812352 juin  13 11:00 ibdata1

-rwxrwxrwx 1 mysql mysql  50331648 juin  13 07:27 ib_logfile0

-rwxrwxrwx 1 mysql mysql  50331648 juin  13 03:59 ib_logfile1

-rwxrwxrwx 1 mysql mysql         0 avril 20 22:12 multi-master.info

drwxrwxrwx 2 mysql mysql      4096 avril 20 22:12 mysql

-rwxrwxrwx 1 mysql mysql         6 oct.  22  2017 mysql_upgrade_info

drwxrwxrwx 2 mysql mysql      4096 avril 20 22:12 performance_schema

drwxrwxrwx 2 mysql mysql      4096 mars   4  2016 phpmyadmin

drwxrwxrwx 2 mysql mysql      4096 avril 20 22:14 postfixadmin

drwxrwxrwx 2 mysql mysql     16384 juin  21  2016 prestashop

drwxrwxrwx 2 mysql mysql     12288 mai    2 23:32 oiduts

drwxrwxrwx 2 mysql mysql     12288 avril 20 21:53 oiduts@002dbackup

-rwxrwxrwx 1 mysql mysql     24576 mai   22 16:32 tc.log

drwxrwxrwx 2 mysql mysql      4096 mars   4  2016 machin

Je rame complètement. Quelqu'un peut-il m'aider svp?

Merci d'avance

Dernière modification par stefaan77 (13-06-2018 12:36:51)

captnfab · 13-06-2018 12:07:05

Plop,

@stefaan77: quelque chose dans /var/log/mysql.err ou /var/log/mysql.log ?

(Et merci d'utiliser les balises [ code ] dans ton message, pour gagner en clarté

, édite ton message pour un exemple )

stefaan77 · 13-06-2018 12:40:29

Merci Captnfab,

dans /var/log/mysql j'ai ceci:

2018-06-13  7:28:00 139945476332608 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: Using Linux native AIO

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13  7:28:00 139945476332608 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13  7:28:01 139945476332608 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13  7:28:01 139945476332608 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13  7:28:01 139945476332608 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13  7:28:01 139945476332608 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13  7:28:01 139945476332608 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13  7:28:01 139945476332608 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13  9:14:01 140062745644096 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: Using Linux native AIO

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13  9:14:02 140062745644096 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13  9:14:03 140062745644096 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13  9:14:03 140062745644096 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13  9:14:03 140062745644096 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13  9:14:03 140062745644096 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13  9:14:03 140062745644096 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13  9:14:03 140062745644096 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13  9:14:03 140062745644096 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13  9:14:03 140062745644096 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13  9:16:53 140263207795776 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Using Linux native AIO

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13  9:16:53 140263207795776 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13  9:16:53 140263207795776 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13  9:16:53 140263207795776 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13  9:16:53 140263207795776 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13  9:16:53 140263207795776 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13  9:16:53 140263207795776 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13  9:20:59 140353830841408 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: Using Linux native AIO

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13  9:20:59 140353830841408 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13  9:21:00 140353830841408 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13  9:21:00 140353830841408 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13  9:21:00 140353830841408 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13  9:21:00 140353830841408 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13  9:21:00 140353830841408 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13  9:21:00 140353830841408 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13  9:21:00 140353830841408 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13  9:21:00 140353830841408 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13  9:25:26 139838482054208 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Using Linux native AIO

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13  9:25:26 139838482054208 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13  9:25:26 139838482054208 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13  9:25:26 139838482054208 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13  9:25:26 139838482054208 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13  9:25:26 139838482054208 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13  9:25:26 139838482054208 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 10:04:15 140238907391040 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Using Linux native AIO

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 10:04:15 140238907391040 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 10:04:15 140238907391040 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 10:04:15 140238907391040 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 10:04:15 140238907391040 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 10:04:15 140238907391040 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 10:04:15 140238907391040 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 10:08:55 140176055401536 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Using Linux native AIO

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 10:08:55 140176055401536 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 10:08:55 140176055401536 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 10:08:55 140176055401536 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 10:08:55 140176055401536 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 10:08:55 140176055401536 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 10:08:55 140176055401536 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 10:11:53 139899352779840 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Using Linux native AIO

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 10:11:53 139899352779840 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 10:11:53 139899352779840 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 10:11:53 139899352779840 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 10:11:53 139899352779840 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 10:11:53 139899352779840 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 10:11:53 139899352779840 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 10:47:14 139821878537280 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Using Linux native AIO

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 10:47:15 139821878537280 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 10:47:15 139821878537280 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 10:47:15 139821878537280 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 10:47:15 139821878537280 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 10:47:15 139821878537280 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 10:47:15 139821878537280 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 11:00:15 140644658240576 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Using Linux native AIO

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 11:00:15 140644658240576 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 11:00:15 140644658240576 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 11:00:15 140644658240576 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 11:00:15 140644658240576 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 11:00:15 140644658240576 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 11:00:15 140644658240576 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 11:07:56 140392795757632 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 11:07:56 140392795757632 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Using Linux native AIO

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 11:07:57 140392795757632 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 11:07:57 140392795757632 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 11:07:57 140392795757632 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 11:07:57 140392795757632 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 11:07:57 140392795757632 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 11:07:57 140392795757632 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 11:10:23 140325929368640 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Using Linux native AIO

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 11:10:23 140325929368640 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 11:10:23 140325929368640 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 11:10:23 140325929368640 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 11:10:23 140325929368640 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 11:10:23 140325929368640 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 11:10:23 140325929368640 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 11:20:59 140110484024384 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: Using Linux native AIO

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 11:20:59 140110484024384 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 11:21:00 140110484024384 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 11:21:00 140110484024384 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 11:21:00 140110484024384 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 11:21:00 140110484024384 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 11:21:00 140110484024384 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 11:21:00 140110484024384 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 11:24:34 140292517993536 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Using Linux native AIO

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 11:24:34 140292517993536 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 11:24:34 140292517993536 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 11:24:34 140292517993536 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 11:24:34 140292517993536 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 11:24:34 140292517993536 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 11:24:34 140292517993536 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

2018-06-13 12:13:49 139896012241984 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: Compressed tables use zlib 1.2.8

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: Using Linux native AIO

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: Using SSE crc32 instructions

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: Completed initialization of buffer pool

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-13 12:13:49 139896012241984 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32111417935

2018-06-13 12:13:50 139896012241984 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

InnoDB: Set innodb_force_recovery to ignore this error.

2018-06-13 12:13:50 139896012241984 [ERROR] Plugin 'InnoDB' init function returned error.

2018-06-13 12:13:50 139896012241984 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2018-06-13 12:13:50 139896012241984 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-13 12:13:50 139896012241984 [ERROR] Unknown/unsupported storage engine: InnoDB

2018-06-13 12:13:50 139896012241984 [ERROR] Aborting

Error in my_thread_global_end(): 1 threads didn't exit

Dernière modification par stefaan77 (13-06-2018 12:40:47)

captnfab · 13-06-2018 12:44:54

Dans ce sujet, on retrouve un message d'erreur similaire : https://serverfault.com/questions/37971 … ntu#597391

Tu peux essayer de faire un

mv /var/lib/mysql/ib_logfile{0,1} /var/tmp

Puis relancer le serveur mysql.

stefaan77 · 13-06-2018 13:51:25

çà ne fonctionne hélas pas. J'ai lu aussi l'autre article, j'ai même supprimé manuellement en accès ftp les fichiers mais çà ne marche pas encore.

J'ai toujours ceci après avoir rebooté le serveur aussi:

sudo service mysql restart

Job for mariadb.service failed. See 'systemctl status mariadb.service' and 'journalctl -xn' for details.

systemctl status mariadb.service -l

 

mariadb.service - MariaDB database server

   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled)

  Drop-In: /run/systemd/generator/mysql.service.d

           └─50-mariadb-$database.conf

   Active: activating (auto-restart) (Result: signal) since mer. 2018-06-13 14:48:43 CEST; 2s ago

  Process: 4055 ExecStartPost=/etc/mysql/debian-start (code=exited, status=203/EXEC)

  Process: 4025 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)

  Process: 3945 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)

  Process: 3939 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)

  Process: 3938 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)

 Main PID: 4025 (code=killed, signal=ABRT)

   Status: "Shutdown in progress"

juin 13 14:48:43 monserveur systemd[1]: mariadb.service: main process exited, code=killed, status=6/ABRT

juin 13 14:48:43 monserveur systemd[1]: Failed to start MariaDB database server.

juin 13 14:48:43 monserveur systemd[1]: Unit mariadb.service entered failed state.

Est-ce que si je tente de ré-installer mysql je perdrai mes bases de données et les utilisateurs? Sinon autan faire cela peut-être?

potemkine17 · 13-06-2018 21:08:40

Si le problème n'est toujours pas résolu, ce lien y aiderait-il ?
https://support.plesk.com/hc/en-us/arti … NE-failed-

mick621 · 13-06-2018 22:42:59

Bonsoir's,

De nos jour je ne sais pas si c'est la commande mysql est bonne pour mariadb (mysql est maintenant privé et mariaDB est open source).

Regarde sur le lien y a une commande pour mariaDB:
https://www.2daygeek.com/start-stop-res … in-linux/#

Par rapport à tes messages d'erreur, dans tes post, MariaDB est pour systemctl et ton serveur est en systemd chépa si les deux peuvent cohabiter ?

Fait tes sauvegardes de ta base de données surtout.

stefaan77 · 14-06-2018 00:02:32

mick621 a écrit :

Bonsoir's,

De nos jour je ne sais pas si c'est la commande mysql est bonne pour mariadb (mysql est maintenant privé et mariaDB est open source).

Regarde sur le lien y a une commande pour mariaDB:
https://www.2daygeek.com/start-stop-res … in-linux/#

Par rapport à tes messages d'erreur, dans tes post, MariaDB est pour systemctl et ton serveur est en systemd chépa si les deux peuvent cohabiter ?

Fait tes sauvegardes de ta base de données surtout.

Là où j'ai du mal à comprendre c'est que j'ai toujours utilisé "service mysql stop" et "service mysql start" ou restart jusqu'ici sans avoir le moindre soucis. Pourquoi ce matin cela ne fonctionne plus... Je n'ai pas changé de système entre deux à ma connaissance.

stefaan77 · 14-06-2018 00:04:25

Toujours la même erreur hélas

mick621 · 14-06-2018 01:02:52

Elle date de quand ta derniere sauvegarde ?

Y a un gars qui a résolu le meme problème que toi ici

merci Clark, qui a fait le travail de travailler. J'ai enlevé les dossiers de données et après j'ai couru l'installation fraîche de mariadb.

Merci,

alix

ré-édite
Répertoire de données par défaut pour MariaDB?
sauvegarde ton dossier data actuelle
Le chemin du repertoire, qui contiens tes bases, est indiqué, dans le fichier: /etc/mysql/my.cnf par la variable datadir (d’après le lien).

Si tu refais une installation 'fraîche" de MariaDB, tu n'aura plu qu'a replacer ton dossier data.

Dernière modification par mick621 (14-06-2018 01:41:08)

mick621 · 14-06-2018 02:11:25

stefaan77 a écrit :

(petit détail supplémentaire, il semble que j'ai eu la visite de quelques IP chinoises que j'ai bloquée avant que cela ne fonctionne plus).

Apres relecture, je m'aperçois que cette petite info peut être la cause de ton soucis ?
Remet comme avant ta manip, peut être que ta aussi blocker ip serveur, qui fessais partie de ta liste.

Debian-facile

#1 13-06-2018 10:54:37

Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#2 13-06-2018 12:07:05

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#3 13-06-2018 12:40:29

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#4 13-06-2018 12:44:54

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#5 13-06-2018 13:51:25

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#6 13-06-2018 21:08:40

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#7 13-06-2018 22:42:59

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#8 14-06-2018 00:02:32

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#9 14-06-2018 00:04:25

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#10 14-06-2018 01:02:52

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

#11 14-06-2018 02:11:25

Re : Je n'arrive pas à relancer le service MySQL sur le serveur Debian

Pied de page des forums