sept. 15 19:06:50 vps301757.ovh.net systemd[1]: Starting MariaDB 10.1.36 database server...
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] Using unique option prefix 'character_set_client' is error-prone and can break in the future. Please use the full name 'character-set-client-handshake' instead.
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Warning] /usr/bin/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'utf8'
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] /usr/bin/mysqld (mysqld 10.1.36-MariaDB) starting as process 363 ...
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [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.
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] InnoDB: Using mutexes to ref count buffer pool pages
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] InnoDB: The InnoDB memory heap is disabled
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] InnoDB: Compressed tables use zlib 1.2.11
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] InnoDB: Using Linux native AIO
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] InnoDB: Using SSE crc32 instructions
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] InnoDB: Initializing buffer pool, size = 128.0M
sept. 15 19:06:51 vps301757.ovh.net mysqld[363]: 2018-09-15 19:06:51 108700891013056 [Note] InnoDB: Completed initialization of buffer pool
sept. 15 19:08:21 vps301757.ovh.net systemd[1]: mariadb.service: Start operation timed out. Terminating.
sept. 15 19:09:51 vps301757.ovh.net systemd[1]: mariadb.service: State 'stop-sigterm' timed out. Skipping SIGKILL.
sept. 15 19:11:21 vps301757.ovh.net systemd[1]: mariadb.service: State 'stop-final-sigterm' timed out. Skipping SIGKILL. Entering failed mode.
sept. 15 19:11:21 vps301757.ovh.net systemd[1]: mariadb.service: Failed with result 'timeout'.
sept. 15 19:11:21 vps301757.ovh.net systemd[1]: Failed to start MariaDB 10.1.36 database server.
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: 2018-09-15 19:12:58 108700891013056 [Note] InnoDB: Highest supported file format is Barracuda.
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: 2018-09-15 19:12:58 108700891013056 [Note] InnoDB: Read redo log up to LSN=685190144
sept. 15 19:12:58 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 363, but reception only permitted for main PID which is currently not known
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: 2018-09-15 19:12:58 108700891013056 [ERROR] mysqld: Can't create/write to file '/tmp/ib5gVV6N' (Errcode: 2 "No such file or directory")
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: 2018-09-15 19:12:58 62dce5fedfc0 InnoDB: Error: unable to create temporary file; errno: 2
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: 2018-09-15 19:12:58 62dce5fedfc0 InnoDB: Assertion failure in thread 108700891013056 in file dict0dict.cc line 1089
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: Failing assertion: dict_foreign_err_file
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: We intentionally generate a memory trap.
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: If you get repeated assertion failures or crashes, even
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: immediately after the mysqld startup, there may be
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: corruption in the InnoDB tablespace. Please refer to
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: about forcing recovery.
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: 180915 19:12:58 [ERROR] mysqld got signal 6 ;
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: This could be because you hit a bug. It is also possible that this binary
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: or one of the libraries it was linked against is corrupt, improperly built,
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: or misconfigured. This error can also be caused by malfunctioning hardware.
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: We will try our best to scrape up some info that will hopefully help
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: diagnose the problem, but since we have already crashed,
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: something is definitely wrong and this may fail.
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: Server version: 10.1.36-MariaDB
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: key_buffer_size=16777216
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: read_buffer_size=262144
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: max_used_connections=0
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: max_threads=153
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: thread_count=0
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: It is possible that mysqld could use up to
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137052 K bytes of memory
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: Hope that's ok; if not, decrease some variables in the equation.
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: Thread pointer: 0x0
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: Attempting backtrace. You can use the following information to find out
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: where mysqld died. If you see no messages after this, something went
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: terribly wrong...
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: stack_bottom = 0x0 thread_stack 0x48400
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(my_print_stacktrace+0x2f)[0xa3845b92bdf]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(handle_fatal_signal+0x586)[0xa38456e4756]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: sigaction.c:0(__restore_rt)[0x62dce6a3e3c0]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: :0(__GI_raise)[0x62dce658bd7f]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: :0(__GI_abort)[0x62dce6576672]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(+0x98d189)[0xa3845ade189]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(+0x984880)[0xa3845ad5880]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(+0x8fa321)[0xa3845a4b321]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(+0x809dff)[0xa384595adff]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x6d)[0xa38456e68cd]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(+0x412e38)[0xa3845563e38]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(_Z11plugin_initPiPPci+0x983)[0xa3845565003]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(+0x36d3c0)[0xa38454be3c0]
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(_Z11mysqld_mainiPPc+0x1b2e)[0xa38454c1e0e]
sept. 15 19:12:59 vps301757.ovh.net mysqld[363]: /usr/lib/libc.so.6(__libc_start_main+0xf3)[0x62dce6578223]
sept. 15 19:12:59 vps301757.ovh.net mysqld[363]: /usr/bin/mysqld(_start+0x2e)[0xa38454b592e]
sept. 15 19:12:59 vps301757.ovh.net mysqld[363]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
sept. 15 19:12:59 vps301757.ovh.net mysqld[363]: information that should help you find out what is causing the crash
Dernière modification par Sirilldu le mar. 18 sept. 2018, 15:12, modifié 1 fois.
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: 2018-09-15 19:12:58 108700891013056 [ERROR] mysqld: Can't create/write to file '/tmp/ib5gVV6N' (Errcode: 2 "No such file or directory")
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: 2018-09-15 19:12:58 62dce5fedfc0 InnoDB: Error: unable to create temporary file; errno: 2
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: 2018-09-15 19:12:58 62dce5fedfc0 InnoDB: Assertion failure in thread 108700891013056 in file dict0dict.cc line 1089
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: Failing assertion: dict_foreign_err_file
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: We intentionally generate a memory trap.
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: If you get repeated assertion failures or crashes, even
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: immediately after the mysqld startup, there may be
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: corruption in the InnoDB tablespace. Please refer to
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
sept. 15 19:12:58 vps301757.ovh.net mysqld[363]: InnoDB: about forcing recovery.
Ça vient de là a priori... Il y a un problème au niveau du répertoire /tmp (mysql va tenter d'écrire dans le répertoire défini dans /etc/mysql/my.cnf au niveau de la directive tmpdir, /tmp par défaut), qui n'a pas l'air accessible (problème de montage, d'espace, de permissions... ?).
«The following statement is not true. The previous statement is true.»
$ journalctl -u mariadb
-- Reboot --
sept. 17 21:13:31 vps301757.ovh.net systemd[1]: Starting MariaDB 10.1.36 database server...
sept. 17 21:13:32 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:32 118824419762112 [Note] Using unique option prefix 'character_set_client' is error-prone and can break in the future. Please use the full name 'character-set-client-handshake' instead.
sept. 17 21:13:32 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:32 118824419762112 [Warning] /usr/bin/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'utf8'
sept. 17 21:13:32 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:32 118824419762112 [Note] /usr/bin/mysqld (mysqld 10.1.36-MariaDB) starting as process 347 ...
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [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.
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [Note] InnoDB: Using mutexes to ref count buffer pool pages
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [Note] InnoDB: The InnoDB memory heap is disabled
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [Note] InnoDB: Compressed tables use zlib 1.2.11
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [Note] InnoDB: Using Linux native AIO
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [Note] InnoDB: Using SSE crc32 instructions
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [Note] InnoDB: Initializing buffer pool, size = 128.0M
sept. 17 21:13:33 vps301757.ovh.net mysqld[347]: 2018-09-17 21:13:33 118824419762112 [Note] InnoDB: Completed initialization of buffer pool
sept. 17 21:15:02 vps301757.ovh.net systemd[1]: mariadb.service: Start operation timed out. Terminating.
sept. 17 21:16:32 vps301757.ovh.net systemd[1]: mariadb.service: State 'stop-sigterm' timed out. Skipping SIGKILL.
sept. 17 21:18:03 vps301757.ovh.net systemd[1]: mariadb.service: State 'stop-final-sigterm' timed out. Skipping SIGKILL. Entering failed mode.
sept. 17 21:18:03 vps301757.ovh.net systemd[1]: mariadb.service: Failed with result 'timeout'.
sept. 17 21:18:03 vps301757.ovh.net systemd[1]: Failed to start MariaDB 10.1.36 database server.
sept. 17 21:20:46 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:46 118824419762112 [Note] InnoDB: Highest supported file format is Barracuda.
sept. 17 21:20:46 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:46 118824419762112 [Note] InnoDB: Read redo log up to LSN=686263296
sept. 17 21:20:46 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: InnoDB: Transaction 1347941 was in the XA prepared state.
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118824419762112 [ERROR] InnoDB: Failed to find tablespace for table '"freshrss"."freshrss_entrytmp"' in the cache. Attempting to load the tablespace with space id 416.
sept. 17 21:20:47 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118824419762112 [ERROR] InnoDB: Failed to find tablespace for table '"freshrss"."freshrss_entry"' in the cache. Attempting to load the tablespace with space id 495.
sept. 17 21:20:47 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: InnoDB: 1 transaction(s) which must be rolled back or cleaned up
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: InnoDB: in total 0 row operations to undo
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: InnoDB: Trx id counter is 1350400
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118824419762112 [Note] InnoDB: 128 rollback segment(s) are active.
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118824419762112 [Note] InnoDB: Waiting for purge to start
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118823952197376 [Note] InnoDB: Starting in background the rollback of recovered transactions
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118823952197376 [Note] InnoDB: Rollback of non-prepared transactions completed
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118824419762112 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 686198145
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118823885055744 [Note] InnoDB: Dumping buffer pool(s) not yet started
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118824419762112 [Note] Plugin 'FEEDBACK' is disabled.
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 6c11f7549fc0 InnoDB: Starting recovery for XA transactions...
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 6c11f7549fc0 InnoDB: Transaction 1347941 in prepared state after recovery
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 6c11f7549fc0 InnoDB: Transaction contains changes to 1 rows
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 6c11f7549fc0 InnoDB: 1 transactions in prepared state after recovery
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118824419762112 [Note] Found 1 prepared transaction(s) in InnoDB
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118824419762112 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.
sept. 17 21:20:47 vps301757.ovh.net mysqld[347]: 2018-09-17 21:20:47 118824419762112 [ERROR] Aborting
sept. 17 21:20:47 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:47 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:47 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:47 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:48 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:48 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:48 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:48 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:48 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:48 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:48 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:49 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:49 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
sept. 17 21:20:50 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 347, but reception only permitted for main PID which is currently not known
Il semble y avoir un problème avec la base de freshrss, je vais la réinstaller pour voir.
$ journalctl -u mariadb
sept. 18 09:03:58 vps301757.ovh.net systemd[1]: Starting MariaDB 10.1.36 database server...
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] Using unique option prefix 'character_set_client' is error-prone and can break in the future. Please use the full name 'character-set-client-handshake' instead.
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Warning] /usr/bin/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'utf8'
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] /usr/bin/mysqld (mysqld 10.1.36-MariaDB) starting as process 352 ...
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [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.
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] InnoDB: Using mutexes to ref count buffer pool pages
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] InnoDB: The InnoDB memory heap is disabled
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] InnoDB: Compressed tables use zlib 1.2.11
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] InnoDB: Using Linux native AIO
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] InnoDB: Using SSE crc32 instructions
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] InnoDB: Initializing buffer pool, size = 128.0M
sept. 18 09:03:59 vps301757.ovh.net mysqld[352]: 2018-09-18 9:03:59 122151797231552 [Note] InnoDB: Completed initialization of buffer pool
sept. 18 09:05:29 vps301757.ovh.net systemd[1]: mariadb.service: Start operation timed out. Terminating.
sept. 18 09:06:59 vps301757.ovh.net systemd[1]: mariadb.service: State 'stop-sigterm' timed out. Skipping SIGKILL.
sept. 18 09:08:29 vps301757.ovh.net systemd[1]: mariadb.service: State 'stop-final-sigterm' timed out. Skipping SIGKILL. Entering failed mode.
sept. 18 09:08:29 vps301757.ovh.net systemd[1]: mariadb.service: Failed with result 'timeout'.
sept. 18 09:08:29 vps301757.ovh.net systemd[1]: Failed to start MariaDB 10.1.36 database server.
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151797231552 [Note] InnoDB: Highest supported file format is Barracuda.
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151797231552 [Note] InnoDB: Read redo log up to LSN=687087616
sept. 18 09:10:30 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151797231552 [Note] InnoDB: 128 rollback segment(s) are active.
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151797231552 [Note] InnoDB: Waiting for purge to start
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151797231552 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 687022425
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151262070528 [Note] InnoDB: Dumping buffer pool(s) not yet started
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151797231552 [Note] Plugin 'FEEDBACK' is disabled.
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151796714240 [Note] /usr/bin/mysqld: Normal shutdown
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151797231552 [Note] /usr/bin/mysqld: ready for connections.
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: Version: '10.1.36-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 0 MariaDB Server
sept. 18 09:10:30 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:30 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151796714240 [Note] Event Scheduler: Purging the queue. 0 events
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151287248640 [Note] InnoDB: FTS optimize thread exiting.
sept. 18 09:10:30 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:30 122151796714240 [Note] InnoDB: Starting shutdown...
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:31 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:31 122151796714240 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
sept. 18 09:10:32 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:32 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:33 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:33 122151796714240 [Note] InnoDB: Shutdown completed; log sequence number 687022435
sept. 18 09:10:33 vps301757.ovh.net mysqld[352]: 2018-09-18 9:10:33 122151796714240 [Note] /usr/bin/mysqld: Shutdown complete
sept. 18 09:10:33 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known
sept. 18 09:10:33 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 352, but reception only permitted for main PID which is currently not known