Discussion:
[389-users] Problem - Could not import LDIF file '/ tmp / ldifESlBSW.ldif'. Error: 65280
Michel Bulgado
2011-07-21 22:04:46 UTC
Permalink
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
Marc Sauton
2011-07-21 23:36:29 UTC
Permalink
Post by Michel Bulgado
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.
michel
2011-07-22 01:25:04 UTC
Permalink
Post by Marc Sauton
Post by Michel Bulgado
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
--
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.
Hi

The script ran it as root, I do not understand how you may be unable
to import the file ldiff stored in /tmp as root who runs the script
and also access any system resource.

It may be that you specify the user under which runs the 389-ds is "nobody"?

I send you the log file generated by the script.

Sorry for my english is very poor

Michel

----------------------------------------------
Webmail, servicio de correo electronico
Casa de las Americas - La Habana, Cuba.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: setup5jSSdH.log
Type: text/x-log
Size: 10859 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20110721/f3d300c9/attachment-0001.bin
Marc Sauton
2011-07-22 04:48:48 UTC
Permalink
Post by michel
Post by Marc Sauton
Post by Michel Bulgado
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
--
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.
Hi
The script ran it as root, I do not understand how you may be unable
to import the file ldiff stored in /tmp as root who runs the script
and also access any system resource.
It may be that you specify the user under which runs the 389-ds is "nobody"?
Yes.
Try either
chown nobody:nobody /tmp/ldifESlBSW.ldif
or
chmod a+r /tmp/ldifESlBSW.ldif

If this is till a problem, what does the command
getenforce
returns?

and also:
id
ls -ldZ /tmp
ls -lZ /tmp/ldifESlBSW.ldif

M.
Post by michel
I send you the log file generated by the script.
Sorry for my english is very poor
Michel
----------------------------------------------
Webmail, servicio de correo electronico
Casa de las Americas - La Habana, Cuba.
Michel Bulgado
2011-07-22 13:35:42 UTC
Permalink
Post by Marc Sauton
Post by Michel Bulgado
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
Marc Sauton
2011-07-22 18:01:20 UTC
Permalink
Post by Michel Bulgado
Post by Marc Sauton
Post by Michel Bulgado
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
"Permissive"
[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.
michel
2011-07-23 04:41:38 UTC
Permalink
Post by Marc Sauton
Post by Michel Bulgado
Post by Marc Sauton
Post by Michel Bulgado
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
"Permissive"
[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.
Rich Megginson
2011-07-25 18:43:54 UTC
Permalink
Post by Michel Bulgado
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.
Post by Michel Bulgado
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
Post by Michel Bulgado
Thanks
Michel
--
389 users mailing list
389-users at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
michel
2011-07-25 20:17:22 UTC
Permalink
Post by Rich Megginson
Post by Michel Bulgado
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.
Post by Michel Bulgado
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
Post by Michel Bulgado
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

I wonder if I will bring problems in the future to work with fedora directory?

http://fpaste.org/fmUu/


#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.
Rich Megginson
2011-07-25 20:22:53 UTC
Permalink
Post by michel
Post by Rich Megginson
Post by Michel Bulgado
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.
Post by Michel Bulgado
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
Post by Michel Bulgado
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.
Post by michel
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.
Post by michel
#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
x86-10.phx2.fedoraproject.org
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)
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 at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
michel
2011-07-27 00:26:01 UTC
Permalink
Post by Rich Megginson
Post by michel
Post by Rich Megginson
Post by Michel Bulgado
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.
Post by Michel Bulgado
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
Post by Michel Bulgado
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.
Post by michel
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.
Post by michel
#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
x86-10.phx2.fedoraproject.org
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)
389 Directory Server is an LDAPv3 compliant server. The base
package includes
the LDAP server and command line utilities for server administration.
Thanks
Michel
Rich

In the previous post you said:

"389 is not a drop in replacement for Active Directory - so You Will
if you run into Problems are Trying to support Windows clients from 389. "

Could explain where it may have problems?

Perhaps you can not deploy policies?
Authenticate computers on the domain
The services that I use on my network, users could authenticate as e
(dovecot) via pop3, squid.

Even through the horde could sork module, which allows you to change
passwords to an LDAP or Windows Active Directory?

What exactly could bring me problems?

regards
Michel


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

Loading...