On 07/25/2011 02:17 PM, michel(a)casa.co.cu wrote:
Rich Megginson<rmeggins(a)redhat.com> escribió:
> On 07/21/2011 04: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
> What version of 389-ds-base? rpm -qi 389-ds-base
>
> FYI, 389 is not a drop in replacement for Active Directory - so you will
> run into problems if you are trying to support windows clients from 389.
>> 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?
> Not sure.
>
> Run setup-ds-admin.pl -ddd - edit the resulting log file to remove any
> sensitive data - post to
fpaste.org and paste the link in an email
>
> Also, is there anything in the directory server errors log -
> /var/log/dirsrv/slapd-INSTNAME/errors
>> Thanks
>> Michel
>> --
I solved the problem I had when trying to import the schema. Ldiff,
basically one of my previous attempts to mount the directory, had
created a directory in / var / lib / dirsrv-INSTANCE on other users,
since they did not allow permission problems mounted directory fedora.
I just had to remove that instance and recreate it running the script.
put in place, the log, since I called attention to the messages that I
returned the script.
I see many messages: error No such object
Those are fine. The way the script works
is that it first attempts to
search for the object, gets "No such object", then adds the object.
I wonder if I will bring problems in the future to work with fedora
directory?
http://fpaste.org/fmUu/ Looks like setup completed successfully?
Note - in the future, use
remove-ds-admin.pl -y
to completely remove everything.
#rpm -qi 389-ds-base
Name : 389-ds-base Relocations: (not relocatable)
Version : 1.2.8.3 Vendor: Fedora Project
Release : 1.el5 Build Date: Mon 02 May
2011 12:36:56 PM CDT
Install Date: Thu 21 Jul 2011 04:20:47 PM CDT Build Host:
x86-10.phx2.fedoraproject.org
Group : System Environment/Daemons Source RPM:
389-ds-base-1.2.8.3-1.el5.src.rpm
Size : 4953090 License: GPLv2 with exceptions
Signature : DSA/SHA1, Mon 02 May 2011 01:00:08 PM CDT, Key ID
119cc036217521f6
Packager : Fedora Project
URL :
http://port389.org/
Summary : 389 Directory Server (base)
Description :
389 Directory Server is an LDAPv3 compliant server. The base package includes
the LDAP server and command line utilities for server administration.
Thanks
Michel
----------------------------------------------
Webmail, servicio de correo electronico
Casa de las Americas - La Habana, Cuba.
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users