Bug 1293949 - RabbitMQ experienceing "unknown error"
Summary: RabbitMQ experienceing "unknown error"
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 6.0 (Juno)
Assignee: Peter Lemenkov
QA Contact: Udi Shkalim
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-23 16:24 UTC by Jeremy
Modified: 2023-09-14 03:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-07 17:54:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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?

Comment 8 Red Hat Bugzilla 2023-09-14 03:15:21 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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