Hi Alessandro, I was looking to log file and it looks like it is starting right after token was lost. Do you have log BEFORE that happen. Anyway, give a try to increase token timeout to value like 10. It looks like you have 2 nodes and by default token timeout is 1 there. 10 is used for 3 and more nodes. Also I'm unsure if this was not changed between 6.3 and 6.4. Just use <totem token="X" consensus="X + 2000" /> where X is like 10000. Regards, Honza Alessandro Bono napsal(a): > > Il 10/02/14 15:55, Jan Friesse ha scritto: >> Ok, but I would still really like to see log from 6.5 (there were huge >> amount of fixes for 6.5). > > Hi Honza > > I find time to force a full backup > note that I forced a full backup on another vm with lots of data, this > is enough to stress host server and cause error on cluster > attached zipped log file with centos 6.5 > > thank you > _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
