LDIF imports

[Joe Fletcher]

Hi,

Is there something hard-coded into 389 v1.4 such that it can only import data from
/var/lib/dirsrv/<instance>/ldif  ?

I've been trying to initialize a new setup with an export we'd been using for 389
v1.3  but every time it failed with a "file not found" error until the ldif was
copied to /var/lib/....etc.

Cheers


This email with all information contained herein or attached hereto may contain
confidential and/or privileged information intended for the addressee(s) only. If you have
received this email in error, please contact the sender and immediately delete this email
in its entirety and any attachments thereto.

[Marc Sauton]

The path to the LDIF file is not hardcoded, it is usually a file and/or
directory permission and/or SELinux label problem to allow the uid running
the LDAP service to read that file.
It should be the same as in the default LDIF directory provided as an
example.
The errors log file should have a more precise indication.
dsctl some-instance ldif2db userroot some-path/some-file.ldif
Thanks,
M.

On Thu, Dec 30, 2021 at 11:58 AM Joe Fletcher <jfletche(a)sscinc.com&gt; wrote:

>  Hi,
>
>
>
>  Is there something hard-coded into 389 v1.4 such that it can only import
>  data from /var/lib/dirsrv/<instance>/ldif  ?
>
>
>
>  I’ve been trying to initialize a new setup with an export we’d been using
>  for 389 v1.3  but every time it failed with a “file not found” error until
>  the ldif was copied to /var/lib/….etc.
>
>
>
>  Cheers
>
>
>
>
>  This email with all information contained herein or attached hereto may
>  contain confidential and/or privileged information intended for the
>  addressee(s) only. If you have received this email in error, please contact
>  the sender and immediately delete this email in its entirety and any
>  attachments thereto.
>  _______________________________________________
>  389-users mailing list -- 389-users(a)lists.fedoraproject.org
>  To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]...
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>

[Joe Fletcher]

Ok. Same file in var/tmp doesn’t work. Copy it to var lib dirsrv and it does work. Selinux
is inactive on this system. Even set to 777 I get the “no such file” error. Not a
show-stopper. I can work with the default location.


On 3 Jan 2022, at 19:03, Marc Sauton <msauton(a)redhat.com&gt; wrote:


**** The e-mail below is from an external source. Please do not open attachments or click
links from an unknown or suspicious origin. ****


The path to the LDIF file is not hardcoded, it is usually a file and/or directory
permission and/or SELinux label problem to allow the uid running the LDAP service to read
that file.
It should be the same as in the default LDIF directory provided as an example.
The errors log file should have a more precise indication.
dsctl some-instance ldif2db userroot some-path/some-file.ldif
Thanks,
M.

On Thu, Dec 30, 2021 at 11:58 AM Joe Fletcher
<[e-mail]<mailto:[e-mail]>> wrote:
Hi,

Is there something hard-coded into 389 v1.4 such that it can only import data from
/var/lib/dirsrv/<instance>/ldif  ?

I’ve been trying to initialize a new setup with an export we’d been using for 389 v1.3 
but every time it failed with a “file not found” error until the ldif was copied to
/var/lib/….etc.

Cheers


This email with all information contained herein or attached hereto may contain
confidential and/or privileged information intended for the addressee(s) only. If you have
received this email in error, please contact the sender and immediately delete this email
in its entirety and any attachments thereto.
_______________________________________________
389-users mailing list --
[e-mail]<mailto:[e-mail]>
To unsubscribe send an email to
[e-mail]<mailto:[e-mail]>
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/<https://...
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines<https://urldefe...
List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]...
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure<https://urldefense.com/v3/__ht...
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://urldefense.com/v3/__https://docs.fedoraproject.org/en-US/project/...
List Guidelines:
https://urldefense.com/v3/__https://fedoraproject.org/wiki/Mailing_list_g...
List Archives:
https://urldefense.com/v3/__https://lists.fedoraproject.org/archives/list...
Do not reply to spam on the list, report it:
https://urldefense.com/v3/__https://pagure.io/fedora-infrastructure__;!!J...
This email with all information contained herein or attached hereto may contain
confidential and/or privileged information intended for the addressee(s) only. If you have
received this email in error, please contact the sender and immediately delete this email
in its entirety and any attachments thereto.