Réplication de la base de données MySQL

Bonjour,

je reviens vers vous après plusieurs essaies de réplication de ma base de données MySQL ( via commandes MySQL uniquement avec le workbench et via phpmyadmin (xampp) ensuite (Wampserver)).

enfaite, je veux mettre en place une architecture master/master, donc j'ai à disposition deux serveurs chacun est à la fois Master et slave, car j'ai besoin de répliquer chaque record fait que ce soit au niveau du serveur 1 ou 2 sur l'autre serveur, auromatiquement .

avec php myAdmin j'ai fait les étapes suivantes :

sur le serveur 01 :

1- j'ai créée une base de donnée contenant une table qui contient 2 colonnes, sans données ajoutées
2- dans la rubrique replication, j'ai configuré le master, j'ai commencé par choisir la base de données à répliquer que je venais justement de créer
dans le my.ini :
j'ai copié :

Code:

binlog_do_db=maDB

j'ai enlevé le commentaire pour

Code:

log-bin=mysql-bin

précisé

Code:

server-id = 1

3-j'ai ajouté un utilisateur qui a les privileges de replication (replication client, replication esclave ) à ma db, en précisant comme hôte l'adresse IP du serveur02
4-j'ai exporté ensuite la base de données

sur le serveur 02 :

1- j'ai importé la Db
2-dans le my.ini
-décommenté

Code:

log-bin=mysql-bin

-

Code:

server-id = 2

-

Code:

binlog-do-db=ma base de données importée

3- j'ai ajouté l'utilisateur pour la base de données avec comme hôte l'adresse du serveur 01.

sur les deux serveurs :

- j'ai ajouté ces cmd de config :

Code:

1
2
3
4
5
6
change master to 
master_host= 'adresse de l'autre serveur' ,
master_user= 'nom user',
master_password= ' le mot de passe',
master_log_file= 'le fichier de log de l'autre serveur',    ( trouvé soit par la cmd show master status ; ou sur phpmyadmin dans rubrique Etat ou replication )
master_log_pos = numero de position de l'atre serveur ;

-j'ai démarré l'esclave

Code:

start slave ;

jusqu'au là tout est bon, chaque serveur est à la fois maître et esclave dans le processus de réplication

Problème au niveau du test

- en ajoutant une donnée ou champ dans l'un des serveur, normalement une réplication devra pouvoir se faire automatiquement au niveau de l'autre serveur mais ca ne s'est pas produit !
en cherchant la cause du problème dans le fichier mysql.log , j'ai les erreurs suivantes :

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
2019-06-20T13:25:40.772336Z 0 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*16384 pages, LSN=2524994
2019-06-20T13:25:40.889699Z 0 [Warning] InnoDB: Starting to delete and rewrite log files.
 100 200
 100 200
2019-06-20T13:25:43.640188Z 0 [Warning] InnoDB: New log files created, LSN=2524994
2019-06-20T14:41:51.203627Z 0 [Warning] wampmysqld64: Arrêt forcé de la tâche (thread) 65  utilisateur: 'root'
 
2019-06-20T14:41:51.204707Z 0 [Warning] wampmysqld64: Arrêt forcé de la tâche (thread) 18  utilisateur: 'root'
 
2019-06-20T14:41:51.205664Z 0 [Warning] wampmysqld64: Arrêt forcé de la tâche (thread) 19  utilisateur: 'root'
 
2019-06-20T14:41:51.206790Z 0 [Warning] wampmysqld64: Arrêt forcé de la tâche (thread) 20  utilisateur: 'root'
 
2019-06-20T15:13:29.172327Z 0 [Warning] wampmysqld64: Arrêt forcé de la tâche (thread) 11  utilisateur: 'root'
 
2019-06-21T08:19:24.537733Z 0 [Warning] wampmysqld64: Arrêt forcé de la tâche (thread) 116  utilisateur: 'root'
 
