-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing an LDIF from locations other than the LDIF directory fails #4280
Comments
Comment from mreynolds (@mreynolds389) at 2020-08-06 17:49:12 Duplicate of #4049 |
Comment from mreynolds (@mreynolds389) at 2020-08-06 17:49:15 Metadata Update from @mreynolds389:
|
Can confirm this is still an issue with 389-ds-base-2.0.15-1.module_el8+14185+adb3f555.x86_64 on CentOS Stream 8. If I move my LDIF file to |
This is still how it works. This was by design because of issues with FS permissions, selinux, and other OS related restrictions that always seem to get in the way of LDIF imports. We will probably still look into changing some of this to be more flexible, but unfortunately it's not a priority at the moment. |
@mreynolds389 It could be worth documenting examples where the ldif is moved to that location first in all the guides to at least show that. Perhaps even a warning if it's outside of ldif_dir that it may fail and to try that? |
Pretty sure the admin guide explains that the export/import is always set to the server's ldif dir, but I'll confirm tomorrow... |
OK I got it now. Makes sense! The Red Hat Directory Server 11 migration docs explicitly tell you to import your LDIF from /tmp: # dsconf -D 'cn=Directory Manager' ldap://server.example.com backend import userRoot /tmp/migration.ldif And the |
@mreynolds389 If the rh docs are saying to use /tmp, that's a bug, and this needs to be fixed IMO. |
Bug 2081352 opened against RH docs. |
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/51227
Issue Description
If you try to import an LDIF from a directory other than /var/lib/dirsrv/slapd-instance_name/ldif/, the import fails with "No such file or directory".
Package Version and Platform
389-ds-base-1.4.3.10-1.module+el8dsrv+7006+9b1e3ef3.x86_64
Steps to reproduce
Actual results
Expected results
Import should succeed.
Additional information
The same works on RHEL 8.2 (389-ds-base-1.4.2.12-2.module+el8dsrv+6428+6e54c518.x86_64).
The text was updated successfully, but these errors were encountered: