There are two separate issues to consider when Calendar Server shuts down:
After issuing stop-cal, it is possible that some child processes were not stopped. For example, stop-cal might stop the cshttpd parent process but not any cshttpd child processes. In this situation, you must stop the remaining Calendar Server processes individually, using the following procedure:
Log in as a user who has administrative rights to the system where Calendar Server is running.
Determine the process ID (PID) of the remaining Calendar Server processes by entering a ps command for each service:
ps -elf | grep cs-process
where cs-process is enpd, csnotifyd, csdwpd, csadmind, or cshttpd. For example:
ps -elf | grep cshttpd
Using the PID of each process that is still running, enter a kill -15 command to kill the process. For example: kill -15 9875
Enter each ps command again to make sure that all Calendar Server processes are stopped.
If a Calendar Server process is still running, enter a kill -9 command to kill it. For example: kill -9 9875
On Linux systems with Calendar Server running, if you search for calendar processes using the ps command, the results might appear confusing. In Linux, the ps command returns the list of threads running rather than the list of processes. There is no known workaround to display only the processes.
If Calendar Server was not properly shutdown, perform the following steps:
Perform the steps in the previous procedure, Fixing stop-cal Problems.
Manually delete all files in the LDAP data cache database directory.
These left over files could cause database corruptions. To delete the files:
Change to the LDAP data cache directory.
The default is /opt/SUNWics5/csdb/ldap_cache, but use the directory pointed to by the local.ldap.cache.homedir.path parameter in the ics.conf file.
Remove all files in the directory.
For example: rm *.*
Check to make sure all files were removed.
For example: ls
Restart Calendar Server.
For instructions on how to configure LDAP data caching, see Configuring Calendar Server for LDAP. For more information about the LDAP data cache, see theSun Java System Communications Services 6 2005Q4 Deployment Planning Guide.