[mysqld] failed to start on boot [résolu]

Applications, problèmes de configuration réseau
Répondre
Sirilldu
archer
Messages : 135
Inscription : mer. 27 mars 2013, 19:45

[mysqld] failed to start on boot [résolu]

Message par Sirilldu » sam. 15 sept. 2018, 19:24

Bonjour,

Ce matin, lors de la mise à jour, j'ai vu passer mariadb, depuis mariadb ne démarre plus au boot.

Le démarrage du serveur est très long :

Code : Tout sélectionner

$ systemd-analyze blame
    4min 31.126s mariadb.service
           837ms lvm2-monitor.service
           755ms dev-vda1.device
           280ms systemd-journal-flush.service
           277ms systemd-networkd.service
           235ms systemd-logind.service
           221ms systemd-udev-trigger.service
           194ms systemd-udevd.service
           189ms systemd-journald.service
           166ms sys-kernel-config.mount
           164ms sys-kernel-debug.mount
           159ms dev-hugepages.mount
           154ms systemd-tmpfiles-setup-dev.service
           154ms tmp.mount
           119ms dev-mqueue.mount
           113ms systemd-tmpfiles-clean.service
           112ms user@1000.service
            99ms systemd-remount-fs.service
            88ms pacman-reanimation.service
            76ms systemd-random-seed.service
            63ms systemd-sysctl.service
            54ms kmod-static-nodes.service
            45ms systemd-user-sessions.service
            39ms systemd-tmpfiles-setup.service
            28ms systemd-update-utmp.service
            20ms proc-sys-fs-binfmt_misc.mount
Le status :

Code : Tout sélectionner

$ systemctl status mysqld.service
● mariadb.service - MariaDB 10.1.36 database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
   Active: failed (Result: timeout) since Sat 2018-09-15 19:11:21 CEST; 3min 47s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 284 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: 279 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
 Main PID: 363
    Tasks: 0 (limit: 2323)
   Memory: 23.3M
   CGroup: /system.slice/mariadb.service

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.

Code : Tout sélectionner

$ journalctl -p err
sept. 15 19:11:21 vps301757.ovh.net systemd[1]: Failed to start MariaDB 10.1.36 database server.
sept. 15 19:13:01 vps301757.ovh.net systemd-coredump[387]: Process 363 (mysqld) of user 89 dumped core.
                                                           
                                                           Stack trace of thread 363:
                                                           #0  0x000062dce658c07b kill (libc.so.6)
                                                           #1  0x00000a38456e461c handle_fatal_signal (mysqld)
                                                           #2  0x000062dce6a3e3c0 __restore_rt (libpthread.so.0)
                                                           #3  0x000062dce658bd7f raise (libc.so.6)
                                                           #4  0x000062dce6576672 abort (libc.so.6)
                                                           #5  0x00000a3845ade189 n/a (mysqld)
                                                           #6  0x00000a3845ad5880 n/a (mysqld)
                                                           #7  0x00000a3845a4b321 n/a (mysqld)
                                                           #8  0x00000a384595adff n/a (mysqld)
                                                           #9  0x00000a38456e68cd _Z24ha_initialize_handlertonP13st_plugin_int (mysqld)
                                                           #10 0x00000a3845563e38 n/a (mysqld)
                                                           #11 0x00000a3845565003 _Z11plugin_initPiPPci (mysqld)
                                                           #12 0x00000a38454be3c0 n/a (mysqld)
                                                           #13 0x00000a38454c1e0e _Z11mysqld_mainiPPc (mysqld)
                                                           #14 0x000062dce6578223 __libc_start_main (libc.so.6)
                                                           #15 0x00000a38454b592e _start (mysqld)
                                                           
                                                           Stack trace of thread 364:
                                                           #0  0x000062dce6a39e5b pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
                                                           #1  0x00000a3845b96f33 n/a (mysqld)
                                                           #2  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #3  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 365:
                                                           #0  0x000062dce6a39e5b pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
                                                           #1  0x00000a3845879460 n/a (mysqld)
                                                           #2  0x00000a38458719fc n/a (mysqld)
                                                           #3  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #4  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 366:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 367:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 368:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 369:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 370:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 371:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 372:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 373:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 374:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 375:
                                                           #0  0x000062dce664a40d syscall (libc.so.6)
                                                           #1  0x000062dce70077aa n/a (libaio.so.1)
                                                           #2  0x00000a38459cdbf1 n/a (mysqld)
                                                           #3  0x00000a3845b0750c n/a (mysqld)
                                                           #4  0x00000a3845a46070 n/a (mysqld)
                                                           #5  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #6  0x000062dce664fa43 __clone (libc.so.6)
                                                           
                                                           Stack trace of thread 379:
                                                           #0  0x000062dce6a39e5b pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
                                                           #1  0x00000a38459d042f n/a (mysqld)
                                                           #2  0x00000a3845a41cec n/a (mysqld)
                                                           #3  0x000062dce6a33a9d start_thread (libpthread.so.0)
                                                           #4  0x000062dce664fa43 __clone (libc.so.6)

Un sudo systemctl start mysqld démarre correctement mariadb.

Auriez-vous des pistes ?

Edit :

Code : Tout sélectionner

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 édition par Sirilldu le mar. 18 sept. 2018, 15:12, édité 1 fois.
Arch 64 | KDE

Avatar de l’utilisateur
FoolEcho
Maître du Kyudo
Messages : 10420
Inscription : dim. 15 août 2010, 11:48
Localisation : Basse-Normandie

Re: [mysqld] failed to start on boot

Message par FoolEcho » dim. 16 sept. 2018, 09:33

Salut,
Sirilldu a écrit :
sam. 15 sept. 2018, 19:24

Code : Tout sélectionner

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.» :nage:

Sirilldu
archer
Messages : 135
Inscription : mer. 27 mars 2013, 19:45

Re: [mysqld] failed to start on boot

Message par Sirilldu » dim. 16 sept. 2018, 19:03

Oui j'ai bien vu cette erreur, j'ai tenté de mettre ce tmp dans tmpfs comme indiqué dans la doc : https://wiki.archlinux.org/index.php/My ... for_tmpdir
Cela ne change pas la situation.
Arch 64 | KDE

Avatar de l’utilisateur
FoolEcho
Maître du Kyudo
Messages : 10420
Inscription : dim. 15 août 2010, 11:48
Localisation : Basse-Normandie

Re: [mysqld] failed to start on boot

Message par FoolEcho » lun. 17 sept. 2018, 19:48

Avec rigoureusement la même erreur ? (le répertoire est bien monté et le service mysql redémarré ?) :|
«The following statement is not true. The previous statement is true.» :nage:

Sirilldu
archer
Messages : 135
Inscription : mer. 27 mars 2013, 19:45

Re: [mysqld] failed to start on boot

Message par Sirilldu » lun. 17 sept. 2018, 21:35

Effectivement ce n'est plus la même erreur :

Code : Tout sélectionner

$ 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.
Arch 64 | KDE

Avatar de l’utilisateur
benjarobin
Maître du Kyudo
Messages : 15196
Inscription : sam. 30 mai 2009, 15:48
Localisation : Lyon

Re: [mysqld] failed to start on boot

Message par benjarobin » lun. 17 sept. 2018, 23:40

Maintenant c'est différent en effet, il te dit que des bases de données sont corrompu, et donc refuse de le lancer, tu dois réparer avant...
Zsh | KDE | PC fixe : core i7, carte nvidia | Portable : Asus ul80vt
Titre d'un sujet : [Thème] Sujet (état)

Sirilldu
archer
Messages : 135
Inscription : mer. 27 mars 2013, 19:45

Re: [mysqld] failed to start on boot

Message par Sirilldu » mar. 18 sept. 2018, 09:31

Après avoir réparer les bases, le problème persiste :

Code : Tout sélectionner

$ 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
Arch 64 | KDE

Avatar de l’utilisateur
benjarobin
Maître du Kyudo
Messages : 15196
Inscription : sam. 30 mai 2009, 15:48
Localisation : Lyon

Re: [mysqld] failed to start on boot

Message par benjarobin » mar. 18 sept. 2018, 11:11

Peux tu donner la sortie de :

Code : Tout sélectionner

systemctl cat mariadb | grep -Ev "^ *#|^ *$"
systemctl cat mysqld | grep -Ev "^ *#|^ *$"
grep -rEv "^ *#|^ *$"  /etc/mysql
df -h
Zsh | KDE | PC fixe : core i7, carte nvidia | Portable : Asus ul80vt
Titre d'un sujet : [Thème] Sujet (état)

Sirilldu
archer
Messages : 135
Inscription : mer. 27 mars 2013, 19:45

Re: [mysqld] failed to start on boot

Message par Sirilldu » mar. 18 sept. 2018, 12:35

Code : Tout sélectionner

$ systemctl cat mariadb | grep -Ev "^ *#|^ *$"
[Unit]
Description=MariaDB 10.1.36 database server
Documentation=man:mysqld(8)
Documentation=https://mariadb.com/kb/en/library/systemd/
After=network.target
After=syslog.target
[Install]
WantedBy=multi-user.target
[Service]
Type=notify
PrivateNetwork=false
User=mysql
Group=mysql
CapabilityBoundingSet=CAP_IPC_LOCK
ProtectSystem=full
PrivateDevices=true
ProtectHome=true
PermissionsStartOnly=true
ExecStartPre=/bin/sh -c "systemctl unset-environment _WSREP_START_POSITION"
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"
ExecStart=/usr/bin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION
ExecStartPost=/bin/sh -c "systemctl unset-environment _WSREP_START_POSITION"
KillSignal=SIGTERM
SendSIGKILL=no
Restart=on-abort
RestartSec=5s
UMask=007
PrivateTmp=true
LimitNOFILE=16364

Code : Tout sélectionner

$ systemctl cat mysqld | grep -Ev "^ *#|^ *$"
[Unit]
Description=MariaDB 10.1.36 database server
Documentation=man:mysqld(8)
Documentation=https://mariadb.com/kb/en/library/systemd/
After=network.target
After=syslog.target
[Install]
WantedBy=multi-user.target
[Service]
Type=notify
PrivateNetwork=false
User=mysql
Group=mysql
CapabilityBoundingSet=CAP_IPC_LOCK
ProtectSystem=full
PrivateDevices=true
ProtectHome=true
PermissionsStartOnly=true
ExecStartPre=/bin/sh -c "systemctl unset-environment _WSREP_START_POSITION"
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"
ExecStart=/usr/bin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION
ExecStartPost=/bin/sh -c "systemctl unset-environment _WSREP_START_POSITION"
KillSignal=SIGTERM
SendSIGKILL=no
Restart=on-abort
RestartSec=5s
UMask=007
PrivateTmp=true
LimitNOFILE=16364

Code : Tout sélectionner

$ grep -rEv "^ *#|^ *$"  /etc/mysql
/etc/mysql/wsrep.cnf:[mysqld]
/etc/mysql/wsrep.cnf:binlog_format=ROW
/etc/mysql/wsrep.cnf:default-storage-engine=innodb
/etc/mysql/wsrep.cnf:innodb_autoinc_lock_mode=2
/etc/mysql/wsrep.cnf:bind-address=0.0.0.0
/etc/mysql/wsrep.cnf:wsrep_on=1
/etc/mysql/wsrep.cnf:wsrep_provider=none
/etc/mysql/wsrep.cnf:wsrep_cluster_name="my_wsrep_cluster"
/etc/mysql/wsrep.cnf:wsrep_slave_threads=1
/etc/mysql/wsrep.cnf:wsrep_certify_nonPK=1
/etc/mysql/wsrep.cnf:wsrep_max_ws_rows=131072
/etc/mysql/wsrep.cnf:wsrep_max_ws_size=1073741824
/etc/mysql/wsrep.cnf:wsrep_debug=0
/etc/mysql/wsrep.cnf:wsrep_convert_LOCK_to_trx=0
/etc/mysql/wsrep.cnf:wsrep_retry_autocommit=1
/etc/mysql/wsrep.cnf:wsrep_auto_increment_control=1
/etc/mysql/wsrep.cnf:wsrep_drupal_282555_workaround=0
/etc/mysql/wsrep.cnf:wsrep_causal_reads=0
/etc/mysql/wsrep.cnf:wsrep_notify_cmd=
/etc/mysql/wsrep.cnf:wsrep_sst_method=rsync
/etc/mysql/wsrep.cnf:wsrep_sst_auth=root:
/etc/mysql/my.cnf:[client]
/etc/mysql/my.cnf:port		= 3306
/etc/mysql/my.cnf:socket		= /run/mysqld/mysqld.sock
/etc/mysql/my.cnf:[mysqld]
/etc/mysql/my.cnf:port		= 3306
/etc/mysql/my.cnf:socket		= /run/mysqld/mysqld.sock
/etc/mysql/my.cnf:skip-external-locking
/etc/mysql/my.cnf:key_buffer_size = 16M
/etc/mysql/my.cnf:max_allowed_packet = 1M
/etc/mysql/my.cnf:table_open_cache = 64
/etc/mysql/my.cnf:sort_buffer_size = 512K
/etc/mysql/my.cnf:net_buffer_length = 8K
/etc/mysql/my.cnf:read_buffer_size = 256K
/etc/mysql/my.cnf:read_rnd_buffer_size = 512K
/etc/mysql/my.cnf:myisam_sort_buffer_size = 8M
/etc/mysql/my.cnf:init_connect                = 'SET collation_connection = utf8_general_ci,NAMES utf8'
/etc/mysql/my.cnf:collation_server            = utf8_general_ci
/etc/mysql/my.cnf:character_set_client        = utf8
/etc/mysql/my.cnf:character_set_server        = utf8
/etc/mysql/my.cnf:tmpdir		= /var/lib/mysqltmp
/etc/mysql/my.cnf:skip-networking
/etc/mysql/my.cnf:server-id	= 1
/etc/mysql/my.cnf:[mysqldump]
/etc/mysql/my.cnf:quick
/etc/mysql/my.cnf:max_allowed_packet = 16M
/etc/mysql/my.cnf:[mysql]
/etc/mysql/my.cnf:no-auto-rehash
/etc/mysql/my.cnf:[myisamchk]
/etc/mysql/my.cnf:key_buffer_size = 20M
/etc/mysql/my.cnf:sort_buffer_size = 20M
/etc/mysql/my.cnf:read_buffer = 2M
/etc/mysql/my.cnf:write_buffer = 2M
/etc/mysql/my.cnf:[mysqlhotcopy]
/etc/mysql/my.cnf:interactive-timeout

Code : Tout sélectionner

$ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
dev                969M       0  969M   0% /dev
run                975M    344K  974M   1% /run
/dev/vda1          9,9G    6,9G  2,6G  73% /
tmpfs              975M       0  975M   0% /dev/shm
tmpfs              975M       0  975M   0% /sys/fs/cgroup
tmpfs              975M    244K  975M   1% /tmp
tmpfs              100M       0  100M   0% /var/lib/mysqltmp
tmpfs              195M       0  195M   0% /run/user/1000
Arch 64 | KDE

Avatar de l’utilisateur
benjarobin
Maître du Kyudo
Messages : 15196
Inscription : sam. 30 mai 2009, 15:48
Localisation : Lyon

