Bug 1293949 - RabbitMQ experienceing "unknown error" [NEEDINFO]
RabbitMQ experienceing "unknown error"
Status: CLOSED INSUFFICIENT_DATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server (Show other bugs)
6.0 (Juno)
Unspecified Unspecified
high Severity high
: ---
: 6.0 (Juno)
Assigned To: Peter Lemenkov
Udi Shkalim
: Unconfirmed, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-23 11:24 EST by Jeremy
Modified: 2016-11-07 12:54 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-07 12:54:56 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
jeckersb: needinfo? (jmelvin)


Attachments (Terms of Use)

  None (edit)
Description Jeremy 2015-12-23 11:24:32 EST
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 11:29:24 EST
-----------------------
    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 12:54:56 EST
Going to close this - we never had enough info to find out what's wrong here?

Note You need to log in before you can comment on or make changes to this bug.