- To: <slug@xxxxxxxxxxx>
- Subject: [SLUG] Invalid credentials error code 49
- From: "Selim Jahangir" <s.jahangir@xxxxxxxxxx>
- Date: Thu, 20 Apr 2006 12:18:42 +1000
- Thread-index: AcZkHTwYqTiK64ZYSWC3l88sewtQqQAAWANAAABbBrA=
- Thread-topic: Invalid credentials error code 49
I have found the following in the log file after typing the command,
ldapadd -x -D "cn=Manager, dc=example, dc=com" -W -f
/etc/openldap/example.com.ldif
-selim
Apr 20 12:10:42 s913lap slapd[12000]: conn=0 fd=12 ACCEPT from
IP=131.181.33.28:58594 (IP=0.0.0.0:389)
Apr 20 12:10:42 s913lap slapd[12000]: conn=0 op=0 BIND
dn="cn=Manager,dc=example,dc=com" method=128
Apr 20 12:10:42 s913lap slapd[12000]: conn=0 op=0 RESULT tag=97 err=49
text=
Apr 20 12:10:42 s913lap slapd[12000]: conn=0 fd=12 closed (connection
lost)
-----Original Message-----
From: slug-bounces@xxxxxxxxxxx [mailto:slug-bounces@xxxxxxxxxxx] On
Behalf Of Selim Jahangir
Sent: Thursday, 20 April 2006 12:07 PM
To: Jamie Wilkinson; slug@xxxxxxxxxxx
Subject: RE: [SLUG] Invalid credentials error code 49
Yeah I did restart after every change in slapd.conf.
selim
-----Original Message-----
From: slug-bounces@xxxxxxxxxxx [mailto:slug-bounces@xxxxxxxxxxx] On
Behalf Of Jamie Wilkinson
Sent: Thursday, 20 April 2006 11:56 AM
To: slug@xxxxxxxxxxx
Subject: Re: [SLUG] Invalid credentials error code 49
This one time, at band camp, Selim Jahangir wrote:
> #rootpw secret
>
> rootpw {SSHA}airnU5gtmX+okEfQzseQsdXEx1QWpJ7/
Did you restart slapd after changing the password?
>[root@s913lap openldap]# ldapadd -x -D "cn=Manager,dc=example,dc=com"
>-W -f /etc/openldap/example.com.ldif
What's /etc/openldap/ldap.conf say that your default host is? (It's
probably ldap:// but sometimes may be ldapi://)
>Enter LDAP Password:
>
>ldap_bind: Invalid credentials (49)
Try adding "loglevel 448" (which will turn on connection logging, access
control list processing messages, and config file processing messages)
and
see what /var/log/ldap.log says happens when you try connecting.
Oh, you'll probably want to add
local4.* -/var/log/ldap.log
to /etc/syslog.conf and restart that too, in order to get the logs.
Alternatively you could restart slapd from the command line with
debugging
enabled like so:
slapd -d 448
and then not have to worry about syslog.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html