Bug 711468 - qpidd complains about missing sasldb file and prevents connections
Summary: qpidd complains about missing sasldb file and prevents connections
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 2.0
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 15:03 UTC by Robert Rati
Modified: 2011-06-07 15:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-07 15:46:42 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Robert Rati 2011-06-07 15:03:32 UTC 
Description of problem:
On RHEL6, I installed qpid-cpp-server and started it.  I have 1 agent (wallaby) and 3 consoles (configd's) communicating with the broker.  Looking the logs, I see:

mrg13 qpidd[28670]: unable to open Berkeley db /var/lib/qpidd/qpidd.sasldb: No such file or directory

Every 2 minutes or so until qpidd eventually stops accepting new connections:
Jun  7 08:50:31 mrg13 qpidd[28670]: unable to open Berkeley db /var/lib/qpidd/qpidd.sasldb: No such file or directory
Jun  7 08:52:41 mrg13 qpidd[28670]: 2011-06-07 08:52:41 error Client max connection count limit exceeded: 500 connection refused


Version-Release number of selected component (if applicable):
qpid-cpp-server-0.10-5

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Robert Rati 2011-06-07 15:46:42 UTC 
It seems something was connecting to my test broker from a machine I wasn't using that was opening up a bunch of connections and causing the issue.
Note You need to log in before you can comment on or make changes to this bug.