2019-06-21T09:54:42.333552Z 180 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=MUL-N003-relay-bin' to avoid this problem.
2019-06-21T15:22:05.356192Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 1, Error_code: 1045
2019-06-21T15:23:05.364901Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 2, Error_code: 1045
2019-06-21T15:24:05.383035Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 3, Error_code: 1045
2019-06-21T15:25:26.396226Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 4, Error_code: 2003
2019-06-21T15:26:26.404880Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 5, Error_code: 1045
2019-06-21T15:27:26.414308Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 6, Error_code: 1045
2019-06-21T15:28:26.423261Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 7, Error_code: 1045
2019-06-21T15:29:26.458003Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 8, Error_code: 1045
2019-06-21T15:30:26.466921Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 9, Error_code: 1045
2019-06-21T15:31:26.483428Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 10, Error_code: 1045
2019-06-21T15:32:47.487665Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 11, Error_code: 2003
2019-06-21T15:34:08.501719Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 12, Error_code: 2003
2019-06-21T15:35:29.515748Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 13, Error_code: 2003
2019-06-21T15:36:50.529869Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 14, Error_code: 2003
2019-06-21T15:38:11.542919Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 15, Error_code: 2003
2019-06-21T15:39:11.558950Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 16, Error_code: 1045
2019-06-21T15:40:11.570382Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 17, Error_code: 1045
2019-06-21T15:41:11.580555Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 18, Error_code: 1045
2019-06-21T15:42:32.596102Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 19, Error_code: 2003
2019-06-21T15:43:32.613634Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 20, Error_code: 1045
2019-06-21T15:44:32.624834Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 21, Error_code: 1045
2019-06-21T15:45:32.635209Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 22, Error_code: 1045
2019-06-21T15:46:32.654210Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 23, Error_code: 1045
2019-06-21T15:47:32.665698Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 24, Error_code: 1045
2019-06-21T15:48:32.677458Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 25, Error_code: 1045
2019-06-21T15:49:32.686575Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 26, Error_code: 1045
2019-06-21T15:50:32.703632Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 27, Error_code: 1045
2019-06-21T15:51:32.714051Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 28, Error_code: 1045
2019-06-21T15:52:32.731882Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 29, Error_code: 1045
2019-06-21T15:53:53.745411Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 30, Error_code: 2003
2019-06-21T15:55:14.748907Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 31, Error_code: 2003
2019-06-21T15:56:35.753770Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 32, Error_code: 2003
2019-06-21T15:57:36.774635Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 33, Error_code: 2003
2019-06-21T15:58:57.789530Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 34, Error_code: 2003
2019-06-21T16:00:18.792828Z 219 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 35, Error_code: 2003
2019-06-24T07:04:33.957448Z 25 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 1, Error_code: 2003
2019-06-24T07:14:50.362321Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 1, Error_code: 2003
2019-06-24T07:16:11.367706Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 2, Error_code: 2003
2019-06-24T07:17:32.369681Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 3, Error_code: 2003
2019-06-24T07:18:53.382470Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 4, Error_code: 2003
2019-06-24T07:20:14.395309Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 5, Error_code: 2003
2019-06-24T07:21:35.398686Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 6, Error_code: 2003
2019-06-24T07:22:35.689294Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 7, Error_code: 1045
2019-06-24T07:23:35.705328Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 8, Error_code: 1045
2019-06-24T07:24:35.721535Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 9, Error_code: 1045
2019-06-24T07:25:35.733004Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 10, Error_code: 1045
2019-06-24T07:26:35.743745Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 11, Error_code: 1045
2019-06-24T07:27:35.753740Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 12, Error_code: 1045
2019-06-24T07:28:35.763299Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 13, Error_code: 1045
2019-06-24T07:29:35.772965Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 14, Error_code: 1045
2019-06-24T07:30:35.789415Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 15, Error_code: 1045
2019-06-24T07:31:35.800297Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 16, Error_code: 1045
2019-06-24T07:32:35.810055Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 17, Error_code: 1045
2019-06-24T07:33:35.828047Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 18, Error_code: 1045
2019-06-24T07:34:35.850345Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 19, Error_code: 1045
2019-06-24T07:35:35.872549Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 20, Error_code: 1045
2019-06-24T07:36:35.894815Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 21, Error_code: 1045
2019-06-24T07:37:35.910670Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 22, Error_code: 1045
2019-06-24T07:38:35.931261Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 23, Error_code: 1045
2019-06-24T07:39:35.948744Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 24, Error_code: 1045
2019-06-24T07:40:35.965740Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 25, Error_code: 1045
2019-06-24T07:41:35.982381Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 26, Error_code: 1045
2019-06-24T07:42:35.999853Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 27, Error_code: 1045
2019-06-24T07:43:36.245541Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 28, Error_code: 1045
2019-06-24T07:44:36.263829Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 29, Error_code: 1045
2019-06-24T07:45:36.274753Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 30, Error_code: 1045
2019-06-24T07:46:36.293029Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 31, Error_code: 1045
2019-06-24T07:47:36.310444Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 32, Error_code: 1045
2019-06-24T07:48:36.327271Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 33, Error_code: 1045
2019-06-24T07:49:36.345711Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 34, Error_code: 1045
2019-06-24T07:50:36.362176Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 35, Error_code: 1045
2019-06-24T07:51:36.379794Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 36, Error_code: 1045
2019-06-24T07:52:36.395655Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 37, Error_code: 1045
2019-06-24T07:53:36.412658Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 38, Error_code: 1045
2019-06-24T07:54:36.428903Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 39, Error_code: 1045
2019-06-24T07:55:36.445924Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 40, Error_code: 1045
2019-06-24T07:56:36.463100Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 41, Error_code: 1045
2019-06-24T07:57:36.480671Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 42, Error_code: 1045
2019-06-24T07:58:36.497480Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 43, Error_code: 1045
2019-06-24T07:59:36.507912Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 44, Error_code: 1045
2019-06-24T08:00:36.517689Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 45, Error_code: 1045
2019-06-24T08:01:36.528078Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 46, Error_code: 1045
2019-06-24T08:02:36.538933Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 47, Error_code: 1045
2019-06-24T08:03:36.549293Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 48, Error_code: 1045
2019-06-24T08:04:36.558370Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 49, Error_code: 1045
2019-06-24T08:05:36.569436Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 50, Error_code: 1045
2019-06-24T08:06:36.580985Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 51, Error_code: 1045
2019-06-24T08:07:36.597879Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 52, Error_code: 1045
2019-06-24T08:08:36.615710Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 53, Error_code: 1045
2019-06-24T08:09:36.626228Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 54, Error_code: 1045
2019-06-24T08:10:36.644692Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 55, Error_code: 1045
2019-06-24T08:11:36.662708Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 56, Error_code: 1045
2019-06-24T08:12:36.680700Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 57, Error_code: 1045
2019-06-24T08:13:36.691672Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 58, Error_code: 1045
2019-06-24T08:14:36.701176Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 59, Error_code: 1045
2019-06-24T08:15:36.716597Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 60, Error_code: 1045
2019-06-24T08:16:36.727516Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 61, Error_code: 1045
2019-06-24T08:17:36.745982Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 62, Error_code: 1045
2019-06-24T08:18:36.762821Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 63, Error_code: 1045
2019-06-24T08:19:36.780517Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 64, Error_code: 1045
2019-06-24T08:20:57.794947Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 65, Error_code: 2003
2019-06-24T08:22:18.810783Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 66, Error_code: 2003
2019-06-24T08:23:39.815103Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 67, Error_code: 2003
2019-06-24T08:25:00.829060Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 68, Error_code: 2003
2019-06-24T08:26:21.834037Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 69, Error_code: 2003
2019-06-24T08:27:42.849322Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 70, Error_code: 2003
2019-06-24T08:29:03.853603Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 71, Error_code: 2003
2019-06-24T08:30:24.867736Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 72, Error_code: 2003
2019-06-24T08:31:45.881898Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 73, Error_code: 2003
2019-06-24T08:33:06.885503Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 74, Error_code: 2003
2019-06-24T08:34:27.901086Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 75, Error_code: 2003
2019-06-24T08:35:48.903467Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 76, Error_code: 2003
2019-06-24T08:37:09.918820Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 77, Error_code: 2003
2019-06-24T08:38:30.935095Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 78, Error_code: 2003
2019-06-24T08:39:51.948507Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 79, Error_code: 2003
2019-06-24T08:41:12.952405Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 80, Error_code: 2003
2019-06-24T08:42:33.966322Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 81, Error_code: 2003
2019-06-24T08:43:54.979261Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 82, Error_code: 2003
2019-06-24T08:45:15.983258Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 83, Error_code: 2003
2019-06-24T08:46:36.998059Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 84, Error_code: 2003
2019-06-24T08:47:58.002121Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 85, Error_code: 2003
2019-06-24T08:49:19.005884Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 86, Error_code: 2003
2019-06-24T08:50:40.010112Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 87, Error_code: 2003
2019-06-24T08:52:01.025782Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 88, Error_code: 2003
2019-06-24T08:53:22.039301Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 89, Error_code: 2003
2019-06-24T08:54:43.053337Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 90, Error_code: 2003
2019-06-24T08:56:04.057173Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 91, Error_code: 2003
2019-06-24T08:57:25.061896Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 92, Error_code: 2003
2019-06-24T08:58:46.065224Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 93, Error_code: 2003
2019-06-24T09:00:07.068186Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 94, Error_code: 2003
2019-06-24T09:01:28.081567Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 95, Error_code: 2003
2019-06-24T09:02:49.084392Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 96, Error_code: 2003
2019-06-24T09:04:10.087811Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 97, Error_code: 2003
2019-06-24T09:05:31.100964Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 98, Error_code: 2003
2019-06-24T09:06:52.106616Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 99, Error_code: 2003
2019-06-24T09:08:13.112710Z 83 [ERROR] Slave I/O for channel '': error connecting to master 'replication_user@10.24.60.213:3306' - retry-time: 60  retries: 100, Error_code: 2003

