Plantronics + Polycom. Now together as Poly Logo

Interpreting the LDAP debug logs

SOLVED
Highlighted
Occasional Visitor

Interpreting the LDAP debug logs

Good day,

 

I am getting this logs (filtered by keyword "ldap") while connecting to LDAP. Do you all know what could possibly be wrong with the LDAP setting based on the logs generated?

 

	0218181247|ldap |1|00|ldapCfg::ldapCfgParamCallBack:ctxt=<0x1089848> type=<0> id=<0> ind=<0>, valueCh=<0> pEdit=<0>
	0218181247|ldap |1|00|ldapCfg::ldapCfgParamCallBack:ctxt=<0x1089848> type=<0> id=<0> ind=<0>, valueCh=<0> pEdit=<0>
	0218181247|ldap |1|00|ldapCfg::ldapCfgParamCallBack:ctxt=<0x1089848> type=<0> id=<0> ind=<0>, valueCh=<0> pEdit=<0>
	0218181247|ldap |1|00|ldapCfg::ldapCfgParamCallBack:ctxt=<0x1089848> type=<5> id=<0> ind=<0>, valueCh=<0> pEdit=<0>
	0218181247|ldap |1|00|ldapCfg::ldapCfgParamCallBack:ctxt=<0x1089848> type=<5> id=<0> ind=<0>, valueCh=<0> pEdit=<0>
	0218181247|ldap |1|00|ldapCfg::ldapCfgParamCallBack:ctxt=<0x1089848> type=<5> id=<0> ind=<0>, valueCh=<0> pEdit=<0>
	0218181247|ldap |*|00|ldapXfer::envDel: task delete OK
	0218181247|ldap |*|00|ldapXfer::envDel: task delete OK
	000147.086|ldap |*|00|Initial log entry. Current logging level 0
	000147.087|ldap |1|00|ldapCfg::lookupHost:No srvLookup host=<10.0.0.1> port=<389>
	000147.087|ldap |1|00|ldapCfg::lookupHost:No srvLookup host=<10.0.0.1> port=<389>
	000147.087|ldap |3|00|ldapCfg::getConnParams:m_pHost=<ldap://10.0.0.1> m_fullAddr=<ldap://10.0.0.1> m_priSrv=<(null)> port=<389> trans=<0>
	000147.087|ldap |3|00|ldapCfg::getConnParams:m_pHost=<ldap://10.0.0.1> m_fullAddr=<ldap://10.0.0.1> m_priSrv=<(null)> port=<389> trans=<0>
	000147.087|ldap |3|00|ldapCfg::getConnParams:m_pHost=<ldap://10.0.0.1> m_fullAddr=<ldap://10.0.0.1> m_priSrv=<(null)> port=<389> trans=<0>
	000147.087|ldap |3|00|ldapCfg::getConnParams:m_pHost=<ldap://10.0.0.1> m_fullAddr=<ldap://10.0.0.1> m_priSrv=<(null)> port=<389> trans=<0>
	000147.087|ldap |1|00|ldapCfg::getBufsSize:m_xferSize=<32> m_cacheSize=<128> (m_secCacheSize=<128>)
	000147.087|ldap |1|00|ldapCfg::getBufsSize:m_xferSize=<32> m_cacheSize=<128> (m_secCacheSize=<128>)
	000147.089|ldap |1|00|ldapCfg::createUtfTable:Loading default UTF settings
	000147.089|ldap |1|00|ldapCfg::createUtfTable:Loading default UTF settings
	000147.089|ldap |1|00|ldapCfg::showUtfTable:createUtfTable
	000147.089|ldap |1|00|ldapCfg::showUtfTable:createUtfTable
	000147.090|ldap |1|00|ldapCfg::showUtfTable:utfsubset[0]=<0> ,<zz> 
	000147.090|ldap |1|00|ldapCfg::showUtfTable:utfsubset[0]=<0> ,<zz> 
	000147.090|ldap |1|00|cDynamicData&colon;:cDynamicData&colon;m_circSize=<128> m_lowMark=<32>
	000147.110|ldap |0|00|ldapData&colon;:newFilter:baseRequest=ldap://10.0.0.1/dc=abc,dc=net?cn,givenName,workNumber,mail?sub
	000147.110|ldap |0|00|ldapData&colon;:newFilter:baseRequest=ldap://10.0.0.1/dc=abc,dc=net?cn,givenName,workNumber,mail?sub
	000147.110|ldap |0|00|ldapData&colon;:newFilter:baseRequest=ldap://10.0.0.1/dc=abc,dc=net?cn,givenName,workNumber,mail?sub
	000203.692|ldap |1|00|ldapCfg::lookupHost:No srvLookup host=<10.0.0.1> port=<389>
	000203.692|ldap |1|00|ldapCfg::lookupHost:No srvLookup host=<10.0.0.1> port=<389>
	000203.693|ldap |1|00|ldapCfg::lookupHost:No srvLookup host=<10.0.0.1> port=<389>
	000203.693|ldap |1|00|ldapCfg::lookupHost:No srvLookup host=<10.0.0.1> port=<389>
	000203.693|ldap |4|00|cDynamicData&colon;:activate:cDynamicData&colon;:activate() m_pCfg->lookupHost() = 1
	000203.693|ldap |0|00|ldapData&colon;:newFilter:baseRequest=ldap://10.0.0.1/dc=abc,dc=net?cn,givenName,workNumber,mail?sub
	000203.693|ldap |0|00|ldapData&colon;:newFilter:baseRequest=ldap://10.0.0.1/dc=abc,dc=net?cn,givenName,workNumber,mail?sub
	000203.693|ldap |0|00|ldapData&colon;:newFilter:baseRequest=ldap://10.0.0.1/dc=abc,dc=net?cn,givenName,workNumber,mail?sub
	000203.825|ldap |4|00|ldapData&colon;:ldapConnBind:ldap_x_bind_s - rc=0x31 <Invalid credentials>
	000203.825|ldap |4|00|ldapData&colon;:ldapConnBind:ldap_x_bind_s - rc=0x31 <Invalid credentials>
	000203.825|ldap |4|00|ldapData&colon;:ldapConnBind:ldap_x_bind_s - rc=0x31 <Invalid credentials>
	000203.825|ldap |4|00|ldapData&colon;:ldapConnBind:ldap_x_bind_s - rc=0x31 <Invalid credentials>
	000203.828|ldap |1|00|ldapCfg::show:<LDAP configuration:> status=<1>
	000203.828|ldap |1|00|ldapCfg::show:<LDAP configuration:> status=<1>
	000203.828|ldap |1|00|ldapCfg::show:<LDAP configuration:> status=<1>
	000203.829|ldap |1|00|   <server version=-1> <sort:ctrl=0x1-cfg=0x0> <vlv=No> <vrCrt=Yes>
	000203.829|ldap |1|00|   <host=ldap://10.0.0.1> <pfix=ldap://> <port=389> <trans=tcp> <bindOnInit=Yes>
	000203.829|ldap |1|00|   <host=ldap://10.0.0.1> <pfix=ldap://> <port=389> <trans=tcp> <bindOnInit=Yes>
	000203.829|ldap |1|00|   <host=ldap://10.0.0.1> <pfix=ldap://> <port=389> <trans=tcp> <bindOnInit=Yes>
	000203.829|ldap |1|00|   <baseDN=dc=abc,dc=net> <filterPrefix=> <sortOrder=cn givenName> <invSortOrder=NULL>
	000203.829|ldap |1|00|ldapCfg::getCaFile:LDAP:CA filepath = /ffs0/ca1.crt
	000203.829|ldap |1|00|ldapCfg::getCaFile:LDAP:CA filepath = /ffs0/ca1.crt
	000203.829|ldap |1|00|ldapCfg::getCaFile:LDAP:CA filepath = /ffs0/ca1.crt
	000203.829|ldap |1|00|ldapCfg::getCaFile:LDAP:CA filepath = /ffs0/ca1.crt
	000203.829|ldap |1|00|ldapCfg::getCaFile:LDAP:CA filepath = /ffs0/ca1.crt
	000203.829|ldap |1|00|ldapCfg::getCaFile:LDAP:CA filepath = /ffs0/ca1.crt
	000203.829|ldap |1|00|   <attrib=cn,givenName,workNumber,mail><sub></ffs0/ca1.crt>
	000203.829|ldap |1|00|   <persistView=No> <persistSearch=No>
	000203.829|ldap |1|00|   <backgroundSyncPeriod=0> <autoQuerySubmitTimeout=1>
	000203.829|ldap |1|00|   <domain=NULL> <user=cn=LDAP user,ou=Common Account,dc=abc,dc=net> <pass=***>
	000203.829|ldap |1|00|   <domain=NULL> <user=cn=LDAP user,ou=Common Account,dc=abc,dc=net> <pass=***>
	0218181237|ldap |1|00|ldapCfg::getSSLv2v3Enabled:LDAP:SSLv2v3 Enabled = 0
	0218181237|ldap |1|00|ldapCfg::getSSLv2v3Enabled:LDAP:SSLv2v3 Enabled = 0
	0218181237|ldap |1|00|ldapCfg::getSSLv2v3Enabled:LDAP:SSLv2v3 Enabled = 0
	0218181237|ldap |1|00|   <SSLv2v3Enabled=0>
	0218181237|ldap |1|00|ldapCfg::showAttr:   Attributes:
	0218181237|ldap |1|00|ldapCfg::showAttr:   Attributes:
	0218181237|ldap |1|00|ldapCfg::showAttr:   [0] <name=cn><label=Last Name><type=last_name><filter=><sticky=No><srch=Yes>
	0218181237|ldap |1|00|ldapCfg::showAttr:   [0] <name=cn><label=Last Name><type=last_name><filter=><sticky=No><srch=Yes>
	0218181237|ldap |1|00|ldapCfg::showAttr:   [1] <name=givenName><label=First Name><type=first_name><filter=><sticky=No><srch=Yes>
	0218181237|ldap |1|00|ldapCfg::showAttr:   [1] <name=givenName><label=First Name><type=first_name><filter=><sticky=No><srch=Yes>
	0218181237|ldap |1|00|ldapCfg::showAttr:   [2] <name=workNumber><label=Ext Number><type=phone_number><filter=><sticky=No><srch=Yes>
	0218181237|ldap |1|00|ldapCfg::showAttr:   [2] <name=workNumber><label=Ext Number><type=phone_number><filter=><sticky=No><srch=Yes>
	0218181237|ldap |1|00|ldapCfg::showAttr:   [3] <name=mail><label=Email><type=other><filter=><sticky=No><srch=Yes>
	0218181237|ldap |1|00|ldapCfg::showAttr:   [3] <name=mail><label=Email><type=other><filter=><sticky=No><srch=Yes>
	0218181237|ldap |3|00|cDynamicData&colon;:processError:login error
	0218181237|ldap |4|00|cDynamicData&colon;:finalizeInit:finalizeInit Failed state=<6>

 

