[389-users] Problem - Could not import LDIF file '/ tmp / ldifESlBSW.ldif'. Error: 65280

michel at casa.co.cu michel at casa.co.cu
Sat Jul 23 04:41:38 UTC 2011


Marc Sauton <msauton at redhat.com> escribió:

> On 07/22/2011 06:35 AM, Michel Bulgado wrote:
>> Marc Sauton wrote:
>>> On 07/21/2011 03:04 PM, Michel Bulgado wrote:
>>>> Hello
>>>>
>>>> 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 Linux
>>>>
>>>> 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 servers?
>>>> [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
>>>> directory.
>>>>
>>>> That I could be doing wrong?
>>>>
>>>> Thanks
>>>> Michel
>>>> -- 
>>>> 389 users mailing list
>>>> 389-users at lists.fedoraproject.org
>>>> https://admin.fedoraproject.org/mailman/listinfo/389-users
>>> Review the file permissions for /tmp/ldifESlBSW.ldif, so that  
>>> ns-slapd can read it.
>>> And maybe review the output of /tmp/setup5jSSdH.log
>>> M.
>> Hello
>>
>> 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:  
>> "Permissive"
>>
>> 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)  
>> context=user_u:system_r:unconfined_t
>>
>> [michel at michel /]$ ls -ldZ /tmp
>> drwxrwxrwt  root root system_u:object_r:tmp_t          /tmp
>>
>> Once again, thanks
>>
>> Michel
>>
>>
>>
> 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
> and
> rpm -q 389-ds-base
> ?
> M.
>

Hi Marc

The script always has been run as root, using sudo.

Suddenly I can think of two options below:

1 - modify the script in the process of creating the temporary file.  
Ldif, this will change the permissions to that file, to nobody.

2 - create an unprivileged user in the system that is not nobody in  
the configuration and that user would define under which runs the  
directory

I'll put the results of the commands

[root at michel ~]# rpm -qf /usr/sbin/setup-ds-admin.pl
389-admin-1.1.16-1.el5.x86_64

[root at michel ~]# rpm -q 389-ds-base
389-ds-base-1.2.8.3-1.el5.x86_64

Michel


----------------------------------------------
Webmail, servicio de correo electronico
Casa de las Americas - La Habana, Cuba.




More information about the 389-users mailing list