Project

General

Profile

Demande #3333

VM lamp : Mysql ne démarre pas tout seul après un reboot cluster

Added by Christian P. Momon 11 months ago. Updated 10 months ago.

Status:
Nouveau
Priority:
Élevée
Assignee:
-
Category:
-
Target version:
Start date:
10/01/2018
Due date:
% Done:

0%

Difficulté:
3 Moyen

Description

Sur la VM lamp, après un reboot cluster, ça fait plusieurs fois que Mysql ne redémarre pas correctement :

(April) root@lamp:~# systemctl status mysql
● mariadb.service - MariaDB database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: activating (start) since Mon 2018-10-01 22:38:34 CEST; 1min 13s ago
  Process: 622 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: 617 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 584 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
 Main PID: 726 (mysqld)
    Tasks: 14 (limit: 4915)
   CGroup: /system.slice/mariadb.service
           └─726 /usr/sbin/mysqld

oct. 01 22:38:34 lamp systemd[1]: Starting MariaDB database server...
oct. 01 22:38:52 lamp mysqld[726]: 2018-10-01 22:38:52 140375755854400 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
oct. 01 22:38:53 lamp mysqld[726]: 2018-10-01 22:38:53 140375755854400 [Note] /usr/sbin/mysqld (mysqld 10.1.26-MariaDB-0+deb9u1) starting as process 726 ...

Un systemctl restart mysql manuel suffit à réparer.

History

#1 Updated by Christian P. Momon 10 months ago

À nouveau le 08/10/2018 :

Last login: Mon Oct 8 17:52:27 2018 from 172.16.0.1
(April) root@lamp:~# systemctl status mysql
● mariadb.service - MariaDB database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Tue 2018-10-09 00:05:37 CEST; 5s ago
Process: 761 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 636 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl
Process: 629 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 612 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 761 (code=exited, status=0/SUCCESS)
Status: "MariaDB server is down"

oct. 09 00:03:52 lamp systemd1: Starting MariaDB database server...
oct. 09 00:04:11 lamp mysqld761: 2018-10-09 0:04:11 140450018579008 [Note] Using unique option prefix 'key_buffer' is error-prone and can break
oct. 09 00:04:12 lamp mysqld761: 2018-10-09 0:04:12 140450018579008 [Note] /usr/sbin/mysqld (mysqld 10.1.26-MariaDB-0+deb9u1) starting as proce
oct. 09 00:05:30 lamp systemd1: mariadb.service: Start operation timed out. Terminating.
oct. 09 00:05:37 lamp systemd1: Failed to start MariaDB database server.
oct. 09 00:05:37 lamp systemd1: mariadb.service: Unit entered failed state.
oct. 09 00:05:37 lamp systemd1: mariadb.service: Failed with result 'timeout'.

Also available in: Atom PDF