|
|
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, PERLHOME/perl -V).
Symptom CSRC installs without error, but when you attempt to navigate the Web user interface exception conditions occur. The CSRCHOME/logs/csrcmw.log file indicates that the CSRC system callout module failed during CSRC intialization and the NASHOME/logs/kjs* file indicates that a file could not be found.
Possible Cause An improper pathname may be specified to the location of your Perl installation.
Recommended Action Check the CSRCHOME/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 a popen() error.
Possible Cause Perl is installed in the wrong directory.
Recommended Action Install Perl in the /opt/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.
Possible Cause The CSRC Middleware could not start up properly due to a possible system extension failure. The failure might be a result of improperly installed Perl or NAS components, or CNR might not be configured correctly.
Recommended Action Check the NAS log files and the csrcmw.log file for this error.
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.)
You start and stop NAS on the Solaris command line. When you do so, the user ID of the user starting or stopping NAS must be the same user ID that you specified as the NAS owner during NAS installation. If a user with a different ID attempts to stop NAS from the command line, NAS silently fails to stop, even if you use the su command to change to that user ID (since only your effective UID is set to the ID you changed to using the su command). Subsequently, if you attempt to start NAS again, a second NAS system is started and you will now have two NAS systems running simultaneously, competing for the same ports.
To determine if you have multiple NAS systems running, enter the following command:
ps -ef | grep nas
The output of the command is similar to the following:
adams 28897 28885 0 Jul 02 ? 0:00 /scratch/nas21/bin/ .kas adams 28942 1 0 Jul 02 ? 0:00 /bin/sh/scratch/nas21/bin/kcs -cset CCSO -eng 2 adams 28943 28942 0 Jul 02 ? 0:12 /scratch/nas21/bin/.kcs -cset CCSO -eng2 adams 28885 1 0 Jul 02 ? 0:00 /bin/sh /scratch/nas21/bin/kas adams 28925 1 0 Jul 02 ? 0:00 /bin/sh /scratch/nas21/bin/kjs -cset CCSO -eng 1 adams 28914 1 0 Jul 02 ? 0:00 /bin/sh /scratch/nas211/bin/kxs -cset CCSO -eng 0 adams 28893 1 0 Jul 02 ? 0:00 /scratch/nas21/orb/orbix/bin/orbixd adams 28916 28914 0 Jul 02 ? 0:07 /scratch/nas21/bin/.kxs -cset CCSO -eng 0 admas 28926 28925 1 Jul 02 ? 36:22 /scratch/nas21/Solaris/JRE_1.1.6_03/bin/sparc/native_threads/jre com.kivasoft.e
For CSRC, a single NAS system runs nine processes, as shown in the output of the previous command. Multiple NAS systems running simultaneously display many running processes when you execute the ps -ef | grep nas command line. You may have to kill the processes using the kill command before you restart a single NAS system.
In a case such as the one described above, you can successfully start NAS, but you cannot stop it using the KIVAes.sh script. To work-around this situation, edit the KIVAes.sh script and rewrite the killsvr() script function so that it does not grep on the LOGNAME environment variable.
For example, in the opening paragraph of the KIVAes.sh script, the su logname command is used instead of the su - logname command. In this case, the switch-user goes through the login procedure and formally changes the real user ID, instead of changing the effective user ID. The LOGNAME environment variable does not change from the original user's ID and the killsvr() function never finds NAS processes to kill. The end result is that NAS silently stays up.
Another work-around for the situation is to print a message to stdout, if no NAS processes are found to kill. In this case, you will receive messages indicating that something is wrong.
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, use the kill command to kill the processes executing for the multiple NAS systems and then start a single NAS system.
For more information on starting and stopping NAS, see the "Before You Begin Installing CSRC" section. For information on multiple NAS systems and killing processes, see the "Determining if Multiple NAS Systems Have Been Accidentally Started" section.
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: Tue Aug 17 08:51:56 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.