Downloads |
Document ID: 41061
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Error Messages
100000 to 199999
200000 to 299999
300000 to 399999
400000 to 499999
500000 to 599999
600000 to 699999
700000 to 799999
900000 to 999999
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This document provides explanations and suggested actions for Cisco Application and Content Networking Software (ACNS) 5.01 syslog error messages.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on Cisco ACNS 5.01.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Error Messages
100000 to 199999
|
Message |
Explanation |
Action |
|---|---|---|
|
CE-ACQ-2-100001: Acquirer failed in db ops : [failure description] |
The message class indicates that the service acquirer encounters a critical error in database operation. |
Contact Cisco Technical Support. |
|
CE-ACQ-2-100002: Acquirer failed in UNS ops : [failure description] |
The message class indicates that the service acquirer encounters a critical error in unified name space (UNS) operation. |
Contact Cisco Technical Support. |
|
CE-ACQ-2-100003: Invalid manifest url: [failure description] |
The message class indicates that the manifest URL given is invalid. |
Double check the manifest URL in the channel for spelling. |
|
CE-ACQ-2-100004: Failed to create Rpc Server : [failure description] |
The message class indicates that the acquirer fails to create the remote procedure call (RPC) server. |
Contact Cisco Technical Support. |
|
CE-ACQ-2-100005: Failed to read [chars] = [chars] from [chars], error = [dec]. Will attempt to correct the problem. |
This can happen due to data corruption. In order to attempt to correct the problem, the acquirer tries to reparse or reupdate the manifest file as required. As a result of this condition some items are sometimes not acquired at first run. |
Contact Cisco Technical Support if you frequently see this message. |
|
CE-ACQ-2-100006: Failed to get channel lock : [failure description] |
The message class indicates that the acquirer has conflict with distribution. It fails to start the acquisition for the channel. |
Contact Cisco Technical Support. |
|
CE-ACQ-2-100007: Request hangs, will restart acquirer to correct the problem |
Due to internal error, the request hangs. You need to restart the acquirer to correct the problem. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-3-111000: Can't read auto registration config. Quitting. |
A necessary internal data structure is not found. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-3-111001: Failed to get default autoregistration interface. |
The system fails to get the default interface on which auto-registration is enabled. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-3-111002: Failed to remove dhclient pid file: <error> |
The system fails to remove a temporary data file. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-4-111003: DHCP server could not be contacted. Using a cached lease. |
The system is not able to contact a DHCP server. The system uses a lease obtained earlier. However, it is still valid. |
No action is required. |
|
CE-AUTOREG-4-111004: DHCP server could not be contacted will retry after 5 minutes |
The system is not able to contact a DHCP server. It retries every five minutes. |
No action is required. |
|
CE-AUTOREG-4-111005: Usable CDM hostname not found in DHCP server response |
The response from the DHCP servers does not contain vendor option information. |
Check the configuration on the DHCP server. |
|
CE-AUTOREG-3-111006: Error while starting up DHCP client (num, num) |
The system fails while it starts up the DHCP client. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-AUTOREG-3-111007: Can't read device mode. Disabling autoregistration |
The system fails to identify the device mode. As a precaution, auto-registration is not done on this system. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-3-111008: Failed to disable auto registation on the default interface (num, num) |
The system fails to disable auto-registration on the default interface. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-5-111009: Auto registration disabled on the default interface. |
The system disables auto- registration on the default interface. |
No action is required. |
|
CE-AUTOREG-3-111010: Auto registration on the default interface failed (num, num) |
The system fails while it does auto-registration on the default interface. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-3-111011: Auto registration enabled on the default interface. |
The system enables auto-registration on the default interface. |
No action is required. |
|
CE-AUTOREG-5-111012: Auto registration configuration found in startup-config. Quitting. |
Auto-registration configuration is found in the startup configuration. Therefore, the default configuration is not applied. |
No action is required. |
|
CE-AUTOREG-3-111013: CE/CR deregistration (cms disable) failed (num, num) |
The system fails when it disables CMS. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-5-111014: CE/CR deregistration (cms disable) successful |
The system successfully disables CMS before it enables it back with the new Content Distribution Manager (CDM) IP. |
No action is required. |
|
CE-AUTOREG-3-111015: CE/CR deregistration (cms deregister) failed (num, num) |
The system fails when it does deregistration. |
No action is required. |
|
CE-AUTOREG-5-111016: CE/CR deregistration (cms deregister) successful |
The system successfully deregisters the Content Engine (CE) before it is registered with the new CDM. |
No action is required. |
|
CE-AUTOREG-3-111017: Insufficient parameters to cfg_bin_runcms |
The program cfg_bin_autoreg_runcms does not receive a required parameter. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-5-111018: Auto registration is disabled. Ignore vendor option information |
Auto-registration is disabled. The vendor option information received in the DHCP server's response is ignored. |
No action is required. |
|
CE-AUTOREG-3-111019: Primary interface configuration failed (num, num) |
The system fails while it configures the primary interface. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-5-111020: Primary interface configuration successful |
The system configures the primary interface successfully. |
No action is required. |
|
CE-AUTOREG-3-111021: Could not get startup-config to check for cdm ip. Assuming it to be present |
The system fails to get the startup configuration when it tries to check if CDM configuration is present. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-5-111022: CDM IP found in startup-config/data server. Quitting. |
The CDM IP is found in the startup-config/data server. Therefore, no configuration changes are made. |
No action is required. |
|
CE-AUTOREG-3-111023: CDM hostname configuration failed (num, num) |
The system fails to configure the CDM hostname received through vendor option information from the DHCP server. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-AUTOREG-3-111024: CDM hostname configuration successful |
The system configures the CDM hostname successfully. |
No action is required. |
|
CE-AUTOREG-3-111025: Enable CMS failed (num, num). Retrying.. (num) |
The system fails while it enables CMS. It retries. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-AUTOREG-2-111026: Enabling CMS failed even after <num> retries. |
The system fails to enable CMS even after it retries <num> times. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-AUTOREG-5-111027: CDM hostname configuration removed (num, num) |
The CDM hostname configuration is removed, since enabling CMS with the CDM fails . |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-AUTOREG-3-111028: Failed to save the running-config to startup-config (num, num) |
The system fails while it saves the configuration to non-volatile Flash storage. |
Contact Cisco Technical Support. |
|
CE-AUTOREG-5-111029: CE/CR successfully registered with the CDM |
The system is successfully registered with the CDM. |
No action is required.. |
|
CE-BANDWD-3-115001: Failed to bind to [item] error number [x] |
The bandwidth module fails to bind [item] in the data server. The error number for the bind is [x]. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115002: The failed operation will be retried in two seconds |
The bandwidth module retries the failed operation in two seconds. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115003: Failed verification registration with data server with error [x] |
The bandwidth module fails to register with data server for verification. The error number is [x]. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-4-115004: Failed to create a thread for notification |
The bandwidth module fails to create a thread for notification from the database. It is restarted by the node manager. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115005: Bandwidth setting failed |
The bandwidth module fails to set bandwidth because of an invalid module. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-6-115006: Set bandwidth for module [name] to [value] |
The bandwidth module sets the bandwidth for module [name] to [value]. |
No action is required. This is an informational message. |
|
CE-BANDWD-3-115007: Error [x] retrieving item [name] from data server |
The bandwidth module fails to get item [name] from the data server. The error number for the get is [x]. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115008: Bandwidth module got error [x] from data server |
The bandwidth module gets error [x] while it tries to receive a whole message from the data server. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115009: Bandwidth module lost connection to data server |
The bandwidth module loses the connection to the data server. It tries the connection again. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115010: Bandwidth module got error [x] on ds_verification_info() |
The bandwidth module gets error [x] while it retrieves verification information from the data server. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115011: Bandwidth module got error [x] on ds_build_verification_ack() |
The bandwidth module gets error [x] while it builds verification acknowledgement (ACK) to the data server. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115012: Bandwidth module got error [x] on ds_send_whole_ack() |
The bandwidth module gets error [x] while it sends verification ACK to the data server. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115013: Bandwidth module got bad type [x] on ds_receive_whole_msg() |
The bandwidth module gets error [x] while it receives a message from the data server. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115014: Bandwidth module got socket error and is restarting |
The bandwidth module gets a socket error. It restarts . |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-5-115015: Bandwidth module failed to connect to the Multicast Sender |
The bandwidth module fails to send a message to the multicast sender. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-6-115016: Bandwidth module: Configured WMT bandwidth is [x] but a lower value is being set [y] due to a lower WMT bandwidth license |
The bandwidth module sets the Windows Media Technology (WMT) value to [y] . This is lower than the configured value of [x}. This is because the bandwidth license configured allows for a lower value. |
This is an informational message to point out the difference between the actual value of bandwidth available and the configured value. |
|
CE-BANDWD-3-115017: Failed notification registration with data server with error [x] |
The bandwidth module fails to register with the data server for notification. The error number is [x]. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BANDWD-3-115018: Bandwidth module got error [x] on ds_notification_info() |
The bandwidth module gets error [x] while it retrieves notification information from the data server for the WMT license. |
The system needs to recover from the error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-BYPS-0-130000: BYPASS: System going out of Bypass mode |
The load on the box is probably reduced. The system switches out of bypass mode. |
No action is required. |
|
CE-BYPS-5-130001: BYPASS: System going Offline BYPASS: reload to return to Online state |
The device goes offline because of overload. |
A reboot is recommended to bring back the system in a stable state. |
|
CE-BYPS-4-130002: BYPASS: System going into Bypass mode |
The load on the box has probably gone above its maximum limit. The device bypasses new connections. |
Reduce load or add additional CEs to handle the load. The device can possibly become unstable if it gets overloaded. |
|
CE-BYPS-4-130003: BYPASS: sysdb_item_set() failed: return value is [error] |
The device overload state fails to be saved successfully in the data server. Device state can be incorrectly displayed. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-BYPS-4-130004: BYPASS: Module [module] not registered due to bad name. |
The specified module fails to register its overload state. The module's state can be displayed incorrectly. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-BYPS-4-130005: BYPASS: Module [module] not registered successfully. |
The specified module fails to register with overload. The module's state can be displayed incorrectly. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-BYPS-1-130006: BYPASS: Module [module] is unable to handle the load. |
The specified module is highly overloaded and is in a critical state. |
Reduce the load on the box. A reboot is probably required to make sure that the device has not entered an unstable state. |
|
CE-BYPS-5-130007: OVERLOAD: Preload did not receive overload message. Preload may not be running |
Preload is not informed of an overload condition. The box gets loaded more if preload begins. |
If preload is not configured, ignore this message. If preload is enabled, contact Cisco Technical Support. |
|
CE-CACHE-2-140001: HTTP proxy fails at startup: [failure description] |
The message class indicates that a critical error occurs while HTTP proxy starts and requests system FD resources. |
Usually, the HTTP proxy is restarted automatically. If problem persists, restart the whole system. Keep tech support information and contact Cisco Technical Support. |
|
CE-CACHE-2-140002: HTTP proxy fails at startup: [failure description] |
The message class indicates that a critical error occurs while HTTP proxy starts and requests virtual address space. |
Usually, the HTTP proxy is restarted automatically. If the problem persists, restart the whole system. Keep tech support information and contact Cisco Technical Support. |
|
CE-CACHE-2-140003: HTTP proxy fails at startup: [failure description] |
The message class indicates that a critical error occurs while HTTP proxy starts and requests virtual memory resources. |
Usually, the HTTP proxy is restarted automatically. If the problem persists, restart the whole system. Keep tech support information and contact Cisco Technical Support. |
|
CE-CACHE-2-140004: HTTP proxy fails at binding to tcp ports: [failure description] |
The message class indicates that a critical error occurs while HTTP proxy starts and fails to bind on specific ports. |
Usually, the HTTP proxy fails to accept requests from the ports which have the problem. It runs and serves traffic on other ports. Restart the whole system if the problem persists. Keep tech support information and contact Cisco Technical Support. |
|
CE-CACHE-3-140005: HTTP proxy failed to load third party plugin library |
The loading of a third party plugin library fails due to the listen port add failure. |
The HTTP proxy restarts, but without the third party plugin. The functionality of the plugin is not available to the HTTP proxy. Keep tech support information and contact Cisco Technical Support. |
|
CE-CLI-3-170000: Can't bind to SysDB at "ENABLE_CFG_PREFIX " error <str> |
Exec fails to establish the connection to the data server. |
Log out and login again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170001: [Procedure]: opendir([dirname]) |
opendir() fails in the Exec. |
Log out and login again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170002: [Procedure]: opendir(<dirname>) |
opendir() fails in the Exec. |
Log out and login again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170003: File [filename] has problem: <error> |
File operations (open, write) fail . |
Log out and login again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-5-170005: CDP-EV: No more interfaces running CDP - removing CDP process |
This message lets the user know about the Cisco Discovery Protocol (CDP) status. |
No action is required. |
|
CE-CLI-3-170006: Can not open [filename] file, errno: [dc] |
Fails to open the memory configuration template file. |
Retry. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-5-170007: Wrong arguments |
The memory configuration program receives the wrong number of arguments. |
Retry. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170008: CLI:sysdb_bind failed in cfs_clear error = [dec] |
The Command Language Interpreter (CLI) fails to establish a connection with the data server. |
Retry. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170009: CLI:sysdb_bind failed in cfs_sync, error = [dec] |
The CLI fails to establish a connection. |
Retry. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170010: CLI:sysdb_bind failed in cfs_mount, error = [dec] |
The CLI fails to establish a connection. |
Retry. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170011: CLI:sysdb_bind failed in cfs_unmount, error = [dec] |
The CLI fails to establish a connection. |
Retry. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170012: CLI:Copy [str] to SS failed. status = ([dec],[dec]). Ignore if you didn't change RealProxy config. |
The safe manager fails to copy the files. |
If Real Proxy configuration has not changed, ignore this message. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170013: [cmd] failed: status = ([dc],[dc]) |
The above command fails . |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170014: Your file system is unmounted, but [str] is not empty! |
Fails to delete the mount point. |
Reboot the device and retry. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170015: General error when deleting [str], errorno = [dc] |
Fails to delete the mount point. |
Reboot the device. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170016: [str]: failed to pick up startup-configuration: [cmd] = ([dc],[dc]) |
Fails to retrieve the startup-configuration. |
Contact Cisco Technical Support. |
|
CE-CLI-2-170017: Can not open interface stat file to read |
The file is missing. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170018: Error when extracting interface status for [dc] |
Fails to retrieve statistics for a specific interface. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170019: failed when reading interface stat file <str> |
Fails to read the interface stat file. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170020: [str] |
The message needs to have information about the error. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170020: Can't read memory.config, so memory cap for Real Proxy is default <str> |
memory.config is not read. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170021: Can't open file [filename] for reading: [error] |
Fails to open a file mentioned in the message. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170022: CDP platform is unknown |
Fails to find the expected CDP information. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170023: Can't open file [filename] for writing |
Fails to open a file mentioned in the message. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170024: Hostname string length is incorrect |
Finds an incorrect hostname string length. |
Use the correct length hostname and retry. |
|
CE-CLI-7-170025: [CLI debug message] |
The message indicates CLI debug information. |
No action is required. |
|
CE-CLI-2-170026: Failed to delete old gateway from route table (no, no) |
Software fails when it tries to remove the previously configured default gateway. |
Contact Cisco Technical Support. |
|
CE-CLI-2-170027: Failed to configure the default gateway (no, no) |
Software fails when it tries to configure the new default gateway. |
Check if the default gateway is valid and correct. Try to reconfigure. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170028: Failed to modify default gateway in sysconfig (no) |
Software fails when it tries to configure the new default gateway. |
Contact Cisco Technical Support. |
|
CE-CLI-3-170029: Failed to stop evaluation for <string>, ret <number> |
Fails to stop evaluation for application. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-6-170030: Stopped evaluation for <string> |
Stops evaluation for application. |
No action is required. |
|
CE-CLI-3-170031: writing to mediafs split file failed. Can't open file |
The writing of new WMT and Real ratios into the history file fails (in mediafs). |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-5-170032: Syslog cleared |
Syslog is cleared. |
No action is required. |
|
CE-CLI-2-170033: populate_ds: verifier registration failed for <string> error = <num> (errno = <num>/<string>) |
Verifier verifies the validity of some CLIs. If this occurs, many CLIs work. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170034: NOTE: populate_ds: unable to set default value via verifier for <string>, rc = <num>; continuing |
The default value for some configuration items is not set. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-7-170035: <various messages> |
Debug messages. |
No action is required. |
|
CE-CLI-2-170036: rule_operation_ds_rule(): rule table is NULL, Cannot read any rules |
Rules are not read. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170037: rule_operation_ds_pattern(): Invalid rules pattern, pattern structure corrupted |
There is an error in the rules pattern. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170038: rule_item_action_string(): Invalid rules action, Action structure corrupted |
Rules action is not determined. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170039: print_valid_patterns(): Invalid rules action, action structure corrupted |
Rules action is not determined. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170040: rule_action_string(): Invalid rules action, action structure corrupted |
Rules action is not determined. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170041: rule_pattern_string(): Invalid rules pattern, pattern structure corrupted |
Error in the rules pattern. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-2-170042: rule_item_pattern_string(): Invalid rules pattern, pattern structure corrupted |
Error in the rules pattern. |
Try again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170043: ver_webserver: SIGTERM received! |
Termination signal is received by process. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-3-170044: ver_webserver: signal(SIGTERM, ...) failed. |
Process fails to issue a SIGTERM successfully. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-5-170045: Auto registration is enabled on this interface. Either disable auto registration, or enable auto registration on a different interface, before proceeding with IP address/dhcp configuration |
Auto-registration is currently enabled on this interface. It needs to be disabled before the IP address/DHCP configuration is made. |
No action is required. |
|
CE-CLI-5-170046: Disabling auto registration.. (num, num) |
When it carries out IP address/DHCP configuration, since the CE is not already registered with the CDM, the system disables auto-registration. |
No action is required. |
|
CE-CLI-5-170047: Could not load kernel module [module name]. |
The specified kernel module is not loaded. The information provided by CLI is probably incomplete. |
Try the CLI again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-5-170048: Could not unload kernel module [module name]. |
The specified kernel module is not unloaded. |
Try the CLI again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CLI-5-170049: Could not read proc interface for smbios. |
The proc interface to smbios is not read. The information provided by the CLI is probably incomplete. |
Try the CLI again. If you frequently see this message, contact Cisco Technical Support. |
|
CE-CR-3-180101: Memory allocation failure |
The memory resource is exhausted. |
Contact Cisco Technical Support. |
|
CE-CR-5-180102: Routing table is rebuilt |
The routing table is rebuilt since one or more of the configuration files are changed. |
No action is required. |
|
CE-CR-5-180201: Keepalive is started/resumed |
The keepalive is started/resumed on this CE. |
No action is required. |
|
CE-CR-4-180202: Keepalive is not received |
The keepalive message for the CE is not received. |
Check the connectivity between the CE and the content router. |
|
CE-CR-3-180301: Failed to open a connection to data server |
This is an internal error. Fails to open a connection to data server. |
Contact Cisco Technical Support. |
|
CE-CR-3-180302: Failed to close a connection to data server |
This is an internal error. Fails to close a connection to data server. |
Contact Cisco Technical Support. |
|
CE-CR-3-180303: Failed to register notifications to data server |
This is an internal error. Fails to register notifications to the data server. |
Contact Cisco Technical Support. |
|
CE-CR-3-180304: Failed to unregister notifications from data server |
This is an internal error. Fails to unregister notifications from the data server. |
Contact Cisco Technical Support. |
|
CE-CR-3-180305: Failed to get notifications from data server |
This is an internal error. Fails to get notifications from the data server. |
Contact Cisco Technical Support. |
|
CE-CR-3-180306: Failed to create a thread |
Fails to create a thread. |
Contact Cisco Technical Support. |
|
CE-CR-3-180307: Failed to free resouces received on VEN socket |
Fails to free resources received on the VEN socket. |
Contact Cisco Technical Support. |
|
CE-CR-3-180308: Failed to get an entire message from the VEN socket |
Fails to get an entire message from the VEN socket. |
Contact Cisco Technical Support. |
|
CE-CR-3-180309: Failed to register as an EDM agent to data server |
Fails to register as an Extended Data Manager (EDM) agent to the data server. |
Contact Cisco Technical Support. |
|
CE-CR-3-180310: Failed to unregister EDM from data server |
Fails to unregister EDM from the data server. |
Contact Cisco Technical Support. |
|
CE-CR-3-180311: Failed to receive EDM information |
Fails to receive EDM information. |
Contact Cisco Technical Support. |
|
CE-CR-3-180312: Failed to assemble an EDM acknowledgement |
Fails to assemble an EDM acknowledgement. |
Contact Cisco Technical Support. |
|
CE-CR-3-180313: Failed to send an acknowledgement |
Fails to send an acknowledgement. |
Contact Cisco Technical Support. |
|
CE-COMMONEDM-4-185000: register_verifier: ver reg err (ret = [error number]) |
The common EDM fails to register its verifier with the data server. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-COMMONEDM-4-185001: register_notifier: notifier reg err (ret = [error number]) |
The common EDM fails to register its notifier with the data server. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-COMMONEDM-4-185002: get verification info err (ret=[error number]) |
The common EDM fails to get information from the data server in the verifier. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-COMMONEDM-4-185003: get notification info err (ret=[error number]) |
The common EDM fails to get information from the data server in the notifier. |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-COMMONEDM-4-185004: could not create /tmp/syslogd_cw2kmode (ret = [errorcode], [description]) |
The common EDM fails to create the specified flag file. The CiscoWorks 2000 mode of syslogd remains unchanged. |
Try to enable/disable CiscoWorks 2000 mode. If you see this message often, contact Cisco Technical Support. |
|
CE-COMMONEDM-4-185005: could not unlink /tmp/syslogd_cw2kmode (ret = [errorcode], [description)] |
The common EDM fails to unlink the specified flag file. The CiscoWorks 2000 mode of syslogd remains unchanged. |
Try to enable/disable CiscoWorks 2000 mode. If you frequently see this message, contact Cisco Technical Support. |
|
CE-COMMONEDM-4-185006: could not open /tmp/syslogd_cw2k_timezone for writing (ret=[errorcode], [description]) |
The common EDM opens the timezone information file. The timezone information used by syslogd remains unchanged. |
Try to change the timezone information. If you frequently see this message, contact Cisco Technical Support. |
|
CE-COMMONEDM-4-185007: could not write to /tmp/syslogd_cw2k_timezone |
The common EDM fails to write to the timezone information file. The timezone information used by syslogd remains unchanged. |
Try to change the timezone information. If you frequently see this message, contact Cisco Technical Support. |
|
CE-SCHED-2-189000: Missing scheduler working thread |
One of the worker threads that the scheduler uses to assign work terminates unexpectedly. The CE Web Proxy cache attempts to recover by restarting itself. |
Contact Cisco Technical Support. |
|
CE-SCHED-5-189001: Reporting of thread and process identifiers |
Upon startup, the CE scheduler reports the internal process and thread identifiers. This information is potentially useful in debugging problems. |
No action is required. |
|
CE-SCHED-4-189002: Scheduler CLI memory allocation failure |
Upon receiving a CLI command to perform an action to modify the behavior of the scheduler, a memory resource allocation fails. This sometimes results in the failure of some CLI commands . |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-SCHED-4-189003: Scheduler CLI file open failure |
Upon receiving a CLI command to perform an action to modify the behavior of the scheduler, a file is not opened. This sometimes results in the failure of some CLI commands . |
If you frequently see this message, contact Cisco Technical Support. |
|
CE-DHCP-0/1/2/3/4/5/6-191000: Descrition |
These messages are generated by the DHCP client. |
If you frequently see this message, contact Cisco Technical Support. |
200000 to 299999
|
Message |
Explanation |
Action |
|---|---|---|
|
CE-DISK-1-200001: disk_check_io(): fork failed (<error>) |
Fork() fails . The system is unstable. |
Reload. If you frequently see this message, contact Cisco Technical Support. |
|
CE-DISK-2-200002: disk_check_io(<device>): open (<error>) |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. |
|
CE-DISK-2-200003: disk_check_io(<device>): seek (<error>) |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. |
|
CE-DISK-2-200004: disk_check_io(<device>): read (<error>) |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. |
|
CE-DISK-2-200005: disk_check_io(<device>): bad disk |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. |
|
CE-DISK-2-200006: disk_check_io(<device>): waitpid (<error>) |
Possible bad disk. Disk operation hangs. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. |
|
CE-DISK-6-200007: disk_check_io(<device>): waitpid (<error>) |
Debug message. |
No action is required. |
|
CE-DISK-2-200008: <diskname> is bad. Check cable or replace it. |
Possible bad disk. |
Replace the bad disk. Reinstall the software if it is disk00. |
|
CE-DISK-2-200009: read signature: open device failed: <device> <error> |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. Reinstall software if it is disk00. |
|
CE-DISK-2-200010: read signature: seek device failed: <device> <error> |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. Reinstall software if it is disk00. |
|
CE-DISK-2-200011: read signature: read device failed: <device> <error> |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. Reinstall software if it is disk00. |
|
CE-DISK-2-200012: write signature: open device failed: <device> <error> |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. Reinstall software if it is disk00. |
|
CE-DISK-2-200013: write signature: seek device failed: <device> <error> |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. Reinstall software if it is disk00. |
|
CE-DISK-2-200014: write signature: write device failed: <device> <error> |
Possible bad disk. |
Issue the show disks details command to decide which disk is bad. Replace the bad disk. Reinstall software if it is disk00. |
|
CE-DISK-2-200015: First disk %s has problems. You need to check cable or replace it, then run "disk recover" command from CLI and re-install software. |
Possible bad disk00. |
Replace disk00. Issue the disk recover command. Reinstall the software. |
|
CE-DISK-4-200016: ruby_disk: allocation data corrupted <magic> <version> < magic 2> |
Allocation data created by the disk configure command is corrupted. |
Issue the disk configure command again. If you frequently see this message, contact Cisco Technical Support. . |
|
CE-DISK-3-200017: ruby_disk: physical disk setup appears to have changed not effecting 'disk config' changes |
Allocation data created by the disk configure command is not used because disk setup has changed. |
Issue the disk configure command again. |
|
CE-DISK-2-200018: Can not create log directory <dir>: <error> |
Fails to create necessary directory. |
Contact Cisco Technical Support. |
|
CE-DISK-2-200019: Can not create log export directory <dir>: <error> |
Fails to create the necessary directory. |
Contact Cisco Technical Support. |
|
CE-DISK-2-200020: Can not symlink from <dir> to <dir>: <error> |
Fails to create symlink directory. |
Contact Cisco Technical Support. |
|
CE-DISK-2-200021: Can not create crash directory <dir>: <error> |
Fails to create the necessary directory. |
Contact Cisco Technical Support. |
|
CE-DISK-3-200022: Unknown disk-layout: sw=<num>, swstore=<num>, swap=<num> |
Fails to handle the partition layout. |
Contact Cisco Technical Support. |
|
CE-DISK-3-200023: Unknown acns5 disk layout: sw=<num>, swstore=<num>, swap=<num> state=<num> |
Fails to handle the partition layout. |
Contact Cisco Technical Support. |
|
CE-DISK-3-200023: Unknown acns5 disk layout: sw=<num>, swstore=<num>, swap=<num> state=<num> |
Fails to handle the partition layout. |
Contact Cisco Technical Support. |
|
CE-DISK-2-200024: First disk not in standard configuration. Run 'disk recover' command and re-install software. |
The first disk does not have the correct partition configuration. |
Issue the disk recover command. Re-install the software. |
|
CE-DISK-4-200025: diskXX is too small <size>MB (<size>MB is needed) |
The specified disk is smaller than 2 GB. This is usually because the Fiber Channel (FC) configuration is not set correctly. |
Replace with a Cisco disk if it is a directly attached disk and not a Cisco one. Reconfigure fiberchannel with a size larger than 2 GB if it is an FC disk. |
|
CE-DIST-2-210000: meta_sender failed in db ops: [failure description] |
The message class indicates that a critical db error occurs in meta_sender operations. |
Usually, the meta_sender service is restarted automatically. Keep tech support information and contact Cisco Technical Support. . |
|
CE-DIST-2-210001: meta_sender failed in channel table ops: [failure description] |
The message class indicates that a critical error occurs in meta_sender operations on the channel table. |
Usually, the meta_sender service is restarted automatically. Keep tech support information and contact Cisco Technical Support. |
|
CE-DIST-2-210002: meta_sender failed in system calls: [failure description] |
The message class indicates that a critical error occurs when meta_sender makes systems calls (for example, select). |
Usually, the meta_sender service is restarted automatically. Keep tech support information and contact Cisco Technical Support. |
|
CE-DIST-2-210003: meta_sender failed in initialization : [failure description] |
The message class indicates that a critical error occurs in meta_sender initialization. |
Usually, the meta_sender service is restarted automatically. Keep tech support information and contact Cisco Technical Support. |
|
CE-DIST-2-211000: meta_receiver failed in ds ops: [failure description] |
The message class indicates that a critical db error occurs in meta_sender operations. |
Usually, the meta_receiver service is restarted automatically. Keep tech support information and contact Cisco Technical Support. |
|
CE-DIST-2-211001: meta_receiver failed in uns ops: [failure description] |
The message class indicates that a critical db error occurs in meta_receiver operations. |
Usually, the meta_receiver service is restarted automatically. Keep tech support information and contact Cisco Technical Support. |
|
CE-DIST-2-211002: meta_receiver failed in sys calls: [failure description] |
The message class indicates that a critical db error occurs in meta_receiver operations. |
Usually, the meta_receiver service is restarted automatically. Keep tech support information and contact Cisco Technical Support. |
|
CE-DIST-2-211003: meta_receiver failed in initialization: [failure description] |
The message class indicates that a critical error occurs in meta_sender starting phase. |
Usually, the meta_receiver service is restarted automatically. Keep tech support information and contact Cisco Technical Support. |
|
CE-DIST-2-211004: meta_receiver full reload failed: error[error_no] channel_id[channel_id] \ root_ce_id[root_ce_id] root_ce_uid[root_ce_uid] |
The message indicates that the meta_receiver fails to do a full reload of the specified channel from the root CE. |
Usually, the meta_receiver service is restarted automatically. Keep tech support information and contact Cisco Technical Support. |
|
CE-DIST-2-211005: meta_receiver saw inconsistent gen id in replication [req/claimed/max gen ids]. |
The message indicates that the meta_receiver sees inconsistent generation ids at the time of meta data replication. |
Usually, the meta_receiver service is restarted automatically. Keep tech support information and contact Cisco Technical Support. |
|
CE-DIST-2-212000: uni_sender failed in db ops: [failure description] |
The message class indicates that the unicast data sender service encounters a critical database error. |
Contact Cisco Technical Support. |
|
CE-DIST-2-212001: uni_sender failed in semaphore ops: [failure description] |
The message class indicates that the unicast data sender service encounters a critical error in semaphore/mutex deployment for its internal datastructure. |
Contact Cisco Technical Support. |
|
CE-DIST-2-212002: uni_sender failed in uns ops: [failure description] |
The message class indicates that the unicast data sender service encounters a critical error in UNS operations. |
Contact Cisco Technical Support. |
|
CE-DIST-2-212003: uni_sender failed in bw ops: [failure description] |
The message class indicates that the unicast data sender service encounters a critical error in bandwidth control. |
Contact Cisco Technical Support. |
|
CE-DIST-2-212004: uni_sender failed in apache ops: [failure description] |
The message class indicates that the unicast data sender service encounters a critical error in the HTTP server library. |
Contact Cisco Technical Support. |
|
CE-DIST-2-213000: uni_receiver failed in db ops: [failure description] |
The message class indicates that the unicast data receiver service encounters a critical error in database operations. |
Contact Cisco Technical Support. |
|
CE-DIST-2-213001: uni_receiver failed in uns ops: [failure description] |
The message class indicates that the unicast data receiver service encounters a critical error in UNS operations. |
Contact Cisco Technical Support. |
|
CE-DIST-2-213002: uni_receiver failed in sys calls: [failure description] |
The message class indicates that the unicast data receiver service encounters a critical error in system calls (select/RPC) . |
Contact Cisco Technical Support. |
|
CE-DIST-2-213003: uni_receiver failed in bw control: [failure description] |
The message class indicates that the unicast data receiver service encounters a critical error in bandwidth control. |
Contact Cisco Technical Support. |
|
CE-DIST-2-213004: uni_receiver failed in HT ops: [failure description] |
The message class indicates that the unicast data receiver service encounters a critical error in the HTTP client library. |
Contact Cisco Technical Support. |
|
CE-DIST-4-214001: Channel Routing topology multicast sender transient error. |
The channel routing module detects that the multicast sender for the receive multicast cloud is the home CE itself. |
The system needs to recover from this transient error automatically. If you frequently see this message, contact Cisco Technical Support. |
|
CE-DIST-2-215000: mcast_sender failed in db ops: [failure description] |
The message class indicates that the multicast file sender service encounters a critical database error. |
Contact Cisco Technical Support. |
|
CE-DIST-2-215001: mcast_sender plug-in failed in db ops: [failure description] |
The message class indicates that the multicast file sender service encounters a critical database error. |
Contact Cisco Technical Support. |
|
CE-DIST-2-215002: mcast_sender failed in rpc ops: [failure description] |
The message class indicates that the multicast file sender service fails to create the RPC server. |
Contact Cisco Technical Support. |
|
CE-DIST-2-215003: mcast_file_sender failed in rpc ops: [failure description] |
The message class indicates that the multicast file sender service fails to create the RPC server. |
Contact Cisco Technical Support. |
|
CE-DIST-2-216000: mcast_receiver failed in db ops: [failure description] |
The message class indicates that the multicast file receiver service encounters a critical database error. |
Contact Cisco Technical Support. |
|
CE-DIST-2-216001: mcast_receiver plug-in failed in db ops: [failure description] |
The message class indicates that the multicast file receiver service encounters a critical database error. |
Contact Cisco Technical Support. |
|
CE-DIST-2-216002: mcast_receiver failed in rpc ops: [failure description] |
The message class indicates that the multicast file receiver service fails to create the RPC server. |
Contact Cisco Technical Support. |
|
CE-DIST-2-216003: mcast_receiver plug-in failed in uns ops: [failure description] |
The message class indicates that the multicast file receiver service encounters a critical error in UNS operations. |
Contact Cisco Technical Support. |
|
CE-DIST-2-217000: mcast system call: [failure description] |
The message class indicates that either the multicast file sender or multicast file receiver encounters a critical error in system calls (fork/execvp). |
Contact Cisco Technical Support. |
|
CE-DNS-1-221000: HTTP DNS cache out of memory |
The internal HTTP DNS resolution cache service runs out of memory. |
The HTTP DNS resolution module tries to recover. However, such a problem is symptomatic of a system-wide memory shortfall. Restart the machine. If you frequently see this message, contact Cisco Technical Support. |