|
|
This appendix lists some typical Cache Engine messages in the following sections:
Each message is categorized as more or less severe according to how it affects the Cache Engine's functionality. The critical and warning message descriptions include an explanation of what may have caused the error and how to solve the problem. The notice messages are simply listed for your information.
During normal operation of your Cache Engine, error messages are logged to the Cache Engine's GUI log. If you have configured a syslog server, the messages are sent to the server. For more information on configuring your syslog server, see "Syslog".
Critical messages are the most severe and may require that you contact the TAC.
Error Message Inode Error: Resetting drive 3.
Explanation Data in the drive (in this case, drive 3) did not match the data in the running directory, as expected. This may be due to corrupt data. When the Cache Engine encounters corrupt data, it flushes the partition's data.
Recommended Action If this message displays frequently, contact the TAC. If it appears occasionally, no action is required.
Error Message Lost drive 3.
Explanation A drive (in this case, drive 3) is not responding to the system.
Recommended Action The Cache Engine may have a hard drive failure. If you see this message frequently, contact the TAC.
Error Message Rebooting because too many threads are dead.
Explanation The source of the problem may be 1) malicious (such as, a denial-of-service attack), 2) the network (if a portion of the network went down, it could prevent the Cache Engine from completing transactions), or 3) the Cache Engine.
Recommended Action If you eliminate the first two possibilities, and suspect the third problem, contact the TAC.
Error Message ThreadsAllGone about to reboot 3.
Explanation The maximum number of concurrent TCP sessions have been used. If transactions do not complete soon (and free up threads), the Cache Engine assumes it is blocked and reboots.
Recommended Action If you see this message frequently, contact the TAC.
Error Message Wccp disabled due to blocked cache.
Explanation If all 2000 threads are used and no transactions are complete in a 30-second interval, the Cache Engine disconnects from WCCP to tell the router to stop sending the Cache Engine web requests. This is an abnormal state.
Recommended Action First, determine if this was a denial-of-service attack; in other words, were all recent requests from the same IP address? If not, contact the TAC for troubleshooting assistance.
Warning messages are moderately severe and indicate a noteworthy condition.
Error Message admin added user Bob.
Explanation Primarily, this message is a security measure designed to inform you that a user (in this case, the admin user) created a new account for a new user, Bob. This user will have access to the Cache Engine's GUI.
Recommended Action None, if authorized. If not authorized, contact your Cache Engine's administrator.
Error Message admin deleted user Bob.
Explanation Primarily, this message is a security measure designed to inform you that a user (in this case, the admin user) deleted an account for a user, Bob.
Recommended Action None, if authorized. If not authorized, contact your Cache Engine's administrator.
Error Message admin modified user Bob.
Explanation Primarily, this message is a security measure designed to inform you that a user (in this case, the admin user) modified an account for a user, Bob.
Recommended Action None, if authorized. If not authorized, contact your Cache Engine's administrator.
Error Message admin unable to change syslog config.
Explanation A user (in this case, the admin user) attempted to change syslog settings and an writing the new configuration to the disk resulted.
Recommended Action Check the new configuration and resend. If the problem persists, contact the TAC.
Error Message admin flushing filesystem at 10.1.3.1.
Explanation A user (in this case, the admin user) flushed the cached contents of a Cache Engine with the IP address 10.1.3.1.
Recommended Action None, if authorized.
Error Message admin rebooting at 10.1.3.1.
Explanation A user (in this case, the admin user) rebooted a Cache Engine with the IP address 10.1.3.1.
Recommended Action None, if authorized.
Error Message DNS not configured.
Explanation DNS has not been set up on the Cache Engine.
Recommended Action If you want to use your Cache Engine in Proxy mode, you must configure a valid DNS server.
Error Message Detected 1000 bad connects.
Explanation Since the Cache Engine's last reboot, it has not connected to the Internet server that a client has requested an object from.
Recommended Action Depending upon the number of total requests, this number may be normal for Internet traffic. If the percentage of bad connects (compared to total requests) is under approximately three percent, then the percentage is normal. Internet servers are often overloaded (or are down) on the Internet. To view the percentage of bad requests compared to your traffic load, enter the CLI command, DiagDump "all" (see "DiagDump" section.)
Error Message Failed read seek to 10.1.3.1 errno=75432 at 3:00PM (GMT).
Explanation The file system failed to read from one of the hard drives.
Recommended Action The Cache Engine may have a hard drive failure. If you see this message frequently, contact the TAC.
Error Message Failed to read at least one url filter list.
Explanation After attempting to enable the URL filtering option, the Cache Engine could not interpret one of the two URL filtering files, either goodurl.lst or badurl.lst.
Recommended Action Create a new, plain test file, and ftp it to the "1_7_0.dir" directory. Try enabling the filter again. If unsuccessful, call the TAC.
Error Message Failed to start proxy mode on port 1234.
Explanation After attempting to activate Proxy mode on a port (in this case, port 1234), the Cache Engine failed to open the port.
Recommended Action Try a different port number as the specified port may already be in use.
Error Message Failed to write DNS information.
Explanation The Cache Engine was not able to write the DNS configuration change to the disk.
Recommended Action The Cache Engine may have a hard drive failure. If you see this message frequently, contact the TAC.
Error Message Failed write seek to 10.1.3.1 errno=75432 at 3:00PM (GMT).
Explanation The file system failed to seek the position it attempted to write to on the disk.
Recommended Action The Cache Engine may have a hard drive failure. If you see this message frequently, contact the TAC.
Error Message Failed writing to 10.1.3.1 errno=75432 at 3:00PM (GMT).
Explanation The file system failed to write to the disk.
Recommended Action The Cache Engine may have a hard drive failure. If you see this message frequently, contact the TAC.
Error Message Forced deleting of user Bob.
The Cache Engine maintains up to 50 different user accounts including the admin user account. When the 51st account is added to the Cache Engine, it will delete one of the other accounts (in this case, Bob's account.)
Recommended Action Do not create more than 50 different user accounts on one Cache Engine.
Explanation This message appears when a Cache Engine rejoins a Cache Engine farm.
Recommended Action None.
Error Message Leaving group.
Explanation This message appears when the Cache Engine is told to "leave group" from the GUI.
Recommended Action None.
Error Message Maximum connection capacity reached.
Explanation This message appears when all 2000 concurrent TCP sessions have been utilized.
Recommended Action If infrequent (during peak traffic or traffic spikes), no action is necessary. If frequent, you may have too much traffic for your Cache Engine(s) to process. We recommend adding another Cache Engine to your cache farm.
Error Message RADIUS: Bad code from 10.1.3.1.
Explanation The RADIUS server 10.1.3.1 could not understand the command code that this Cache Engine sent it.
Recommended Action Check that the RADIUS server and the Cache Engine are configured properly.
Error Message RADIUS: Found no active servers.
Explanation After configuring and enabling the RADIUS authentication on the Cache Engine, the Cache Engine could not locate the RADIUS server(s) you specified.
Recommended Action Check that you entered the correct RADIUS information on the Cache Engine. Also check that the RADIUS server is functioning correctly.
Error Message RADIUS: Incorrect shared secret with 10.1.3.1.
Explanation The key the Cache Engine supplied to the RADIUS server was not recognized by the RADIUS server.
Recommended Action Verify that you entered the correct secret key for the RADIUS configuration.
Error Message Resetting our filesystem.
Explanation This message is logged when a user flushes the cached content on the Cache Engine.
Recommended Action No action required if this was an authorized action.
Error Message There are 10 dead tasks out of 2000.
Explanation Ten of 2000 possible concurrent TCP connections are permanently hung.
Recommended Action Contact the TAC.
Error Message Unable to initialize DNS.
Explanation Most likely, a memory allocation error occurred during bootup.
Recommended Action Contact the TAC.
Error Message Unable to set DNS servers correctly.
Explanation Most likely, there was an error writing to the disk.
Recommended Action Contact the TAC.
Error Message Unable to set domain name.
Explanation Most likely, there was an error writing to the disk.
Recommended Action Contact the TAC.
Notice messages inform you of normal but significant conditions. Some sample notices are:
Posted: Sat Sep 28 02:35:01 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.