Guest

Cisco Application and Content Networking System (ACNS) Software

Syslog Error Messages for ACNS 5.01

Cisco - Syslog Error Messages for ACNS 5.01

Document ID: 41061

Updated: Nov 30, 2005

   Print

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.
CE-DNS-2-221001: HTTP DNS cache has no configured nameservers to query The internal HTTP DNS resolution cache service has no configured DNS nameservers to send queries to. As a result, it is unable to do its job. Many services are disrupted. Configure DNS nameservers in the CLI.
CE-DNS-2-221002: HTTP DNS cache has detected an inconsistent internal state The internal HTTP DNS resolution cache service has detected an inconsistent internal state. Such an instance is indicative of memory corruption of some kind. Whether the corruption is hardware or software is unknown until further investigation is undertaken. The HTTP DNS resolution service causes the entire proxy caching application to exit and restart. If you frequently see this message, contact Cisco Technical Support.
CE-DNS-2-221003: HTTP DNS cache unable to open a UDP socket to send queries on The internal HTTP DNS resolution cache service is unable to open an ephemeral UDP socket to send DNS requests to any of the configured DNS servers. The HTTP DNS resolution module tries to recover. However, such a problem is symptomatic of a system-wide network resource shortfall. Restart the machine. If you see this message often, contact Cisco Technical Support.
CE-DNS-6-221004: Periodic HTTP DNS statistics report Every ten seconds, a LOG_INFO priority message is sent to the syslog process. It lists the average number of milliseconds taken to resolve a request, the number of requests resolved, and the number of times that the DNS service retries requests due to a configured DNS server not responding. No action is required.
CE-DNS-5-221005: Persistent write failure on ephemeral DNS server query socket The HTTP caching DNS service sends resolution requests that it fails to satisfy from its cache to a configured upstream DNS server through an ephemeral UDP socket. If the service is unable to write to the socket for longer than 30 seconds, it shuts down the socket and attempts to open another. This is perhaps indicative of a greater system-wide networking subsystem problem. No action is required. The cache process attempts to recover automatically
CE-DNS-2-221006: Unable to perform data server operations The system DNS cache needs to be able to get the configuration and changes to the configuration from the data server. This message indicates that it fails to do that and hence is not able to run. This can be indicative of a major system problem if it is persistent. No action is required. The cache process restarts in an attempt to recover. If it is persistent, a reboot of the system is probably required.
CE-DNS-4-221007: DNS has not been able to PIN the entries [name] requested The system DNS cache allows users to configure static entries in the DNS cache. The cache is unable to set this entry. Remove and add the entry in the configuration again.
CE-DNS-2-221008: DNS is not able to listen on address [address] port [port] The system DNS cache attempts to open a port on which to listen for requests. It fails . This can be a system wide resource issue or possibly a conflict with another running application. If this occurs on the loopback address, it is a sign that the system is in a indeterminate state. Change the listen parameters in the configuartion. If this occurs on the loopback address, a reboot is probably required.
CE-DS-3-230300: Unexpected msg type, ds client and server out of sync. Data server client sees an unexpected message type in response from the data server. This means that the communication between data server and client is out of sync. Client process needs to recover. If not, restart the system
CE-DS-3-230301: Client read error Client side gets read error when reading from data server. Client tries to recover. If it does not recover, there can be some problem with the data server. You need to restart the system.
CE-DS-3-230302: Invalid response header from data server Client gets an invalid response header from the data server. This means that the communication between data server and the client are out of sync, or that the data server runs in an abnormal state. Client process needs to recover. If it does not recover, restart the system.
CE-DS-3-230303: Client timed out on read Client times out on reading from data server. If you see this message again, then the data server has a problem. Keep the system state and contact Cisco Technical Support.
CE-DS-5-230500: remaining time is 0. Calc_remaining_time sees a timeout and returns to 0. If you see this message again, then there is something wrong with the data server. You need to restart the system.
CE-DS-2-231200: SYSFS is not mounted. Detects no SYSFS mounted. Is unable to dump stack trace. Check if the SYSFS is configured. If not, configure SYSFS and restart the system.
CE-DS-2-231201: Failed to set RLIMIT_AS. Fails to set RLIMIT_AS. Contact Cisco Technical Support to report this error.
CE-DS-2-231202: Failed to set RLIMIT_RSS. Fails to set RLIMIT_RSS. Contact Cisco Technical Support to report this error.
CE-DS-3-231300: Failed to send verification msg. Fails to send a message to the verifier through vensock. If you see this message again, restart the system.
CE-DS-3-231301: DS svr failed to set signal handler for SIGPIPE to SIG_IGN. DS server fails to set signal handler for SIGPIPE to SIG_IGN. No action is required.
CE-DS-2-232200: data server malloc errror. Fails in malloc. This probably means that there is a memory problem. Contact Cisco Technical Support.
CE-DS-3-232300: connect error Fails to establish connection. Restart the system.
CE-DS-3-232301: select error Selects return error. No action is required.
CE-DS-3-232302: getsockopt error Getsockopt returns error. No action is required.
CE-DS-3-232303: write error Write returns error. If you frequently see this message, contact Cisco Technical Support.
CE-DS-3-232304: read error Read returns error. If you frequently see this message, contact Cisco Technical Support.
CE-FTP_EXPORT-0/1/2/3/4/5/6-251001 This message class indicates that the native ftp_export code exposes error/notice/information. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-3/5-270000: Proxy failover service failed in ds ops: [failure description] The message indicates that the outgoing proxy service fails in data server operations. If this message occurs occasionally, it can be ignored. Either the service itself retries a few times, or eventually, node manager restarts the service. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-3-270001: Proxy failover service failed in sys calls: [failure descripti on] The message indicates that the outgoing proxy service fails in system calls (for example, select). If this message occurs occasionally, it can be ignored. Node manager restarts the service, and retries the system calls. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270004: System mem low, no buffer for appended req header System memory is low. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-3-270005: ERROR: xact == NULL when calling close_ntlm_conn The transaction record is null. No action is required.
CE-HTTP-2-270006: process_ntlm_type1_msg: malloc error for type1_msg, return Memory allocation error. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270007: process_ntlm_type1_msg: malloc error for host_name, return Memory allocation error. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270008: process_ntlm_type1_msg: malloc error for domain_name, return Memory allocation error. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270009: Unexpected NTLM username length : <number> Unexpected NTLM username length. Check the NTLM username. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270010: process_ntlm_type3_msg: unexpected type-3 message, ntlm_state=<number> Unexpected state in NTLM. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270011: process_ntlm_type3_msg: malloc error for type3_msg Memory allocation error. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270012: process_ntlm_type3_msg: malloc error for type3_msg->domain_name Memory allocation error. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270013: process_ntlm_type3_msg: malloc error for type3_msg->username Memory allocation error. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270014: process_ntlm_type3_msg: malloc error for type3_msg->dc_addr Memory allocation error. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270015: process_ntlm_type3_msg: malloc error for type3_msg->lm_resp Memory allocation error. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270016: process_ntlm_type3_msg: malloc error for type3_msg->nt_resp Memory allocation error. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-3-270017: Recovering from a lost data server connection Cache loses connection to data server. It tries to reconnect. No action is required. The system recovers automatically.
CE-HTTP-3-270018: Retrying connection to data server Cache loses connection to data server. It retries to reconnect. No action is required.. The system recovers automatically. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270019: Retry of connection to data server did not succeed Cache loses connection to data server. It fails to reconnect. Save tech support information. If you frequently see this message, contact Cisco Technical Support.
CE-HTTP-2-270020: Retry of connection to data server did not succeed Cache loses connection to the data server. It fails to reconnect. It is restarted by the node manager. If this occurs frequently, save tech support information and contact Cisco Technical Support.
CE-HTTP-2-270021: Failed to get list after 3 retries Cache fails to get the list from the data server. It opens a new connection to get it. If this occurs frequently, save tech support information and contact Cisco Technical Support.
CE-HTTP-2-270022: Failed to get connect to dataserter after 3 retries Cache fails to get the list from the data server. It exits and gets restarted by nodemanager. If this occurs frequently, save tech support information and contact Cisco Technical Support.
CE-HTTP-2-270023: Failed to get list after 3 retries Cache fails to get the list from the data server. It opens a new connection to get it. If this occurs frequently, save tech support information and contact Cisco Technical Support.
CE-HTTP-7-270024: Rule Sequence not found Rule sequence is not found. No action is required. This is a debug message.
CE-HTTP-7-270025: Rule Item not found in Sequence Rule item is not found in sequence. No action is required. This is a debug message.
CE-HTTP-2-270026: Invalid switch during rule processing Invalid switch at the time of rule processing Collect support information and contact Cisco Technical Support.
CE-HTTP-2-270027: Invalid switch during rule processing Invalid switch at the time of rule processing. Collect support information and contact Cisco Technical Support.
CE-HTTP-5-270028: Informational message about DSCP processing Informational message about Differentiated Services Code Point (DSCP) processing. No action is required.
CE-ICP-6-296001: heal_open_sock(): fail to bound to port <cluster_heal_port> Either fails to bind to the port <cluster_heal_port> or fails to set socket option associated with the port <cluster_heal_port>. If you frequently see this message, contact Cisco Technical Support.
CE-ICP-6-296002: Healing Mode: the corner case happens If two pending requests have almost the same expire time, the IMA Control Protocol (ICP) module tries to attach both the pending requests to the same timer. No action is required.
CE-ICP-6-296003: heal_set_pending_req(): pending_req is NULL The pending request list is possibly empty. No action is required.
CE-ICP-6-296004: heal_init(): init free_index: num_threads = <num_threads>, NUM_THREADS = <NUM_THREADS> Initializes the free index array for all working threads. No action is required.

300000 to 399999