Re: [mysqld] failed to start on boot

Message par benjarobin » mar. 18 sept. 2018, 13:18

Je n'ai pas trop d'analyser la chose, mais en gros tu as supprimé :

Code : Tout sélectionner

/etc/mysql/my.cnf:log-bin=mysql-bin
/etc/mysql/my.cnf:binlog_format=mixed
Pour rajouter :

Code : Tout sélectionner

/etc/mysql/my.cnf:init_connect                = 'SET collation_connection = utf8_general_ci,NAMES utf8'
/etc/mysql/my.cnf:collation_server            = utf8_general_ci
/etc/mysql/my.cnf:character_set_client        = utf8
/etc/mysql/my.cnf:character_set_server        = utf8
/etc/mysql/my.cnf:tmpdir		= /var/lib/mysqltmp
/etc/mysql/my.cnf:skip-networking
As tu essayé avec la configuration par défaut ?
Zsh | KDE | PC fixe : core i7, carte nvidia | Portable : Asus ul80vt
Titre d'un sujet : [Thème] Sujet (état)

Sirilldu
archer
Messages : 135
Inscription : mer. 27 mars 2013, 19:45

Re: [mysqld] failed to start on boot

Message par Sirilldu » mar. 18 sept. 2018, 14:15

Je viens d'essayer avec la configuration par défaut, mysqld ne démarre toujours pas au boot.

On retrouve l'erreur Can't create/write to file '/tmp/ibEYVxjK'

Code : Tout sélectionner

