Re: [389-users] replica="unknown": Unable to acquire replica: error: no such replica

[Jared Carter <jared.carter99@xxxxxxxxx>]

Hi Rich, thanks for the reply.  Running this on RHEL 5.7.  Versions of all the 389 stuff I'm using are:

389-ds-base-1.2.5-1.el5
389-dsgw-1.1.4-1.el5
389-ds-1.1.3-6.el5
389-adminutil-1.1.8-4.el5
389-admin-1.1.10-1.el5
389-admin-console-1.1.4-3.el5
389-admin-console-doc-1.1.4-3.el5
389-console-1.1.3-6.el5
389-ds-console-1.2.0-5.el5
389-ds-console-doc-1.2.0-5.el5

How I built a new ldap instance is I built an admin instance first using the script 
/usr/sbin/setup-ds-admin.pl

Then I created a user instance, by opening the 389 admin console.

• Right Click on "Server Group" and select "Create Instance Of" -> "389 Directory Server"
  • Fill in the following Values
    • Server Identifier: <ENV>
    • Network Port: 389
    • Base DN: dc=cyberdyne dc=com
    • Directory Manager DN: cn=Directory Manager
    • Directory Manager Password: ****
      
    • Confirm Password: *****
    • Server Runtime (UNIX) user ID: nobody
  • Click "OK"
    

So then I had my user instance running, with nothing in it, default schema.  Now after that set, this is where I've tried various things, from copying over the schema directory from my good working ldap server to my new one and then trying to setup replicaiton through the 389 admin client.  I would get the "replica="unknown": Unable to acquire replica: error: no such
      replica" error that way.  I  also tried without copying the schema over, got the error that way as well.  Also got the error trying to initialize the new one from the old one in the 389 client.  Note that I did setup replication users on both nodes as well as was trying to use those users for the replication.  

Seems like I'm missing a step in building this new node.  Any help would be great.  I do realize we are using an older version of the 389.  We did run into an issue last time we upgraded versions.  The user instance of ldap wouldn't start under the new version, so due to some constraints we had to roll back the version and have not been able to roll forward again.

On Wed, Dec 14, 2011 at 1:16 PM, Rich Megginson <rmeggins@xxxxxxxxxx> wrote:

On 11/30/2011 12:22 PM, Jared Carter wrote:

Hopefully someone can help me out.  I'm trying to build a new ldap server and replicate the data from one of my current nodes.

If somebody can direct me to a howto on this that would be great.  Right now I've built the new ldap server, but when i setup the replication using either the 389 client or a perl script I keep getting replica errors.  Any ideas, something simple I'm missing?  Error logs below.

What is your platform and version?   Note that you are using a quite old version of 389 - I suggest upgrading to the latest stable which is 389-ds-base-1.2.9.9

Also, can you provide exactly what steps you have followed so far to set up replication?

[30/Nov/2011:10:34:37 -0800] - dblayer_instance_start: pagesize: 4096, pages: 9259981, procpages: 45973
[30/Nov/2011:10:34:37 -0800] - cache autosizing: import cache: 204800k
[30/Nov/2011:10:34:37 -0800] - li_import_cache_autosize: 50, import_pages: 51200, pagesize: 4096
[30/Nov/2011:10:34:37 -0800] - WARNING: Import is running with nsslapd-db-private-import-mem on; No other process is allowed to access the database
[30/Nov/2011:10:34:37 -0800] - dblayer_instance_start: pagesize: 4096, pages: 9259981, procpages: 46009
[30/Nov/2011:10:34:37 -0800] - cache autosizing: import cache: 204800k
[30/Nov/2011:10:34:37 -0800] - li_import_cache_autosize: 50, import_pages: 51200, pagesize: 4096
[30/Nov/2011:10:34:37 -0800] - import userRoot: Beginning import job...
[30/Nov/2011:10:34:37 -0800] - import userRoot: Index buffering enabled with bucket size 100
[30/Nov/2011:10:34:37 -0800] - import userRoot: Processing file "/tmp/ldifqNKrJP.ldif"
[30/Nov/2011:10:34:37 -0800] - import userRoot: Finished scanning file "/tmp/ldifqNKrJP.ldif" (9 entries)
[30/Nov/2011:10:34:38 -0800] - import userRoot: Workers finished; cleaning up...
[30/Nov/2011:10:34:38 -0800] - import userRoot: Workers cleaned up.
[30/Nov/2011:10:34:38 -0800] - import userRoot: Cleaning up producer thread...
[30/Nov/2011:10:34:38 -0800] - import userRoot: Indexing complete.  Post-processing...
[30/Nov/2011:10:34:38 -0800] - import userRoot: Flushing caches...
[30/Nov/2011:10:34:38 -0800] - import userRoot: Closing files...
[30/Nov/2011:10:34:38 -0800] - All database threads now stopped
[30/Nov/2011:10:34:38 -0800] - import userRoot: Import complete.  Processed 9 entries in 1 seconds. (9.00 entries/sec)
    389-Directory/1.2.5 B2010.012.2034
    tx-ds05.prd.cyberdyne.com:390 (/etc/dirsrv/slapd-tx-ds05)

[30/Nov/2011:10:34:38 -0800] - 389-Directory/1.2.5 B2010.012.2034 starting up
[30/Nov/2011:10:34:38 -0800] - I'm resizing my cache now...cache was 209715200 and is now 8000000
[30/Nov/2011:10:34:38 -0800] - slapd started.  Listening on All Interfaces port 390 for LDAP requests
[30/Nov/2011:10:39:58 -0800] NSMMReplicationPlugin - conn=10 op=3 replica="unknown": Unable to acquire replica: error: no such replica
[30/Nov/2011:10:39:59 -0800] NSMMReplicationPlugin - conn=11 op=3 replica="unknown": Unable to acquire replica: error: no such replica
[30/Nov/2011:10:39:59 -0800] NSMMReplicationPlugin - conn=12 op=3 replica="unknown": Unable to acquire replica: error: no such replica
[30/Nov/2011:10:48:22 -0800] NSMMReplicationPlugin - conn=13 op=3 replica="unknown": Unable to acquire replica: error: no such replica
[30/Nov/2011:10:48:22 -0800] NSMMReplicationPlugin - conn=14 op=3 replica="unknown": Unable to acquire replica: error: no such replica

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users