Bug 200989

Summary: "Consumer server unreachable" message even though server is reachable
Product: [Retired] 389 Reporter: Daniel Lipsitt <danlipsitt>
Component: Replication - GeneralAssignee: Rich Megginson <rmeggins>
Status: CLOSED DUPLICATE QA Contact: Chandrasekar Kannan <ckannan>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: benl
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-18 06:22:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 152373, 240316    

Description Daniel Lipsitt 2006-08-02 00:25:08 UTC
Description of problem:
When I create a replication agreement, I get a dialog saying:

"Consumer server unreachable or invalid credentials supplied. Unable to perform
subtree duplication verification. Do you wish to continue?"

If I continue, the replication nonetheless occurs. The error message appears
immediately, which made me suspect that the reachability test does not occur. I
attempted a packet capture with ethereal, and saw no traffic to the consumer on
port 389 or 636. I see the message even though I supply the correct credentials.
I believe it also occurs no matter what port I select.

Version-Release number of selected component (if applicable):
fedora-ds-1.0.2-1.RHEL4

Steps to Reproduce:
1. New replication agreement
2. select "Using encrypted SSL connection"
3. Enter bind and password info
4. click Next

Comment 1 Rich Megginson 2006-09-05 21:07:52 UTC
Try to reproduce using ldapsearch from the command line.
cd /opt/fedora-ds/shared/bin
./ldapsearch -h remotehost -p remoteport -Z -P
/opt/fedora-ds/alias/slapd-yourhost-cert8.db -D "repl manager DN" -w
replmanpassword -s base -b "" "objectclass=*"

Comment 2 Daniel Lipsitt 2006-09-05 21:24:33 UTC
I get:

SSL initialization failed: error -8174 (security library: bad database.)


Comment 3 Rich Megginson 2006-09-05 21:39:39 UTC
Is replication working?

Comment 4 Daniel Lipsitt 2006-09-07 18:17:43 UTC
Yes, replication is working.

Comment 5 Rich Megginson 2006-09-07 18:21:48 UTC
Ok.  I'm trying to gauge the severity of this issue.  It sounds like a low
severity i.e. it's just some random (possibly bogus) error message in the
console when setting up the replication agreement.  Other than that, everything
seems to be working fine?

Comment 6 Daniel Lipsitt 2006-09-07 19:16:02 UTC
Yes, things seem to work fine if you ignore the message. If you don't know that
you can ignore it, it prevents you from setting up replication at all.

By the way, I see that I didn't mention that my supplier is x86_64 and my
consumer is x86. I don't know whether that's significant.

Comment 7 Chandrasekar Kannan 2007-10-18 06:22:14 UTC

*** This bug has been marked as a duplicate of 179193 ***