|
|
This appendix describes problems you might encounter after installing the CSRC required software packages, and suggests recommended actions.
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 issued and accepted. Check that a cluster has been created.
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.
Recommended Action Set a valid license for CNR. For more information, see the
"What to Do After You Install CNR" section.
Symptom While attempting to update the LDAP directory server with the CSRC directory schema during CSRC installation, Perl errors occurred.
Possible Cause You may not be executing the expected Perl binary.
Recommended Action Run the perl -V command to make sure your Perl distribution is intact. Check the PATH environment variable and ensure that you are executing the expected perl binary by setting the variable to specify the complete path to Perl (for example, C:\Program Files\CSRC\Perl\bin\MSWin 32-x86\perl -V).
Symptom CSRC installs without error, but when you attempt to navigate the Web user interface exception conditions occur. The C:\Program Files\CSRC\logs\csrcmw.log file indicates that the CSRC system callout module failed during CSRC initialization.
Possible Cause An improper pathname may be specified to the location of your Perl installation.
Recommended Action Check the C:\Program Files\CSRC\conf\csrc.cfg file to ensure that you specified the proper pathname to the location of your Perl installation.
Symptom The built-in system callout in the installed csrc.cfg file failed with an open() error.
Possible Cause Perl is installed in the wrong directory.
Recommended Action Install Perl in the C:\Program Files\CSRC\Perl directory.
Symptom You can successfully navigate the CSRC Web pages, but the icons are not properly displayed.
Possible Cause The Web server is not properly configured. For the Apache Web server, the alias entries that you added to the httpd.conf file are not specified in the required order.
Recommended Action Check the order of the alias entries you added in the httpd.conf file and re-order them as described in the "What to Do After You Install Apache" section, and then reload the Apache Web server daemon.
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.
Symptom NAS fails to properly load the CSRC Middleware extension, as indicated by the NAS kjs log.
Possible Cause The CSRC middleware failed during initialization, possibly because Perl was installed in wrong place, CNR/DHCP was not configured correctly, the LDAP or the CNR password was incorrectly specified during CSRC installation.
Recommended Action Check the NAS log files for this error or look at the CSRC log file CSRCROOT\logs\csrcmw.log, which should have an entry that indicates what failed.
Symptom Problems connecting to LDAP
Possible Cause Multiple
Recommended Action Try one of the following procedures:
Symptom The Web user interface pages display a NAS Error page.
Possible Cause NAS may not be running.
Recommended Action Ensure that NAS is running. If it is not, start NAS. If it is running, make sure that only one NAS system is active at a time. (See the "Before You Begin Installing CSRC" section.)
Symptom Server Error pages display when you attempt to navigate the CSRC Web user interface.
Possible Cause The NAS may not be running, or more than one NAS may be running.
Recommended Action Determine if NAS is started. If it is not, start it and when it achieves a steady-state (after about 30 seconds), try navigating the CSRC Web user interface again. If NAS is started, ensure that only one NAS is started. If more than one NAS is started, stop the processes executing for the multiple NAS systems and then start a single NAS system.
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 log for error conditions.
Posted: Fri Oct 15 13:13:26 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.