RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 984968 - Qpid is not starting correctly on F18, F19 and CentOS 6.4
Summary: Qpid is not starting correctly on F18, F19 and CentOS 6.4
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: RDO
Classification: Community
Component: distribution
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Darryl L. Pierce
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-16 13:46 UTC by Dave Neary
Modified: 2015-06-22 00:08 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-17 18:04:14 UTC
Embargoed:

Attachments (Terms of Use)

Description Dave Neary 2013-07-16 13:46:23 UTC 
On a clean Fedora 18, Fedora 19 and CentOS 6.4 installation, we have reports of qpid not starting, and having issues starting because of a missing sasldb file.

* http://openstack.redhat.com/forum/discussion/326/fedora18-packstack-post-installation-issues
* http://openstack.redhat.com/forum/discussion/293/error-on-openstack-status/p1
* http://openstack.redhat.com/Qpid_errors
* http://openstack.redhat.com/forum/discussion/289/fresh-install-broken-after-restart/p1
Comment 1 Steven Hardy 2014-01-07 22:16:28 UTC 
Hmm, I think I may have duplicated this bug with my report under bug #1049488

This problem still seems to occur with latest RDO Havana installed via the F20 repos, several services fail to connect to until qpidd is restarted after reboot, this is a repeatable failure on my test platform.
Comment 2 Alan Pevec 2014-01-09 17:39:19 UTC 
Steve, do you see qpidd.sasldb corruption as described in http://openstack.redhat.com/Qpid_errors ?
Comment 3 Steven Hardy 2014-05-20 09:42:21 UTC 
(In reply to Alan Pevec from comment #2)
> Steve, do you see qpidd.sasldb corruption as described in
> http://openstack.redhat.com/Qpid_errors ?

No, I don't think that was the problem, but recent qpid versions seem to have fixed my issue, which I think was a duplicate of bz #1055660 and not related to the sasldb problem.
Comment 5 Lars Kellogg-Stedman 2015-03-17 18:04:14 UTC 
I'm closing this bz: F18 and F19 are both end-of-life, and our deployments are now using rabbitmq.
Note You need to log in before you can comment on or make changes to this bug.