[PVE-User] Losing quorum - cluster broken
Nicolas Costes
nicolas.costes at univ-nantes.fr
Thu Apr 23 15:32:41 CEST 2015
Strange fact too : as soon as the interfaces a set promiscuous (when
tcpdumping), the cluster stays up, no problem anymore :
Apr 23 15:13:58 yin corosync[487815]: [TOTEM ] Retransmit List: 1f6 1f7 1f8
1f9 1fe 1ff 200 201 206 207 208 209 20e 20f 210 211
Apr 23 15:14:00 yin corosync[487815]: [TOTEM ] Retransmit List: 1f6 1f7 1f8
1f9 1fe 1ff 200 201 206 207 208 209 20e 20f 210 211
Apr 23 15:14:03 yin kernel: device vmbr0 entered promiscuous mode
Apr 23 15:15:04 yin pvedaemon[489365]: <root at pam> successful auth for user
'root at pam'
Apr 23 15:15:14 yin pmxcfs[491033]: [status] notice: received log
--
Apr 23 15:13:58 hongcha kernel: device vmbr0 entered promiscuous mode
Apr 23 15:13:59 hongcha corosync[198585]: [TOTEM ] Retransmit List: 1fa 1fb
1fc 1fd 202 203 204 205 20a 20b 20c 20d
Apr 23 15:14:01 hongcha corosync[198585]: [TOTEM ] Retransmit List: 1fa 1fb
1fc 1fd 202 203 204 205 20a 20b 20c 20d
Apr 23 15:14:03 hongcha corosync[198585]: [TOTEM ] Retransmit List: 1fa 1fb
1fc 1fd 202 203 204 205 20a 20b 20c 20d
Apr 23 15:15:00 hongcha pvedaemon[192076]: ipcc_send_rec failed: Transport
endpoint is not connected
Apr 23 15:15:03 hongcha pmxcfs[198755]: [status] notice: received log
So : what does promiscuous mode allow that has been forbidden since the last
updates ?
--
Nicolas Costes
Responsable de parc informatique
IUT de la Roche-sur-Yon
Université de Nantes
More information about the pve-user
mailing list