Hi Steve, thanks for your response. A clue for my pb: I have the problem when I set the heartbeat in corosync.conf on a bridge IF (br0) ; when I set the heartbeat with two ring number on two eth IF , I have no more the problem. I 've tested with last release delivered with RHEL6 , meaning : corosynclib-1.2.3-21.el6.x86_64 corosync-1.2.3-21.el6.x86_64 I can also test with 1.2.8 if you think it is relevant, but perhaps the fact that it happens when using a bridge IF can tell you if it has been fixed or not in any release ?
By the way, could you tell me for this time and future eventual problems how I can get "a backtrace of the core file" so I can send it to you everytime ? And by the way again, what do you mean by "z stream" ? Thanks for your help Alain > There are several bugs fixed between 1.2.1 and our current stable > version 1.2.8. I would recommend updating to the latest z stream. For > your specific failure scenario, I'd need to see a backtrace of the core > file to tell you which patch you would want to cherrypick. > > Regards > -steve > _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
