Waiting for quorum message on Cache and Inference logs while trying to start two clusters with different cluster namesbut with the same multicast address and on same machines.
book
Article ID: KB0090020
calendar_today
Updated On:
Products
Versions
TIBCO BusinessEvents Enterprise Edition
-
Not Applicable
-
Description
Resolution: Description: ========= Waiting for quorum message on Cache and Inference logs while trying to start two clusters with different cluster names but with same multicast address and on same machines.
Environment: ========== TIBCO BusinessEvents 5.x Operating System(s): All
Symptoms: ========== The following are Log trace snippets from cache and inference engine.
Cache Log : ------------ Waiting for quorum: At least [1] or more storage enabled members (seeders) have to be present in the cluster for proper functioning. Currently there are [0] storage enabled members in the cluster. 2013 Feb 06 12:25:28:327 GMT -6 CustGrading-CustGrading_CA_01 Info [main] - [runtime.service] Waiting for quorum: At least [1] or more storage enabled members (seeders) have to be present in the cluster for proper functioning. Currently there are [0] storage enabled members in the cluster. 2013 Feb 06 12:25:38:328 GMT -6 CustGrading-CustGrading_CA_01 Info [main] - [runtime.service] Waiting for quorum: At least [1] or more storage enabled members (seeders) have to be present in the cluster for proper functioning. Currently there are [0] storage enabled members in the cluster. 2013 Feb 06 12:25:48:330 GMT -6 CustGrading-CustGrading_CA_01 Info [main] - [runtime.service]
Inference Log : ------------ Waiting for quorum: At least [1] or more storage enabled members (seeders) have to be present in the cluster for proper functioning. Currently there are [0] storage enabled members in the cluster. 2013 Feb 06 12:42:08:634 GMT -6 CustGrading-CustGrading_INF_01 Info [main] - [runtime.service] Waiting for quorum: At least [1] or more storage enabled members (seeders) have to be present in the cluster for proper functioning. Currently there are [0] storage enabled members in the cluster. 2013 Feb 06 12:42:18:635 GMT -6 CustGrading-CustGrading_INF_01 Info [main] - [runtime.service] Waiting for quorum: At least [1] or more storage enabled members (seeders) have to be present in the cluster for proper functioning. Currently there are [0] storage enabled members in the cluster. 2013 Feb 06 12:42:28:637 GMT -6 CustGrading-CustGrading_INF_01 Info [main] - [runtime.service]
Cause: ====== Trying to start two clusters with different cluster names but with the same multicast address and on the same machines .
Resolution: ========= This error is related to a network/parameter issue. We recommend using for the IP parameter 0.0.0.0 which means use all network interfaces for multicast. Change the settings for the property:
be.engine.cluster.as.discover.url to: be.engine.cluster.as.discover.url=tibpgm://9999/0.0.0.0;224.0.0.1/
If you have a second application running with a different cluster name , then for that use:
Waiting for quorum message on Cache and Inference logs while trying to start two clusters with different cluster namesbut with the same multicast address and on same machines.