Hello
since few time I get those repeated messages in syslog
Jul 8 10:20:18 ldap slapd[28833]: conn=312612 op=0 do_bind: invalid dn (uid=,ou=Personnes,dc=xxxxx,dc=fr)
this happen exactly every minute
Anyone could give me some pointers ?
Thanks
Frank Bonnet wrote:
Hello
since few time I get those repeated messages in syslog
Jul 8 10:20:18 ldap slapd[28833]: conn=312612 op=0 do_bind: invalid dn (uid=,ou=Personnes,dc=xxxxx,dc=fr)
This DN is invalid, since uid does not allow the empty string as value. The client that tries to bind with that DN is doing something incorrect, you can't blame slapd for this.
p.
this happen exactly every minute
Anyone could give me some pointers ?
Thanks
Hello
I don't blame slapd ;-)
is there any way to track down le IP address of the client if slapd is in debug mode ?
On 07/08/2010 10:32 AM, Pierangelo Masarati wrote:
Frank Bonnet wrote:
Hello
since few time I get those repeated messages in syslog
Jul 8 10:20:18 ldap slapd[28833]: conn=312612 op=0 do_bind: invalid dn (uid=,ou=Personnes,dc=xxxxx,dc=fr)
This DN is invalid, since uid does not allow the empty string as value. The client that tries to bind with that DN is doing something incorrect, you can't blame slapd for this.
p.
this happen exactly every minute
Anyone could give me some pointers ?
Thanks
On Thu, 8 Jul 2010, Frank Bonnet wrote:
Hello
I don't blame slapd ;-)
is there any way to track down le IP address of the client if slapd is in debug mode ?
Given the appropriate loglevel (discussed in this thread), look for "conn=312612" messages. The connection (i.e. "ACCEPT") message preceding your error should be of great interest...
(note that, of course, conn= numbers do change. I'm only pasting yours, you might want to use a more recent one.)
On 07/08/2010 10:32 AM, Pierangelo Masarati wrote:
Frank Bonnet wrote:
Hello
since few time I get those repeated messages in syslog
Jul 8 10:20:18 ldap slapd[28833]: conn=312612 op=0 do_bind: invalid dn (uid=,ou=Personnes,dc=xxxxx,dc=fr)
This DN is invalid, since uid does not allow the empty string as value. The client that tries to bind with that DN is doing something incorrect, you can't blame slapd for this.
p.
this happen exactly every minute
Anyone could give me some pointers ?
Thanks
I finally found the client in debug mode thanks to all for your help !
On 07/08/2010 02:51 PM, Aaron Richton wrote:
On Thu, 8 Jul 2010, Frank Bonnet wrote:
Hello
I don't blame slapd ;-)
is there any way to track down le IP address of the client if slapd is in debug mode ?
Given the appropriate loglevel (discussed in this thread), look for "conn=312612" messages. The connection (i.e. "ACCEPT") message preceding your error should be of great interest...
(note that, of course, conn= numbers do change. I'm only pasting yours, you might want to use a more recent one.)
On 07/08/2010 10:32 AM, Pierangelo Masarati wrote:
Frank Bonnet wrote:
Hello
since few time I get those repeated messages in syslog
Jul 8 10:20:18 ldap slapd[28833]: conn=312612 op=0 do_bind: invalid dn (uid=,ou=Personnes,dc=xxxxx,dc=fr)
This DN is invalid, since uid does not allow the empty string as value. The client that tries to bind with that DN is doing something incorrect, you can't blame slapd for this.
p.
this happen exactly every minute
Anyone could give me some pointers ?
Thanks
On 07/ 8/10 08:26 PM, Frank Bonnet wrote:
Hello
since few time I get those repeated messages in syslog
Jul 8 10:20:18 ldap slapd[28833]: conn=312612 op=0 do_bind: invalid dn (uid=,ou=Personnes,dc=xxxxx,dc=fr)
Check your network to see where the malformed bind request originates. It is client problem, not a server problem.
openldap-technical@openldap.org