RE: daemon: bind(6) failed errno=98 (Address already in use)

["Gerry Maddock" <gerrym@futuremetals.com>]

I found the problem. I had whitespace in front of: rootpw 	secret
In the slapd.conf file. I removed the whitespace and restarted ldap, tested
ldapadd and it worked fine. Thanks to everyone who responded earlier!

		-----Original Message-----
		From: Bennett, Tony - CNF [mailto:Bennett.Tony@cnf.com] 
		Sent: Friday, January 03, 2003 11:15 AM
		To: 'Gerry Maddock'; openldap-software@OpenLDAP.org
		Subject: RE: daemon: bind(6) failed errno=98 (Address
already in use)

		This looks like an IPv6 issue...

		Look at:  http://www.openldap.org/faq/data/cache/652.html
		                           and
	
http://www.openldap.org/lists/openldap-software/200211/msg00384.html

		-tony

		>  -----Original Message-----
		> From: 	Gerry Maddock
[mailto:gerrym@futuremetals.com] 
		> Sent:	Friday, January 03, 2003 7:43 AM
		> To:	openldap-software@OpenLDAP.org
		> Subject:	daemon: bind(6) failed errno=98 (Address
already in use)
		> Importance:	High
		> 
		> I know this problem has been addressed before, but I was 
		> unable to find an answer that made any sense.  I have 
		> openldap-2.0.21-1 on a RH7.2 sys with pretty much the 
		> defaults on the slapd.conf file (the only parts changed
were 
		> adding my domain name to the examples) I can post the 
		> slapd.conf if needed, but as stated earlier it's the RH 
		> default slapd with only my domain name added in.
		> Ok, when I run: slapd -d 256 I get:
		> 
		> slapd -d 256
		> 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
		> 
		> 
		> ON previous mails, I see people stating that another
process 
		> is using port 389. I  then ran netstat -nat| grep 389 and
saw:
		> tcp        0      0 0.0.0.0:389             0.0.0.0:*

		>       LISTEN
		> 
		> I then killed ldap with: service ldap stop and reran
netstat 
		> to see if that port was still in use and it wasn't:
		> Netstat -nat|grep 389 returned no results.
		> 
		> I then checked to ensure all firewalling programs were
killed:
		> service ipchains stop
		> service iptables stop
		> service portsentry stop
		> 
		> I then restart ldap (service ldap start), try to use
ldapadd, 
		> and as usual, nothing. 
		> I'm at a loss here, if there is anyone who can help me it 
		> would be greatly appreciated.

<<attachment: winmail.dat>>