[Fedora-directory-users] Trouble registering a new DS instance with an existing Configuration Directory Server
3:17 a.m.
Hello list,
I have/want the following configuration:
box1: RHDS master server
box2: A read only replica.
The installation on box1 completed sucessfully, but some problem has arised on
box2.
Installation of the RPM-files works well, but running setup-ds-admin.pl
is troublesome. As recommended in the docoumentation I want to use the
existing Configuration Directory Server on box1 for the replica
install on box2, but the installation fails with the following error:
Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.
[08/05/20:12:23:04] - [Setup] Info Administration port
[08/05/20:12:23:37] - [Setup] Info 9830
[08/05/20:12:23:37] - [Setup] Info The interactive phase is complete.
The script will now set up your
servers. Enter No or go Back if you want to change something.
[08/05/20:12:23:37] - [Setup] Info Are you ready to set up your servers?
[08/05/20:12:23:42] - [Setup] Info yes
[08/05/20:12:23:42] - [Setup] Info Creating directory server . . .
[08/05/20:12:23:46] - [Setup] Info Your new DS instance 'd20dcvl002'
was successfully created.
[08/05/20:12:23:46] - [Setup] Info Creating the configuration
directory server . . .
[08/05/20:12:23:46] - [Setup] Info Error adding entry 'cn=Red Hat
Directory Server, cn=Server Group, cn=d20dcvl002.internsone2.local,
ou=internsone2.local, o=NetscapeRoot'. Error: No such object
[08/05/20:12:23:46] - [Setup] Fatal Could not register the directory
server with the configuration directory server.
[08/05/20:12:23:46] - [Setup] Fatal Exiting . . .
Log file is '/tmp/setupCvZ4zW.log'
-------------------------------------------------------------------------------------------------------------
SSL/TLS is disabled on box1. The o=NetscapeRoot DIT looks okay, and the
branch for box1 seems to be correct and working.
Do you have any suggestions for how I can debug this problem?
Thanks,
Erling Ringen Elvsrud
8:55 a.m.
New subject: [Fedora-directory-users] Trouble registering a new DS instance with an existing Configuration Directory Server
Hello,
We experienced the same issue...
Erling Ringen Elvsrud a écrit :
Hello list,
I have/want the following configuration:
box1: RHDS master server
box2: A read only replica.
The installation on box1 completed sucessfully, but some problem has arised on
box2.
[08/05/20:12:23:46] - [Setup] Fatal Could not register the directory
server with the configuration directory server.
[08/05/20:12:23:46] - [Setup] Fatal Exiting . . .
Erling Ringen Elvsrud
We setted up 2 Fedora Core 8 Virtual machines : vmware-fds1 and vmware-fds2
yum update before installation.
On the first one, installation of FDS 1.1 with yum and setup. It works
fine.
One the second one, copycat.
We tried to join the administration domain created in the first one and
got the same message.
Both Virtual Machines are one the same LAN. The network is OK.
Both servers are in NTP sync, this is helpfull.
The setup log is in the attached file.
Here is the slapd log of vmware-fds1 :
*
Stage 1 : FDS Startup*
Fedora-Directory/1.1.0 B2008.03.27
vmware-fds1.inrp.fr:389 (/etc/dirsrv/slapd-vmware-fds1)
[23/May/2008:13:35:50 +0200] conn=0 fd=64 slot=64 connection from
127.0.0.1 to 127.0.0.1
[23/May/2008:13:35:50 +0200] conn=0 op=0 BIND dn="" method=128 version=3
[23/May/2008:13:35:50 +0200] conn=0 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn=""
[23/May/2008:13:35:50 +0200] conn=0 op=1 SRCH
base="cn=admin-serv-vmware-fds1, cn=Fedora Administration Server, cn=
Server Group, cn=vmware-fds1.inrp.fr, ou=inrp.fr, o=NetscapeRoot"
scope=2 filter="(nsExecRef=*)" attrs="nsExecRef n
sLogSuppress"
[23/May/2008:13:35:50 +0200] conn=0 op=1 RESULT err=0 tag=101 nentries=0
etime=0
[23/May/2008:13:35:50 +0200] conn=0 op=2 UNBIND
[23/May/2008:13:35:50 +0200] conn=0 op=2 fd=64 closed - U1
[23/May/2008:13:35:51 +0200] conn=1 fd=64 slot=64 connection from
127.0.0.1 to 127.0.0.1
[23/May/2008:13:35:51 +0200] conn=1 op=0 BIND dn="" method=128 version=3
[23/May/2008:13:35:51 +0200] conn=1 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn=""
[23/May/2008:13:35:51 +0200] conn=1 op=1 SRCH
base="cn=admin-serv-vmware-fds1, cn=Fedora Administration Server, cn=
Server Group, cn=vmware-fds1.inrp.fr, ou=inrp.fr, o=NetscapeRoot"
scope=2 filter="(nsExecRef=*)" attrs="nsExecRef n
sLogSuppress"
[23/May/2008:13:35:51 +0200] conn=1 op=1 RESULT err=0 tag=101 nentries=0
etime=0
[23/May/2008:13:35:51 +0200] conn=1 op=2 UNBIND
[23/May/2008:13:35:51 +0200] conn=1 op=2 fd=64 closed - U1
*
Stage 2 : Setup on vmware-fds2 *
Configuration directory server URL :
*ldap://vmware-fds1.inrp.fr:389/o=NetscapeRoot*
Configuration directory server admin ID *admin*
Configuration directory server admin password : *******
Configuration directory server admin domain : *inrp.fr*
[23/May/2008:14:31:46 +0200] conn=2 fd=64 slot=64 connection from
195.83.134.21 to 195.83.134.29
[23/May/2008:14:31:46 +0200] conn=2 op=0 BIND dn="" method=128 version=3
[23/May/2008:14:31:46 +0200] conn=2 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn=""
[23/May/2008:14:31:46 +0200] conn=2 op=1 SRCH base="o=NetscapeRoot"
scope=2 filter="(uid=admin)" attrs="dn"
[23/May/2008:14:31:46 +0200] conn=2 op=1 RESULT err=0 tag=101 nentries=1
etime=0
[23/May/2008:14:31:46 +0200] conn=2 op=2 BIND dn="uid=admin,
ou=Administrators, ou=TopologyManagement, o=NetscapeRo
ot" method=128 version=3
[23/May/2008:14:31:46 +0200] conn=2 op=2 RESULT err=0 tag=97 nentries=0
etime=0 dn="uid=admin,ou=administrators,ou=
topologymanagement,o=netscaperoot"
[23/May/2008:14:31:46 +0200] conn=2 op=3 SRCH base="ou=inrp.fr,
o=NetscapeRoot" scope=0 filter="(objectClass=*)" at
trs="dn"
[23/May/2008:14:31:46 +0200] conn=2 op=3 RESULT err=0 tag=101 nentries=1
etime=0
[23/May/2008:14:31:46 +0200] conn=2 op=4 UNBIND
[23/May/2008:14:31:46 +0200] conn=2 op=4 fd=64 closed - U1
*Stage 3 : Are you ready to set up your servers? : YES*
[23/May/2008:14:38:30 +0200] conn=3 fd=64 slot=64 connection from
195.83.134.21 to 195.83.134.29
[23/May/2008:14:38:30 +0200] conn=3 op=0 BIND dn="" method=128 version=3
[23/May/2008:14:38:30 +0200] conn=3 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn=""
[23/May/2008:14:38:30 +0200] conn=3 op=1 SRCH base="o=NetscapeRoot"
scope=2 filter="(uid=admin)" attrs="dn"
[23/May/2008:14:38:30 +0200] conn=3 op=1 RESULT err=0 tag=101 nentries=1
etime=0
[23/May/2008:14:38:30 +0200] conn=3 op=2 BIND dn="uid=admin,
ou=Administrators, ou=TopologyManagement, o=NetscapeRo
ot" method=128 version=3
[23/May/2008:14:38:30 +0200] conn=3 op=2 RESULT err=0 tag=97 nentries=0
etime=0 dn="uid=admin,ou=administrators,ou=
topologymanagement,o=netscaperoot"
[23/May/2008:14:38:30 +0200] conn=3 op=3 SRCH base="o=NetscapeRoot"
scope=0 filter="(objectClass=*)" attrs="* aci"
[23/May/2008:14:38:30 +0200] conn=3 op=3 RESULT err=0 tag=101 nentries=1
etime=0
[23/May/2008:14:38:30 +0200] conn=3 op=4 MOD dn="o=NetscapeRoot"
[23/May/2008:14:38:30 +0200] conn=3 op=4 RESULT err=0 tag=103 nentries=0
etime=0
[23/May/2008:14:38:30 +0200] conn=3 op=5 SRCH base="cn=Fedora Directory
Server, cn=Server Group, cn=vmware-fds2.inr
p.fr, ou=inrp.fr, o=NetscapeRoot" scope=0 filter="(objectClass=*)"
attrs="* aci"
[23/May/2008:14:38:30 +0200] conn=3 op=5 RESULT err=32 tag=101
nentries=0 etime=0
[23/May/2008:14:38:30 +0200] conn=3 op=6 ADD dn="cn=Fedora Directory
Server, cn=Server Group, cn=vmware-fds2.inrp.f
r, ou=inrp.fr, o=NetscapeRoot"
*[23/May/2008:14:38:30 +0200] conn=3 op=6 RESULT err=32 tag=105
nentries=0 etime=0*
[23/May/2008:14:38:30 +0200] conn=3 op=7 UNBIND
[23/May/2008:14:38:30 +0200] conn=3 op=7 fd=64 closed - U1
HELP !
--
*Nicolas CAREL
**Service Commun Informatique
*IT Manager
Trust my certificate : http://igc.cru.fr/trust.php
*Institut National de Recherche Pédagogique
<http://www.inrp.fr/>*19 allée de Fontenay - B.P. 17424 - 69347 LYON
CEDEX 07
Standard : 04 72 76 61 00 - Télécopie : 04 72 76 61 10
[08/05/23:14:23:23] - [Setup] Info This program will set up the Fedora Directory and
Administration Servers.
It is recommended that you have "root" privilege to set up the software.
Tips for using this program:
- Press "Enter" to choose the default and go to the next screen
- Type "Control-B" then "Enter" to go back to the previous screen
- Type "Control-C" to cancel the setup program
[08/05/23:14:23:23] - [Setup] Info Would you like to continue with set up?
[08/05/23:14:23:32] - [Setup] Info yes
[08/05/23:14:23:32] - [Setup] Info BY SETTING UP AND USING THIS SOFTWARE YOU ARE
CONSENTING TO BE BOUND BY
AND ARE BECOMING A PARTY TO THE AGREEMENT FOUND IN THE
LICENSE.TXT FILE. IF YOU DO NOT AGREE TO ALL OF THE TERMS
OF THIS AGREEMENT, PLEASE DO NOT SET UP OR USE THIS SOFTWARE.
[08/05/23:14:23:32] - [Setup] Info Do you agree to the license terms?
[08/05/23:14:24:02] - [Setup] Info yes
[08/05/23:14:24:02] - [Setup] Info Your system has been scanned for potential problems,
missing patches,
etc. The following output is a report of the items found that need to
be addressed before running this software in a production
environment.
Fedora Directory Server system tuning analysis version 10-AUGUST-2007.
NOTICE : System is i686-unknown-linux2.6.24.7-92.fc8 (1 processor).
WARNING: 503MB of physical memory is available on the system. 1024MB is recommended for
best performance on large production system.
NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds
(120 minutes). This may cause temporary server congestion from lost
client connections.
WARNING: There are only 1024 file descriptors (hard limit) available, which
limit the number of simultaneous connections.
WARNING: There are only 1024 file descriptors (soft limit) available, which
limit the number of simultaneous connections.
[08/05/23:14:24:02] - [Setup] Info Would you like to continue?
[08/05/23:14:24:13] - [Setup] Info yes
[08/05/23:14:24:13] - [Setup] Info Choose a setup type:
1. Express
Allows you to quickly set up the servers using the most
common options and pre-defined defaults. Useful for quick
evaluation of the products.
2. Typical
Allows you to specify common defaults and options.
3. Custom
Allows you to specify more advanced options. This is
recommended for experienced server administrators only.
To accept the default shown in brackets, press the Enter key.
[08/05/23:14:24:13] - [Setup] Info Choose a setup type
[08/05/23:14:24:30] - [Setup] Info 2
[08/05/23:14:24:30] - [Setup] Info Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
<hostname>.<domainname>
Example: eros.example.com.
To accept the default shown in brackets, press the Enter key.
[08/05/23:14:24:30] - [Setup] Info Computer name
[08/05/23:14:24:50] - [Setup] Info vmware-fds2.inrp.fr
[08/05/23:14:24:50] - [Setup] Info The servers must run as a specific user in a specific
group.
It is strongly recommended that this user should have no privileges
on the computer (i.e. a non-root user). The setup procedure
will give this user/group some permissions in specific paths/files
to perform server-specific operations.
If you have not yet created a user and group for the servers,
create this user and group using your native operating
system utilities.
[08/05/23:14:24:50] - [Setup] Info System User
[08/05/23:14:25:00] - [Setup] Info dirsrv
[08/05/23:14:25:00] - [Setup] Info System Group
[08/05/23:14:25:05] - [Setup] Info dirsrv
[08/05/23:14:25:05] - [Setup] Info Server information is stored in the configuration
directory server.
This information is used by the console and administration server to
configure and manage your servers. If you have already set up a
configuration directory server, you should register any servers you
set up or create with the configuration server. To do so, the
following information about the configuration server is required: the
fully qualified host name of the form
<hostname>.<domainname>(e.g. hostname.example.com), the port number
(default 389), the suffix, the DN and password of a user having
permission to write the configuration information, usually the
configuration directory administrator, and if you are using security
(TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
number (default 636) instead of the regular LDAP port number, and
provide the CA certificate (in PEM/ASCII format).
If you do not yet have a configuration directory server, enter 'No' to
be prompted to set up one.
[08/05/23:14:25:05] - [Setup] Info Do you want to register this software with an existing
configuration directory server?
[08/05/23:14:25:21] - [Setup] Info yes
[08/05/23:14:25:21] - [Setup] Info Please specify the information about your configuration
directory
server. The following information is required:
- host (fully qualified), port (non-secure or secure), suffix,
protocol (ldap or ldaps) - this information should be provided in the
form of an LDAP url e.g. for non-secure
ldap://host.example.com:389/o=NetscapeRoot
or for secure
ldaps://host.example.com:636/o=NetscapeRoot
- admin ID and password
- admin domain
- a CA certificate file may be required if you choose to use ldaps and
security has not yet been configured - the file must be in PEM/ASCII
format - specify the absolute path and filename
[08/05/23:14:25:21] - [Setup] Info Configuration directory server URL
[08/05/23:14:30:15] - [Setup] Info ldap://vmware-fds1.inrp.fr:389/o=NetscapeRoot
[08/05/23:14:30:15] - [Setup] Info Configuration directory server admin ID
[08/05/23:14:30:34] - [Setup] Info admin
[08/05/23:14:30:34] - [Setup] Info Configuration directory server admin password
[08/05/23:14:31:29] - [Setup] Info Configuration directory server admin domain
[08/05/23:14:31:47] - [Setup] Info inrp.fr
[08/05/23:14:31:47] - [Setup] Info The standard directory server network port number is
389. However, if
you are not logged as the superuser, or port 389 is in use, the
default value will be a random unused port number greater than 1024.
If you want to use port 389, make sure that you are logged in as the
superuser, that port 389 is not in use.
[08/05/23:14:31:47] - [Setup] Info Directory server network port
[08/05/23:14:32:30] - [Setup] Info 389
[08/05/23:14:32:30] - [Setup] Info Each instance of a directory server requires a unique
identifier.
This identifier is used to name the various
instance specific files and directories in the file system,
as well as for other uses as a server instance identifier.
[08/05/23:14:32:30] - [Setup] Info Directory server identifier
[08/05/23:14:33:04] - [Setup] Info vmware-fds1
[08/05/23:14:33:04] - [Setup] Info The suffix is the root of your directory tree. The
suffix must be a valid DN.
It is recommended that you use the dc=domaincomponent suffix convention.
For example, if your domain is example.com,
you should use dc=example,dc=com for your suffix.
Setup will create this initial suffix for you,
but you may have more than one suffix.
Use the directory server utilities to create additional suffixes.
[08/05/23:14:33:04] - [Setup] Info Suffix
[08/05/23:14:33:55] - [Setup] Info dc=inrp, dc=fr
[08/05/23:14:33:55] - [Setup] Info Certain directory server operations require an
administrative user.
This user is referred to as the Directory Manager and typically has a
bind Distinguished Name (DN) of cn=Directory Manager.
You will also be prompted for the password for this user. The password must
be at least 8 characters long, and contain no spaces.
[08/05/23:14:33:55] - [Setup] Info Directory Manager DN
[08/05/23:14:34:54] - [Setup] Info cn=Directory Manager
[08/05/23:14:34:54] - [Setup] Info Password
[08/05/23:14:35:17] - [Setup] Info Password (confirm)
[08/05/23:14:35:30] - [Setup] Info The Administration Server is separate from any of your
web or application
servers since it listens to a different port and access to it is
restricted.
Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.
[08/05/23:14:35:30] - [Setup] Info Administration port
[08/05/23:14:36:15] - [Setup] Info 9869
[08/05/23:14:36:15] - [Setup] Info The interactive phase is complete. The script will now
set up your
servers. Enter No or go Back if you want to change something.
[08/05/23:14:36:15] - [Setup] Info Are you ready to set up your servers?
[08/05/23:14:38:25] - [Setup] Info yes
[08/05/23:14:38:25] - [Setup] Info Creating directory server . . .
[08/05/23:14:38:29] - [Setup] Info Your new DS instance 'vmware-fds1' was
successfully created.
[08/05/23:14:38:29] - [Setup] Info Creating the configuration directory server . . .
[08/05/23:14:38:30] - [Setup] Info Error adding entry 'cn=Fedora Directory Server,
cn=Server Group, cn=vmware-fds2.inrp.fr, ou=inrp.fr, o=NetscapeRoot'. Error: No such
object
[08/05/23:14:38:30] - [Setup] Fatal Could not register the directory server with the
configuration directory server.
[08/05/23:14:38:30] - [Setup] Fatal Exiting . . .
Log file is '/tmp/setupuRJ2k2.log'
9:19 a.m.
New subject: [Fedora-directory-users] Trouble registering a new DS instance with an existing Configuration Directory Server
Nicolas CAREL wrote:
Hello,
We experienced the same issue...
I believe this is a bug -
https://bugzilla.redhat.com/show_bug.cgi?id=431103 - the bug gives
instructions about how to workaround the problem.
Erling Ringen Elvsrud a écrit :
> Hello list,
>
> I have/want the following configuration:
>
> box1: RHDS master server
> box2: A read only replica.
>
> The installation on box1 completed sucessfully, but some problem has arised on
> box2.
>
> [08/05/20:12:23:46] - [Setup] Fatal Could not register the directory
> server with the configuration directory server.
> [08/05/20:12:23:46] - [Setup] Fatal Exiting . . .
>
> Erling Ringen Elvsrud
>
We setted up 2 Fedora Core 8 Virtual machines : vmware-fds1 and
vmware-fds2
yum update before installation.
On the first one, installation of FDS 1.1 with yum and setup. It works
fine.
One the second one, copycat.
We tried to join the administration domain created in the first one
and got the same message.
Both Virtual Machines are one the same LAN. The network is OK.
Both servers are in NTP sync, this is helpfull.
The setup log is in the attached file.
Here is the slapd log of vmware-fds1 :
*
Stage 1 : FDS Startup*
Fedora-Directory/1.1.0 B2008.03.27
vmware-fds1.inrp.fr:389 (/etc/dirsrv/slapd-vmware-fds1)
[23/May/2008:13:35:50 +0200] conn=0 fd=64 slot=64 connection from
127.0.0.1 to 127.0.0.1
[23/May/2008:13:35:50 +0200] conn=0 op=0 BIND dn="" method=128 version=3
[23/May/2008:13:35:50 +0200] conn=0 op=0 RESULT err=0 tag=97
nentries=0 etime=0 dn=""
[23/May/2008:13:35:50 +0200] conn=0 op=1 SRCH
base="cn=admin-serv-vmware-fds1, cn=Fedora Administration Server, cn=
Server Group, cn=vmware-fds1.inrp.fr, ou=inrp.fr, o=NetscapeRoot"
scope=2 filter="(nsExecRef=*)" attrs="nsExecRef n
sLogSuppress"
[23/May/2008:13:35:50 +0200] conn=0 op=1 RESULT err=0 tag=101
nentries=0 etime=0
[23/May/2008:13:35:50 +0200] conn=0 op=2 UNBIND
[23/May/2008:13:35:50 +0200] conn=0 op=2 fd=64 closed - U1
[23/May/2008:13:35:51 +0200] conn=1 fd=64 slot=64 connection from
127.0.0.1 to 127.0.0.1
[23/May/2008:13:35:51 +0200] conn=1 op=0 BIND dn="" method=128 version=3
[23/May/2008:13:35:51 +0200] conn=1 op=0 RESULT err=0 tag=97
nentries=0 etime=0 dn=""
[23/May/2008:13:35:51 +0200] conn=1 op=1 SRCH
base="cn=admin-serv-vmware-fds1, cn=Fedora Administration Server, cn=
Server Group, cn=vmware-fds1.inrp.fr, ou=inrp.fr, o=NetscapeRoot"
scope=2 filter="(nsExecRef=*)" attrs="nsExecRef n
sLogSuppress"
[23/May/2008:13:35:51 +0200] conn=1 op=1 RESULT err=0 tag=101
nentries=0 etime=0
[23/May/2008:13:35:51 +0200] conn=1 op=2 UNBIND
[23/May/2008:13:35:51 +0200] conn=1 op=2 fd=64 closed - U1
*
Stage 2 : Setup on vmware-fds2 *
Configuration directory server URL :
*ldap://vmware-fds1.inrp.fr:389/o=NetscapeRoot*
Configuration directory server admin ID *admin*
Configuration directory server admin password : *******
Configuration directory server admin domain : *inrp.fr*
[23/May/2008:14:31:46 +0200] conn=2 fd=64 slot=64 connection from
195.83.134.21 to 195.83.134.29
[23/May/2008:14:31:46 +0200] conn=2 op=0 BIND dn="" method=128 version=3
[23/May/2008:14:31:46 +0200] conn=2 op=0 RESULT err=0 tag=97
nentries=0 etime=0 dn=""
[23/May/2008:14:31:46 +0200] conn=2 op=1 SRCH base="o=NetscapeRoot"
scope=2 filter="(uid=admin)" attrs="dn"
[23/May/2008:14:31:46 +0200] conn=2 op=1 RESULT err=0 tag=101
nentries=1 etime=0
[23/May/2008:14:31:46 +0200] conn=2 op=2 BIND dn="uid=admin,
ou=Administrators, ou=TopologyManagement, o=NetscapeRo
ot" method=128 version=3
[23/May/2008:14:31:46 +0200] conn=2 op=2 RESULT err=0 tag=97
nentries=0 etime=0 dn="uid=admin,ou=administrators,ou=
topologymanagement,o=netscaperoot"
[23/May/2008:14:31:46 +0200] conn=2 op=3 SRCH base="ou=inrp.fr,
o=NetscapeRoot" scope=0 filter="(objectClass=*)" at
trs="dn"
[23/May/2008:14:31:46 +0200] conn=2 op=3 RESULT err=0 tag=101
nentries=1 etime=0
[23/May/2008:14:31:46 +0200] conn=2 op=4 UNBIND
[23/May/2008:14:31:46 +0200] conn=2 op=4 fd=64 closed - U1
*Stage 3 : Are you ready to set up your servers? : YES*
[23/May/2008:14:38:30 +0200] conn=3 fd=64 slot=64 connection from
195.83.134.21 to 195.83.134.29
[23/May/2008:14:38:30 +0200] conn=3 op=0 BIND dn="" method=128 version=3
[23/May/2008:14:38:30 +0200] conn=3 op=0 RESULT err=0 tag=97
nentries=0 etime=0 dn=""
[23/May/2008:14:38:30 +0200] conn=3 op=1 SRCH base="o=NetscapeRoot"
scope=2 filter="(uid=admin)" attrs="dn"
[23/May/2008:14:38:30 +0200] conn=3 op=1 RESULT err=0 tag=101
nentries=1 etime=0
[23/May/2008:14:38:30 +0200] conn=3 op=2 BIND dn="uid=admin,
ou=Administrators, ou=TopologyManagement, o=NetscapeRo
ot" method=128 version=3
[23/May/2008:14:38:30 +0200] conn=3 op=2 RESULT err=0 tag=97
nentries=0 etime=0 dn="uid=admin,ou=administrators,ou=
topologymanagement,o=netscaperoot"
[23/May/2008:14:38:30 +0200] conn=3 op=3 SRCH base="o=NetscapeRoot"
scope=0 filter="(objectClass=*)" attrs="* aci"
[23/May/2008:14:38:30 +0200] conn=3 op=3 RESULT err=0 tag=101
nentries=1 etime=0
[23/May/2008:14:38:30 +0200] conn=3 op=4 MOD dn="o=NetscapeRoot"
[23/May/2008:14:38:30 +0200] conn=3 op=4 RESULT err=0 tag=103
nentries=0 etime=0
[23/May/2008:14:38:30 +0200] conn=3 op=5 SRCH base="cn=Fedora
Directory Server, cn=Server Group, cn=vmware-fds2.inr
p.fr, ou=inrp.fr, o=NetscapeRoot" scope=0 filter="(objectClass=*)"
attrs="* aci"
[23/May/2008:14:38:30 +0200] conn=3 op=5 RESULT err=32 tag=101
nentries=0 etime=0
[23/May/2008:14:38:30 +0200] conn=3 op=6 ADD dn="cn=Fedora Directory
Server, cn=Server Group, cn=vmware-fds2.inrp.f
r, ou=inrp.fr, o=NetscapeRoot"
*[23/May/2008:14:38:30 +0200] conn=3 op=6 RESULT err=32 tag=105
nentries=0 etime=0*
[23/May/2008:14:38:30 +0200] conn=3 op=7 UNBIND
[23/May/2008:14:38:30 +0200] conn=3 op=7 fd=64 closed - U1
HELP !
--
*Nicolas CAREL
**Service Commun Informatique
*IT Manager
Trust my certificate : http://igc.cru.fr/trust.php
*Institut National de Recherche Pédagogique
<http://www.inrp.fr/>*19 allée de Fontenay - B.P. 17424 - 69347 LYON
CEDEX 07
Standard : 04 72 76 61 00 - Télécopie : 04 72 76 61 10
------------------------------------------------------------------------
--
Fedora-directory-users mailing list
Fedora-directory-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users
5811
days inactive
5811
days old
389-users@lists.fedoraproject.org
2 comments
3 participants
participants (3)
-
Erling Ringen Elvsrud -
Nicolas CAREL -
Rich Megginson