[PVE-User] Cluster does not start, corosync timeout...
Marco Gaiarin
gaio at sv.lnf.it
Thu Jul 4 12:35:44 CEST 2019
We had a major power outgage here, and our cluster have some trouble on
restart. The worster was:
Jul 3 19:58:40 pvecn1 corosync[3443]: [MAIN ] Corosync Cluster Engine ('2.4.4-dirty'): started and ready to provide service.
Jul 3 19:58:40 pvecn1 corosync[3443]: [MAIN ] Corosync built-in features: dbus rdma monitoring watchdog systemd xmlconf qdevices qnetd snmp pie relro bindnow
Jul 3 19:58:40 pvecn1 corosync[3443]: notice [MAIN ] Corosync Cluster Engine ('2.4.4-dirty'): started and ready to provide service.
Jul 3 19:58:40 pvecn1 corosync[3443]: info [MAIN ] Corosync built-in features: dbus rdma monitoring watchdog systemd xmlconf qdevices qnetd snmp pie relro bindnow
Jul 3 20:00:09 pvecn1 systemd[1]: corosync.service: Start operation timed out. Terminating.
Jul 3 20:00:09 pvecn1 systemd[1]: corosync.service: Unit entered failed state.
Jul 3 20:00:09 pvecn1 systemd[1]: corosync.service: Failed with result 'timeout'.
after fiddling a bit, we solved all the stuff and cluster goes back as
normal.
But... some host in the cluster missed from /etc/hosts: this suffices
to have corosync not to start correctly?
Looking at docs (https://pve.proxmox.com/pve-docs/pve-admin-guide.html):
While it’s often common use to reference all other nodenames in /etc/hosts with their IP this is not strictly necessary for a cluster, which normally uses multicast, to work. It maybe useful as you then can connect from one node to the other with SSH through the easier to remember node name.
this mean i've not multicast correctly working? I was sure i had...
Thanks.
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.it/
Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN)
marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f +39-0434-842797
Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
More information about the pve-user
mailing list