[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Regarding LDAP error
Raghu,
Looks like there is some process already listening to port 389 which by
default slapd tries to start at.
Either knock of the process running on 389 or try to start slapd on another
port.
To start on another port, use slapd -h "ldap://localhost:666"; where 666 is
some other port other than 389. Ensure that the port is available.
Good Luck,
Jeeva Venkataraman,
Software Engineer,MediaOcean.
Everything is permanent, till it changes and after it changes, its permanent
again.
-----Original Message-----
From: raghu [mailto:raghu@qsoftindia.com]
Sent: Monday, May 13, 2002 1:48 AM
To: Venkataraman, Jeeva
Subject: Regarding LDAP error
Dear Jeeva
I tried with your sugesstion , running the slapd with debug mode and Iam
getting the following error.
#./slapd -d 9
(#) $OpenLDAP: slapd 2.0.11-Release (Tue Aug 21 17:23:00 EDT 2001) $
root@stripples.devel.redhat.com:/usr/src/build/34468-i386/BUILD/openldap-2.0
.
11/servers/slapd
daemon_init: listen on ldap:///
daemon_init: 1 listeners to open...
ldap_url_parse_ext(ldap:///)
daemon: socket() failed errno=97 (Address family not supported by protocol)
daemon: bind(6) failed errno=98 (Address already in use)
daemon: bind(6) failed
slapd stopped.
connections_destroy: nothing to destroy.
and the slapd.conf file is
# $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.8.8.6 2001/04/20 23:32:43
kurt Exp $
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema
include /etc/openldap/schema/redhat/rfc822-MailMember.schema
include /etc/openldap/schema/redhat/autofs.schema
include /etc/openldap/schema/redhat/kerberosobject.schema
# Define global ACLs to disable default read access.
# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral ldap://root.openldap.org
pidfile //var/run/slapd.pid
argsfile //var/run/slapd.args
# Create a replication log in /var/lib/ldap for use by slurpd.
#replogfile /var/lib/ldap/master-slapd.replog
# Load dynamic backend modules:
# modulepath /usr/sbin/openldap
# moduleload back_ldap.la
# moduleload back_ldbm.la
# moduleload back_passwd.la
# moduleload back_shell.la
# The next two lines allow use of TLS for connections using a dummy test
# certificate, but you should generate a proper certificate by changing to
# /usr/share/ssl/certs, running "make slapd.pem", and fixing permissions on
# slapd.pem so that the ldap user or group can read it.
#TLSCertificateFile /usr/share/ssl/certs/slapd.pem
#TLSCertificateKeyFile /usr/share/ssl/certs/slapd.pem
#######################################################################
# ldbm database definitions
#######################################################################
database ldbm
suffix "dc=qsoft,dc=com"
#suffix "o=My Organization Name,c=US"
rootdn "cn=Manager,dc=qsoft,dc=com"
#rootdn "cn=Manager,o=My Organization Name,c=US"
# Cleartext passwords, especially for the rootdn, should
# be avoided. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw chintu123
# rootpw {crypt}ijFYNcSNctBYg
# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd/tools. Mode 700 recommended.
directory /var/lib/ldap
# Indices to maintain
index objectClass,uid,uidNumber,gidNumber,memberUid eq
index cn,mail,surname,givenname eq,subinitial
# Replicas to which we should propagate changes
#replica ldap-1.example.com:389 tls=yes
# bindmethod=sasl saslmech=GSSAPI
# authcId=host/ldap-master.example.com@EXAMPLE.COM
Please help me how to rectify the problem
Regards
Raghu