Use this task to collect data when Calendar Server is experiencing a database problem in a Calendar Lookup Database/Database Wire Protocol (CLD/DWP) deployment.
A Calendar Server CLD/DWP installation comprises a multi-tiered deployment with multiple servers connecting to a distributed back-end Calendar Server database. If a database problem occurs in this environment, you must provide detailed information about your network topology and front-end and back-end servers to facilitate the identification of the issue.
Collect the general system information as explained in To Collect Required Debug Data for Any Calendar Server Problem.
Provide a detailed explanation of how you have set up your Calendar Server deployment. For example, you could have
Two front-end servers and two back-end servers
Two front-end servers and one back-end server
Three front-end servers and three back-end servers
and so on.
Provide the specific name of each machine in your deployment. Identify whether it is a front-end server or back-end server.
(Solaris only) Run the cscapture script to gather Calendar Server information:
(Other platforms) Run the capture_environment.pl script.
First go to the directory where the script is located. For example:
cd /export/home/myscripts perl capture_environment.pl
This command creates a file named archive.tar.gz, which contains Calendar Server database logs, system statistics, and configuration information, and database information.
Obtain user information for at least 2 users impacted by the problem and 2 users unaffected by the problem.
If no users can connect to the database, please include this information.
Use the csattribute command to get the LDIF entry of each user. The csattribute command displays the user's DN and the attributes of the specified user. following is a sample DN:
Run the command as follows:
cal-svr-base/cal/sbin/csattribute -v list uid
csattribute -v list uid
The directory on the Calendar Server machine dedicated to holding the Calendar Server program, and configuration, maintenance, and information files. The default location for UNIX and Linux versions of Calendar Server is /var/opt/mps/serverroot/.
User ID of the user you are searching for.
Get the LDIF entry of the domain where the impacted user resides.
Use the domain portion of the DN shown by the csattribute command in the preceding step.
dir-root/shared/bin/ldapsearch -h hostname -p port -D "cn=Directory Manager" -w password -s base -b "baseDN" "(objectclass=*)" > /tmp/domain.ldif
dir-root\shared\bin\ldapsearch.exe -h hostname -p port -D "cn=Directory Manager" -w password -s base -b "baseDN" "(objectclass=*)" > C:\domain.ldif
The directory on the Directory Server machine dedicated to holding the server program, and configuration, maintenance, and information files. The default location for UNIX and Linux versions of Calendar Server is /var/opt/mps/serverroot/.
Name of the host running Directory Server. You can omit -h hostname if the Directory Server is running locally.
Port number on which Directory Server is listening. The default is 389. You can omit port if the Directory Server is running on port 389.
If you have not already done so, set the Calendar Server debug log level to Debug and provide all errors printed to the Calendar Server logs.
Provide all log files with pointers to timestamps or error messages. For example:
[04/Jul/2006:19:49:52 +0200] mouline cshttpd: General Error: chttp_ctx_async_connect: ASock_Connect failed: pctx->s 924500 [04/Jul/2006:19:49:52 +0200] mouline cshttpd: General Notice: CldCacheInit: attemptint to open cache database for 25278
If you have not already done so, provide specific steps showing how to reproduce the problem.
Include any observed error messages from the Web UI, WCAP commands, and the Calendar Server log files and timestamps showing when the error occurred.