Regards,
KCP88

Message 1 of 3
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Polycom Employee & Community Manager

Re: Interpreting the LDAP debug logs

Hello KCP88,

welcome to the Polycom Community.

It is always useful to include the currently used SIP or UC Software version as issues experienced may already be addressed in a newer release.

This also allows yourself and others to check against current software release notes.

The above is also stated in the "Read First: Welcome to the Polycom VoIP Forum"

Therefore the Polycom VoIP FAQ contains this post here:

Question: How can I find out my SIP UC Software Version or the BootROM Version of my Phone?
Resolution: Please check here

 

Simply looking at your log:

	000203.825|ldap |4|00|ldapData&colon;:ldapConnBind:ldap_x_bind_s - rc=0x31 <Invalid credentials>

or

	0218181237|ldap |3|00|cDynamicData&colon;:processError:login error

 

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

View solution in original post

Message 2 of 3
2 REPLIES 2
Highlighted
Polycom Employee & Community Manager

Re: Interpreting the LDAP debug logs

Hello KCP88,

welcome to the Polycom Community.

It is always useful to include the currently used SIP or UC Software version as issues experienced may already be addressed in a newer release.

This also allows yourself and others to check against current software release notes.

The above is also stated in the "Read First: Welcome to the Polycom VoIP Forum"

Therefore the Polycom VoIP FAQ contains this post here:

Question: How can I find out my SIP UC Software Version or the BootROM Version of my Phone?
Resolution: Please check here

 

Simply looking at your log:

	000203.825|ldap |4|00|ldapData&colon;:ldapConnBind:ldap_x_bind_s - rc=0x31 <Invalid credentials>

or

	0218181237|ldap |3|00|cDynamicData&colon;:processError:login error

 

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

View solution in original post

Message 2 of 3
Highlighted
Occasional Visitor

Re: Interpreting the LDAP debug logs

Hi Steffen,

 

Sorry my bad. Found that I used a wrong password. Thanks for your advice.

 

Regards,
Kcp88

Message 3 of 3