Re: [389-users] db import failure, when setting replication up

Noriko Hosoi <nhosoi@xxxxxxxxxx> · Tue, 17 May 2011 13:01:36 -0700



    Hi Reinhard,

    
    Reinhard Nappert wrote:
    
      
      Hi Noriko,
       
      I have to correct
            myself. The box which had the import issue was on a 1.2.7.5
            system. The other box was running 1.2.8.2.
       
      So, it looks like you
            have fixed the issue with 1.2.8.2.
    
    *relieved*  Thanks for testing it on 1.2.8.2!

    --noriko

    
      Thanks,
      -Reinhard
      

        From:
          389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx
          [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On
            Behalf Of Reinhard Nappert

          Sent: Tuesday, May 17, 2011 3:21 PM

          To: General discussion list for the 389 Directory
          server project.

          Subject: Re: [389-users] db import failure, when
          setting replication up

        
      1.2.8.2
       
      -Reinhard
      

        From:
          389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx
          [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On
            Behalf Of Noriko Hosoi

          Sent: Tuesday, May 17, 2011 2:16 PM

          To: General discussion list for the 389 Directory
          server project.

          Subject: Re: [389-users] db import failure, when
          setting replication up

        
      It looks to me you have hit this bug...  Which version of
      389-ds-base you are running?

      Bug 684996
        - Exported tombstone cannot be
            imported correctly. 

      
      The patch should be in the version 1.2.8.2.

      Thanks,

      --noriko

      
      On 05/17/2011 11:03 AM, Reinhard Nappert wrote:
      
        
        Hi,
         
        I have seen the following:
         
        I set 2 systems up in MMR.
              Replication worked. For some reason, I needed to take one
              of the boxes out of the replication and disabled
              replication. Later on, I enabled it again and created the
              shadowing agreement to the other box. Now, I saw the
              following errors during the import of the db:
         
        [17/May/2011:11:46:04 -0400]
              NSMMReplicationPlugin - multimaster_be_state_change

              : replica o=base is going offline; disabling replication

              [17/May/2011:11:46:07 -0400] - WARNING: Import is running
              with nsslapd-db-privat

              e-import-mem on; No other process is allowed to access the
              database

              [17/May/2011:11:46:08 -0400] - import userRoot: WARNING:
              Skipping entry "nsuniqu

              eid=06869502-7fe011e0-8f589300-7e7b2163,ou=sample,o=base"
              which has no parent, 
        ending at line 0 of file "(bulk
              import)"

              [17/May/2011:11:46:08 -0400] - import userRoot: WARNING:
              bad entry: ID 453

              .....
         
        Any idea, what is going on
              there?
         
        Thanks,
        -Reinhard
        
--
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
    
    
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users