Re: Import an ldif

Mark Reynolds <mreynolds@xxxxxxxxxx> · Thu, 31 Jan 2019 10:16:26 -0500



    On 1/31/19 9:51 AM,
      John.Berger@xxxxxxxxxxxxxx wrote:

    
        Mark,
         
        Thanks for the
            follow up.  I was able to change the schema value to off
            just fine.  However, when we edited the dse.ldif file for
            the DS that is running on port 389 (slapd-test) the
          nsslapd-syntaxcheck: off value was not in the file so we just
            added it and restarted the ldap server.  The import still
            failed to pull in the users that had values that were blank.
         
        Most likely I
            am missing something or edited the wrong dse.ldif file.
      
    
    This is why I said to use ldapmodify.  If you edit dse.ldif while
      the server is running those changes get overwritten.  If you want
      to directly edit dse.ldif, then stop the server first and then
      make your changes. Try that and let me know how it goes.
    Thanks,
    Mark

    
        Please bear
            with me because I am not a Unix person at all, so many times
            things like this confuse me.
         
        My apologies,
         
        John
        
          
            From: Mark Reynolds
                <mreynolds@xxxxxxxxxx>
                

                Sent: Wednesday, January 30, 2019 3:11 PM

                To: General discussion list for the 389 Directory
                server project.
                <389-users@xxxxxxxxxxxxxxxxxxxxxxx>; Berger, John
                <John.Berger@xxxxxxxxxxxxxx>

                Subject: Re: [389-users] Import an ldif
          
        
          On 1/30/19 3:58 PM, 
              John.Berger@xxxxxxxxxxxxxx wrote:
        
        
          We are trying to import an ldif file from
            our old Sun One Directory Server 5.2. We have the 389 server
            set up and running. I can initialize the database I want to
            import in and it seems to work fine. However, we have a lot
            of users that do not get imported in due a syntax error on
            certain attributes because they are blank. Example:  We have
            an attribute called Title which was never required so many
            of the users have it blank. These error on import. 
            Is there a way to get the 389 server to disregard that
              and load the user anyway? Basically we want to pull
              everything in even if the fields are blank.
        
        Ideally you could write a script to strip those empty
          attributes from the LDIF. 
          
        Otherwise you can turn off schema checking (syntax checking
          might also need to be disabled)
        cn=config

            nsslapd-schemacheck: off

            nsslapd-syntaxcheck: off 
        Use ldapmodify to set these attributes (same as Sun DS), and
          stop the server before you import.  After the import completes
          you should turn these settings back "on".
          
        HTH,
        Mark
         
        
          Regards,
           
          John
          

          _______________________________________________
          389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
          To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
          Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
          List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
          List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
        
      
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx