Bonjour,
J'essaie depuis 2 jours de démarrer mariadb et il me dit que

Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.

du coup je aller voir dans/var/log/mysql/error.log et il m'indique que InnoDB is unsupported en m'affichant ces erreurs :

2018-05-30 14:50:55 139795396121152 [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-05-30 14:50:55 139795396121152 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-05-30 14:50:55 139795396121152 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-30 14:50:55 139795396121152 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-30 14:50:55 139795396121152 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-05-30 14:50:55 139795396121152 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-05-30 14:50:55 139795396121152 [Note] InnoDB: Using Linux native AIO
2018-05-30 14:50:55 139795396121152 [Note] InnoDB: Using SSE crc32 instructions
2018-05-30 14:50:55 139795396121152 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-05-30 14:50:55 139795396121152 [Note] InnoDB: Completed initialization of buffer pool
2018-05-30 14:50:55 139795396121152 [Note] InnoDB: Restoring page 0 of tablespace 0
2018-05-30 14:50:55 139795396121152 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2018-05-30 14:50:55 139795396121152 [ERROR] InnoDB: space header page consists of zero bytes in data file ./ibdata1
2018-05-30 14:50:55 139795396121152 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2018-05-30 14:50:55 139795396121152 [ERROR] Plugin 'InnoDB' init function returned error.
2018-05-30 14:50:55 139795396121152 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-05-30 14:50:55 139795396121152 [Note] Plugin 'FEEDBACK' is disabled.
2018-05-30 14:50:55 139795396121152 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-05-30 14:50:55 139795396121152 [ERROR] Aborting

Du coup quelqun aurai une piste ? je suis sur debian 9

3 réponses


Un pb de logfile ? , voir ce post

voir aussi le première ligne qui explique pourquoi il est passé sur Innodb

2018-05-30 14:50:55 139795396121152 [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.
Microse
Auteur

eum plus de id_logfile mais toujours les même erreurs...