Bug 1293949

Summary:	RabbitMQ experienceing "unknown error"
Product:	Red Hat OpenStack	Reporter:	Jeremy <jmelvin>
Component:	rabbitmq-server	Assignee:	Peter Lemenkov <plemenko>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Udi Shkalim <ushkalim>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0 (Juno)	CC:	apevec, jeckersb, jmelvin, lhh, srevivo
Target Milestone:	---	Keywords:	Unconfirmed, ZStream
Target Release:	6.0 (Juno)	Flags:	jeckersb: needinfo? (jmelvin)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-07 17:54:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jeremy 2015-12-23 16:24:32 UTC

Description of problem: Current OSP environment is performing slow, while checking the status of pacemaker, it appears that Rabbitmq is experiencing issues and has stopped


Version-Release number of selected component (if applicable):
rabbitmq-server-3.3.5-3.el7ost.noarch 

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
I will attach a link to sosreports and sysstat logs.

Comment 4 Jeremy 2015-12-23 16:29:24 UTC

-----------------------
    rabbitmq-server_monitor_10000 on pcmk-itw-rhos-ctl-3 'unknown error' (1): call=328, status=Timed Out, exit-reason='none', last-rc-change='Mon Dec 14 06:26:33 2015', queued=0ms, exec=0ms
-----------------------

It looks like pacemaker tried to check the status of rabbitmq, but it did not return. However, pacemaker recovered from this problem. Your output shows that everything is currenlty fine:

-----------------------
 Clone Set: rabbitmq-server-clone [rabbitmq-server]
     Started: [ pcmk-itw-rhos-ctl-1 pcmk-itw-rhos-ctl-2 pcmk-itw-rhos-ctl-3 ]
-----------------------

This seems to be unrelated to the message in the rabbitmq logs, which just shows that one of the connections dropped. When this happens, the client should automatically re-establish the connection.

Comment 7 Peter Lemenkov 2016-11-07 17:54:56 UTC

Going to close this - we never had enough info to find out what's wrong here?