MariaDB ne démarre pas

Tags: #<Tag:0x00007f78b93b9a28>

Bonsoir,
Quand j’essayé de démarré mariaDB une erreur se produit j’ai pu trouvé ceci

Nov  9 22:02:54 vps669185 systemd[1]: Starting MariaDB 10.1.41 database server...
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] /usr/sbin/mysqld (mysqld 10.1.41-MariaDB-0+deb9u1) starting as process 13569 ...
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [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.
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: The InnoDB memory heap is disabled
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: Compressed tables use zlib 1.2.8
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: Using Linux native AIO
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: Using SSE crc32 instructions
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: Completed initialization of buffer pool
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: Highest supported file format is Barracuda.
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: 128 rollback segment(s) are active.
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB: Waiting for purge to start
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.44-86.0 started; log sequence number 12989957446
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140066932389632 [Note] InnoDB: Dumping buffer pool(s) not yet started
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] Plugin 'FEEDBACK' is disabled.
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [Note] Recovering after a crash using tc.log
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [ERROR] Can't init tc log
Nov  9 22:02:55 vps669185 mysqld[13569]: 2019-11-09 22:02:55 140067539125376 [ERROR] Aborting
Nov  9 22:02:58 vps669185 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Nov  9 22:02:58 vps669185 systemd[1]: Failed to start MariaDB 10.1.41 database server.
Nov  9 22:02:58 vps669185 systemd[1]: mariadb.service: Unit entered failed state.
Nov  9 22:02:58 vps669185 systemd[1]: mariadb.service: Failed with result 'exit-code'.

Que faire ?

Un peu de lecture en cherchant sur “[ERROR] Can’t init tc log”, et j’ai vu 2 suggestions:

Déja fait
Et je vais tester la deuxième technique

J’ai des nouveaux fichiers je dois ouvrir le quelle ?
Screen