Cisco Cisco Agent Desktop 8.0 トラブルシューティングガイド

After the license is received from the Cisco Desktop Licensing and Resource

Manager (LRM) service, CAD starts to download the agent profile from the

LDAP database.

09:50:21:192 INFO DESK1048 Load the Agent Profile.

09:50:21:660 INFO [0x60c] DESK1113 ReadLoginMethod: Get Login Method from

LDAP successfully. Login Method = 0.

09:50:35:778 DEBUG [0x60c] AgentConnectionManager.cpp[413]

CAgentConnectionManager::RetrieveAgentProfile: XXXXXX Begin Get Agent Profile...

Client waits for 15 seconds and then times out with a socket error.

09:50:50:504 DEBUG [0x60c] LCLDAP.cpp[491] ldap_client::LCLDAP::Get: LDAP error

<−5> <Timed out>. Try again.

09:50:50:504 DEBUG [0x161c] LDAPConnectionCheckerThread.cpp[196] ldap_client::

LDAPConnectionCheckerThread::ldapMonitor: Socket error: recv return <−1>.

09:50:50:520 INFO STD0005 Client <Calabrio LDAP> disconnected from service at

<X.X.X.X>.

09:50:50:520 ERROR DESK3110 Error: get agent returned: <An unexpected

error occurred.>.

Solution

This issue is usually due to high CPU usage on the CAD server. The two common causes are:

Standalone LAPD Daemon (SLAPD) process traces run at the DEBUG,TRACE, or DUMP level.
With Release 8.x and later, the CAD server default trace levels are set to DEBUG with the exception
of CDBR Tool and SLAPD process.

CDBR Tool −−> Default is DUMP (this is normal)

♦

SLAPD −−> Default is OFF

♦

Logging of SLAPD is extremely intensive and can cause significant login delays and high CPU
utlization if it is set to DEBUG for long periods of time. The recommendation is to turn logging off
after the recreate.

Cisco Bug ID CSCub77630 − "LRM fails over faster than originally designed, causing severe
instability."
This defect also causes high CPU usage on the server, which hampers the agent profile download
step.

Refer to CSCub77630 for more information.

Updated: Jul 10, 2013

Document ID: 116243