[389-users] Problem - Could not import LDIF file '/ tmp / ldifESlBSW.ldif'. Error: 65280
msauton at redhat.com
Fri Jul 22 18:01:20 UTC 2011
On 07/22/2011 06:35 AM, Michel Bulgado wrote:
> Marc Sauton wrote:
>> On 07/21/2011 03:04 PM, Michel Bulgado wrote:
>>> Recently I just installed 389-ds-1.2.1-1.el5.noarch from EPEL repo,
>>> because in my company we use Active Directory and want to migrate to
>>> I have installed CentOS 5.6 x86_64.
>>> The problem persists when trying to run setup-ds-admin.pl and at the
>>> very end I get an error message.
>>> [11/07/21, 17:08:27] - [Setup] Info Are you ready to set-up your
>>> [11/07/21, 17:08:28] - [Setup] Info yes
>>> [11/07/21, 17:08:28] - [Setup] Info Creating directory server. . .
>>> [11/07/21, 17:08:29] - [Setup] Info Could not import LDIF file '/ tmp /
>>> ldifESlBSW.ldif'. Error: 65280. Output: Importing data ...
>>> [11/07/21, 17:08:29] - [Setup] Fatal Error: Could not create directory
>>> server instance 'michel'.
>>> [11/07/21, 17:08:29] - [Setup] Fatal Exiting. . .
>>> Log file is '/ tmp/setup5jSSdH.log'
>>> Maybe you can help me, google searching for someone I saw the same
>>> problem happened to him and recommended him to move or delete the file
>>> 10-presence.ldif directory schema, but that file does not exist in that
>>> That I could be doing wrong?
>>> 389 users mailing list
>>> 389-users at lists.fedoraproject.org
>> Review the file permissions for /tmp/ldifESlBSW.ldif, so that
>> ns-slapd can read it.
>> And maybe review the output of /tmp/setup5jSSdH.log
> I try changing the file permissions on /tmp but the file disappears
> once you get the script error message and your name changes randomly.
> I have a disable SELinux, I thought it could be an issue of it, in
> fact I ran getenforce to make sure and I returned the message:
> I ran the other commands and this is what I get:
> [michel at michel /]$ id
> uid=500(michel) gid=500(michel) groups=500(michel),502(computacion)
> [michel at michel /]$ ls -ldZ /tmp
> drwxrwxrwt root root system_u:object_r:tmp_t /tmp
> Once again, thanks
For some reason, something unusual happens with the temporary files from
the templates to create the instance.
May be try running setup-ds-admin.pl using sudo or as root.
What about a
rpm -qf /usr/sbin/setup-ds-admin.pl
rpm -q 389-ds-base
More information about the 389-users