[Date Prev][Date Next] [Chronological] [Thread] [Top]
Re: (ITS#3746) Lock table errors

To: openldap-its@OpenLDAP.org
Subject: Re: (ITS#3746) Lock table errors
From: quanah@symas.com
Date: Mon, 23 May 2005 23:56:59 GMT

--On Monday, May 23, 2005 4:43 PM -0700 Howard Chu <hyc@symas.com> wrote:

> In all 2.2 releases slurpd logs as much error information as the target
> server provides. So your question should be, is there any way to get the
> slave server to provide more useful error messages in its LDAP responses?
> I think in this case it will be hard, since the real message (Lock table
> is out of available locks) is run in a BDB callback that has no access to
> the original caller. The only message the BDB library gives back to the
> caller is "Not enough space" which will probably not be helpful on its
> own.
>
> In general the server does not provide details for internal errors in
> LDAP messages; relying instead on the system logger to record the
> details. And in general I think that's appropriate, as the internals will
> mean nothing to a remote client anyway, and a sysadmin must login to the
> slave server to diagnose and fix the problem regardless.

Okay, where specifically at loglevel 256 does it say that in relation to 
the connection that caused the error? :)  All I see is err=80

ldap-test1:/var/log> grep conn=854 /var/log/ldap
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 848112 
local4.debug] conn=854 fd=10 ACCEPT from IP=171.67.16.99:55365 
(IP=0.0.0.0:389)
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 998954 
local4.debug] conn=854 op=0 SRCH base="" scope=0 deref=0 
filter="(objectClass=*)"
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 706578 
local4.debug] conn=854 op=0 SRCH attr=supportedSASLMechanisms
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 362707 
local4.debug] conn=854 op=0 SEARCH RESULT tag=101 err=0 nentries=1 text=
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 347666 
local4.debug] conn=854 op=1 BIND dn="" method=163
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 347666 
local4.debug] conn=854 op=2 BIND dn="" method=163
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 347666 
local4.debug] conn=854 op=3 BIND dn="" method=163
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 951063 
local4.debug] conn=854 op=3 BIND authcid="service/ldap@stanford.edu"
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 996101 
local4.debug] conn=854 op=3 BIND 
dn="cn=replicator,cn=service,cn=applications,dc=stanford,dc=edu" 
mech=GSSAPI ssf=56
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 177021 
local4.debug] conn=854 op=4 MOD 
dn="suRegID=873b1090f61311d2ae660800209269ec,cn=People,dc=Stanford,dc=edu"
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 324647 
local4.debug] conn=854 op=4 MOD attr=telephoneNumber title 
facsimileTelephoneNumber suGwAffilPhone1 suGwAffilMailCode1 
suVisibAffilPhone1 homePostalAddress suPermanentAddress suSearchID 
suVisibAffiliation2 suVisibMailAddress suPrivilegeGroup suVisibEmail 
suVisibPermanentAddress suCardNumber suGwAffiliation2 suVisibHomePhone 
homePhone suVisibHomeAddress uid suLocalAddress mail suVisibLocalAddress 
suVisibSunetID suPrimaryOrganizationID suVisibPermanentPhone suMailAddress 
suPermanentPhone suSunetID suVisibStreet suProxyCardNumber suVisibMailCode
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 324647 
local4.debug] conn=854 op=4 MOD attr=o suVisibIdentity ou suGwAffiliation1 
suGeneralID street suGwAffilAddress1 givenName suVisibAffilAddress1 
displayName suUnivID suAffiliation suRegisteredNameLF sn suMailCode cn 
suDisplayAffiliation postalAddress description suVisibAffiliation1 
suRegisteredName suDisplayNameLF entryCSN modifiersName modifyTimestamp
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 217296 
local4.debug] conn=854 op=4 RESULT tag=103 err=0 text=
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 177021 
local4.debug] conn=854 op=5 MOD 
dn="suRegID=873b43bcf61311d2ae660800209269ec,cn=People,dc=Stanford,dc=edu"
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 324647 
local4.debug] conn=854 op=5 MOD attr=suMailCode telephoneNumber title 
facsimileTelephoneNumber street postalAddress suGwAffilPhone1 
suGwAffilMailCode1 suVisibAffilPhone1 suVisibHomeAddress homePostalAddress 
uid suPermanentAddress suSearchID mail suVisibAffiliation2 
suVisibMailAddress suPrivilegeGroup suVisibSunetID suPrimaryOrganizationID 
suVisibPermanentPhone suVisibEmail suVisibPermanentAddress suMailAddress 
suPermanentPhone suCardNumber suSunetID suGwAffiliation2 suVisibHomePhone 
homePhone suProxyCardNumber suVisibStreet o suVisibIdentity
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 324647 
local4.debug] conn=854 op=5 MOD attr=ou suGwAffiliation1 suGeneralID 
suGwAffilAddress1 givenName suUnivID suVisibAffilAddress1 displayName 
suRegisteredNameLF suAffiliation sn cn suDisplayAffiliation description 
suVisibAffiliation1 suRegisteredName suDisplayNameLF entryCSN modifiersName 
modifyTimestamp
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 217296 
local4.debug] conn=854 op=5 RESULT tag=103 err=0 text=
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 177021 
local4.debug] conn=854 op=6 MOD 
dn="suRegID=874060b8f61311d2ae660800209269ec,cn=People,dc=Stanford,dc=edu"
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 324647 
local4.debug] conn=854 op=6 MOD attr=title facsimileTelephoneNumber 
homePostalAddress suPermanentAddress suGwAffilAddress1 suSearchID 
suVisibAffiliation2 suPrivilegeGroup suMailCode suVisibEmail 
suVisibPermanentAddress postalAddress suCardNumber suGwAffiliation2 
suVisibHomePhone homePhone suVisibHomeAddress street uid mail 
suVisibAffilAddress1 suVisibSunetID suPrimaryOrganizationID 
suVisibPermanentPhone suPermanentPhone suSunetID suVisibTelephoneNumber 
suVisibStreet suProxyCardNumber suVisibMailCode o suVisibIdentity ou 
suGwAffiliation1
May 23 14:42:51 ldap-test1.Stanford.EDU slapd[18458]: [ID 324647 
local4.debug] conn=854 op=6 MOD attr=telephoneNumber suGeneralID givenName 
displayName suUnivID suAffiliation suVisibAffilPhone1 suRegisteredNameLF sn 
cn suDisplayAffiliation suVisibAffiliation1 description suRegisteredName 
suGwAffilPhone1 suDisplayNameLF entryCSN modifiersName modifyTimestamp
May 23 14:42:52 ldap-test1.Stanford.EDU slapd[18458]: [ID 217296 
local4.debug] conn=854 op=6 RESULT tag=103 err=80 text=
May 23 14:42:52 ldap-test1.Stanford.EDU slapd[18458]: [ID 338319 
local4.debug] conn=854 op=7 UNBIND
May 23 14:43:03 ldap-test1.Stanford.EDU slapd[18458]: [ID 952275 
local4.debug] conn=854 fd=10 closed




Now of course, if I go and edit the log file, and parse through it, I do 
find:



May 23 14:42:52 ldap-test1.Stanford.EDU slapd[18458]: [ID 446079 
local4.debug] bdb(dc=stanford,dc=edu): Lock table is out of available locks
May 23 14:42:52 ldap-test1.Stanford.EDU slapd[18458]: [ID 651871 
local4.debug] => bdb_idl_insert_key: c_put id failed: Not enough space (12)
May 23 14:42:52 ldap-test1.Stanford.EDU slapd[18458]: [ID 697391 
local4.debug] Attribute index add failure


but that is not associated with any connection ID, making finding the error 
on a busy system less than easy.
So, is it possible to get the syslog output at least tied to the connection 
that created it, so that its easy to find? :)



--Quanah

--
Quanah Gibson-Mount
Product Engineer
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Prev by Date: Re: (ITS#3746) Lock table errors
Next by Date: Re: (ITS#3746) Lock table errors
Index(es):
- Chronological
- Thread