sept. 18 13:49:01 vps301757.ovh.net systemd[1]: Starting MariaDB 10.1.36 database server...
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] /usr/bin/mysqld (mysqld 10.1.36-MariaDB) starting as process 324 ...
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [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 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] InnoDB: Using mutexes to ref count buffer pool pages
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] InnoDB: The InnoDB memory heap is disabled
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] InnoDB: Compressed tables use zlib 1.2.11
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] InnoDB: Using Linux native AIO
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] InnoDB: Using SSE crc32 instructions
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] InnoDB: Initializing buffer pool, size = 128.0M
sept. 18 13:49:02 vps301757.ovh.net mysqld[324]: 2018-09-18 13:49:02 105918387470272 [Note] InnoDB: Completed initialization of buffer pool
sept. 18 13:50:32 vps301757.ovh.net systemd[1]: mariadb.service: Start operation timed out. Terminating.
sept. 18 13:52:02 vps301757.ovh.net systemd[1]: mariadb.service: State 'stop-sigterm' timed out. Skipping SIGKILL.
sept. 18 13:53:32 vps301757.ovh.net systemd[1]: mariadb.service: State 'stop-final-sigterm' timed out. Skipping SIGKILL. Entering failed mode.
sept. 18 13:53:32 vps301757.ovh.net systemd[1]: mariadb.service: Failed with result 'timeout'.
sept. 18 13:53:32 vps301757.ovh.net systemd[1]: Failed to start MariaDB 10.1.36 database server.
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: 2018-09-18 13:55:35 105918387470272 [Note] InnoDB: Highest supported file format is Barracuda.
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: 2018-09-18 13:55:35 105918387470272 [Note] InnoDB: Read redo log up to LSN=687087616
sept. 18 13:55:35 vps301757.ovh.net systemd[1]: mariadb.service: Got notification message from PID 324, but reception only permitted for main PID which is currently not known
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: 2018-09-18 13:55:35 105918387470272 [ERROR] mysqld: Can't create/write to file '/tmp/ibEYVxjK' (Errcode: 2 "No such file or directory")
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: 2018-09-18 13:55:35 60550bdc3fc0  InnoDB: Error: unable to create temporary file; errno: 2
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: 2018-09-18 13:55:35 60550bdc3fc0  InnoDB: Assertion failure in thread 105918387470272 in file dict0dict.cc line 1089
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: InnoDB: Failing assertion: dict_foreign_err_file
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: InnoDB: We intentionally generate a memory trap.
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: InnoDB: If you get repeated assertion failures or crashes, even
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: InnoDB: immediately after the mysqld startup, there may be
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: InnoDB: corruption in the InnoDB tablespace. Please refer to
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: InnoDB: about forcing recovery.
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: 180918 13:55:35 [ERROR] mysqld got signal 6 ;
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: This could be because you hit a bug. It is also possible that this binary
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: or one of the libraries it was linked against is corrupt, improperly built,
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: or misconfigured. This error can also be caused by malfunctioning hardware.
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: We will try our best to scrape up some info that will hopefully help
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: diagnose the problem, but since we have already crashed,
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: something is definitely wrong and this may fail.
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: Server version: 10.1.36-MariaDB
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: key_buffer_size=16777216
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: read_buffer_size=262144
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: max_used_connections=0
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: max_threads=153
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: thread_count=0
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: It is possible that mysqld could use up to
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137052 K  bytes of memory
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: Hope that's ok; if not, decrease some variables in the equation.
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: Thread pointer: 0x0
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: Attempting backtrace. You can use the following information to find out
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: where mysqld died. If you see no messages after this, something went
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: terribly wrong...
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: stack_bottom = 0x0 thread_stack 0x48400
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(my_print_stacktrace+0x2f)[0x19e5f3d5bdf]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(handle_fatal_signal+0x586)[0x19e5ef27756]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: sigaction.c:0(__restore_rt)[0x60550c8143c0]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: :0(__GI_raise)[0x60550c361d7f]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: :0(__GI_abort)[0x60550c34c672]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(+0x98d189)[0x19e5f321189]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(+0x984880)[0x19e5f318880]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(+0x8fa321)[0x19e5f28e321]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(+0x809dff)[0x19e5f19ddff]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x6d)[0x19e5ef298cd]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(+0x412e38)[0x19e5eda6e38]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(_Z11plugin_initPiPPci+0x983)[0x19e5eda8003]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(+0x36d3c0)[0x19e5ed013c0]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(_Z11mysqld_mainiPPc+0x1b2e)[0x19e5ed04e0e]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/lib/libc.so.6(__libc_start_main+0xf3)[0x60550c34e223]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: /usr/bin/mysqld(_start+0x2e)[0x19e5ecf892e]
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
sept. 18 13:55:35 vps301757.ovh.net mysqld[324]: information that should help you find out what is causing the crash.
Si je veux repartir sur une base propre de mariadb, est-ce que cela suffit :

Code : Tout sélectionner

$ sudo pacman -Rns mariadb
$ sudo rm -rf /var/lib/mysql
$ sudo rm -rf /etc/mysql
Arch 64 | KDE

Avatar de l’utilisateur
benjarobin
Maître du Kyudo
Messages : 15196
Inscription : sam. 30 mai 2009, 15:48
Localisation : Lyon

Re: [mysqld] failed to start on boot

Message par benjarobin » mar. 18 sept. 2018, 14:40

Si tu veux repartir sur une base saine et supposant que tu aies sauvegardé tout ce que tu avais besoin, tu dois faire ceci (en root):

Code : Tout sélectionner

systemctl stop mysqld.service
rm -rf /var/lib/mysql
rm -rf /etc/mysql
pacman -S mariadb
mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql
systemctl start mysqld.service
Zsh | KDE | PC fixe : core i7, carte nvidia | Portable : Asus ul80vt
Titre d'un sujet : [Thème] Sujet (état)

Sirilldu
archer
Messages : 135
Inscription : mer. 27 mars 2013, 19:45

Re: [mysqld] failed to start on boot

Message par Sirilldu » mar. 18 sept. 2018, 15:11

Merci à vous deux, suite à là réinstallation de mariadb, retour a la normal.
Arch 64 | KDE

Répondre