Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 658198

Summary: Starting cumin brings down one node in MRG cluster
Product: Red Hat Enterprise MRG Reporter: Mike Cressman <mcressma>
Component: qpid-cppAssignee: Alan Conway <aconway>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: high Docs Contact:
Priority: urgent    
Version: 1.3   
Target Milestone: Next Errata   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-08 20:12:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Qpid debug log file during cluster error none

Description Mike Cressman 2010-11-29 16:35:35 UTC
Created attachment 463528 [details]
Qpid debug log file during cluster error

Description of problem:
Running a 4-cluster (2 machines, 2 nodes per machine).

While cluster is running, start cumin on one of the machines.
Within 2 minutes, one node gets out of sync and leaves the cluster.

Error from log:
2010-11-25 09:20:16 error Execution exception: invalid-argument: anonymous.ukvruatamqa01.hs.local.8004.4: confirmed < (612082+0) but only sent < (612081+0) (qpid/SessionState.cpp:154)
2010-11-25 09:20:16 critical cluster(10.34.24.18:15729 READY/error) local error 58711697 did not occur on member 10.34.24.19:8415: invalid-argument: anonymous.ukvruatamqa01.hs.local.8004.4: confirmed < (612082+0) but only sent < (612081+0) (qpid/SessionState.cpp:154)
2010-11-25 09:20:16 critical Error delivering frames: local error did not occur on all cluster members : invalid-argument: anonymous.ukvruatamqa01.hs.local.8004.4: confirmed < (612082+0) but only sent < (612081+0) (qpid/SessionState.cpp:154) (qpid/cluster/ErrorCheck.cpp:89)
2010-11-25 09:20:16 notice cluster(10.34.24.18:15729 LEFT/error) leaving cluster messaging1
2010-11-25 09:20:16 notice Shut down 


Version-Release number of selected component (if applicable):
MRG 1.3

How reproducible:
Consistent at customer site

Steps to Reproduce:
1. Run cluster
2. Start cumin
3.
  
Actual results:
One node gets out of sync and leaves the cluster

Expected results:
All nodes successfully stay in sync

Additional info:

Cumin was installed as per instructions and the only file updated was /etc/cumin/cumin.conf where the only line edited was "brokers:" by adding the hosts and ports of the brokers to monitor (in the format; brokers: <host>:<port>, <host>:<port>, <host>:<port>, <host>:<port>).

See attached log file containing debug logs during an occurrence.  Cumin service was started at about 2010-11-26 14:05, and at approx 14:06 a WebUI was launched.  At 14:07:12 the broker shut down.

Comment 2 Alan Conway 2010-12-08 20:12:47 UTC

*** This bug has been marked as a duplicate of bug 654872 ***