On 1/31/19 9:51 AM, john.ber...@us.fujitsu.com 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:
offvalue 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
*Sent:* Wednesday, January 30, 2019 3:11 PM
*To:* General discussion list for the 389 Directory server project.
<389-users@lists.fedoraproject.org>; Berger, John
*Subject:* Re: [389-users] Import an ldif
On 1/30/19 3:58 PM, john.ber...@us.fujitsu.com
<mailto:john.ber...@us.fujitsu.com> 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@lists.fedoraproject.org
<mailto:389-users@lists.fedoraproject.org>
To unsubscribe send an email to389-users-le...@lists.fedoraproject.org
<mailto:389-users-le...@lists.fedoraproject.org>
Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html
<https://urldefense.proofpoint.com/v2/url?u=https-3A__getfedora.org_code-2Dof-2Dconduct.html=DwMD-g=09aR81AqZjK9FqV5BSCPBw=dWiGkhrpTYElk4V9q_NpSc2K8EN8z9bMIRnOec4Am_w=naZYpGxhTwE7AsgNJU3vObaAlrbU9lPeZ4ORnuHiv-o=HZmMTZh-cUHeN01DZp31xLFOdu73ibSYJ4OhvuqN3_Y=>
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
<https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wiki_Mailing-5Flist-5Fguidelines=DwMD-g=09aR81AqZjK9FqV5BSCPBw=dWiGkhrpTYElk4V9q_NpSc2K8EN8z9bMIRnOec4Am_w=naZYpGxhTwE7AsgNJU3vObaAlrbU9lPeZ4ORnuHiv-o=f37RmCFC-oLPMSkMMtddt-2AjIfNwxfpQPlage1IGbc=>
List Archives:https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.fedoraproject.org_archives_list_389-2Dusers-40lists.fedoraproject.org=DwMD-g=09aR81AqZjK9FqV5BSCPBw=dWiGkhrpTYElk4V9q_NpSc2K8EN8z9bMIRnOec4Am_w=naZYpGxhTwE7AsgNJU3vObaAlrbU9lPeZ4ORnuHiv-o=Bf4gfFr9pP3P6M-4kkyTWwUA1ac-VU6qgqIoaTxVpTY=>
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