avez-vous une idée sur la cause du problème ou une solus envisageable ?

petite précision en faisant le test du port 3306, voici le resultat

Code:

1
2
 
Port 3306 is not found associated with TCP protocol

et pour l'Etat de chaque serveur, il est effectivement Master et slave au même temps !

Solution trouvée ! :D

Pour que cela puisse servir à d'autres personnes qui rencontreraient le même problème, pourrrais-tu nous partager la solution que tu as trouvée ?

solution trouvée

Salut,

le problème n'était pas le port, ni la configuration, toutes les étapes précedemment citées sont correctes
le problème c'est le protocole DHCP, en redémarrant l'hôte n'aura pas forcément la même adresse IP , donc le mieux est de la fixer pour ne pas avoir telles erreurs de réplication surtout l'erreur 2003, c'est de la casse tête !

bon je suis là en cas de besoin, je réponderai à vos questions !

A+

Salut enigmma .

Je ne comprends pas la nature de votre problème.
MySql, à moins de l'utiliser en local sur votre ordinateur, doit normalement être accessible par n'importe quel utilisateur dans votre réseau local ou depuis internet.
De ce fait, vos deux serveurs doivent avoir une adresse IP fixe et si possible toujours la même.
Il faut au niveau de votre box/routeur, que les adresses soient définies à partir de vos adresses MAC et de les rendre fixe.
Ouvrir les ports 80 et 443 afin de rediriger les flux vers les serveurs.

Tout cela aurait dû être fait lors de l'installation de vos serveurs MySql.

D'autre part, vous auriez dû faire les choses étape par étape, comme par exemple tester d'abord la réplication Master/Slave avant de basculer vers Master/Master.
La réplication n'est pas très compliquée à mettre en place. Il existe des tas de didacticiels sur le net, plus ou moins bien écrits.

Le gros du problème avenir sera la synchronisation, et que faire en cas de plantage pour redémarrer.

@+

Salut Artemus24 .

Citation:

MySql, à moins de l'utiliser en local sur votre ordinateur, doit normalement être accessible par n'importe quel utilisateur dans votre réseau local ou depuis internet.
De ce fait, vos deux serveurs doivent avoir une adresse IP fixe et si possible toujours la même.
Il faut au niveau de votre box/routeur, que les adresses soient définies à partir de vos adresses MAC et de les rendre fixe.
Ouvrir les ports 80 et 443 afin de rediriger les flux vers les serveurs.

qu'est ce que vous voulez dire par, il doivent être noramelement accessible par n'importe quel utilisteur dans le réseau ?
voilà en détail le problème que j'avais :
- en configurant la réplication master/slave par exemple , on précise l'adresse ip du master par

Code:

change master to MASTER_HOST = 'host_id'

j'avais pas fixé l'adresse IP, du coup le lendemain quand le host essaie de se connecter au master il n'arrive pas car l'adresse IP change à cause du DHCP