Message Explanation Action
CE-NODEMGR-3-330001: Memconfig: Can not get the config from flash [errno] Memconfig tool fails to get saved configuration from Flash. Try to reload the box. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330002: Memconfig: Can not get the cookie info [errno] Memconfig tool fails to read the cookie. Try to reload the box. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330003: Memconfig: Can not determine platform! Assume it is CE507! Memconfig tool fails to determine the hardware device type. Assume the lowest end platform CE507. Try to reload the box. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330004: Memconfig: Can not open [template] file, [errno] Memconfig tool fails to open the memconfig template file to read . Try to reload the box. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330005: Memconfig: Can not open [memconfig file] for write, [errno] Memconfig tool fails to open the memconfig file to write . Try to reload the box. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330006: External Flash operation completed. In case a reboot is requested when a Flash operation is in progress, reboot is delayed until the Flash operation is completed. This message is to specify that the Flash operation is completed successfully and the device reboots after some time. No action is required.
CE-NODEMGR-5-330007: Flash device is busy, a software image upgrade might be under way, waiting for it to finish. In case a reboot is requested when a Flash operation is in progress, reboot is delayed until the Flash operation is completed. No action is required. Wait for the Flash device to be free.
CE-NODEMGR-2-330008: Wait flash device timeout. Forcing a reboot now... In case a reboot is requested when a Flash operation is in progress, reboot is delayed until the Flash operation is completed. This message implies that the Flash device is not free after 15 minutes. The box reboots . No action is required. The box needs to reboot soon.
CE-NODEMGR-0-330009: Nodemgr Exiting. This message can be generated by a large set of unrecoverable error conditions. This message needs to be preceded by a more specific error message. Reboot box to recover. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330010: system call '[system call]' failed, ret: [return code] errno: [error no] at [filename:lineno] A system call made by node manager is unsuccessful. A more specific error message needs to precede this message. Refer to the action of the preceding more specific error message.
CE-NODEMGR-0-330011: Rebooting the box because of fatal system error. A system call made by node manager is unsuccessful. The only way for recovery is through a reboot. This message needs to be preceded by a system call failed message. No action is required. The box reboots after a short period of time.
CE-NODEMGR-0-330012: Could not fork process while attempting to reload: [errno]. Forking off a process is unsuccessful at the time of an attempted reload. Box needs to reboot. Power down the system if the box fails to reboot. Attempt a reload again after powerup. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330013: Child failed to reload successfully. The child process forked to invoke reload is unsuccessful. Box needs to reboot. Power down the system if the box fails to reboot. Attempt a reload again after powerup. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-0-330014: Hard reboot the box now due to timeout. As a safety net, if everything else fails, the system hangs on a reboot request. This message is printed by an alarm handler which reboots the device. No action is required. Box needs to reboot. Power down if all else fails. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330015: DEVICE WILL BE REBOOTED SOON. A reboot is requested. The box reboots soon. No action is required.
CE-NODEMGR-0-330016: Rebooting the box because of unrecoverable error. An unrecoverable system error occurs . This message needs to be preceded by a more specific message about the system error. The device reboots itself. No action is required.
CE-NODEMGR-3-330017: open failed("/dev/null", O_RDONLY) returned [retcode], errno = [errno] An attempt to open the null device for reading fails . This signifies a more general system level failure. This message needs to be accompanied by other messages that explain more about the failure. The system is in an unstable condition. If it fails to reboot itself, power cycle it. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330018: open [filename] failed: [errno] The node manager fails to open a file for logging a service's messages. No action is required, the messages are not logged. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330019: dup failed: [errno] The node manager fails to duplicate a file descriptor to redirect the messages from application/service to log file. No action is required. The messages are not logged. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-4-330020: chmod for [directory] failed: [error] [errno] Node manager fails to change access permissions on the core dump directory while starting an application/service. No action is required. If the application causes a core dump, it is possibly not logged.
CE-NODEMGR-4-330021: chdir to [directory] failed: [errno] Node manager fails to change directory attributes. No action is required. The core dump size is probably not limited. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330022: setrlimit for RLIMIT_CORE failed: [errno] Node manager fails to set the core dump limit. No action is required. The code dump size is probably not limited. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330023: exited pid [process id] not my direct child A process terminates. However, it is not directly spawned by the node manager. No action is required.
CE-NODEMGR-5-330024: Service [program name] exited normally with code [status] The specified service exits as expected. No action is required.
CE-NODEMGR-3-330025: Service [program name] died due to signal [signal no]:[signal name] The specified service started by nodemanager dies unexpectedly due to the specified signal. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330026: Service [program name] died abnormally with status [status no] The specified service started by node manager dies due to some abnormal condition. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330027: pid [process id] exits A process exits . No action is required.
CE-NODEMGR-5-330028: healthprobe pid [process id] exits A health probe process exits . No action is required.
CE-NODEMGR-3-330029: Someone is trying to kill with pid of [process id]. This message is printed if a kill attempt is made with a zero or non-negative process id. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330030: Process [process id] killed with SIGTERM does not return within [millisecond] ms, trying to use SIGKILL. The node manager attempts to terminate a process using SIGTERM. However, the process does not return in the specified time. The process is killed using SIGKILL. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330031: Can not kill process with pid: [process id] An unsuccessful attempt is made by the node manager to kill the specified process using SIGKILL. If a service is affected, try to disable and enable the service. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330032: Stopping service: [service name]. The node manager stops the specified service. No action is required.
CE-NODEMGR-5-330033: Service [service name] is already stopped. An attempt is made to stop a service which is already stopped. No action is required.
CE-NODEMGR-0-330034: fork failed while stopping service [service name]. The node manager fails to fork a child process while it attempts to stop a service. No action is required. The box reboots.
CE-NODEMGR-3-330035: Service [service name] can not be successfully stopped. The node manager is unable to stop the specified service. No action is required. The box reboots.
CE-NODEMGR-5-330036: Stop service [service name] using: [command] with pid: [process id] This message is notification from the node manager that the specified service is being stopped. No action is required.
CE-NODEMGR-3-330037: execve error while trying to stop service: [error]. The node manager fails to execute the stop command to stop a service. No action is required. The node manager directly tries to kill the process.
CE-NODEMGR-3-330038: Start service fork failed: [error]. The node manager fails to fork a process to start a service. No action is required. An attempt is made again to start the service after a period of time.
CE-NODEMGR-3-330039: Service [service] has not returned within [sec] seconds. Will try stopping it. The node manager starts a service. However, it does not respond for the specified seconds. It probably waits on some resource. No action is required. The node manager stops the process and tries to restart later.
CE-NODEMGR-3-330040: Started service [service] using: [cmd] with pid: [pid] The node manager starts the specified service. No action is required.
CE-NODEMGR-3-330041: Start Service execve error: [error] The node manager tries to start a service. However, the execve command fails . A restart is attempted. No action is required.
CE-NODEMGR-3-330042: Service start program [program] does not exist? err: [errorno] While checking a services support binaries, the node manager fails to find a specific binary to start a service. The installation of software can be incomplete/corrupt. Try to reinstall by issuing the copy ftp install or other installation commands.
CE-NODEMGR-3-330043: Service stop program [program] does not exist? err: [errorno] While checking services support binaries, the node manager fails to find a specific binary to stop a service. The installation of software can be incomplete/corrupt. Try to reinstall by issuing the copy ftp install or other installation commands.
CE-NODEMGR-3-330044: Service health_probe program [program] does not exist? err: [errno] While checking services support binaries, the node manager fails to find a specific binary to stop a service. The installation of software can be incomplete/corrupt. Try to reinstall by issuing the copy ftp install or other installation commands.
CE-NODEMGR-0-330045: Rebooting the box because service [service] is dead A critical service dies . The only way to recover is by rebooting the box. No action is required. The box needs to reboot shortly. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330046: Stopping the service [service] because it is restarting too often. The specified service is restarted by node manager more often than required. Contact Cisco Technical Support.
CE-NODEMGR-3-330047: Rebooting the box because service [service] keeps restarting The node manager restarts the specified service more often than required. The recommended way out of this problem is to reboot the box. No action is required. The box reboots automatically. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330048: DEBUG: respawn_count = [count], period: [secs] The node manager has to restart a process. This is the count-th restart of the process. The process is restarted within secs number of seconds. No action is required. Node manager probably restarts certain processes. However, if a process restarts very often, contact Cisco Technical Support.
CE-NODEMGR-3-330049: Service [service] is dead, do nothing according to the config. The specified service becomes inoperational. According to specifications, it should not be restarted. No action is required.
CE-NODEMGR-3-330050: Fork for health_probe failed: [error] The node manager fails to fork to run a health probe. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330051: Start health_probe for service [service] using: [cmd] with pid: [pid] The node manager starts a heath probe service. No action is required.
CE-NODEMGR-3-330052: health probe execve error: [error] The node manager fails to execute in order to run a health probe. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330053: Health_probe for service [service] timed out. The health probe for the specified service times out. No action is required. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330054: DEBUG: service health probe took [sec] seconds to return The health probe started by node manager is completed in [sec] seconds. No action is required.
CE-NODEMGR-3-330055: Health probe for service [service] failed, ret code: [error]. The health probe for the specified service fails . The node manager stops and restarts the service if needed. No action is required. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330056: Health probe exit with a signal [signal] A health probe started by the node manager exits with a specified signal. The node manager stops the service and restarts it if needed. No action is required. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330057: Health_probe for service [service] died abnormally with status [error] A health probe started by the node manager exits in an abnormal fashion. The node manager stops the service and restarts it if needed. No action is required. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-7-330058: nodemgr: entering start_loop The node manager starts to run its main code loop. No action is required.
CE-NODEMGR-5-330059: " Switching to run level [runlevel no] The node manager switches its run level. It starts services based on the new run level. No action is required.
CE-NODEMGR-3-330060: waitpid returns error: [error no]. The node manager is interrupted by an error when it waits in waitpid. No action is required. It is normal to see this message during a reboot.
CE-NODEMGR-3-330061: no child alive. The node manager waits in waitpid. It is awakened because there are no children of the node manager left alive. No action is required.
CE-NODEMGR-7-330062: loop_counter = [count], child_pid = [pid] This is the debug message printed by the node manager. It provides useful information mainly for development purposes. No action is required.
CE-NODEMGR-3-330063: Putenv error adding new path [path] The node manager fails to set the path environment variable. The node manager is unable to start services properly. A reboot fixes the problem. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-1-330064: [frame]: [function name]([arg1], [arg2], [arg3], [arg4], .... The node manager receives a critical signal and quits. The information printed is backtrace of the calls made by the node manager. Node manager needs to restart automatically. The box probably runs in an unstable mode. Cisco recommends a reboot .
CE-NODEMGR-1-330065: nodemgr: signal [signal no] received The node manager receives a critical signal. A backtrace needs to follow this message. The node manager most likely exits. Node manager needs to restart automatically. The box probably runs in an unstable mode. Cisco recommends a reboot.
CE-NODEMGR-3-330066: Failed to open [error], ret : [ret code], errno: [error no] The node manager fails to open the specified file. The node manager is possibly not able to get information about local disks and services can be affected. System is probably in an unstable condition. Cisco recommends a reboot .
CE-NODEMGR-3-330067: Too many local disks The node manager finds too many disks attached to the system. You probably use an unsupported configuration. Disconnect any unsupported drives and then reboot.
CE-NODEMGR-5-330068: personality_allows_service called for [service] The personality_allows_service is called for the specified service. No action is required.
CE-NODEMGR-5-330069: Device personality: [device personality], Service personality = [service personality] The device personality and the service personality are printed for debugging purposes. No action is required.
CE-NODEMGR-4-330070: nodemgr:touch_service_enabled_flag_file: could create /tmp/service_enabled ([service]) The node manager fails to create a flag file for the specified service. This can be a transient problem. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-4-330071: nodemgr:touch_service_enabled_flag_file: could not open [filename] ([error]) The node manager fails to open a flag file for the specified service. This can be a transient problem. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-4-330072: nodemgr:delete_service_enabled_flag_file: could not unlink [filename] ([error]) The node manager fails to delete the flag file for the specified service. This can be a transient problem. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-0-330073: execl /sbin/mingetty failed: ret [return code], errno: [errno] The mingetty process is not started for debugging. Internal debugging message. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-5-330074: No personality found, setting default personal\ ity: CE. The node manager fails to determine the device type: CE, Content Router (CR), or CDM. CE is assumed. Contact Cisco Technical Support.
CE-NODEMGR-5-330075: Reboot requested by CLI. Reboot is requested using the reload CLI command. No action is required.
CE-NODEMGR-3-330076: Reboot requested by [reboot source]. Reboot is requested by the specified source. No action is required.
CE-NODEMGR-5-330077: Reload config requested by [source]. A request is made by the specified source to reload the node manager configuration file. Contact Cisco Technical Support.
CE-NODEMGR-5-330078: " Stop all servies (except mingetty) requested by [source]. A request is made by the specified source to the node manager to stop all services. No action is required.
CE-NODEMGR-5-330079: Shutdown requested by [source]. The specified source requests the box to be shutdown. No action is required.
CE-NODEMGR-5-330080: [source] requests start service [service] The specified source requests the node manager to start the specified service. No action is required.
CE-NODEMGR-5-330081: [source] requests start service [service] which is already enabled. The specified source requests the node manager to start the specified service. However, the service already runs . No action is required.
CE-NODEMGR-5-330082: [source] requests stop service [service]. The specified source requests the node manager to stop the service. No action is required.
CE-NODEMGR-5-330083: [source] requests stop service [service] which is already disabled. The specified source requests the node manager to stop the specified service. However, the service is already disabled. No action is required.
CE-NODEMGR-5-330084: [source] requests restart service [service]. The specified source requests the node manager to restart the specified service. No action is required.
CE-NODEMGR-5-330085: [source] requests forcestart service [service] The specified source requests the node manager to start the specified service irrespective of the device mode. No action is required.
CE-NODEMGR-5-330086: [source] requests forcestart service [service] which is already enabled. The specified source requests a force restart of the specified service. However, the service is already enabled. No action is required.
CE-NODEMGR-3-330087: Error in read the req, errno: [error] The node manager server fails to read a request. The requesting application needs to print out a separate error which specifies the action to be carried out.
CE-NODEMGR-3-330088: Failed to set NONBLOCK for new_fd, ret [status], errno [error code] The node manager fails to set the NONBLOCK attribute for a new file descriptor. The corresponding request is not processed by the node manager. The requesting application needs to print out a separate error. This specifies the action to be carried out.
CE-NODEMGR-3-330089: Check request, select: ret = [status], errno = [error] Select call fails while checking a request in the node manager server. The request is not processed. The requesting application needs to print out a separate error. This specifies the action to be carried out.
CE-NODEMGR-0-330090: Memory allocation of [size] bytes failed! Rebooting the box. The node manager fails to allocate memory. The box is probably in an unstable state. No action is required. The box reboots itself.
CE-NODEMGR-5-330091: ERROR: Not enough timer allocated, should never happen The node manager runs out of timer resources. The device is probably under heavy load. Additional memory is allocated for the timer. Reduce the load on the box. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330092: Program error, cancel NULL timer A call is made to cancel a timer which does not exist. No action is required. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330093: Program error, cancel failed The node manager is called to cancel a timer. However, the timer is not found in the node manager's internal structures. Possible memory corruption. Reboot the box. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330094: killtilldead: iteration count reached 60, bailing out (trying to kill [process] ...) The node manager is unable to successfully disable the specified process. The process can still run and possibly interfere with normal device operations. Reboot the box. If you frequently see this message, contact Cisco Technical Support.
CE-NODEMGR-3-330095: parse_get_str: Can not allocate more memory! The node manager fails to allocate memory while it parses its configuration file. Do not reboot the box. Contact Cisco Technical Support.
CE-NODEMGR-0-330096: REBOOT BOX NOW FROM WITHIN nodemgr_clt!!! A reload request is made to the node manager client. The box reboots itself. No action is required.
CE-NODEMGR-6-330097: Create codecoverage directory [dir path] This message is information only to indicate that the codecoverage directory is created for a process. This needs to be seen only when running an instrumented image. No action is required.
CE-NODEMGR-6-330098: Error create codecoverage directory [dir path] This message is to indicate that the codecoverage directory is not created successfully for a process. This needs to be seen only for an instrumented image. If this happens, the process does not work properly. Contact the codecoverage change owner to investigate the problem.
CE-NTP-0/1/2/3/4/5/6-340000: [failure-description] This message class indicates that the native Linux Network Time Protocol (NTP) code exposes error/notice/information. If error messages occur, check the NTP configuration or device configuration. If you frequently see this message, contact Cisco Technical Support.
CE-NTP-5-340001: [host-ip/name]: not a valid host address The message indicates that an invalid NTP server host address is specified. Retry with the correct NTP server host address.
CE-NTP-5-340002: Maximum NTP servers reached. The message indicates that the maximum NTP server limit is reached. Do not configure more NTP servers than the maximum limit.
CE-NTP-5-340003: Must configure NTP servers before enabling NTP service. The message indicates that no NTP server is configured. NTP service is not enabled. Configure at least one NTP server before you enable NTP service.
CE-NTP-3-340004: failed to open ntp [drift|config] file: [file-name] The message indicates that NTP service fails to open ntp driftfile or configfile. Check the NTP configuration and device status. If you frequently see this message, contact Cisco Technical Support.
CE-NTP-3-340005: nodemgr failed to start/stop ntpd The message indicates that the NTP command fails because nodemgr fails to start/stop ntpd. Check device status. Reload the device and reinstall sysimg. If you frequently see this message, contact Cisco Technical Support.
CE-NTP-3-340006: failed to retrieve configuration from data-server, error=[err_code] The message indicates that the NTP command fails because the NTP binary fails to retrieve the configuration from the data-server. Check the device status and reload the device. If you frequently see this message, contact Cisco Technical Support.
CE-NTP-7-340007: [NTP debugging message] The message provides NTP debugging information. No action is required.
CE-PAM-3-345000: Wrong authentication method to get authentication debugging The message indicates that the wrong authentication method is selected for debugging If error message occurs, reconfigure authentication method parameters, and check the condition of the disks. Set debug option again by issuing the debug authentication command. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345001: Can't open file (TACACS+) The message indicates that the system fails to open the etc/pam.d/ce_http_tacacs_config configuration file for request authentication through TACACS+ protocol. The parameters of authentication are not saved. If an error message occurs, check the TACACS+ protocol configuration and the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345002: Can't open file (RADIUS) The message indicates that the system fails to open the etc/pam.d/ce_http_radius_config configuration file for request authentication through RADIUS protocol. The parameters of authentication are not saved. If an error message occurs, check the RADIUS protocol configuration and the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345003: Can't open file (NTLM) The message indicates that the system fails to open the etc/pam.d/ce_http_ntlm_config configuration file for request authentication through NTLM protocol. The parameters of authentication are not saved. If error message occurs, check NTLM protocol configuration and the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345004: Can't open file (LDAP) The message indicates that the system fails to open the etc/pam.d/ce_http_ldap_config configuration file for request authentication through LDAP protocol. The parameters of authentication are not saved. If error message occurs, check LDAP protocol configuration and the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345005: Wrong option to set authentication debugging The message indicates that the wrong authentication method is set for debugging. If an error message occurs, reconfigure authentication method parameters, and check the condition of the disks. Set debug option again by issuing the debug authentication command. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345006: can't open /tmp/user_authenticate_debug file to set debugging information The message indicates that the system fails to open the tmp/user_authenticate_debug configuration file to set debugging information. If an error message occurs, check the condition of the disks. Set debug option again by issuing the debug authentication command. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345007: can't open /tmp/request_authenticate_debug file to set debugging in formation The message indicates that the system fails to open the tmp/request_authenticate_debug configuration file to set debugging information. If an error message occurs, check the condition of the disks. Set debug option again by issuing the debug authentication command. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-2-345008: Can not create directory for pam module <reason> The message indicates that the system does not have the tmp directory configured. If an error message occurs, the system has the serious software image set up or configuration problems. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345009: Can't open /etc/pam.d/content_engine_config file The message indicates that the system fails to open the etc/pam.d/content_engine_config configuration file for a user's authentication. The parameters of authentication are not saved. If an error message occurs, check the user's authentication configuration and the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-2-345010: Can not create log directory for pam module The message indicates that the system does not have the tmp directory configured. If an error message occurs, check the user's authentication configuration and the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345011: can't open /tmp/user_authenticate_stats file The message indicates that the system fails to open the /tmp/user_authenticate_stats authentication statistical file to reset the statistics. The statistical information of authentication is not cleared. If an error message occurs, check the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345012: can't open /tmp/user_authenticate_stats file to report statistics The message indicates that the system fails to open authentication statistical file /tmp/user_authenticate_stats to update statistics. The statistical information of authentication is lost. If an error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-2-345013: Failed to lock authentication statistical file The message indicates that the system fails to set software lock for request authentication statistical file to reset statistics. The statistical information of request authentication is not cleared. If an error message occurs, check the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-2-345014: Can not create log directory for pam module The message indicates that the system does not have the tmp directory configured. If error message occurs, the system has the serious software image set up or configuration problems. Contact Cisco Technical Support.
CE-PAM-3-345015: can't open /tmp/user_ldap_stats file The message indicates that the system fails to open the /tmp/user_ldap_stats LDAP authentication statistical file to reset statistics. The statistical information of LDAP authentication is not cleared. If error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345016: can't open /tmp/user_radius_stats file The message indicates that the system fails to open RADIUS authentication statistical file /tmp/user_radius_stats to reset statistics. The statistical information of RADIUS authentication is not cleared. If error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345017: can't open /tmp/user_tacacs_stats file The message indicates that the system fails to open the /tmp/user_tacacs_stats TACACS+ authentication statistical file to reset statistics. The statistical information of TACACS+ authentication is not cleared. If error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345018: can't open /tmp/user_ntlm_stats file The message indicates that the system fails to open the /tmp/user_ntlm_stats NTLM authentication statistical file to reset statistics. The statistical information of NTLM authentication is not cleared. If error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345019: Failed to write authentication statistical file The message indicates that the system fails to write the authentication statistical file to reset statistics. The statistical information of authentication method is not cleared. If an error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345020: Failed to close authentication statistical file after writing The message indicates that the system fails to close the authentication statistical file after statistics are cleared. If an error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345021: Failed to lock authentication statistical file The message indicates that the system fails to lock the authentication statistical file after statistics are cleared. If an error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-2-345022: Failed to lock authentication statistical file The message indicates that the system fails to lock the authentication statistical file to display statistics. If error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345023: Unknown authentication method The message indicates that the wrong authentication method is selected. If an error message occurs, reconfigure authentication method parameters and check the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345024: Filed to open statistical file for authentication The message indicates that the system fails to open the authentication statistical file. An authentication method's statistics are not displayed. If an error message occurs, check the authentication method's configuration and the condition of the disks. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345025: Statistical file is corrupted The message indicates that the authentication statistical file has incorrect or corrupted information. If an error message occurs, check the authentication method's configuration and the condition of the disks. Clear the authentication statistical information, and redisplay it. If the statistical file is corrupted again, contact Cisco Technical Support. Otherwise, continue to authenticate the users.
CE-PAM-3-345026: Failed to close authentication statistical file after reading The message indicates that the system fails to close the authentication statistical file after statistics are displayed. If error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345027: A field of Statistical file is corrupted The message indicates that the authentication statistical file has incorrect or corrupted information in one of the fields. If an error message occurs, check the authentication method's configuration and the condition of the disks. Clear the authentication statistical information, and redisplay it. If the statistical file is corrupted again, contact Cisco Technical Support. Otherwise, continue to authenticate the users.
CE-PAM-3-345028: Failed to read authentication statistical file The message indicates that the system fails to read the authentication statistical file to display statistics. If an error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345029: tmp directory doesn't exist The message indicates that the system does not have the tmp directory configured. If an error message occurs, the system has the serious software image set up or configuration problems. If you frequently see this message, contact Cisco Technical Support.
CE-PAM-3-345030: Failed to lock authentication statistical file The message indicates that the system fails to lock the authentication statistical file to display statistics. If error message occurs, check the condition of the disks and if the system's /tmp directory exists. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350000: sysdb_bind failed: <str> Parser server fails to establish a connection with the data server, which contains configuration registry. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350001: Bad arguments to parser_malloc Parser attempts to allocate zero size memory. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350002: Bad pointer to parser_free Parser gets null memory pointer to be freed. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350003: parser_free before parser_malloc called Parser attempts to free the memory that is never allocated. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350004: Bad magic in parser free 1 Unexpected magic number is detected in the memory block. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350005: Bad magic in parser free 2 Unexpected magic number is detected in the memory block. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350006: sysdb_item_set of uint32 <str><dc><str> Fails to set an item in the data server. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350007: wrong sysdb datatype at <str>, <dc>, expect <dc> Does not receive expected PACKED type data from the data server. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350008: sysdb_directory_get_last: '<error>' sysdb_directory_get_last() fails. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350009: sysdb_item_set of packed <str> : <str> Error occurs while retrieving data from the data server. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350010: sysdb_iterator_create: <str> Error occurs while setting an option in the data server. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350011: sysdb_iterator_next_data() failed <str> Error occurs in a data server operation. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350012: sysdb_iterator_free: <str> Error occurs in a data server operation. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350013: <str> Coption Not Present:<str>, <str>, Expected coptions are not present. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350014: <str>: new_cmd buffer null <function name> Expected coptions are not present. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350015: <str> No endcoption mark for <hex>: <str> No endcoption mark is found. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350016: <str> Incomplete endcoption mark for <hex>: <str> Incomplete endcoption mark is found. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350017: <str>: invalid input (no 'B'): '<str>' Invalid coption is found. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350018: <str>: bgcoption missing ',' after id: '<str>' The bgcoption is missing. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350019: <str>: bgcoption missing ',' after type: '<str>' The bgcoption is missing. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350020: <str>: bgcoption missing ',' after path count: '<str>' The bgcoption is missing. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350021: <str>:no nxcoption:'<str>' An expected nxcoption is missing. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350022: <str>: incorrect nested coption:'<str>' Incorrect nested ctoption is found. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350023: <str>: invalid NXCOPTION mark:'<str>' Incorrect NXCOPTION mark is found. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350024: <str>: missing '=' in sysdb string <str> for command '<str>' Missing = in sysdb string. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350025: <str>: Possible loop detected in command '<str>' Loop is detected in the command. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350026: <str>: missing equal '<' in sysdb string '<str>' for command '<str>' Missing equal in sysdb string found. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350027: <str>: Unknown object type <dec> in nvgen_command Unknown object type is found. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350028: <str>: Unknown object type <dec> in replace_type Unknown object type is found. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350029: Invalid object format '<str>' Invalid object type is found. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350030: <str>: debug registration failed: <dc> The debug registration fails. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350031: sysdb_bind: <str> Error occurs while establishing the connection with the data server. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350033: Shell failed to write msg to parser server. Shell fails to write a message to the parser server. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350034: parser_server reconnect succeeded Shell process is able to reconnect to the parser server. No action is required.
CE-PARSER-2-350035: parser_server reconnect failed. Shell fails to connect to the parser server. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PARSER-3-350036: Endoption doesn't match! <dec> This is a syntax error. The endoption does not match. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PRELD-2-362001: Preload CLI sysdb bind error Fails to bind to the system wide configuration database. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PRELD-2-362002: Preload notification registration failed Notification registration for the preload proxy module fails . Reload. If you frequently see this message, contact Cisco Technical Support.
CE-PRELD-2-362003: Preload select returned less than zero The select call on preload socket descriptors fails . No action is required. If you frequently see this message, contact Cisco Technical Support.
CE-PRELD-3-363001: preload_threads_invoke(): Unable to start preload thread-[<thread_index>] Fails to create the preload thread for the concurrent session with identity <thread_index>. If you frequently see this message, contact Cisco Technical Support.
CE-PRELD-3-363002: preload_threads_invoke(): Unable to join preload thread-[<thread_index>] Fails to join the preload for the concurrent session with identity <thread_index>. If you frequently see this message, contact Cisco Technical Support.
CE-PRELD-3-363003: [preload] mms stream files won't be preloaded as wmt is not enabled. WMT is not enabled. The mms stream files are not preloaded. Enable WMT. If you frequently see this message, contact Cisco Technical Support.
CE-PRELD-3-363004: Error setting preload dscp: <item>, ret=<error_no:> The DSCP setting for dscp for <item> HTTP or WMT fails with the <error_no> error. If you frequently see this message, contact Cisco Technical Support.
CE-PRELD-5-365001: preload: error <error_no> in bind to sysdb Preload fails to bind to sysdb and returns the <error_no> error. If you frequently see this message, contact Cisco Technical Support.
CE-PRELD-5-365002: <meta_info> Preload meta information. No action is required.

400000 to 499999

Message Explanation Action
CE-RTSP-3-403000: [Procedure] System call error: <system call name> <err msg> System call fails . System is probably in a weird state. Try to reenable the service that causes the error. If you frequently see this message, contact Cisco Technical Support. .
CE-RTSP-3-403001: [Procedure] RTSP [service] user license agreement not accepted <mesg> RTSP Proxy/ Subscriber user license agreement is not accepted. Accept the license agreement and retry to enable RTSP services.
CE-RTSP-3-403002: [Procedure] Could not set Real [service] Logpath variable in temp file <mesg> Fails to set the Real [service] Logpath variable in the temp file. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-3-403003: [Procedure] Failed to move temp file with accesslog path variable to Real Proxy configuration file <error_message> Fails to move the temp file to the configuration file. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-3-403004: [Procedure] External/Fast Ethernet/Gigabit Ethernet IP not configured. Using the local host IP External/Fast Ethernet/Gigabit Ethernet IP is not available. Configure External/Fast Ethernet/Gigabit Ethernet IP and retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-3-403005: [Procedure] Failed to disable Real [service] evaluation. on entering valid license key Fails to disable Real Proxy/Subsciber evaluation. on entering valid license key. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-3-403006: [Procedure] Failed to start/stop Real Subscriber <error_mesg> Fails to start/stop Real Subscriber. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-3-403007: [Procedure] Failed to disable Real [service] <error_mesg> Fails to disable Real Proxy/Subsciber. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-3-403008: [Procedure] Failed to enable Real [service] evaluation <error_msg> Fails to enable Real Proxy/Subscriber. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-3-403009: [Procedure] Failed to create symbolic link for Real Subscriber VOD <error_mesg> Fails to create symbolic link for Real Subscriber video on demand (VOD). Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-3-403010: [Procedure] Failed to set Real Subscriber default/maximum archive file size Fails to set Real Subscriber default/maximum archive file size. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-3-403011: [Procedure] Failed to get Real [service] Configuration <error_mesg> Fails to get Real Proxy/Subscriber configuration. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-RTSP-6-406001: [Procedure] Disabled Real [service] evaluation on entering valid license key Disables Real Proxy/Subscriber evaluation. No action is required.
CE-RTSP-6-406002: [Procedure] Maximum file size for Real Subscriber archieving <size> Real Subscriber file size information. No action is required.
CE-RTSP-6-406003: [Procedure] Started/Stopped the Real Subscriber Starts /stops the Real Subscriber. No action is required.
CE-RTSP-6-406004: [Procedure] Enabled Real [service] evaluation Enables Real Proxy/Subscriber evaluation. No action is required.
CE-RTSP-6-406005: [Procedure] [Interface type] IP not available using Interface type] IP External/Fast Ethernet/Gigabit Ethernet IP is not available. No action is required.
CE-RTSP-7-406005: [Real Subscriber CLI Bin Debug Msg] Debug message. No action is required.
CE-RTSPG-2-408200: [Procedure] - RTSP Gateway error log init failed <error_mesg> RTSP gateway error log initialization fails. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-RTSPG-2-408201: [Procedure] - Failed to generate RTSP Gateway error log config file <mesg> Fails to generate RTSP gateway error log configuration file when the debug level is changed. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-RTSPG-2-408202: [Procedure] - Memory allocation failed during errorlog initialization for RTSP Gateway Memory allocation failure. Attempts to allocate zero size memory. Reload. If you frequently see this message, contact Cisco Technical Support.
CE-RTSPG-2-408203: [Procedure] - Failed to create/open RTSP Gateway errorlog client configuration file: <file_path> Fails to create/open RTSP Gateway configuration file. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-RTSPG-2-408204: [Procedure] - Failed to initialize debug library for RTSP Gateway Fails to initialize debug library. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-RTSPG-2-408205: [Procedure] - Interface IP address not configured RTSPG fails to start. It requires an interface IP address. RTSPG sleeps 15 seconds and exits. Configure interface IP address.
CE-RTSPG-3-408300: [Procedure] - Failed to set item <mesg> Fails to set item in the data server. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-RTSPG-3-408301: [Procedure] - Unable to signal self to get errlog config <mesg> Unable to send signal to itself to get configuration. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-2-412001: <procedure>: invalid switch Encounters an invalid pattern or action type. Check rule configuration. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-2-412002: <procedure>: rule is NULL The argument rule passes a NULL pointer. Check rule configuration. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-2-412003: rule_del(): <parameter> entry not found Tries to remove a parameter that is not configured. Issue the show rule all command to check for configured parameters.
CE-RULES-2-412004: default switch in <procedure> Encounters an invalid pattern type. Check rule configuration. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-2-412005: <procedure> error: invalid else Pattern type is neither SRC_IP or DST_IP. Check rule configuration. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-2-412006: error allocating new pattern table System fails to allocate memory for the new pattern table. Contact Cisco Technical Support.
CE-RULES-2-412007: Error allocating new action table System fails to allocate memory for the new action table. Contact Cisco Technical Support.
CE-RULES-2-412008: error allocating new Rule table System fails to allocate memory for the new rule table. Contact Cisco Technical Support.
CE-RULES-2-412009: rule_of_port_sort() error: NULLP The argument passes a NULL pointer for sorting. Check rule configuration for configured destination ports. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-2-412010: Rule:pattern_match_request: failed to alloc memory System fails to allocate memory for the new pattern list. Contact Cisco Technical Support.
CE-RULES-2-412011: rule_show_stat(); Internal error Rule statistics entry is NULL. Check rule configuration. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-3-413001: <procedure>: Can't create new list System fails to allocate memory for new list. Contact Cisco Technical Support.
CE-RULES-3-413002: rule_add_port(): new_list_head is NULL System fails to allocate memory for new port list. Contact Cisco Technical Support.
CE-RULES-3-413003: rule_add_port(): cur_list NULL System fails to allocate memory for new port list. Contact Cisco Technical Support.
CE-RULES-3-413004: rule_create_port_list(): failed to malloc new_list_head System fails to allocate memory for new port list. Contact Cisco Technical Support.
CE-RULES-3-413005: rule_create_ip_list() new_list is NULL System fails to allocate memory for new IP list. Contact Cisco Technical Support.
CE-RULES-3-413006: rule_del_ip(): error creating new list System fails to allocate memory for new IP list. Contact Cisco Technical Support.
CE-RULES-3-413007: rule_add_regex(): failed to create new list System fails to allocate memory for new regex list. Contact Cisco Technical Support.
CE-RULES-3-413008: rule_create_regex_list(): memory allocation failed System fails to allocate memory for new regex list. Contact Cisco Technical Support.
CE-RULES-3-413009: rule_create_regex_list() can't allocate regex System fails to allocate memory for new regex list. Contact Cisco Technical Support.
CE-RULES-3-413010: rule_del_regex(): failed to create new list System fails to allocate memory for new regex list. Contact Cisco Technical Support.
CE-RULES-3-413011: ctype is null The ctype member in the response header can have a null value. No action is required. The system sometimes purposely checks for this NULL value.
CE-RULES-3-413012: error allocation new action table System fails to allocate memory for new action table. Contact Cisco Technical Support.
CE-RULES-3-413013: Malloc for action_sel failed System fails to allocate memory. Contact Cisco Technical Support.
CE-RULES-3-413014: rule_process_verif_msg(): <filename> <line_no> <ds_get_verification_info call failed> errno = <error_no> The ds_get_verification_info call fails with error number <error_no> in file <filename> line <line_no>. Contact Cisco Technical Support.
CE-RULES-3-413015: register_verifier(): <filename> <line_no> <register_verifier failed for item> <item> The register_verifier call fails for item <item> in file <filename> line <line_no>. Contact Cisco Technical Support.
CE-RULES-3-413016: rule_server_main(): ERROR request processing timed out Request times out. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-3-413017: rule_server_rpc_main(): RpcUdsServer_new() returned NULL server Launching of new rule_server possibly fails . Reload the CE. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-3-413018: rules_daemon : RpcUdsServer_accept returned a NULL client The RpcUdsServer_accept returns a NULL client. No action is required. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-3-413019: rules_daemon() client_thread_create failed err = <error_no> Creation of new client thread fails with error number <error_no>. No action is required. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-5-415001: Ignoring invalid URL rewrite original URL=<old_url> new URL=<new_url> Ignores invalid URL rewrite. No action is required.
CE-RULES-5-415002: Ignoring invalid URL transformation URL=<old_url> new URL=<new_url> Ignores invalid URL transformation. No action is required.
CE-RULES-5-415003: rule_show_stat(); Error opening tty Fails to open the terminal for writing rules statistics. No action is required.
CE-RULES-6-416001: rule_del_port(): old_list is NULL The old port list is probably empty. No action is required.
CE-RULES-6-416002: send_verif_ack(): error building ack, error = <error_no> Error in building the acknowledgement message. No action is required.
CE-RULES-6-416003: rule_process_verif_msg(): unknown event = <sysdb_info.event> Unknown event is encountered while receiving rule process verification message. No action is required.
CE-RULES-6-416004: rule_process_notif_msg(): <file_name> <line_no> <ds_get_notification_info call failed> errno = <error_no> Error <error_no> occurs in file <file_name> in line <line_no> while receiving Rule process notification message. No action is required.
CE-RULES-6-416005: rule_process_notif_msg(): <file_name> <line_no> ds_free_ven_resource failed Error occurs in file <file_name> line <line_no> when the data server tries to free the resource. No action is required.
CE-RULES-6-416006: Failed to get the full message from the ds Rule process fails to receive the complete message from the data server. No action is required.
CE-RULES-6-416007: rule_register_notifier(): <file_name> <line_no> <rule_register_notifier failed for item> <rule_action_notif_tuple> Err <error_no> Error <error_no> occurs in file <file_name> in line <line_no> for item <rule_action_notif_tuple> when the rule process registers notification. No action is required.
CE-RULES-6-416008: rule_register_notifier(): <file_name> <line_no> <rule_register_notifier failed for item> <rule_pattern_notif_tuple> Error occurs in file <file_name> in line <line_no> for item <rule_pattern_notif_tuple> when the rule process registers notification. No action is required.
CE-RULES-6-416009: rule_register_notifier(): <file_name> <line_no> <rule_register_notifier failed for item> <rule_pattern_delta_tuple> Error occurs in file <file_name> in line <line_no> for item <rule_pattern_delta_tuple> when the rule process registers notification. No action is required.
CE-RULES-6-416010: rule_register_notifier(): <file_name> <line_no> <rule_register_notifier failed for item> <rule_debug_notif_tuple> Error occurs in file <file_name> in line <line_no> for item <rule_debug_notif_tuple> when the rule process registers notification. No action is required.
CE-RULES-6-416011: rule_register_notifier(): <file_name> <line_no> <rule_register_notifier failed for item> <rule_action_delta_tuple> Error occurs in file <file_name> in line <line_no> for item <rule_action_delta_tuple> when the rule process registers notification. No action is required.
CE-RULES-6-416012: Rule Item Not found in the Sequence Rule item is not found in the fetched sequence. No action is required.
CE-RULES-6-416013: rule_daemon : Bind failed in sysdb Data server fails to bind the socket. If you frequently see this message, contact Cisco Technical Support.
CE-RULES-6-416014: send_verif_ack(): error sending ack, error = <error_no> Error in acknowledging the acknowledgement message. No action is required.
CE-RULES-6-416015: rule_process_notif_msg (): Unknown Event Unknown event occurs when sending rule process notification message. No action is required.
CE-SNMP-2-430001: bind_data server_sock() failed: <return value> Fails to connect to the data server. If this message occurs, the SNMP agent does not accept configuration from CLI, send traps, or retrieve any CISCO-CONTENT-ENGINE-MIB statistics. Contact Cisco Technical Support if this is the case.
CE-SNMP-2-430002: ds_edm_register() failed: <item name return value> EDM registration fails with the data server <return value>. If this message occurs, the SNMP agent does not retrieve any statistics defined in the CISCO-CONTENT-ENGINE_MIB file. Contact Cisco Technical Support if this is the case.
CE-SNMP-2-430003: ds_verification_register() failed: <str> Verification registration fails with the data server. If this message occurs, the user is unable to configure SNMP related features. Contact Cisco Technical Support if this is the case.
CE-SNMP-2-430004: ds_notification_register() failed: <str> Notification registration with the data server fails . If this message occurs, the SNMP agent is probably unable to generate traps. Contact Cisco Technical Support if this is the case.
CE-SNMP-3-430005: [Procedure]:Failed open [filename]. errno: [dc], [str] Error occurs while opening [filename] file. If you frequently see this message, contact Cisco Technical Support.
CE-SNMP-3-430006: [Procedure]: Failed to read [filename]. errno: [dc], [str] Encounters an error while reading a /proc file. If you frequently see this message, contact Cisco Technical Support.
CE-SNMP-3-430007: [Procedure]: Failed to read [filename]. End-of-file. Encounters unexpected End-of-file in a /proc file. If you frequently see this message, contact Cisco Technical Support.
CE-SNMP-2-430008: [filename] has more data than SNMP Agent expects:possible kernel version and SNMP Agent application code mismatch. Unexpected number of data fields is found in a /proc file. If you frequently see this message, contact Cisco Technical Support.
CE-SNMP-2-430009: Incorrect number of data items found in [filename] Unexpected number of data fields is found in a /proc file. If you frequently see this message, contact Cisco Technical Support.
CE-SNMP-2-430010: / proc/net/snmp header line has unexpected format. Possible kernel version and SNMP Agent application code mismatch. Unknown header information is found in /proc/net/ARP. If you frequently see this message, contact Cisco Technical Support.
CE-SNMP-2-430011: / proc/net/snmp sscanf parsing error STAT_NET_ICMP entry.num_items read = <dc>, num_items expected = 26 Unknown number of data fields is found in /proc/net/SNMP. If you frequently see this message, contact Cisco Technical Support.
CE-SNMP-2-430012: / proc/net/snmp has more data than SNMP Agent expects: chars read = [dc] chars processed = [dc] possible kernel version and snmp application code mismatch Unknown number of data fields is found in /proc/net/SNMP. If you frequently see this message, contact Cisco Technical Support.
CE-SNMP-2-430013: snmp Agent process terminated. The SNMP agent process terminates due to connection failure with the data server. The SNMP agent process is restarted by the node manager process. If you frequently see this message, contact Cisco Technical Support.
CE-SNMP-3-430014: SNMP server could not set Contact data item in data server (error code). A change is made in the SNMP server contact information. However, the change is not recorded in the data server. Try to set the contact data item again. If it fails repeatedly , contact Cisco Technical Support.
CE-SNMP-3-430015: SNMP server could not set Location data item in data server (error code). A change is made in the SNMP server location information. However, the change is not recorded in the data server. Try to set the location data item again. If it fails repeatedly, contact Cisco Technical Support.
CE-SSHD-0/1/2/3/4/5/6-440000: [failure-description] This message class indicates that the native Linux SSHD code exposes error/notice/information. If error messages occur, check the SSHD configuration or device configuration. If you frequently see this message, contact Cisco Technical Support.
CE-SSHD-3-440001: read [ssh_session_file] failed, errno=[err_code]([failure-description]). The message indicates that the SSH service fails to read the ssh_session_file.  
CE-SSHD-3-440002: write [ssh_session_file] failed, errno=[err_code]([failure-description]). The message indicates that the SSH service fails to write the ssh_session_file. If this message occurs occasionally, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-SSHD-3-440003: lseek [ssh_session_file] failed, errno=[err_code]([failure-description]). The message indicates that the SSH service fails to seek the ssh_session_file. If this message occurs occasionally, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-SSHD-3-440004: can't open [ssh_session_file], errno=[err_code]([failure-description]). The message indicates that the SSH service fails to open the ssh_session_file. If this message occurs occasionally, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-SSHD-3-440005: can't create [ssh_session_file], errno=[err_code]([failure-description]). The message indicates that the SSH service fails to create the ssh_session_file. If this message occurs occasionally, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-SSHD-3-440006: failed to start /usr/sbin/sshd, [failure-description]. The message indicates that the SSH service fails to start the SSHD process. Retry to issue the ssh command. Restart the SSH service and reboot the device. If you frequently see this message, contact Cisco Technical Support.
CE-SSHD-3-440007: usr/sbin/sshd did not exit, [failure-description]. The message indicates that the SSH service fails because the SSHD process does not exit. Retry to issue the ssh command. Restart the SSH service and reboot the device. If you frequently see this message, contact Cisco Technical Support.
CE-SSHD-3-440008: ssh session failed, possibly because of incorrect login. The message indicates that the active SSH session fails, possibly because of incorrect login, or because of internal SSHD errors. Retry SSH login with correct username/password.
CE-SSHD-3-440009: ssh session succeeded. The message indicates that the the active SSH session proceeds successfully. No action is required.
CE-SSHD-3-440010: Internal error: Could not change owner (error) SSH is not enabled due to an internal error. Contact Cisco Technical Support.
CE-SYSMON-3-445000: Error in read the req, errno: [error] The system fault monitor fails to read a request. The request is skipped. No action is required.
CE-SYSMON-3-445001: Failed to set NONBLOCK for new_fd, ret [status], errno [error no]. The system fault monitor fails to set the NONBLOCK attribute on a request. The request is skipped. No action is required.
CE-SYSMON-3-445002: select: ret = [status], errno = [error no] The select call within the system fault monitor fails . If you frequently see this message, contact Cisco Technical Support.
CE-SYSMON-3-445003: Incorrect system id [system identifier] An unknown system identifier is received by the system fault monitor. Contact Cisco Technical Support.
CE-SYSMON-3-445004: Incorrect device id [device id] An unknown device identifier is received by the system fault monitor. Contact Cisco Technical Support.
CE-SYSMON-3-445005: Incorrect timestamp [timestamp] An improper timestamp is received by the system fault monitor. Contact Cisco Technical Support.
CE-SYSMON-3-445006: Incorrect severity [severity level] An unknown severity level is received by the system fault monitor. Contact Cisco Technical Support.
CE-SYSMON-3-445007: error [error code] when binding to data server The system fault monitor fails to make a connection to to the data server. A fault is probably not reported. Contact Cisco Technical Support.
CE-SYSMON-3-445008: error [error code] when setting [data item name] The system fault monitor fails to set a value for the specified data server item name. A fault is probably not reported. Contact Cisco Technical Support.
CE-SYSMON-5-445009: sysmon: entering start_loop The system fault monitor starts up. Contact Cisco Technical Support.
CE-SYSMON-5-445010: Fault detected: [description] The system fault monitor detects a fault. Take corrective action to fix the fault. If no fault actually exists, contact Cisco Technical Support.
CE-TRNSLG-3-460001: TRANSLOG: tlog_begin_mark(): write failed, Write fails. No action is required.
CE-TRNSLG-3-460002: Unable to open transaction log file: Unable to open transaction log file. No action is required.
CE-TRNSLG-3-460003: TRANSLOG: tlog_commit():write failed, errno = Write fails. No action is required.
CE-TRNSLG-3-460004: Log directory non-existent -transaction logging terminated: Log directory is non-existent. Check to see if log directory exists.
CE-TRNSLG-3-460005: Log path is not a directory - transaction logging terminated: Log path is not a directory. Check to see if log path is a directory.
CE-TRNSLG-3-460006: Logging filesystem nearly full and unable to delete: Logging file system is nearly full. No action is required.
CE-TRNSLG-3-460007: TRANSLOG: translog_set_trap(): sysdb_item_set failed Item set fails. No action is required.
CE-TRNSLG-2-460008: TRANSLOG: system mem low. Clean up mem alloced System memory is low. No action is required.
CE-TRNSLG-2-460009: TRANSLOG: system mem low. Buffer allocation aborted. Buffer allocation fails. No action is required.
CE-TRNSLG-3-460010: TRANSLOG: tlog_end_mark(): write failed, errno = Write fails. No action is required.
CE-TRNSLG-5-460011: process info: tlog_logger_init() process_id Process id and pthread id. No action is required.
CE-TVOUT-7-470001: [debug message] Class of debug messages for TV-out service. No action is needed.
CE-TVOUT-3-470002: Unable to determine TV-out hardware: [error] An error occurs accessing data about the type of TV-out hardware installed on the box. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470003: TV-out hardware was not detected: [error] TV-out hardware is not detected to be installed on the box. Either the hardware itself is not detected, or the detection software fails to run after the last box reload. Verify that a supported A/V decoder card is properly installed and reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-6-470004: TV-out hardware was detected: <card type> Notes the A/V decoder card type found installed on the box. No action is required.
CE-TVOUT-3-470005: Cannot allocate memory for [target] General memory allocation failure for the specified target. System is probably in an undefined state. Try to reenable the TV-out service. If message persists, reload the box. Since this message is probably due to low memory conditions, try to reduce the overall number of services enabled. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470006: Unable to determine stream type: [error] An error occurs processing the stream type to be decoded. System is probably in an undefined state. Check the log for additional messages and further action. If no other messages are found, try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470007: On file close: [system error] Close of a file descriptor generates a system error. System is probably in an undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470008: Cannot open <file>: [system error] Unable to open the specified file due to system error. System is probably in an undefined state. Verify that the channel replication status and the cdnfs are stable. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470009: Unable to process overlay image: [error] Fails to process an overlay image for on screen display due to the error encountered. Verify that any overlay image files are valid and meet TV-out specifications as detailed in the ACNS Software Deployment and Configuration Guide. Try to reenable the TV-out service. If you see this message often, contact Cisco Technical Support.
CE-TVOUT-5-470010: On overlay image processing: [error] While processing an overlay image for on screen display, an error is encountered. This probably causes the resulting display to be skewed or incomplete. Verify that any overlay image files are valid and meet TV-out specifications as detailed in the ACNS Software Deployment and Configuration Guide. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470011: AV-001: Unable to open MPEG device interface Fails to open the control interface to the MPEG device driver. System is probably in an undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470012: AV-001: Unable to setup OSD region: [error] An error is encountered setting up the on screen display region through the device driver. Verify that any overlay image files are valid and meet TV-out specifications as detailed in the ACNS Software Deployment and Configuration Guide. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470013: AV-001: Unable to setup decode: [error] An error is encountered setting up the decode of a stream through the device driver. Verify that any overlay image files are valid and meet TV-out specifications as detailed in the ACNS Software Deployment and Configuration Guide. Try to reenable the TV-out service. If you see this message, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-47014: AV-001: Unable to start OSD: [error] An error is encountered starting the on screen display through the device driver. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470015: [sysdb error message] Class of sysdb error messages for the TV-out service. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470016: [sysdb warning message] Class of sysdb warning messages for the TV-out service. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470017: [sysdb notice message] Class of sysdb notice messages for the TV-out service. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470018: Unable to connect to cms database: Cannot check [target] Unable to connect to CMS database. The specified target is unable to be retrieved. Verify that CMS is enabled and runs normally. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470019: Failed query of cms database: [target] not found - [action] In query of the CMS database, the specified target is unable to be found. This often indicates incomplete or missing data. Verify that CMS is enabled and runs normally. Take specified action, if any. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470020: Unable to decode <file path> on <playlist>: [error] Decode of the specified file path on the specified playlist fails due to error encountered. Partial decode has probably occurred. System is probably in an undefined state. Check for additional messages and further action. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470021: Invalid <position> for <playlist> with <total files>: reset to top An invalid position is encountered at the time of the playback of the specified playlist. Therefore, playback is restarted. An invalid position probably occurs due to a dynamic change in the number of media files or by seeking through the playlist using playback controls. This message is generally harmless. However, it sometimes indicates a software issue. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470022: Skipping [media type] on <playlist>: unavailable <url> The specified media type is skipped on the specified playlist since specified url is not currently available on the box. Check log for additional messages and further action. Verify channel assignment and manifest file attributes. This message is often transitory due to fluctuations in channel replication status. Try to reenable the TV-out service. If you this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470023: Media file <url> will be skipped for duration of <playlist> due to playback error The media file specified by the url is skipped for the duration of the specified playlist due to an error encountered when the media file stream is being decoded. Check for additional messages and further action. Verify that the media file is valid as detailed in the ACNS Software Deployment and Configuration Guide. If media file is invalid, remove it from the playlist. If media file is valid, verify that it is free of errors and/or corrupted data. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470024: Unable to determine next random position: [error] Playlist is unable to determine the next random position due to error encountered. Playlist is probably restarted. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470025: Current schedule for <playlist> no longer applies The specified playlist detects a schedule modification that invalidates the current session. Playback of the specified playlist is stopped. No action is required.
CE-TVOUT-6-470026 : New <url> replaces old <url> on <playlist> Due to a channel configuration change, the old url is replaced by the new url on the specified playlist. No action is required.
CE-TVOUT-3-470027: Unable to connect to uns for resolve of <url> on <playlist> TV-out service is unable to connect to the UNS service to determine the local file path for the specified url on the specified playlist. System is probably in an undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470028: Unknown <client> requests <state> for <playlist> An unknown client attempts to change the state of the specified playlist. The request is ignored. No action is required.
CE-TVOUT-4-470029: Select returned <errno>: [system error] General failure occurs at the time of socket communications. System is probably in undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470030: Invalid overlay image setting for <playlist>: [error] Detects an overlay image setting outside allowable parameters on the specified playlist. Verify that overlay image parameters are valid as detailed in the ACNS Software Deployment and Configuration Guide. If invalid, modify playlist configuration. If valid, try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470031: Unable to set overlay image <url> for <playlist> An unspecified error occurs when setting up the overlay image using the specified url for the specified playlist. Check for additional messages and further action. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470032: Invalid <request> received by <playlist> from <client> A request is received by specified playlist from the specified client that is not understood. The request is ignored. No action is required.
CE-TVOUT-4-470033: TV-out signal default to <format>: [error An error is encountered when accessing the TV-out signal format configuration. The default format is used instead of the configured format. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470034: Unable to register as statistics EDM for <subtree> An unspecified error occurs when attempting to register as the external data manager for tvout statisitcs. TV-out service statistics are probably unavailable. Try to reenable the TV-out service. If message persists, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470035: Unsupported message type received as statistics EDM An unsupported message type is received by TV-out service. This is generally harmless. However, it sometimes indicates a software issue. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-6-470036: Processing statistics request for <item Notes a statistics request for the specified item. No action is required.
CE-TVOUT-4-470037: Unable to process statistics request: [error] An error is encountered at the time of the processing of a statistics request. TV-out service statistics are probably unavailable. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-6-470038: Device manager returned <number> available for playback Notes the number of device interfaces that are available for playback. No action is required.
CE-TVOUT-3-470039: Device manager returned no devices so playback cannot be attempted Since no device interfaces are successfully initialized, playback is not attempted. TV-out service is in idle mode. Check log for additional messages and further action. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470040: Device manager cannot init <number>: <status> One or more device interfaces fails to be initialized. Check log for additional messages and further action. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-2-470041: Daemon failed: [system error] TV-out service fails to run as a background process and exits . TV-out service can be restarted automatically. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-2-470042: Exit in main after [type]: [exception] The specified exception is detected, causing the TV-out service to immediately exit. TV-out service can be restarted automatically. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-6-470043: Returning result from Main: <result> An usual result is returned by the main call. This is generally a harmless message. However, it sometimes indicates a software issue. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470044: Cannot create transaction logs: [system error] An error is encountered that prevents the TV-out service from creating transaction logs. This generally indicates that transaction-logging is not enabled on the box. Verify that transaction-logging is enabled. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470045: Unable to send transaction log data: [system error] Fails to send transaction log data due to the system error encountered. Transaction log is probably incomplete. System is probably in a undefined state. Verify that transaction-logging is enabled. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-6-470046: Initializing TV-out service Notes that the TV-out service is initialized. This occurs on startup and whenever an exception occurs . No action is required.
CE-TVOUT-4-470047: TV-out service Exception: [exception] The specified TV-out service exception occurs . The TV-out service is re-initialized without a full restart. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470048: Cannot create pid <file>: [system error] The specified pid file is not created due to a system error. This message is generally harmless. However, it sometimes indicates a software issue. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470049: Trouble closing pid <file>: [system error] The specified pid file is not closed normally due to system error. This message is generally harmless. However, it sometimes indicates a software issue. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470050: Cannot init uns client context : [status] Context for the UNS client interface fails to be initialized successfully. Try to reenable the TV-out service. If message persists, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470051: Uns cannot resolve invalid URL <url>: [error] The specified URL is not resolved to a local file path on the box since it is not understood due to the specified error. Verify channel assignment and manifest file attributes. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470052: Uns returned unsupported resolve action for <url>: [resolveAction] In a request to UNS for the local file path for the specified URL, an unsupported action is returned. Verify channel assignment and manifest file attributes. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470053: Uns unable to provide file path for playable <url> The local file path is not determined for the specified URL due to a problem encountered with a UNS object. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470054: Uns unable to resolve <url>: [error] The specified URL is unable to be resolved to a local file path due to the error encountered. Verify channel replication status and content attributes. Verify that acquisition and/or distribution processes run normally. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470055: Uns rpc failed for [action]: [status] Unable to request the specified action due to failure in the remote procedure call to UNS. System is probably in an undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-6-470056: [playlist processing messages] Class of informational messages regarding playlist processing. No action is required.
CE-TVOUT-5-470057: Unable to gracefully stop <playlist> An unspecified error occurs when the specified playlist is requested to stop. The playlist is probably aborted subsequently. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-6-470058: Manual playback requested for <playlist> Notes a manual playback request for the specified playlist. No action is required.
CE-TVOUT-5-470059: Requested <playlist> is already active A playback request is made for the specified playlist. However, the specified playlist already actively plays . The request is ignored. No action is required.
CE-TVOUT-4-470060: Requested <playlist> is not available for playback A playback request is made for the specified playlist. However, it is currently unavailable. Verify that the playlist is assigned to the box. If it is assigned, verify that CMS is enabled and runs normally. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470061: Socket failure for [target]: [system error] A failure occurs in socket communications for the specified target due to a system error. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470062: Unable to launch <playlist>: [error] The specified playlist is not launched due to the error encountered. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470063: Calling to abort any active decode of <playlist> The specified playlist is requested to terminate while actively decoding a media file stream. This probably occurs if TV-out service is disabled, or the box is reloaded. No action is required.
CE-TVOUT-3-470064: Failed to send term signal to child <pid>: [system error] A system error is encountered after requesting termination of the child process at the specified pid. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470065: Waitpid on child <pid> returned error: [system error] A system error is encountered when checking the exit status of the child process at the specified pid. The last playback session is probably aborted unexpectedly. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-5-470066: Last playback session was in manual mode; relaunching <playlist> The specified playlist is automatically restarted in manual mode. This occurs when the last shutdown of the TV-out service causes the manual playback of the specified playlist to be aborted. No action is required.
CE-TVOUT-4-470067: Unable to add <playlist> to playback list: [error] The specified playlist is unable to be added to the the playback list due to the specified error. The specified playlist is not scheduled or manually launched. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470068: AV-002: sem_init error: <errno> Semaphore initialization operation fails . System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470069: AV-002: Unable to open w/o memory Initialization fails to obtain memory. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470070: AV-002: Unable to open control interface: <status> Initialization fails to obtain a control interface handle to the driver. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470071: AV-002: Unable to configure PUSH: <inputType> Initialization fails to put the interface into push mode. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470072: AV-002: Unable to get push handle: <status> Initialization fails to get proper access to the driver. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470073: AV-002: setupDecode - Unsuported stream type specified: <streamType> Interface is requested to setup for a stream type that it does not support. Contact Cisco Technical Support since this problem indicates a problem with the higher layers of the software.
CE-TVOUT-3-470074: AV-002: setupDecode - SetDemuxPUSH error: <status> An error occurs when setting up the interface for the stream type. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470075: AV-002: setupDecode - PlayPUSH error: <status> An error occurs when entering the interface into play mode. System is probably in a undefined state. Try to reenable the TV-out service. If message persists, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470076: AV-002: decode - GetBuffer error: <status> An error occurs when attempting to get a buffer for the stream data. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470077: AV-002: decode - PushBuffer error <status> when writing <bytesDecoded> of <streamLength> bytes An error occurs when attempting to push a buffer of stream data to the driver. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470078: AV-002: pauseDecode - PausePUSH error: <status> The driver interface fails to enter into pause mode as requested. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470079: AV-002: resumeDecode - PlayPUSH error: <status> The driver interface fails to enter into play mode as requested. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470080: AV-002: stopDecode - EOS PushBuffer error: <status> An error occurs when attempting to push an end-of -stream indication to the driver. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-3-470081: AV-002: stopDecode - StopPUSH error: <status> The driver interface fails to enter into stop mode as requested. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-2-470082: CARIBBEAN called RMPanic with status=<reason>. Exiting The driver interface callback indicates a panic condition. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470083: AV-002: callbackRMF - Unexpected message : <msg_id> val : <msg_parm> An unexpected message is received from the driver interface. System is probably in a undefined state. This is generally harmless., However, it probably indicates a software issue. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-TVOUT-4-470084: AV-002: callbackRMF - StopPush error: <errno> The driver interface callback fails to enter into stop mode as requested. System is probably in a undefined state. Try to reenable the TV-out service. If you see this message again, reload the box. Contact Cisco Technical Support if this problem continues to occur.
CE-URLFLT-2-490200: Out of memory [related information] The process runs out of memory when trying to allocate more memory. Nodemgr restarts the process. Otherwise, reboot the box. Contact Cisco Technical Support with the message detail.
CE-URLFLT-3-490300: Error connecting to [type of filter server] server The CE is having problems talking with the filtering server. Filtering is not performed normally. Check status of the external filtering server. If the filtering server runs OK, check the network connectivity between CE and the filtering server.
CE-URLFLT-3-490301: Error code in filtering server response Filtering server sends back error code. The filtering server probably has a problem. Check corresponding CE statistics on the feature to see if the error code counter explains the problem. If not, contact Cisco Technical Support with the information.
CE-URLFLT-6-490600: Initializing [type of filtering server] filtering module The CE initializes the filtering module to work with the filtering server. Expect to see message CE-URLFLT-4-490701 soon after this message. If not, look for error messages in the log and act accordingly.
CE-URLFLT-6-490601: Done initializing [type of filtering server] filtering module CE completes initializing the filtering module and is ready to do filtering. No action is required.
CE-URLFLT-6-490602: Initializing connections to [type of filter server] server The CE initializes connections to external filter server. Expect to see message CE-URLFLT-4-490703 in the log soon. Otherwise, look for error messages in the log and act accordingly.
CE-URLFLT-6-490603: Done Initializing connections to [type of filter server] server The CE completes initializing connections to external filter server. No action is required.
CE-URLFLT-6-490604: Connecting to [type of filter server] server The CE establishes connections to external filter server. Expect to see message CE-URLFLT-4-490705 in the log soon. Otherwise, look for error messages in the log and act accordingly.
CE-URLFLT-6-49065: Done connecting to [type of filter server] server That CE is connected to external filter server. No action is required.
CE-URLFLT-6-490606: Closing connections to [type of filter server] server The CE closes connections to the external filter server. Expect to see message CE-URLFLT-4-490707 in the log soon. Otherwise, look for error messages in the log and act accordingly.
CE-URLFLT-6-490607: Done closing connections to [type of filter server] server The CE disconnects from the external filter server. No action is required.
CE-URLFLT-6-491600: Restarting connections to N2H2 server The CE closes the previous connections to the N2H2 server and reopens them. No action is required.
CE-URLFLT-6-491601: Done restarting connections to N2H2 server The CE closes the previous connections to the N2H2 server and reopens them. No action is required.
CE-URLFLT-6-491602: N2H2 server configuration change The N2H2 server configuration on the CE is modified. The message prints the corresponding changes. No action is required.
CE-URLFLT-6-491603: N2H2 server is configured, connections will be open The user configures the N2H2 server on the CE. The CE opens connections to the N2H2 server. No action is required.
CE-URLFLT-6-491604: Number of connections up after initialization Print out the total connections up between CE and N2H2 server. No action is required.
CE-URLFLT-6-491605: Number of connections configured by hidden CLI This is to print out the new number of connections specified by hidden CLI as well as the old number of connections No action is required.
CE-URLFLT-7-491706: Number of available connections This is to print out the number of connections that are not busy. No action is required.
CE-URLFLT-3-492300: Initiailizing filtering module with no active connections Websense is enabled. However, there is no Websense server configured. No active connections are established. Filtering does not take effect. No action is required.
CE-URLFLT-4-492400: Username exceeds maximum Username for this request exceeds the maximum length allowed by Websense protocol when filling in the username in the filtering request to Websense server. The username is truncated to maximum length allowed and sent to Websense server. It sometimes results in incorrect filtering results. No action is required.
CE-URLFLT-6-492602: Free up memory used by Websense filtering module Freeing up memory used by Websense module. No action is required.
CE-URLFLT-6-492603: Done free up memory used by Websense filtering module Memory used by Websense module is freed. No action is required.
CE-URLFLT-3-493301: Error initializing local list Error occurs when initializing the local list. Local list filtering does not function correctly. Try to reboot the box. If you frequently see this message, contact Cisco Technical Support.
CE-URLFLT-3-494300: Request processing timeout RPC call for filtering daemon timeout for streaming traffic. Try to reboot the box. If you frequently see this message, contact Cisco Technical Support.
CE-URLFLT-3-494301: Error creating filtering daemon Problem creating filtering RPC server. Filtering for streaming traffic does not work. The daemon is restarted. If you frequently see this message, contact Cisco Technical Support.
CE-URLFLT-3-494302: Error getting client There is no filtering call to the filtering daemon for prolonged time. This error is very unlikely to happen. Reboot the box. If you frequently see this message, contact Cisco Technical Support.
CE-URLFLT-3-494303: Error creating working thread to handle new client Filtering daemon is having problem creating a new thread to handle a RPC connection. Server is probably overloaded. Reboot the box. If you frequently see this message, contact Cisco Technical Support.
CE-URLFLT-3-494304: Error with locking There is internal error in filtering daemon that is caused by locking problem. Filtering probably does not work correctly. Contact Cisco Technical Support with the detailed error message and file a bug.
CE-URLFLT-3-494305: Unsupported Scheme This is an internal error in filtering daemon. Filtering probably does not work correctly. Contact Cisco Technical Support with the detailed error message and file a bug.
CE-URLFLT-3-494306: Error clearing filtering stats This is an internal error in filtering daemon. Filtering probably does not work correctly. Contact Cisco Technical Support with the detailed error message and file a bug.

500000 to 599999

Message Explanation Action
CE-WCCP-3-500001: A particular application may be down. Since a particular application is down, keepalives for that application are halted. Wait for a few seconds for the application to restart. If you frequently see this message, contact Cisco Technical Support.
CE-WCCP-3-500002: No interface is configured. Physical interface is not configured for WCCP. Wait for a few seconds. Sometimes address configuration takes time. Otherwise, check the WCCP configuration
CE-WCCP-3-500003: Malformed Router Id component received from router. Malformed router ID is received in the i_see_you message. Check the WCCP configuration parameters or contact Cisco Technical Support.
CE-WCCP-3-500004: Malformed Router View component received from router. Malformed router view component is received in i_see_you message. Check the WCCP configuration parameters or contact Cisco Technical Support.
CE-WCCP-3-500005: Router Id component > WCCP2_MAX_ROUTERS in i_see_you. Router ID in the i_see_you message is greater than the maximum supported. Check the WCCP configuration parameters or contact Cisco Technical Support.
CE-WCCP-3-500006: Router Id component from router -- length incorrect. Router ID component length is incorrect in i_see_you. Check the WCCP configuration parameters or contact Cisco Technical Support.
CE-WCCP-5-500007: ISU from new router. ISU from the new router. Create a new router entry for this service. No action is required.
CE-WCCP-5-500008: A new view from the router with the given change number. A new view is received from router in i_see_you message. No action is required.
CE-WCCP-3-500009: Num of Routers in ISU message are out of range. Number of routers in i_see_you message are either less than zero or greater than WCCP2_MAX_ROUTERS. Check the WCCP configuration parameters or contact Cisco Technical Support.
CE-WCCP-3-500010: Num of CEs in ISU message are out of range. Number of CEs in i_see_you message are either less than zero or greater than WCCP2_MAX_WEB_CACHES. Check the WCCP configuration parameters or contact Cisco Technical Support.
CE-WCCP-3-500011: Malformed view component - incorrect length. View component in i_see_you has incorrect length. Check the WCCP configuration parameters or contact Cisco Technical Support.
CE-WCCP-5-500012: Created new Rtr entry. Creates new router entry from i_see_you message. No action is required.
CE-WCCP-5-500013: (Masking) New CE notified. New CE joins the farm. No action is required.
CE-WCCP-5-500014: New CE notified. New CE joins the farm. No action is required.
CE-WCCP-5-500015: No assignment sent: CE is not in Router View. Assignment are not made until CE is seen by the router. No action is required.
CE-WCCP-5-500016: No assignment sent: CE is not seen by All Rtrs. CE needs to be seen by all the routers in the farm. Check WCCP configuration on the CE and the router.
CE-WCCP-5-500017: No assignment sent: CE is not lowest IP Add. Only lead CE gets to make the assignments. Lead CE is the one with lowest IP address in the farm. No action is required.
CE-WCCP-5-500018: New WC in mask compute assign. New CE joins using mask assignment. No action is required.
CE-WCCP-5-500019: New WC in hash compute assign. New CE joins using hash assignment. No action is required.
CE-WCCP-3-500020: Received an invalid AssignState during Mask allocation. Valid AssignStates are NORMAL or PERCENTAGE or WEIGHT. Contact Cisco Technical Support if this message repeats.
CE-WCCP-3-500021: Received an invalid AssignState during Hask allocation. Valid AssignStates are NORMAL or PERCENTAGE or WEIGHT. Contact Cisco Technical Support if this message repeats.
CE-WCCP-5-500022: OverLoad flags are not set for Hash. Overload flag should be WC_UNDERLOAD, WC_OVERLOAD, or WC_NORMAL_LOAD. No action is required.
CE-WCCP-5-500023: OverLoad flags are not set for Mask. Overload flag should be WC_UNDERLOAD, WC_OVERLOAD, or WC_NORMAL_LOAD. No action is required.
CE-WCCP-5-500024: Removing router -ID from Router Table. Removes a router either due to configuration change or a timeout. No action is required.
CE-WCCP-5-500025: Error Removing CE seen by Rtr for the service. Fails to find CE in the service. No action is required.
CE-WCCP-5-500026: New CE entry being created for CE seen by router. Creation and initialization of new entry for this CE starts . No action is required.
CE-WCCP-3-500027: Number of CEs is more than the max. Number of CEs in the service are more than the maximum supported. Contact Cisco Technical Support.
CE-WCCP-5-500028: Removing WC due to timeout. Removes a WC due to timeout. No action is required.
CE-WCCP-5-500029: Removal Query from rtr which is not configured. Processes an incoming removal query message from the router. No action is required.
CE-WCCP-5-500030: WCCP Version 2 terminated. WCCP Version 2 functionality is stopped. No action is required.
CE-WCCP-5-500031: WCCP Version 2 is enabled or disabled. WCCP Version 2 functionality is enabled or disabled. No action is required.
CE-WCCP-3-500032: Failed to enable client IP spoofing. Fails to enable client IP spoofing. Contact Cisco Technical Support.
CE-WCCP-3-500033: Failed to disable client IP spoofing. Fails to disable client IP spoofing. Contact Cisco Technical Support.
CE-WCCP-5-500034: Overload message received by wccp. CE is overloaded with the traffic. No action is required.
CE-WCCP-5-500035: Bypassing bucket due to overload. CE is overloaded. Therefore, it bypasses the new traffic. No action is required.
CE-WCCP-5-500036: Bypassing due to overload during slowstart. CE is in slow start mode. Buckets are bypassed due to overload. No action is required.
CE-WCCP-5-500037: Shutdown Msg - Wrong Version. Shutdown message is received with wrong INTER_CACHE_VERSION. No action is required.
CE-WCCP-5-500038: Shutdown Msg sent to wrong CE. This CE should not have received the shutdown message. No action is required.
CE-WCCP-5-500039: SHUTDOWN REQUEST from an unknown Content Engine. Receives SHUTDOWN REQUEST from an unknown CE. No action is required.
CE-WCCP-5-500040: Shutdown Msg - unknown type Valid types of shutdown msgs are WCCP2_SHUTDOWN_REQUEST or WCCP2_SHUTDOWN_RESPONSE. No action is required.
CE-WCCP-5-500041: Bucket Load Req: wc not found. Bucket load request message is received for the CE that is not found. No action is required.
CE-WCCP-5-500042: Mask Assign Load Req: wc not found. Mask load request message is received for the CE that is not found. No action is required.
CE-WCCP-5-500043: LOAD REQ MSG has malformed id component. Bucket load request message that is received is malformed. No action is required.
CE-WCCP-5-500044: LOAD REQ MSG received, has malformed REQ component. Bucket load request message that is received has malformed REQ component. No action is required.
CE-WCCP-5-500045: (Mask)LOAD REQ MSG has malformed id component. (Mask) maskassign load request message that is received has malformed REQ component. No action is required.
CE-WCCP-5-500046: (Mask)LOAD REQ MSG received, has malformed REQ component. (Mask) maskassign load request message that is received has malformed REQ component. No action is required.
CE-WCCP-5-500047: LOAD UPDATE MSGreceived, msg is malformed. Bucket load update msg is received. It is malformed. No action is required.
CE-WCCP-5-500048: LOAD UPDATE MSGreceived, msg is malformed. Bucket load update msg is received. It is malformed. No action is required.
CE-WCCP-5-500049: MASKING LOAD UPDATE MSG received, msg is malformed. (Mask) maskassign load update msg is received. It is malformed. No action is required.
CE-WCCP-5-500050: LOAD QUERY MSG received, msg is malformed. Bucket load query msg received, message is malformed. No action is required.
CE-WCCP-5-500051: LOAD QUERY MSG to wrong target. Bucket load query msg is received. It is not for this CE. No action is required.
CE-WCCP-5-500052: Target CE for the msg is different than this CE. Target CE for the message is different than this CE. No action is required.
CE-WCCP-5-500053: (Mask)LOAD QUERY MSG received, msg is malformed. Mask load query message is received. It is malformed. No action is required.
CE-WCCP-5-500054: (Mask) Target CE for the msg is different than this CE. (Mask) Target CE for the message is different than this CE. No action is required.
CE-WCCP-6-500055: (wccp_keepalive_init): Entered. Trying to connect to wccp. Enters WCCP routine which initializes connectivity to WCCP process and initializes timer to send keepalive messages. No action is required.
CE-WCCP-3-500056: (wccp_liveness_init): Error connecting to wccp! Application fails to connect to WCCP process. Verify application as well as WCCP configuration. If message persists, contact Cisco Technical Support.
CE-WCCP-3-500057: wccp_liveness_update(): Could not send alive message. wccp_liveness_update() routine fails to send liveness heartbeat (keepalive) message to the WCCP process. Verify application as well as WCCP configuration. If message persists, contact Cisco Technical Support.
CE-WCCP-3-500058: (wccp_liveness_connect): connect() to wccp failed. Connection from application to WCCP process fails. Verify application as well as WCCP configuration. If message persists, contact Cisco Technical Support.
CE-WCCP-3-500059: (wccp_liveness_connect): Cannot open socket to wccp. Connection from application to WCCP process fails due to socket failure. Verify application as well as WCCP configuration. If message persists, contact Cisco Technical Support.
CE-WMT-1-511010: There is no IP address configured. To make the WMT server work, the box has to be configured with an IP addresses. Configure an IP address or configure the external-ip by issuing the external-ip command.
CE-WMT-2-512000: System fork error <errno> Fork operation fails . System is in weird state. Try to reenable the service that causes this. Reboot if it does not work. Contact Cisco Technical Support if this problem continues to occur.
CE-WMT-2-512004: System call error: <system call name> <err msg> System call fails . System is possibly in a weird state. Try to reenable the service that causes this. Reboot if it does not work. Contact Cisco Technical Support if this problem continues to occur.
CE-WMT-2-512010: Configuration error: max sessions > [max allowed]/ Bandwidth > [max bandwidth] The configured maximum sessions/bandwidth is higher than the platform supported limit. Change the maximum session/bandwidth configuration to be within the platform limits.
CE-WMT-2-512020: Unable to get WMT statistics region <error_msg> The shared memory that stores WMT statistics are not accessible . Make sure that the system does not experience major problem that causes this. Try to reenable (disable and then enable) WMT service.
CE-WMT-2-512030: Unable to get WMT status region, terminating. The shared memory that stores WMT internal data is not accessible. WMT service terminates . Make sure the system does not experience a major problem that causes this. Try to reenable (disable and then enable) WMT service.
CE-WMT-2-512035: WMT Server unable to allocate free memory. Malloc fails. Check the system status and see if some process takes excessive memory. Reduce the load if the box is under high load.
CE-WMT-2-512040: WMT logging process can not create socket. Failure to create a socket by WMT logging process. System is probably in a weird state. This is a system level problem. If rebooting the box does not help, contact Cisco Technical Support.
CE-WMT-2-512045: WMT multicast process cannot create socket. Failure to create a socket by WMT logging process. System is probably in weird state. This is a system level problem. If rebooting the box does not help, contact Cisco Technical Support.
CE-WMT-2-512048: WMT setsockopt error: <which option>. Unable to set the socket option by the WMT process. System is probably in a weird state. This is a system level problem. If rebooting the box does not help, contact Cisco Technical Support.
CE-WMT-2-512050: WMT Multicast failed at asf_init(). Multicast fails at asf_init(). No action is required because this only affects one request. If the message persists, contact Cisco Technical Support.
CE-WMT-2-512060: WMT CLI handling thread failed. The WMT server uses a separate thread to handle all CLI related activities. This includes configuration change, statistics reporting, and so on. For some reason, this thread cannot either be created or exited abnormally. Try to reenable the WMT service. Contact Cisco Technical Support if the message persists.
CE-WMT-2-512070: WMT initiation to backend failed <client type> <errno>. The WMT server is unable to initiate connection with a backend daemon. The client type can be either UNS, Rule or UrlFiltering. The reason for this problem is likely the backend daemond process is not functioning correctly. Try to reenable WMT service. Contact Cisco Technical Support if the message persists.
CE-WMT-3-513000: Failed to set/get the item This is an internal error. No action is required because this only affects one request. If it continues to occur, contact Cisco Technical Support.
CE-WMT-3-513010: WMT Multicast to open/write an .nsc file. <Error code> This is an internal error. Creating/writing a temporary file fails. No action is required because this only affects one request. If message persists, contact Cisco Technical Support.
CE-WMT-3-513011: Failed to get wmt multicast station name Fails to get WMT multicast station name. No action is required because this can be a transient error. If message persists, contact Cisco Technical Support.
CE-WMT-3-513012: Failed to get data manager information Fails to get data manager information. No action is required because this can be a transient error. If message persists, contact Cisco Technical Support.
CE-WMT-3-513015: [Procedure]: called without statis Reason for this error is wrong arguments passed. Pass correct arguments. If message persists, contact Cisco Technical Support.
CE-WMT-3-513020: Failed to clear wmt statistics Fails to clear windows media statistics. Retry the command. If message persists, Cisco Technical Support.
CE-WMT-3-513030: Needs to accept the wmt license agreement before enabling Tries to enable WMT without accepting the WMT license agreement. Accept the WMT license agreement and enable WMT.
CE-WMT-3-513031: Failed to disable the evaluation of wmt license agreement Fails to disable the WMT evaluation upon installation of valid license key. No action is required. If message persists, contact Cisco Technical Support.
CE-WMT-3-513040: Failed to open/update/read the configuration file Fails to open/update/read the configuration file. Retry the configuration. If message persists, contact Cisco Technical Support.
CE-WMT-3-513041: Failed to start/stop WMT Fails to start/stop WMT. Retry the command. If message persists, contact Cisco Technical Support.
CE-WMT-3-513045: Wrong number of arguments Wrong number of arguments. Need to pass correct number of arguments.
CE-WMT-3-513046: Wrong media file size Wrong media file size. No action is required. If message persists, contact Cisco Technical Support.
CE-WMT-3-513047: [module]: Failed to initialize mms [transport protocol] wccp liveness during init Initialization of mms TCP/UDP WCCP liveness fails. No action is required. If message persists, contact Cisco Technical Support.
CE-WMT-4-514001: Disallowed all protocols. Disallows all the protocol. WMT server or proxy is not able to serve the request. No action is required.
CE-WMT-5-515000: Information regarding WMT Server status. \ Normally shows starting/terminating status. To show the WMT server status, such as starting or terminating. No action is needed. This is for notice purpose only.
CE-WMT-5-515001: Disabled the evaluation of wmt license agreement Disables the WMT evaluation upon installation of valid license key. No action is required.
CE-WMT-5-515005: Schedule(s) for <station_name> added/removed Adds /removes some/all the WMT multicast station schedules. No action is required.
CE-WMT-5-515008: Updated the configuration information to the file Updates the configuration information. No action is required.
CE-WMT-5-515010: Possible infinite loop, select with return = <return code> ready = <return code> WMT proxy server has waiting in an infinite loop when engaging with the original server. Can be that the original server stops sending data for a long time or there is a packet mismatch between the original server and the WMT Proxy server. No action is needed. If message persists, contact Cisco Technical Support.
CE-WMT-5-515011: Default and maximum bandwidth information Default and maximum bandwidth information. No action is required
CE-WMT-5-515012: [module]: Will retry [times] mms tcp WCCP liveness init after [interval] seconds Retries information for WCCP liveness. No action is required.
CE-WMT-5-515013: [module]: Successfully initialized mms [transport protocol] wccp liveness during init Initialization of mms TCP/UDP WCCP liveness is successful. No action is required.
CE-WMT-5-515020: Preload TOS bits changed Preload ToS bits are changed. No action is required.
CE-WMT-7-517000: WMT Debug message Debug messages from WMT. No action is required.
CE-LIBCMN-5-520001: Errorlog - messed up file name: <file name> Errorlog file naming code does something wrong. Delete all the files in the /localX/errorlog directory.
CE-LIBCMN-3-520002: Errorlog directory can't be created/accessed, errno = <number> Errorlog module fails to create/access the directory where it places all the log messages. Contact Cisco Technical Support.
CE-LIBCMN-2-520003: platform.c:platform_internal_type: can't open etc/MODEL: <error> CE is not able to read the system cookie. Contact Cisco Technical Support.
CE-LIBCMN-2-520004: platform.c:platform_internal_type: can't figure out model from /etc/MODEL CE fails to recognize the system cookie. Contact Cisco Technical Support.
CE-LIBCMN-3-520005: The standby group <group no> could not be brought down The interface of that just failed are not able to be brought down. Contact Cisco Technical Support.
CE-LIBCMN-3-520006: Error while removing arp entries <error> CE-LIBCMN-3-520006: Could not remove the arp entry for <address> CE fails to remove the ARP entries assciated with the failed interface. The stale ARP entries eventually time out, and fresh ones are cached. If it happens everytime a failover happens, contact Cisco Technical Support.
CE-LIBCMN-6-520007: Could not reach the default gateway on <interface> CE fails to reach the configured default gateway on through <interface>. This is an informational message. No action is required.
CE-LIBCMN-6-520008: Standby interface <interface> of group <group no> could not be brought up! CE-LIBCMN-6-520008: Standby interface <interface> of group <group no> has either link down or is seeing more than the allowed number of errors CE fails to bring up <interface> while it searches for a usable interface. This is an informational message. No action is required.
CE-LIBCMN-5-520009: Standby group <group no> is up on interface <interface> CE finds the <interface> to be usable and brings up the standby group on this interface. No action is required.
CE-LIBCMN-5-520010: No interface of the standby group <group no> are usable. CE fails to find any usable interface in the standby group. Check if any of the member interfaces of the standby are up. If not, check for cabling, CE interface configuration, and switch configuration. If yes, the standby feature has a problem. Contact Cisco Technical Support.
CE-LIBCMN-3-520011: Error while trying to reach the gateway <error>. CE encounters a problem while it tries to reach the gateway. Contact Cisco Technical Support.
CE-LIBCMN-3-520012: Error opening socket for checking link status <error> CE-LIBCMN-3-520012: SIOCDEVPRIVATE on <interface> failed while checking link status <error> CE encounters a problem while it tries to check the interface link status Contact Cisco Technical Support.
CE-LIBCMN-3-520013: Route <net_ip> <netmask> <gateway> could not be removed/added CE encounters a problem while it tries to add/remove the static IP routes after a failover link status. Contact Cisco Technical Support.
CE-STDBY-3-522001: Standby item protection semaphore open/write/signal/close error. Standby process encounters a problem while it tries to access the semaphore that protects the standby data server item. Contact Cisco Technical Support.
CE-STDBY-4-522002: Interface <interface> is down Standby process finds that the interface <interface> is down. Check the cable, switch configuration, and the CE's interface configuration for any problems. Issue the shut and no shut commands on the CE interface. If the interface is still down, contact Cisco Technical Support.
CE-STDBY-4-522003: Unable to reach the gateway Standby process finds that the CE is no longer able to reach the default gateway. Try to ping the default gateway manually. If ping does not work, look for any network problems, and the router configuration. If ping works, contact Cisco Technical Support.
CE-STDBY-4-522004: Interface <interface> has seen more errors than allowed Standby process finds that the currently active interface experiences excessive input/output errors. Look for any problems in the switch and CE interface configurations. If the configurations are correct, contact Cisco Technical Support.
CE-STDBY-7-522005: Standby group <group no> is up on <interface> Standby group is currently active on the interface <interface>. No action is required.
CE-ACL-3-533010: Failed to clear acl statistics Fails to clear access control list statistics. Retry the command later. If message persists, contact Cisco Technical Support.
CE-ACL-3-533011: directory /tmp doesn't exist The message indicates that the system does not have a configured tmp directory. If the error message occurs, the system has the serious software image set up or configuration problems. Contact Cisco Technical Support.
CE-ACL-3-533012: can't open /tmp/.acl_request file to get acl query The message indicates that the system fails to open ACL request file. If an error message occurs, reconfigure ACL list, query ACL list through debug commands, try to access the ACL list later, and reboot the CE. If the message persists, contact Cisco Technical Support.
CE-ACL-3-533013: ACL lock failed. Internal error. The message indicates that the system fails to lock the ACL table. If an error message occurs, reconfigure the ACL list, try to access the ACL list, and try to reboot CE. If the message persists, contactCisco Technical Support.
CE-ACL-3-533014: ACL unlock failed. Internal error. The message indicates that the system fails to unlock ACL table. If an error message occurs, reconfigure the ACL list, try to access the ACL list, and try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540001: Change a authentication server's status The message indicates that the authentication server's status is changed. This is a normal authmod mode. No action is required.
CE-AUTHMOD-3-540002: Reset server's status string to default The message indicates that authmod resets the default server's status. This is a normal authmod mode. No action is required.
CE-AUTHMOD-3-540003: Server's list current status timed out, try default status The message indicates that server's list current status is timed out. Authmod tries the default server's status. This is a normal authmod mode. No action is required.
CE-AUTHMOD-4-540004: Use default server's status; all servers are dead The message indicates that all authentication servers are dead. Authmod uses the default server's status. This is a normal authmod mode. No action is required.
CE-AUTHMOD-3-540005: Failed to reset authentication server status The message indicates that the authmod fails to reset authentication server status. If error message occurs repeatedly, stop request authentication, kill/spawn authmod, and try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540006: TACACS+ enable path not found in the data server The message indicates that the data server does not register the TACACS enabled CLI command. If error message occurs, disable TACACS+ authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540007: Authmod debug path returned error for TACACS+ enable path The message indicates that the data server returns an error for the TACACS enabled CLI command. If error message occurs, disable TACACS+ authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540008: Fail to add handle into conn table The message indicates that the NTLM Samba fails to add the handle into the connection table. If error message occurs repeatedly, stop request authentication, kill/spawn authmod, and try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540009: NTLM request failed to free connection The message indicates that the NTLM request fails to free the connection. If error message occurs repeatedly, stop request authentication, kill/spawn authmod, and try to reboot CE. If the message persists, contactCisco Technical Support.
CE-AUTHMOD-3-540010: Failed to detach a thread The message indicates that the system fails to detach a thread. If error message occurs repeatedly, stop request authentication, kill/spawn authmod, and try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540011: Username can't be an empty string The message indicates that the username is an empty string. Check the username and password that the user enters for authentication.
CE-AUTHMOD-5-540012: Thread monitor kills one thread The message indicates that the system kills one authmod working thread. This is a normal authmod mode. No action is required.
CE-AUTHMOD-5-540013: Thread monitor spawns one thread The message indicates that the system spawns one authmod working thread. This is a normal authmod mode. No action is required.
CE-AUTHMOD-3-540014: Fail to create a working thread The message indicates that the system fails to create an authmod working thread. If error message occurs repeatedly, stop request authentication, kill/spawn authmod, and try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540015: No working thread can be created, QUIT !! The message indicates that the system fails to create any authmod working thread. If error message occurs repeatedly, stop request authentication, kill/spawn authmod, and try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540016: Fail to create dispatch thread The message indicates that the system fails to create an authmod dispatch thread. If error message occurs repeatedly, stop request authentication, kill/spawn authmod, and try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540017: Fail to create a monitor thread The message indicates that the system fails to create an authmod monitor thread. If error message occurs repeatedly, stop request authentication, kill/spawn authmod, and try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540018: Failed to lock authentication server status The message indicates that the authmod fails to lock authentication server status. If error message occurs repeatedly, stop request authentication, kill/spawn authmod, and try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540019: Failed to bind data server socket The message indicates that the system has a problem with binding the data server socket. If error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540020: Failed the data server verification The message indicates that the system has a problem with the data server verification. If error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540021: Authmod debug path is invalid The message indicates that the data server returns an error for authmod debug path. If error message occurs, disable authentication and enable it again. Disable authentication, debug, and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540022: Authmod debug path not found in the data server The message indicates that the data server does not register the authmod debug CLI command. If error message occurs, disable authentication and enable it again. Disable authentication, debug, and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540023: Authmod debug path returns an error The message indicates that the data server returns an error for authmod debug path. If error message occurs, disable authentication and enable it again. Disable authentication, debug, and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540024: Authmod debug log is invalid The message indicates that the data server returns error for authmod debug log. If error message occurs, disable authentication and enable it again. Disable authentication, debug, and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540025: Authmod debug log not found in the data server The message indicates that the data server does not register the authmod debug log CLI command. If error message occurs, disable authentication and enable it again. Disable authentication, debug, and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540026: Authmod debug log returns an error The message indicates that the data server returns an error for authmod debug log. If error message occurs, disable authentication and enable it again. Disable authentication, debug, and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540027: RADIUS enable path not found in the data server The message indicates that the data server does not register the RADIUS server enable CLI command. If error message occurs, disable RADIUS authentication and enable it again. Disable authentication, debug, and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-4-540028: Data server RADIUS enable path returned error The message indicates that the data server returns an error for the RADIUS enable CLI command. If error message occurs, disable RADIUS authentication and enable it again. Disable authentication, debug, and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-5-540029: Pending request timed out The message indicates that an authentication request in a pending state is expired. This is a normal authmod mode. No action is required.
CE-AUTHMOD-3-540030: sendto() failed The message indicates that the system fails to write data to the socket. If error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-5-540031: Auth Module got 0 size auth message with the client. Process is exiting. The message indicates that the system reads empty data from the socket. This is a normal authmod mode. No action is required.
CE-AUTHMOD-5-540032: Auth Module returned error to the client The message indicates that the authentication module returns an error to the client. This is a normal authmod mode. No action is required.
CE-AUTHMOD-3-540033: Failed to allocate the memory. Process is exiting The message indicates that the system fails to allocate the memory. If error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540034: Select failed The message indicates that the system's socket select fails . If error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540035: Failed to lock authentication server mutex The message indicates that the system fails to lock authentication server mutex. If error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540036: Failed to create polling thread The message indicates that the system fails to create polling thread. If an error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540037: Fail to create socket The message indicates that the system fails to create a socket. If an error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540038: Failed to bind a socket The message indicates that the system fails to bind a socket. If an error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540039: Authentication Module failed to set signal handler The message indicates that the authentication module fails to set signal handler. If an error message occurs, disable authentication and enable it again. Try to reboot CE. If the message persists, contact Cisco Technical Support.
CE-AUTHMOD-3-540040: Failed to open LDAP config file The message indicates that the system fails to open the LDAP authentication configuration file. If an error message occurs, first try to reconfigure LDAP authentication. Try to authenticate a request, try to disable and enable LDAP authentication, and try to reboot CE. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540041: Failed to read LDAP server config The message indicates that the system fails to read the LDAP authentication configuration file. If an error message occurs, first try to reconfigure LDAP authentication. Try to authenticate a request, try to disable and enable LDAP authentication, and try to reboot CE. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540042: Missed LDAP port number configuration The message indicates that the system fails to read the LDAP authentication port. If an error message occurs, first try to reconfigure LDAP authentication. Try to authenticate a request, try to disable and enable LDAP authentication, and try to reboot CE. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540043: Invalid LDAP server address The message indicates that the system fails to read the LDAP server IP address. If an error message occurs, first try to reconfigure LDAP authentication. Try to authenticate a request, try to disable and enable LDAP authentication, and try to reboot CE. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540044: Failed memory allocation for LDAP server authentication The message indicates that the system fails to allocate the memory for LDAP configuration. If an error message occurs, first try to reconfigure LDAP authentication. Try to authenticate a request, try to disable and enable LDAP authentication, and try to reboot CE. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540045: Server Error; Samba failed to authenticate user The message indicates that the authentication server has a problem. If an error message occurs, check the status of the authentication server. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540046: Protocol Error; Samba failed to authenticate user The message indicates that the authentication protocol has a problem. If an error message occurs, check the status of the authentication server and query another user. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540047: Invalid Password; Samba failed to authenticate user The message indicates that the authenticated user has an incorrect password. If an error message occurs, check the status of authentication server, check the user password configuration, and query another user. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540048: Samba failed to authenticate user The message indicates that the user authentication fails. If an error message occurs, check the status of authentication server, check the user password configuration, and query another user. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540049: No Domain Controllers available The message indicates that there are no available domain controllers. If error message occurs, check the configuration of the CE, validate the status of authentication server, and verify the network topology and connections. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540050: There is no connection available The message indicates that there is no NTLM connection available. If an error message occurs, check the status of authentication server and query another user. If you see this message again, contact Cisco Technical Support.
CE-AUTHMOD-3-540051: There is no NTLM handle The message indicates that there is no NTLM handle available. If an error message occurs, check the status of authentication server and query another user. If you see this message again, contact Cisco Technical Support.
CE-BMRNG-7-550001: <various messages> Boomerang debug messages. No action is required.
CE-BMRNG-3-550002: <function>: Memory allocation problem: <data> -or- Can not allocate memory -or- error allocating Boomerang transaction log! Boomerang module runs out of memory. Disable and reenable the module. If this does not work, reload. Contact Cisco Technical Support if reload does not work.
CE-BMRNG-3-550003: select err on boom_cli_vensock fd <number> (<error>) Boomerang module fails to talk to data server. Contact Cisco Technical Support.
CE-BMRNG-2-550004: Can't create log directory for boomerang's translog (<error>) Boomerang module fails to make directory for logs. Contact Cisco Technical Support.
CE-BMRNG-2-550005: boom_agent: can't talk to data server. Boomerang module fails to talk to data server. Contact Cisco Technical Support.
CE-BMRNG-3-550006: sorry, NTP mode isn't supported in this boom-client port Boomerang does not support NTP mode. No action is required.
CE-BMRNG-3-550007: sendto failed to send <number> bytes to <address> (<error>) Boomerang module fails to send DNS race. Check network configuration and DNS race destination.
CE-BMRNG-3-550008: domain name is NULL; -or- <name> is too long; -or- <name> is not a valid domain name Domain name too long: <name> Boomerang module receives a bad domain name. Check boomerang server configuration.
CE-BMRNG-3-550009: <name> is an alias of another domain Domain name is already an alias of other domain. Check boomerang configuration or use a different name.
CE-BMRNG-3-550010: No domain <name> Tries to remove a non-existent domain. Check the supplied domain name.
CE-BMRNG-3-550011: Error [<function> at <line>] looking up parent domain <name> Tries to create an alias for non-existent domain. Check the supplied domain name.
CE-BMRNG-3-550012: Invalid encryption type: <number> Unsupported encryption type. Contact Cisco Technical Support.
CE-BMRNG-3-550013: Socket error in file <file> at line <line> (<error>) Boomerang module fails to create socket. Contact Cisco Technical Support.
CE-BMRNG-3-550014: No origin-server or content-server configured for <doamin>, request dropped by DNS Boomerang Boomerang module drops request because no origin-server or content-server is configured. Configure no origin-server or content-server.
CE-BMRNG-3-550015: Boomerang logging sem lock failed. Internal error -or- <function>: pthread_mutex_lock failed! Boomerang fails to obtain lock. Contact Cisco Technical Support.
CE-BMRNG-3-550016: Boomerang logging sem unlock failed. Internal error -or- <function>: pthread_mutex_unlock failed! Boomerang fails to release lock. Contact Cisco Technical Support.
CE-BMRNG-3-550017: Boomerang logging: Cannot open file <name> (<error>) Boomerang fails to open log file. Contact Cisco Technical Support.
CE-BMRNG-3-550018: Domain not added Boomerang fails to add a new domain name. Check the domain name.
CE-BMRNG-3-550019: DNS A-Record misses DNS A-Record misses. This should not happen. Contact Cisco Technical Support.
CE-BMRNG-3-550020: Error! bad pTrig->mode <number> at file <file> line <line> Unsupported mode. Contact Cisco Technical Support.
CE-BUFMGR-2-560001: Http cache buffer manager: out of type <type> memory There is either a buffer leak, or the buffer manager code has bugs. Divert HTTP traffic and reload. If you see this message again, contact Cisco Technical Support with syslog and errorlog.
CE-BUFMGR-4-560002: Thread <thread> memory really low (<count>), data free <free>, header free <free> HTTP cache buffer manager runs low on memory. System is probably overloaded. Reduce HTTP caching load.
CE-BUFMGR-2-560003: Http cache buffer manager: shmget error <error> <string> Cache buffer manager fails to initialize memory. System is probably low on memory. Reload. If you see this message again, contact Cisco Technical Support.
CE-BUFMGR-2-560004: Http cache buffer manager: failed to clean up resources <error> Cache buffer manager fails to initialize memory. System fails on clean up previous shared memory. Reload. If you see this message again, contact Cisco Technical Support.
CE-BUFMGR-6-560005: Http cache buffer manager uses <number> bytes Cache buffer manager starts. Cache buffer manager starts and prints out memory size to be initialized. No action is required.
CE-AUTHCACHE-5-570001: Authcache is 100% full Authcache is full and needs to replace old entry to accommendate new ones. To improve performance, adjust the authcache size to a bigger size.
CE-AUTHCACHE-5-570002: authCacheDaemon() process_id = <pid> pthread_id = <pthread_id> Reports the start up information on authcache daemon process. No action is required.
CE-AUTHCACHE-2-570003: http_ce_search_wrap: Fail to send auth message to http_authmod !!" len =<msg_len> errno = <err no> Cache fails to send authentication message to authmod module. Contact Cisco Technical Support.
CE-AUTHCACHE-5-570004: authMsgDaemon() process_id = <pid> pthread_id = <pthread_id> Reports the start up information on the authmsg daemon process. No action is required.
CE-LOGGING-2-580001: Could not create/attach/detach shared memory area. Debug commands may not work: <error> CE fails to setup a critical shared memory area. Contact Cisco Technical Support.
CE-LOGGING-2-580002: Could not access/attach/detach shared memory area. Debug commands may not work: <error> CE fails while it accesses a critical shared memory area. Contact Cisco Technical Support.
CE-LOGGING-2-580003: table pointer NULL. Module: <module> The module does not have access to a critical shared memory area. Contact Cisco Technical Support.
CE-LOGGING-2-580004: Could not access/attach shared memory area. Debug commands may not work A module fails while it accesses a critical shared memory area. Contact Cisco Technical Support.
CE-RBCP-7-590001: <various messages> Debug messages. No action is required.
CE-RBCP-5-590002: IP Address configuration successful (type: <num>, sense = <num>, ip = <ip>, mask = <mask>) IP address configuration on the NM-CE interface is successful. No action is required.
CE-RBCP-3-590003: IP Address configuration failed (type: <num>, sense = <num>, ip = <ip>, mask = <mask>) IP address configuration on the NM-CE interface fails . Reconfigure the IP address on the router. If you see this message again, contact Cisco Technical Support.
CE-RBCP-5-590004: Sending ip address configuration response. Sends IP address configuration result to the router. No action is required.
CE-RBCP-3-590005: do_set_ip(): sendto: <message> NM-CE fails while it sends IP address configuration result to the router. Reconfigure the IP address on the router. If you see this message again, contact Cisco Technical Support.
CE-RBCP-5-590006: default gateway configuration successful <default gw> Default gateway configuration on the NM-CE is successful. No action is required.
CE-RBCP-3-590007: Default gateway configuration failed <default gw> Default gateway configuration on the NM-CE fails . Reconfigure the default gateway on the router. If you see this message again, contact Cisco Technical Support.
CE-RBCP-5-590008: Sending defaultgw configuration response. Sends default gateway configuration result to the router. No action is required.
CE-RBCP-3-590009: do_set_defaultgw(): sendto: <message> NM-CE fails while it sends default gateway configuration result to the router. Reconfigure the default gateway on the router. If you see this message again, contact Cisco Technical Support.
CE-RBCP-5-590010: Sending shutdown complete message NM-CE sends the shutdown complete message to the router. No action is required.
CE-RBCP-3-590011: do_shutdown(): sendto: <message> NM-CE fails while it sends the shutdown response to the router. Contact Cisco Technical Support.
CE-RBCP-3-590012: recvfrom <message> NM-CE fails while it receives RBCP messages. Contact Cisco Technical Support.
CE-RBCP-5-590013: RBCP Registration ACK from <num>. The NM-CE receives registration ack from router. No action is required.
CE-RBCP-5-590014: RBCP Registration Request from <num>. The NM-CE receives registration request message from router. No action is required.
CE-RBCP-5-590015: RBCP IP address set message from <num> The NM-CE receives IP address set message from router. No action is required.
CE-RBCP-5-590016: RBCP default gateway set message from <num> The NM-CE receives default gateway set message from router. No action is required.
CE-RBCP-5-590017: RBCP shutdown message from <num> The NM-CE receives shutdown message from router. No action is required.
CE-RBCP-5-590018: RBCP reload message from <num> The NM-CE receives a reload message from router. No action is required.
CE-RBCP-1-590019: RBCP: Nodemgr failed to reload in 60sec. Forcing a reload The NM-CE fails to reload the NM in a graceful manner. If you see this message often, contact Cisco Technical Support.
CE-RBCP-3-590020: <name>: Error while opening socket: <error> The NM-CE fails while it creates a socket. Contact Cisco Technical Support.
CE-RBCP-3-590021: <name>: Error in bind: <error> The NM-CE fails while it binds a socket. Contact Cisco Technical Support.
CE-RBCP-3-590022: rbcpd: cannot fork: <error> The NM-CE fails while it forks a process. Contact Cisco Technical Support.
CE-RBCP-3-590023: rbcp_register: exec_show_hardware return ret = <num>, ret1=<num>, ret2=<num> The NM-CE fails while it gets status information. Contact Cisco Technical Support.
CE-RBCP-3-590024: rbcp_register: can not open <name>: <error> The NM-CE fails while it opens a file. Contact Cisco Technical Support.
CE-RBCP-3-590025: rbcp_register: error while reading <name>: <error> The NM-CE fails while it reads a file. Contact Cisco Technical Support.
CE-RBCP-3-590026: Error while sending registration message: <error> The NM-CE fails while it sends registration message. Contact Cisco Technical Support.
CE-RBCP-5-590027: rbcp_register: Registration message successfully sent The NM-CE sends the registration message successfully. No action is required.

600000 to 699999

Message Explanation Action
CE-STATS-4-600000: register_edm: edm reg err (ret = [error_code]) The statistics provider application fails to register with the data server. If you frequently see this message, contact Cisco Technical Support.
CE-STATS-4-600001: ds_connect: ds connect err (ret = [error_code]) The statistics provider application fails to connect to the data server. If you frequently see this message, contact Cisco Technical Support.
CE-STATS-4-600002: msg get err (ret=[error_code]) The statistics provider application fails to retrieve a message from the data server. If you frequently see this message, contact Cisco Technical Support.
CE-STATS-4-600003: get edm info err (ret=[error_code]) The statistics provider application fails to retrieve information from the data server. If you frequently see this message, contact Cisco Technical Support.
CE-STATS-3-600004: Failed to open /proc/net/netstat. The statistics provider application fails to open the proc interface. If you frequently see this message, contact Cisco Technical Support.
CE-STATS-3-600005: / proc/net/netstat header line has unexpected format. Possible kernel version and cache application code mismatch. header line = [line], cache expects line = [line]. The /proc/net/netstat format and the format expected by the statistics provider application vary. Contact Cisco Technical Support.
CE-STATS-3-600006: / proc/net/netstat had sscanf parsing error. num_items read = %d, num_items expected = 65 The /proc/net/netstat format and the format expected by the statistics provider application vary. Contact Cisco Technical Support.
CE-STATS-3-600007: Failed to open /proc/net/snmp. errno: [error], [description] The statistics provider application fails to open the proc interface. Contact Cisco Technical Support.
CE-STATS-3-600008: Failed to read /proc/net/snmp. errno: [error], [description] The statistics provider application fails to read the proc interface. Contact Cisco Technical Support.
CE-STATS-3-600009: Failed to read /proc/net/snmp. End-of-file. The statistics provider application fails to read the proc interface. No data is read. Contact Cisco Technical Support.
CE-STATS-3-600010: / proc/net/snmp has more data than cache expects: possible kernel version and cache application code mismatch Format of /proc/net/SNMP interface varies from expected format. Contact Cisco Technical Support.
CE-STATS-3-600011: / proc/net/snmp header line has unexpected format. Possible kernel version and cache application code mismatch. ix = [itemno], header line = [header], cache expects line = [expected] Format of /proc/net/SNMP interface varies from expected format. Contact Cisco Technical Support.
CE-STATS-3-600012: / proc/net/snmp sscanf parsing error STAT_NET_IP entry. num_items read = %d, num_items expected = 19 Format of /proc/net/SNMP interface varies from expected format. Contact Cisco Technical Support.
CE-STATS-3-600013: / proc/net/snmp sscanf parsing error STAT_NET_ICMP entry. num_items read = %d, num_items expected = 26 Format of /proc/net/SNMP interface varies from expected format. Contact Cisco Technical Support.
CE-STATS-3-600014: / proc/net/snmp sscanf parsing error STAT_NET_TCP entry. num_items read = %d, num_items expected = 21 Format of /proc/net/SNMP interface varies from expected format. Contact Cisco Technical Support.
CE-STATS-3-600015: / proc/net/snmp sscanf parsing error STAT_NET_UDP entry num_items read = %d, num_items expected = 4 Format of /proc/net/SNMP interface varies from expected format. Contact Cisco Technical Support.
CE-STATS-3-600016: / proc/net/snmp has more data than cache expects: chars read = [chars read] chars processed = [chars processed] possible kernel version and cache application code mismatch Format of /proc/net/SNMP interface varies from expected format. Contact Cisco Technical Support.
CE-STATS-3-600017: malloc for fds failed. Fails to allocate memory. If you frequently see this message, contact Cisco Technical Support.
CE-STATS-6-600018: Returning IP/ICMP/UDP/TCP stats. Statistics for the specified protocol are returned. No action is required.
CE-STATS-6-600019: Clearing IP/ICMP/UDP/TCP stats. Statistics for the specified protocol are cleared. No action is required.
CE-STATS-5-600020: Statistics thread startup notice Logs the thread and process ID's of the statistics thread of the content router. No action is required.
CE-STATS-5-600021: Statistics thread stack space notice Logs the location of the thread stack space for the statistics thread of the content router. No action is required.
CE-STATS-3-600022: Failed to create Content Router statistics thread The content router statistics thread is not created for some reason. Statistics are not gathered. The machine needs to be restarted, as such a problem is potentially indicitive of a system wide memory shortfall. If you frequently see this message, contact Cisco Technical Support.
CE-WI-5-610001: Set RLIMIT_AS to <memory_limit> Sets the max address space limit to <memory_limit> bytes. No action is required.
CE-WI-5-610002: Set RLIMIT_RSS to <memory_limit> Sets the largest resident set size, to <memory_limit> bytes. This affects swapping. Processes that exceed their Resident Set Size are more likely to have physical memory taken from them. No action is required.
CE-WI-3-610003: Webserver could not connect to the SF agent <IP-Address>:<Port> Webserver is not able to connect to the SmartFilter (SF) agent that runs on host <IP-Address> port <Port>. Contact Cisco Technical Support.
CE-WI-5-610004: get_request_data: offset = <offset> size = <size> length = <length> Size is total bytes of request data that remains to be read. Length is the bytes to be fetched in a single read. Web server gets the request data that starts from offset <offset> of <length> bytes repeatedly until the size becomes zero. No action is required.
CE-WI-3-610005: get_request_data: data_length = <length>, cannot cp data The Web server is not able to fetch the request data of length <length> bytes. The <length> is probably less than 0 or else greater than the predefined max length. Contact Cisco Technical Support.
CE-WI-5-610006: after : get_request_data: offset = <offset> size = <size> length = <length> Size is total bytes of request data that remains to be read. Length is the bytes to be fetched in a single read. Web server gets the request data that starts from offset <offset> of <length> bytes repeatedly until the size becomes zero. No action is required.
CE-WI-5-610007: Reboot initiated from GUI User initiates reload of CE from the GUI. No action is required.
CE-WI-5-610008: GUI : <exit_code> <exit_code> denotes whether the reload of CE initiated from the GUI succeeds or fails . Contact Cisco Technical Support.
CE-WI-3-610009: Webserver is unable to bind to port <listen_port> Web server is not able to bind to the listening port no <listen_port>. Contact Cisco Technical Support.
CE-RPC-2-620000: Usage: [failure description] Incorrect usage while invoking the program. Check the usage and try again. If the error occurred without any intervention from user, contact Cisco Technical Support.
CE-RPC-2-620001: Malloc failed: [failure description] Malloc fails . Check errorlog for more information. The program will be restarted by nodemgr. If you see this message again, contact Cisco Technical Support.
CE-RPC-2-620003: Failed to create [server description] server Fails to create a uniRPC server for inter-process communication. Check errorlog for more information. The program is restarted by nodemgr. If you see this message again, contact Cisco Technical Support.
CE-CSE-2-632000: [Procedure] - System call error: <systemcall name> <err msg> System call fails . System can possibly be in a weird state. If this message occurs periodically, it can be ignored. If you see this message often, contact Cisco Technical Support.
CE-CSE-3-633000: [Procedure] - Unable to establish connection with the Data Server <error_message> Fails to establish a connection with the data server. This is due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-CSE-3-633001: [Procedure] - Unable to release the connection with the Data Server <error_message> Fails to release the connection with the data server. This is due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-CSE-3-633002: [Procedure] - Failed to receive message from the Data Server <error_message> Fails to receive the message from the data server. This is due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-CSE-3-633003: [Procedure] - Failed to get information from EDM <error_message> Fails to get information from the EDM. This is due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-CSE-3-633004: [Procedure] - Failed to send acknowledgement to the Data Server <error_message> Fails to send the acknowledgment for the information received from the data server. This is due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-CSE-3-633005: [Procedure] - Failed to register with Data Manager <error_message> Fails to register with EDM. This is due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-CSE-3-633006: [Procedure] - Failed to unregister Data Manager <error_message> Fails to unregister with EDM. This is due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-CSE-3-633007: [Procedure] - Failed to release the resource acquired by the Data Server <error_message> Fails to unregister with EDM. This is due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-CSE-3-633008: [Procedure] - read event failed <error_message> Read event fails . This is due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-CSE-3-633009: [Procedure] CSE received error code <error_message> Fails to serve the request by Cisco Streaming Engine. Retry the request. If you see this message again, contact Cisco Technical Support.
CE-CSE-3-633010: [Procedure] Failed to get Cisco Streaming Engine Configuration <error_message> Fails to get the configuration of Cisco Streaming Engine. Retry the command. If you see this message again, contact Cisco Technical Support.
CE-CSE-3-633011: [Procedure] Failed to set Cisco Streaming Engine bandwidth <bw> <error_message> Fails to the change the bandwidth configuration of Cisco Streaming Engine. Retry the command. If you see this message again, contact Cisco Technical Support.
CE-CSE-3-633012: [Procedure] Failed to start Cisco Streaming Engine <error_message> Error occurs while starting Cisco Streaming Engine. Retry the command. If you see this message again, contact Cisco Technical Support.
CE-CSE-3-633013: [Procedure] Failed to stop Cisco Streaming Engine <error_message> Error occurs while stopping Cisco Streaming Engine. Retry the command. If you see this message again, contact Cisco Technical Support.
CE-CSE-3-633014: [Procedure] Failed to set accesslog filename variable in temp file <error_message> Unable to set accesslog filename in temp file. Retry the command. If you see this message again, contact Cisco Technical Support.
CE-CSE-3-633015: [Procedure] Failed to move temp file with accesslog filename to configuration file <error_message> Fails to move the temp file to the configuration file. Retry the command. If you see this message again, contact Cisco Technical Support.
CE-CSE-6-636000: [Procedure] Cisco Streaming Engine Started Cisco Streaming Engine is started and running. No action is required.
CE-CSE-6-636001: [Procedure] Cisco Streaming Engine Stopped Cisco Streaming Engine is stopped. No action is required.
CE-CSE-7-637000: [Cisco Streaming Engine CLI bin Debug] Debug message for Cisco Streaming Engine. No action is required.
CE-LSR-2-642000: Generic Error Generic error causes process failure. System is in weird state. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-UNILOG-2-650001: failed to bind data server to Fails to bind to data server. If you frequently see this message, contact Cisco Technical Support.
CE-UNILOG-2-650002: logger daemon to exit ! Unable to initialize data server connection and logger daemon to exit. If you frequently see this message, contact Cisco Technical Support.
CE-UNILOG-2-650003: Cannot open logd.conf file, exiting ! Unable to open logd.conf file and logger daemon to exit. If you frequently see this message, contact Cisco Technical Support.
CE-UNILOG-2-650004: Exiting, failed to register notifier on item Fails to register notifier on item and logger daemon to exit. If you frequently see this message, contact Cisco Technical Support.
CE-UNILOG-2-650005: log dir is not a directory Log dir is not a directory and logger daemon to exit. If you frequently see this message, contact Cisco Technical Support.
CE-UNILOG-3-650006: Error: log directory cannot be created Log directory is not created. If you frequently see this message, contact Cisco Technical Support.
CE-UNILOG-3-650007: Error: log directory cannot be accessed. errno = Log directory is not accessed. If you frequently see this message, contact Cisco Technical Support.
CE-UNILOG-3-650008: can not start translog service: Translog service is not started. If you frequently see this message, contact Cisco Technical Support.
CE-FFS-5-660001: process info: ffs_dumper() process_id Dumper process ID and pthread ID. No action is required.
CE-POSTGRE-1-661001: Lower free disk space on STATEFS partition: [failure description] DB fills the STATEFS partition. A&D content replication is temporarily stopped. Issue the cms database maintenance full command to reclaim disk space on STATEFS. Restart A&D services. If the free disk space on STATEFS is still less than 10% after database maintenance, it is possible that there is too much content replicated to the CE. Contact Cisco Technical Support.
CE-POSTGRE-1-661002: Unique index violation: [failure description] Database server fails to hold constrain for unique index . It allows you to insert a duplicate key into a unique index. Contact Cisco Technical Support.
CE-POSTGRE-1-661003: Foreign key referential integrity violation: [failure description] Database server fails to hold foreign key constrain. It allows to insert record into reference table with foreign key which is not found in master table. Contact Cisco Technical Support.
CE-POSTGRE-1-661004: Wrong record returned from database server: [failure description] Database server returns records for a query with column number which does not match the expecting column number. Contact Cisco Technical Support.
CE-POSTGRE-1-661005: Unable to create Database connection: [failure description] Database client fails to create connection with the backend server. It is possible that the postgres server process is killed, is hanging, or all of database connections are timed out. Contact Cisco Technical Support.
CE-POSTGRE-1-661006: Database system in recovery mode: [failure description] Database system is in recovery mode. Contact Cisco Technical Support.
CE-POSTGRE-1-661007: Failed to do full vacuuming: [failure description] Postgres server returns error when vacuum daemon executes the vacuum full SQL statement. Contact Cisco Technical Support.
CE-STREAMCACHE-3-673000: [Procedure] Invalid options passed Options passed in are invalid. Passed the correct arguments and retry the command.
CE-STREAMCACHE-3-673001: [Procedure] Must pass in Real Proxy and RTSP Redirector binary path Invalid path is specified. Must pass Real Proxy and RTSP redirector binary path. Passed the correct binary path and retry the command.
CE-STREAMCACHE-3-673002: [Procedure] Failed to execute IP address check stript <error_mesg> Fails to execute the script which checks for IP address. Retry the command. If you see this message often, contact Cisco Technical Support.
CE-STREAMCACHE-3-673003: [Procedure] Host name not configured <error_mesg> Host name configuration is not available. Configure the hostname and retry the command.
CE-STREAMCACHE-3-673004: [Procedure] Real Proxy needs hostname other than local host <error_mesg> Real Proxy needs host name other than local host. Configure the hostname other than localhost and retry the command.
CE-STREAMCACHE-3-673005: [Procedure] No IP address available in /etc/hosts. <error_mesg> No IP address is available in the /etc/hosts file. Configure the IP address and retry the command.
CE-STREAMCACHE-3-673006: [Procedure] Unknown return status from IP address check script Invalid return status is received from the IP address check script. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673007: [Procedure] Failed to spawn a process/thread <error_mesg> Fails to spawn a process/thread. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673008: [Procedure] MonitorMediaConfigAndWaitProcess failed MonitorMediaConfigAndWaitProcess fails . Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673009: [Procedure] Failed to set the resource limit <error_mesg> Fails to set the resource limit. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673010: [Procedure] Failed to bind to sysdb <error_mesg> Fails to bind to sysdb. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673011: [Procedure] Failed to initialize the status collector <error_mesg> Fails to initialize the status collector. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673012: [Procedure] - Unknown read event <error_message> Unknown read event. This is probably due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673013: [Procedure] - Failed to [action] [directory_name] directory <error_mesg> Fails to create/open/change directory. This is probably due to the internal error. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673014: [Procedure] - Failed to get IP address of media proxy Fails to get IP address of media proxy.  
CE-STREAMCACHE-3-673015: [Procedure] - Failed to get item <error_mesg> Fails to get item. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673016: [Procedure] - Failed to start a new session <error_mesg> Fails to start a new session. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673017: [Procedure] - Failed to start a new session Fails to start a new session. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673018: [Procedure] - System call failed: <system call> <error_mesg> System call fails . System is probably in a weird state. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673019: [Procedure] - Program <program name> died quickly during restart. Stop spawning The child process fails immediately after it starts . Stop spawning it to avoid paranoidly If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673020: [Procedure] - Failed to restart a process <process name> Fails to restart a process. If this message occurs periodically, it can be ignored. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673021: [Procedure] - WaitProcess failed WaitProcess fails. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673022: [Procedure] - Program <program name> died due to signal <signal number> Program exits due to a signal. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673023: [Procedure] - Program <program name> died abnormally with status <status code> Program exits abnormally. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673024: [Procedure] - Unexpected value of item <item name> Receives unexpected value of item. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673025: [Procedure] - Failed to get notification info Fails to get notification info. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673026: [Procedure] Failed to unbind from sysdb <error_mesg> Fails to bind from sysdb. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673027: [Procedure] Failed to Register [action] <error_mesg> Fails to register verification/notification. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673028: [Procedure] Failed to get [action] information <error_mesg> Fails to get verification/notification information. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673029: [Procedure] Failed to free ven resources <error_mesg> Fails to free VEN resources. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673030: [Procedure] Failed to build EDM/verification ACK <error_mesg> Fails to build verification/EDM acknowledgement. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673031: [Procedure] Item [fields] is NULL <error_mesg> Item name/new value/old value is empty. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673032: [Procedure] Unexpected sysdb type/item length <error_mesg> Unexpected sysdb type/item length. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673033: [Procedure] Failed to receive whole message <error_mesg> Fails to receive whole message. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673034: [Procedure] Received unexpected message type <error_mesg> Receives unexpected message type. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673035: [Procedure] Failed to send ACK <error_mesg> Fails to send acknowledgement. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673036: [Procedure] Failed to get EDM information <error_mesg> Fails to get EDM information. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673037: [Procedure] EDM List not supported <error_mesg> EDM list is not implemented. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673038: [Procedure] EDM [action] failed <error_mesg> EDM registration/unregistration fails . Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673039: [Procedure] Failed in RTSP reconfiguration <error_mesg> Error occurs at the time of RTSP reconfiguration. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673040: [Procedure] [Resource] operation <operation name> failed <error_mesg> Error occurs at the time of file/pipe operation. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673041: [Procedure] Unknown EDM item <item name> failed <error_mesg> Unknown EDM item. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673042: [Procedure] gethostbyname failed <error_mesg> Fails to get host details by name. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673043: [Procedure] Failed to get local IP address <error_mesg> Fails to get local IP address. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-3-673044: [Procedure] Failed to register as stats EDM Fails to register as stats EDM. Retry the command. If you frequently see this message, contact Cisco Technical Support.
CE-STREAMCACHE-6-676000: [Procedure] Hostname check in /etc/hosts is successful Successfully checks the host name in /etc/hosts file. No action is required.
CE-STREAMCACHE-6-676001: [Procedure] Shutting down, no spawning of child anymore Shutting down is in progress. No spawning of child process. No action is required.
CE-STREAMCACHE-6-676002: [Procedure] Process with PID <PID> exited Process exits. No action is required.
CE-STREAMCACHE-6-676003: [Procedure] PID <pid> not my direct child This process is a grandchild. No action is required.
CE-STREAMCACHE-6-676004: [Procedure] Program <Program name> exited normally with code <status code> Program exits normally. No action is required.
CE-STREAMCACHE-6-676005: [Procedure] Killing all processes related to <Path> Kills all the process which are descendents of this process. No action is required.
CE-STREAMCACHE-6-676006: [Procedure] Failed to unregister [service] <error_mesg> Fails to unregister verification/notification. No action is required.
CE-STREAMCACHE-6-676007: [Procedure] System call failed: <system call> System call fails . No action is required.
CE-SSRV-3-678300: Error occurred in Streaming Server. <error msg> Error occurs in Streaming Server No action is required.

700000 to 799999

Message Explanation Action
CE-CMS-7-700000: <message> An event occurs that is potentially interesting for debugging. No action is required.
CE-CMS-?-700001: <message> An event occurs for which no further explanation is provided. No action is documented for this event .
CE-CMS-?-700002: <exception-name> [: <exception-message>] : <stacktrace> An unhandled exception is thrown. If this message occurs periodically, it can be ignored. If you see this message often, contact Cisco Technical Support.
CE-CMS-0-700003: <exception-name> [: <exception-message>] : <stacktrace> An error causes the program to exit. If this message occurs frequently or under specific circumstances, contact Cisco Technical Support.

900000 to 999999

Message Explanation Action
CE-SYS-[priority]-900000: [Kernel Message] This class of messages is generated by the Kernel. It is potentially useful for debugging a problem that is encountered. More severe priorities (0 is the highest, seven the lowest) are more likely to be of concern. These messages need to be passed to Cisco Technical Support in conjunction with a problem that is encountered.
CE-SYS-5-900001: [system bootup messages] These are system boot up messages. These messages are mostly informational. However, it is potentially helpful when debugging certain boot up problems.
CE-SYS-5-900002: [system bootup messages] These are system boot up messages (from system initialization till syslogd is started). These messages are mostly informational. However, it is potentially helpful when debugging certain boot up problems.

Related Information

Updated: Nov 30, 2005
Document ID: 41061