Troubleshooting Run-Time Problems

This appendix describes problems you might encounter after installing the CSRC required software packages, and suggests recommended actions.

Troubleshooting CNR Run-Time Problems

Symptom After installing CNR, the csrcmw.log file indicates that the system callout failed for reasons relating to a login failure or to an inability to communicate with a cluster.

Possible Cause CNR installation and/or configuration.

Recommended Action Check that you can successfully log in to CNR. Check that a valid license key has been installed.

Note You can only perform operations on a CNR cluster after you have connected to the cluster and entered a valid license key.

Symptom The built-in system callout in the installed csrc.cfg file failed with an invalid session error.

Possible Cause Cisco Network Registrar does not have a valid license set.

Troubleshooting NDS Run-Time Problems

Symptom During installation, the attempt to populate LDAP with CSRC schema information fails and the installer notifies you that the failure occurred.

Possible Cause The slapd directory server daemon (NDSROOT\slapd-HOSTNAME\start-slapd) and the NDS Administrative Server (NDSROOT\start-admin) were not started before installing CSRC.

Recommended Action Start the NDS slapd daemon and re-install CSRC.

Troubleshooting CSRC Run-Time Problems

Symptom Unexpected errors occur.

Possible Cause CSRC or dependency configuration error.

Recommended Action Increase the logging level in the csrc.cfg file and then reproduce the problem. Check the BASEDIR\CSRC\logs\csrcmw.log for error conditions. You must restart the CSRC Servlet Engine before logging level changes take effect.

Table of Contents