|
|
This appendix provides troubleshooting information for Essentials installation and setup. It contains the following sections:
If the Login Manager dialog box on the CiscoWorks2000 desktop does not appear correctly when you try to log in for the first time after upgrading, clear your browser cache as follows, then reenter the server URL in your browser.
For Microsoft Internet Explorer:
Step 1 Select View > Internet Options. The Internet Options dialog box appears.
Step 2 Select the General tab.
Step 3 Click Delete Files.
For Netscape Navigator:
Step 1 Select Edit > Preferences. The Preferences dialog box appears.
Step 2 Select Advanced > Cache.
Step 3 Click Clear Memory Cache, then click OK in the Memory Cache dialog box.
Step 4 Click Clear Disk Cache, then click OK in the Disk Cache dialog box.
The following types of error messages might appear during the installation:
All of the messages that appear during installation are logged in the /var/tmp/ciscoinstall.log file.
Table A-1 shows error messages that might occur during installation and describes the reasons for the errors.
| Message | Reason for Message | User Action |
|---|---|---|
Base package did not install. Exiting. | Installation program cannot install a required package. | Contact your technical support representative. |
Cannot backup /etc/services, no change will be made. | Installation program cannot make a copy of /etc/services before modifying it. | Make sure there is enough space in /tmp. |
Cannot change ownership of library. Exiting. | Installation program cannot write to product root directory. | Check the permissions on the directory you specified. |
Cannot create <directory>. | Installation program cannot write to the directory you specified. | Check the permissions on the directory you specified. |
Cannot create symlink: ln -s <root> /opt/CSCOpx. | Installation program cannot create a link from /opt/CSCOpx to the product root directory you specified. | Contact your technical support representative. |
Cannot determine the Essentials version. | Installation disk is corrupted. | Contact your technical support representative. |
Cannot determine the version of <product>. | Installation program cannot determine product version. | Contact your technical support representative. |
Cannot make list of packages for installation. | Installation suffered a major failure. | Contact your technical support representative. |
Cannot upgrade. | Upgrade failed. | Contact your technical support representative. |
Copy <setupdir> to <nmsroot> failed. | Installation program could not write to product root directory. | Check the permissions on the root. |
Installation in progress. | You are already running an installation on this machine. | Run only one installation program at a time. |
Missing file <file>. | Installation program cannot find a file. | Contact your technical support representative. |
No syslog facility is available. | No available syslog facilities. | Make one of the facilities available. |
Not enough disk space: <root>. | File system has insufficient space to load Essentials. | Make at least 4 GB of disk space available on the partition on which you install Essentials. |
Package verification failed: <pkg> aborting. | While loading packages, one loaded incorrectly. | Contact your technical support representative. |
Syslog is not running. | Installation program cannot start syslogd on this machine. | Restart syslogd. |
The components have dependency errors. | Installation program suffered a major failure. | Contact your technical support representative. |
User must be root. | You must be root to install. | Log in as root and enter the correct password. |
User 'bin' appears in '/usr/lib/cron/at.deny'. Software Image Manager requires 'bin' to be able to run 'at'. Contact your local technical support representative to edit the file /usr/lib/cron/at.deny and remove the entry for bin. User 'bin' appears in '/usr/lib/cron/cron.deny'. Software Image Manager requires 'bin' to be able to run 'crontab'. Contact your local technical support representative to edit the file /usr/lib/cron/cron.deny and remove the entry for bin. | Software Management requires that the user bin be allowed to use at and cron. | Edit the relevant files to allow the user bin to use at and cron. For information, see "Allowing the User bin to Use at and cron" section. |
Wrong OS. | Operating system is not Solaris or not a supported version of Solaris. | Make sure you are running Solaris 2.6. |
If the Essentials installation fails during Syslog Analysis installation, make sure you do not have the Cisco DNS/DHCP Manager (CDDM) installed on the same machine as Essentials. CDDM, which can be downloaded from CCO, provides syslog and TFTP daemons as part of its product. You cannot run CDDM Syslog or TFTP on the same machine as Essentials because they are not compatible. Make sure the server on which you install Essentials is not running CDDM Syslog or TFTP.
WARNING: The tftp directory `/tftpboot' appears to be NFS mounted. Using NFS directories often increases the software transfer time and may cause a failure during distribution of the software to the device. Contact your local technical support representative to make `/tftpboot' a local directory.
If you try to remove Essentials but the uninstallation program fails to delete a package, try running the uninstallation program again. Several circumstances can cause a package not to uninstall successfully. Usually, running the uninstallation program again will remove the package.
The CiscoWorks2000 server uses port 80 by default. This port is normally used by web servers. If you receive an error message that an existing web server is already configured to run on port 80, and the alternative port 1741 is used instead, verify that you entered the correct URL for the server:
http://server_name:1741
where server_name is the name of the machine where CiscoWorks2000 was installed, and 1741 is the alternative port on which CiscoWorks2000 is installed if port 80 is in use.
Use the following command to make sure your server is running:
ping server_name
If you get a message that the server is "alive," and get a proxy error when you try to connect to the server, make sure the proxy is set up correctly. If your server is configured to use a proxy server outside the firewall (specified in Netscape Navigator under Options > Network Preferences > Proxies), you will get proxy errors if you configured the proxy to ignore requests to a certain machine, set of machines, or domain.
Your proxy is set up incorrectly if:
If the Daemon Manager is not running, CiscoWorks2000 cannot run. When you install or uninstall CiscoWorks2000, the Daemon Manager is temporarily stopped and then restarted. If the install or uninstall process is interrupted, the Daemon Manager might remain in the stopped state.
To start or stop the Daemon Manager:
Step 1 Log in as root.
Step 2 Open a shell window.
Step 3 Start the server by entering the following:
# /etc/init.d/dmgtd start
Step 4 Stop the server by entering the following:
# /etc/init.d/dmgtd stop
You can check back-end server process failures by selecting CiscoWorks2000 Server > Administration > Process Management > Process Status. Only users with administrator privileges can start and stop processes. For details, refer to Getting Started with the CiscoWorks2000 Server.
If the desktop buttons do not work, Java and JavaScript are not enabled. Make sure you enable Java and JavaScript.
Make sure the browser cache is not set to zero.
Do not resize the browser window while the desktop main page is loading. This can cause a Java error.
For more information about setting up browsers, refer to Installing and Setting Up CiscoWorks2000 CD One on Windows NT.
To improve system performance for Essentials, consider these options:
Posted: Thu Feb 3 11:14:51 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.