Citation:

D'autre part, vous auriez dû faire les choses étape par étape, comme par exemple tester d'abord la réplication Master/Slave avant de basculer vers Master/Master.
La réplication n'est pas très compliquée à mettre en place. Il existe des tas de didacticiels sur le net, plus ou moins bien écrits.

c'est exactement ca ce que j avais fait et comme j'ai dit j'ai pu résoudre le problème et la réplication a été faite avec succès

Citation:

Le gros du problème avenir sera la synchronisation, et que faire en cas de plantage pour redémarrer.

avez vous une idée sur la solution en cas de plantage ???

@+[/QUOTE]

Salut enigmma.

Citation:

Envoyé par enigmma

qu'est ce que vous voulez dire par, il doivent être normalement accessible par n'importe quel utilisateur dans le réseau ?

Je pensais avoir été clair dans mes explications.

Votre serveur MySql doit posséder une adresse IP fixe.
Votre serveur MySql doit être vu (ou accessible) par n'importe quel utilisateur dans votre réseau local, mais aussi depuis internet.
Pour vérifier cela, vous faites un ping de l'adresse IP de votre serveur MySql.
Si le ping ne fonctionne pas, soit ce n'est pas la bonne adresse IP, soit le port est fermé, soit un problème de pare-feu, soit un problème de routeur (NAT).

Autrement dit, est-ce que tout est correcte coté réseau ?

Citation:

Envoyé par enigmma

j'avais pas fixé l'adresse IP, du coup le lendemain quand le host essaie de se connecter au master il n'arrive pas car l'adresse IP change à cause du DHCP

Sinon comment vos utilisateurs peuvent se connecter s'ils ne connaissent pas l'adresse IP de votre serveur MySql ?

Vous devez rendre cette adresse IP fixe dans votre serveur DHCP !

Citation:

Envoyé par enigmma

avez vous une idée sur la solution en cas de plantage ???

Il n'y a pas de solution toute faite en cas de plantage. Pourquoi ?
Parce que l'origine du plantage implique d'abord de le résoudre, si vous pouvez le faire, avant d'effectuer la synchronisation entre les deux serveurs.
L'origine peut-être un problème de disque plein, un plantage applicatif, un problème d'alimentation, ...

Le plantage de l'un des serveurs fait que celui-ci s'est arrêté pendant que l'autre, qui fonctionne normalement, a continué à traiter les requêtes.
Pour résoudre ce problème, vous devez identifier la dernière opération soit par un date soit par un numéro d'identification.
Il suffit alors de reprendre toutes les requêtes après ce point de reprise et de les transférer vers l'autre serveur.
Pour identifier ce point de reprise, il faut chercher manuellement.
Ce sujet a déjà été traité sur le net.

@+