Hi Stéphane,

You have a problem with your JGroups configuration on the 2nd node.
13:46:28,567 WARN jgroups.protocols.FD_SOCK I was suspected by 10.1.100.1:33394; ignoring the SUSPECT message 13:46:28,608 WARN protocols.pbcast.GMS I (10.1.100.2:33415) am not a member of view [10.1.100.1:33394|2] [10.1.100.1:33394], shunning myse lf and leaving the group (prev_members are [10.1.100.1:33394 10.1.100.2:33415 ], current view is [10.1.100.1:33394|1] [10.1.100.1:33394, 10
.1.100.2:33415])
13:46:28,620 ERROR continuent.hedera.channel Unhandled JGroups message type (class org.jgroups.ExitEvent): ExitEvent.
Make sure that you don't have another version of JGroups in your classpath that would be incompatible. If you have multiple instances of JGroups running on the same network, make sure to use different multicast addresses and group names in your configurations.
13:46:30,383 INFO controller.virtualdatabase.debug Checking virtual database configuration with remote controllers. 13:46:30,422 ERROR controller.virtualdatabase.debug Channel unavailable while checking configuration compatibility org.continuent.hedera.channel.NotConnectedException: ChannelNotConnectedException
As the group communication channel is broken (not connected on one end) the configuration compatibility check fails and that's why you get the incompatible configuration message (yes I know it's quite cryptic at this point!). But once you get your JGroups configuration straighten up that should work fine.

Hope this helps,
Emmanuel

--
Emmanuel Cecchet
FTO @ Frog Thinker Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to