Cisco ACNS Software Alarms and Error Messages Guide, Release 5.5.x
Chapter 3: Error Messages and Recovery Procedures
Downloads: This chapterpdf (PDF - 1.66MB) The complete bookPDF (PDF - 8.0MB) | Feedback

Error Messages and Recovery Procedures

Table Of Contents

Error Messages and Recovery Procedures

Access Control List Messages

ACL-3

Acquisition Messages

ACQ-2

Authentication Messages

AUTH-3

AUTH-6

Authorization Cache Messages

AUTHCACHE-2

AUTHCACHE-3

AUTHCACHE-5

Authorization Mode Messages

AUTHMOD-2

AUTHMOD-3

AUTHMOD-4

AUTHMOD-5

Auto Registration Messages

AUTOREG-2

AUTOREG-3

AUTOREG-4

AUTOREG-5

Bandwidth Messages

BANDWD-3

BANDWD-4

BANDWD-5

BANDWD-6

Boomerang Messages

BMRNG-2

BMRNG-3

BMRNG-7

Buffer Manager Messages

BUFMGR-2

BUFMGR-4

BUFMGR-6

Bypass Messages

BYPS-0

BYPS-1

BYPS-4

BYPS-5

BYPS-6

Cache Messages

CACHE-2

CACHE-3

Content Delivery Network File Server Messages

CDNFS-n

Common Internet File System Server Messages

CIFSSVR-3

Cleanup Messages

CLEAN-AD-2

Command Line Interface Messages

CLI-2

CLI-3

CLI-4

CLI-5

CLI-6

CLI-7

Content Management Service Messages

CMS-0

CMS-n

CMS-4

CMS-7

Common Extended Data Manager Messages

COMMONEDM-4

Content Routing Messages

CR-3

CR-4

CR-5

Cisco Streaming Engine Messages

CSE-2

CSE-3

CSE-6

CSE-7

Debug Messages

DDBG-7

Dynamic Host Configuration Protocol Client Messages

DHCP-n

DHCP-3

DHCP-5

Disk Messages

DISK-0

DISK-1

DISK-2

DISK-3

DISK-4

DISK-5

DISK-6

Distribution Messages

DIST-2

DIST-4

DIST-

Domain Name Server Messages

DNS-1

DNS-2

DNS-4

DNS-5

DNS-6

Data Server Messages

DS-0

DS-2

DS-3

DS-5

Firewall Feature Set

FFS-5

File Transfer Protocol Messages

FTP-n

File Transfer Protocol Export Messages

FTP_Export-n

File Transfer Protocol Proxy Messages

FTP-PROXY-2

FTP-PROXY-3

FTP-PROXY-4

FTP-PROXY-5

FTP-PROXY-6

FTP-PROXY-7

Hypertext Transfer Protocol Messages

HTTP-2

HTTP-

HTTP-3

HTTP-5

Interactive Communicating Application Protocol Messages

ICAP-3

Internet Cache Protocol Messages

ICP-6

Internet Daemon Messages

INETD-n

IP/TV Program Manager Messages

IPTVPM-3

IPTVPM-4

IPTVPM-5

IPTVPM-6

IPTVPM-7

Common Library Messages

LIBCMN-2

LIBCMN-3

LIBCMN-5

LIBCMN-6

LIBCMN-7

Logging Messages

LOGGING-1

LOGGING-2

Label Switch Routing Messages

LSR-2

Minimal Getty Messages

MINGETTY-n

Module Utilities Messages

MODUTILS-n

Network Attached Storage Messages

NAS-0

NAS-1

NAS-2

NAS-3

NAS-4

NAS-5

NAS-6

Node Manager Messages

NODEMGR-0

NODEMGR-1

NODEMGR-2

NODEMGR-3

NODEMGR-4

NODEMGR-5

NODEMGR-6

NODEMGR-7

Network Time Protocol Messages

NTP-n

NTP-3

NTP-5

NTP-7

Port to Application Mapping Messages

PAM-2

PAM-3

Parser Messages

PARSER-2

PARSER-3

PARSER-4

PAC File Server Messages

PFS-3

PFS-5

Preferences Module Messages

PM-3

PM-6

Postgres Server Messages

POSTGRE-1

Preload Messages

PRELD-2

PRELD-3

PRELD-5

Router Blade Configuration Protocol Messages

RBCP-1

RBCP-3

RBCP-5

RBCP-7

RealProxy Messages

REALPXY-2

REALPXY-3

REALPXY-4

REALPXY-7

RealSubscriber Messages

REALSRV-3

REALSRV-7

Remote Proxy Caching Messages

RPC-2

Remote Shell Protocol Messages

RSH-n

RealServer Manager Messages

RSM-2

RSM-3

RSM-4

RSM-6

RSM-7

Real Time Streaming Protocol Messages

RTSP-3

RTSP-6

RTSP-7 

Real Time Streaming Protocol Gateway Messages

RTSPG-2

RTSPG-3

Rules Messages

RULES-2

RULES-3

RULES-5

RULES-6

Scheduler Messages

SCHED-2

SCHED-4

SCHED-5

SMART Disk Messages

SMARTD-n

Simple Network Management Protocol Messages

SNMP-2

SNMP-3

SNMP-5

Secure Shell Messages

SSHD-n

SSHD-3

Streaming Server Messages

SSRV-3

Statistics Messages

STATS-3

STATS-4

STATS-5

STATS-6

Standby Messages

STDBY-3

STDBY-4

STDBY-7

Stream ing Cache Messages

STREAMCACHE-3

STREAMCACHE-5

STREAMCACHE-6

STREAMCACHE-7

System Messages

SYS-n

SYS-5

System Monitor Messages

SYSMON-1

SYSMON-3

SYSMON-5

System Utilities Messages

SYSUTL-1

SYSUTL-3

SYSUTL-5

SYSUTL-6

Sysvinit Messages

SYSVINIT-n

Telnet Messages

TELNET-n

Trivial File Transfer Protocol Messages

TFTP-2

TFTP-3

TFTP-4

TFTP-5

TFTP-7

Translog Messages

TRNSLG-2

TRNSLG-3

TRNSLG-5

TRNSLG-6

TV Out Messages

TVOUT-2

TVOUT-3

TVOUT-4

TVOUT-5

TVOUT-6

TVOUT-7

Unilog Messages

UNILOG-2

UNILOG-3

Upgrade Messages

UPG-2

UPG-3

URL Filter Messages

URLFLT-2

URLFLT-3

URLFLT-4

URLFLT-6

URLFLT-7

Linux Utilities Messages

UTILLIN-n

Vcron Messages

VCRON-n

Web Cache Communication Protocol Messages

WCCP-3

WCCP-4

WCCP-5

WCCP-6

Websense Server Messages

WEBSENSE-SERVER-3

WEBSENSE-SERVER-5

WEBSENSE-SERVER-6

Webserver Messages

WI-3

WI-5

Windows Media Technologies Messages

WMT-1

WMT-2

WMT-3

WMT-4

WMT-5

WMT-7


Error Messages and Recovery Procedures


This chapter lists the ACNS Release 5.5 system error messages. Each message is followed by an explanation and a recommended action.

Access Control List Messages

This section contains access control list (ACL) messages.

ACL-3

Error Message    CE-ACL-3-533010: Failed to clear acl statistics 

Explanation    The system failed to clear ACL statistics.

Recommended Action    Retry the command later. If the problem persists, contact Cisco TAC.

Error Message    CE-ACL-3-533011: directory /tmp doesn't exist 

Explanation    The system does not have a tmp directory configured.

Recommended Action    The system has software image set up or configuration problems that need to be addressed immediately. Contact Cisco TAC.

Error Message    CE-ACL-3-533012: can't open /tmp/.acl_request file to get acl query 

Explanation    The system cannot open the ACL request file.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Reconfigure the ACL.
2. Query the ACL by using debug commands.
3. Attempt to access the ACL later.
4. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-ACL-3-533013: ACL lock failed. Internal error. 

Explanation    The system cannot lock the ACL table.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Reconfigure the ACL.
2. Access the ACL later.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-ACL-3-533014: ACL unlock failed. Internal error. 

Explanation    The system cannot unlock the ACL table.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Reconfigure the ACL.
2. Access the ACL later.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-ACL-3-533015: Internal error: Incorrect permission flag. 

Explanation    The permission flag entered is incorrect.

Recommended Action    Check the flag entered, and reconfigure the ACL.

Error Message    CE-ACL-3-533016: Internal error: Incorrect username or groupname flag. 

Explanation    The username or groupname flag entered is incorrect.

Recommended Action    Check the flag entered, and reconfigure the ACL.

Error Message    CE-ACL-3-533017: Username string length exceeds the limit. 

Explanation    The length of the username entered exceeds the configured limit.

Recommended Action    Reconfigure the permissible length of the ACL username string.

Error Message    CE-ACL-3-533018: Groupname string length exceeds the limit. 

Explanation    The length of the groupname entered exceeds the configured limit.

Recommended Action    Reconfigure the permissible length of the ACL groupname string.

Error Message    CE-ACL-3-533019: Groupname string can't be empty. 

Explanation    The groupname string was not entered for the ACL command.

Recommended Action    Ensure that the groupname string is entered, and reconfigure the ACL.

Error Message    CE-ACL-3-533020: Group name shouldn't have delimited comma symbol. 

Explanation    The groupname string of the ACL command contains invalid characters (comma symbol).

Recommended Action    Reenter the groupname string using valid characters, and reconfigure the ACL.

Error Message    CE-ACL-3-533021: Access List entry position in the access list should 
be above 1. 

Explanation    The entry position value of the ACL command has been incorrectly configured.

Recommended Action    Check the ACL command configuration, and set the correct entry position value.

Error Message    CE-ACL-3-533022: Internal error: Problem to allocate memory. 

Explanation    Memory could not be allocated.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-ACL-3-533023: Problem to obtain ACL entry. 

Explanation    An attempt to get a record from the ACL failed.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Check the command entered.
2. Reconfigure the ACL.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Acquisition Messages

This section contains acquisition messages.

ACQ-2

Error Message    CE-ACQ-2-100001: Acquirer failed in Database operation: [failure 
description].

Explanation    Acquirer encountered a critical error in the database operation.

Recommended Action    Follow these steps, in the given order, until one of them solves the problem:

1. Run the cms database maintenance command.
2. If the problem persists, reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100002: Acquirer failed to connect to UNS server: [failure 
description].

Explanation    The UNS server failed to start or is busy.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100003: Failed to disable request=[chars] due to Database 
error: [chars] Restarting the acquirer process.

Explanation    Acquirer restarted because of data corruption.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100004: Failed to create Rpc Server: [failure description].

Explanation    The rpc server could not be created because of one of two reasons:

1. Another instance of acquirer is running.
2. The port that the rpc server needs to listen on is being used by other services.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100005: Request with url=[chars] has been disabled due to 
database error: Failed to read [chars] = [chars] from [chars], error = [dec].

Explanation    The database is corrupted. Acquirer tried to recover the request by reparsing the manifest file but recovery failed and acquirer disabled the request.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100006: Failed to get channel lock: [failure description].

Explanation    Acquirer is in conflict with distribution and failed to start the acquisition for the channel.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Configure a different Content Engine as the root Content Engine and then reconfigure the original root Content Engine to be the root Content Engine again.
2. Unassign the root Content Engine from the channel, and assign it back as the root Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100007: Request hangs, will restart acquirer to correct the 
problem.

Explanation    The request could not be executed because of an internal error. Acquirer restarted to correct the problem.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100008: Corrupt data received via rpc for call [chars]

Explanation    Acquirer received corrupt rpc data.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100009: Failed to read Channel=[chars], Channel table may 
have been dropped accidentally. Restarting acquirer to wait for its creation.

Explanation    Acquirer could not read the channel because the channel table was accidently dropped by a command. Acquirer restarted and is waiting for the channel table to be created.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100010: Failed to acquire start-url.

Explanation    Acquirer is unable to acquire the start-url for the crawl job. The start-url has to be corrected.

Recommended Action    Correct the start-url in the manifest file, and try again. If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100011: Failed to write in to NAS.

Explanation    The acquirer is unable to write on the network-attached storage (NAS) device.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Make sure the NAS device is not corrupt.
2. Check for free space on the device by running the show statistics cdnfs command. The physical file system space free line tells you the free space available on the device.
3. If the free space available is insufficient, remove excess files on the file system (without removing the files in the CE directory).
4. Assign Content Engine space in line with what is available on the NAS device.
5. Ensure that other applications are not filling up the NAS file system that is used by the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-ACQ-2-100012: Some acquisition tasks are not in active root 
channels.

Explanation    Acquirer failed to read the channel table but could read the other tables.

Recommended Action    Check if acquirer is running normally by using the show acquirer command. If acquirer is not running normally, contact Cisco TAC.

Authentication Messages

This section contains authentication messages.

AUTH-3

Error Message    CE-AUTH-3-110002: Username is too long(longer than 250 bytes).

Explanation    The username is longer than 250 bytes.

Recommended Action    Ensure that username is within the prescribed limits.

Error Message    CE-AUTH-3-110003: Failed to release pam handler.

Explanation    None.

Recommended Action    Attempt the login again. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTH-3-110004: Failed to add transient user.

Explanation    None.

Recommended Action    Contact Cisco TAC.

AUTH-6

Error Message    CE-AUTH-6-110001: General AUTH module debug message ID.

Explanation    None.

Recommended Action    No action is required.

Authorization Cache Messages

This section contains authorization cache messages.

AUTHCACHE-2

Error Message    CE-AUTHCACHE-2-570003: http_ce_search_wrap: Fail to send auth message 
to http_authmod!!" len =<msg_len> errno = <err no> 

Explanation    Cache is unable to send authentication message to the authorization mode module.

Recommended Action    Contact Cisco TAC.

AUTHCACHE-3

Error Message    CE-AUTHCACHE-3-570006: Unexpected NTLM proxy request header 

Explanation    Cache received a proxy authorization NTLM header meant for the Content Engine. However, NTLM request authentication is not enabled on the Content Engine.

Recommended Action    Contact Cisco TAC.

AUTHCACHE-5

Error Message    CE-AUTHCACHE-5-570001: Authcache is 100% full 

Explanation    Authorization cache is full. Old entries will be deleted to accommodate new entries.

Recommended Action    To improve performance, increase the size of the authorization cache.

Error Message    CE-AUTHCACHE-5-570002: authCacheDaemon() process_id = <pid> pthread_id 
= <pthread_id> 

Explanation    The message is the startup information of the authCache daemon process.

Recommended Action    No action is required.

Error Message    CE-AUTHCACHE-5-570004: authMsgDaemon() process_id = <pid> pthread_id 
= <pthread_id> 

Explanation    The message is the startup information of authMsg daemon process.

Recommended Action    No action is required.

Error Message    CE-AUTHCACHE-5-570005: malloc failure, system may be low in memory! 

Explanation    The message is a report on malloc failure and low memory warning for the whole system.

Recommended Action    Write down Content Engine status, and contact Cisco TAC.

Authorization Mode Messages

This section contains authorization mode messages.

AUTHMOD-2

Error Message    CE-AUTHMOD-2-540052: Failed to establish GC connection for AD search 

Explanation    An error occurs when the Content Engine connects to Global Catalog (GC) servers for Active Directory (AD) search. When an AD group search is enabled and there is no GC connection, user authorization fails.

Recommended Action    Check GC server address configurations and Enum user configurations. Check the status of the GC server.

Error Message    CE-AUTHMOD-2-540053: Failed to establish LDAP server connection for AD 
search 

Explanation    An error occurs when the Content Engine connects to LDAP servers for an AD search. When an AD group search is enabled and there is no LDAP server connection, user authorization fails.

Recommended Action    Check LDAP server and Enum user configurations, and check the status of the configured LDAP servers.

Error Message    CE-AUTHMOD-2-540063: Configure thread has a failure           

Explanation    The configure thread encountered an error while processing a message.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

AUTHMOD-3

Error Message    CE-AUTHMOD-3-540001: Change in authentication server status 

Explanation    The authentication server status has changed.

Recommended Action    This message indicates a normal authorization mode state. No action is required.

Error Message    CE-AUTHMOD-3-540002: Reset server status string to default 

Explanation    The authorization mode has reset the server status to default.

Recommended Action    This message indicates a normal authorization mode state. No action is required.

Error Message    CE-AUTHMOD-3-540003: Server list current status timed out, try default 
status 

Explanation    The server list is currently in the timed-out status. Authorization mode is trying to restore the default status.

Recommended Action    This messages indicates a normal authorization mode state. No action is required.

Error Message    CE-AUTHMOD-3-540005: Failed to reset authentication server status 

Explanation    Authorization mode failed to reset the authentication server status.

Recommended Action    If the problem occurs repeatedly, follow these steps in the given order until one of them solves the problem:

1. Stop the request authentication.
2. Terminate the authorization mode process.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540008: Failed to add handle into conn table 

Explanation    The NTLM Samba failed to add the handle into the connection table.

Recommended Action    If the problem occurs repeatedly follow these steps in the given order until one of them solves the problem:

1. Stop the request authentication.
2. Terminate the authorization mode process.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540009: NTLM request failed to free connection 

Explanation    The NTLM request failed to free the connection.

Recommended Action    If the problem occurs repeatedly follow these steps in the given order until one of them solves the problem:

1. Stop the request authentication.
2. Terminate the authorization mode process.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540010: Failed to detach a thread 

Explanation    The system cannot detach a thread.

Recommended Action    If the problem occurs repeatedly, follow these steps in the given order until one of them solves the problem:

1. Stop the request authentication.
2. Terminate the authorization mode process.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540011: Username can't be an empty string 

Explanation    The username is an empty string.

Recommended Action    Ensure that the username is not an empty string.

Error Message    CE-AUTHMOD-3-540014: Fail to create a working thread 

Explanation    The system is unable to create an authorization mode working thread.

Recommended Action    If the problem occurs repeatedly, follow these steps in the given order until one of them solves the problem:

1. Stop the request authentication.
2. Terminate the authorization mode process.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540015: No working thread can be created, QUIT!! 

Explanation    The System is unable to create an authorization mode working thread.

Recommended Action    If the problem occurs repeatedly, follow these steps in the given order until one of them solves the problem:

1. Stop the request authentication.
2. Terminate the authorization mode process.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540016: Fail to create dispatch thread 

Explanation    The system is unable to create an authorization mode dispatch thread.

Recommended Action    If the problem occurs repeatedly, follow these steps in the given order until one of them solves the problem:

1. Stop the request authentication.
2. Terminate the authorization mode process.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540017: Fail to create a monitor thread 

Explanation    The system unable to create an authmod monitor thread.

Recommended Action    If the problem occurs repeatedly, follow these steps in the given order until one of them solves the problem:

1. Stop the request authentication.
2. Terminate the authorization mode process.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540018: Failed to lock authentication server status 

Explanation    Authorization mode failed to lock the authentication server status.

Recommended Action    If the problem occurs repeatedly, follow these steps in the given order until one of them solves the problem:

1. Stop the request authentication.
2. Terminate the authorization mode process.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540019: Failed to bind data server socket 

Explanation    The system is unable to bind the data server socket.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540030: sendto() failed 

Explanation    The system failed to write data to the socket.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540033: Failed to allocate the memory. Process is exiting 

Explanation    The system failed to allocate memory.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540034: Select failed 

Explanation    The system socket select failed.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540035: Failed to lock authentication server mutex 

Explanation    The system failed to lock the authentication server mutex.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540036: Failed to create polling thread 

Explanation    The system failed to create a polling thread.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540037: Fail to create socket 

Explanation    The system failed to create a socket.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540038: Failed to bind a socket 

Explanation    The system failed to bind a socket.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540039: Authentication Module failed to set signal 
handler 

Explanation    The authorization mode failed to set a signal handler.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540040: Failed to open LDAP config file 

Explanation    The system is unable to open an LDAP authentication configuration file.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Reconfigure LDAP authentication.
2. Authenticate a request.
3. Disable and enable LDAP authentication.
4. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540041: Failed to read LDAP server config 

Explanation    The system is unable to read the LDAP authentication configuration file.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Reconfigure LDAP authentication.
2. Authenticate a request.
3. Disable and enable LDAP authentication.
4. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540042: Missed LDAP port number configuration 

Explanation    The system is unable to read the LDAP authentication port.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Reconfigure LDAP authentication.
2. Authenticate a request.
3. Disable and enable LDAP authentication.
4. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540043: Invalid LDAP server address 

Explanation    The system is unable to read the LDAP server IP address.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Reconfigure LDAP authentication.
2. Authenticate a request.
3. Disable and enable LDAP authentication.
4. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540044: Failed memory allocation for LDAP server 
authentication 

Explanation    The system is unable to allocate memory for LDAP configuration.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Reconfigure LDAP authentication.
2. Authenticate a request.
3. Disable and enable LDAP authentication.
4. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540045: Server Error; Samba failed to authenticate user 

Explanation    Authentication server failed to authenticate the user.

Recommended Action    Check the authentication server status. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540046: Protocol Error; Samba failed to authenticate user 

Explanation    The authentication protocol failed to authenticate the user.

Recommended Action    Check the authentication server status. Query another user. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540047: Invalid Password; Samba failed to authenticate 
user 

Explanation    The authenticated user has an incorrect password.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Check authentication server status.
2. Check user password configuration.
3. Query another user.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540048: Samba failed to authenticate user 

Explanation    User authentication fails.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Check authentication server status.
2. Check user password configuration.
3. Query another user.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540049: No Domain Controllers available 

Explanation    No Domain Controllers are available.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Check Content Engine configuration.
2. Validate authentication server status.
3. Verify network topology and connections.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540050: There is no connection available 

Explanation    The NTLM connection is not available.

Recommended Action    Check the authentication server status. Query another user. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540051: There is no NTLM handle 

Explanation    The NTLM handle is not available.

Recommended Action    Check the authentication server status. Query another user. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540054: Failed to bind Data Server 

Explanation    The system was unable to get a data server connection.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540055: Failed Data Server verification 

Explanation    The system was unable to get a data server connection.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540056: Failed to remove authmod connection structure 

Explanation    The system was unable to remove the authorization mode structure.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540057: Failed Data Server notification 

Explanation    The system was unable to get the data server connection.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540058: Failed to reset NTLM server status string 

Explanation    The system was unable to set the NTLM server status string to default.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540059: Failed to reset RADIUS server status string 

Explanation    The system was unable to set the RADIUS server status string to default.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-3-540065: Failed to reset a server status string 

Explanation    The system was unable to set the authentication server status string to default.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

AUTHMOD-4

Error Message    CE-AUTHMOD-4-540004: Use default server's status; all servers are dead 

Explanation    No authentication server is functional. Authorization mode uses the default server status.

Recommended Action    This message indicates a normal authorization mode state. No action is required.

Error Message    CE-AUTHMOD-4-540006: TACACS+ enable path not found in the data server 

Explanation    The data server is unable to register the tacacs enable command.

Recommended Action    Disable TACACS+ authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540007: Authmod debug path returned error for TACACS+ 
enable path 

Explanation    The data server returns an error for the tacacs enable command.

Recommended Action    Disable TACACS+ authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540020: Failed the data server verification 

Explanation    The data server verification failed.

Recommended Action    Disable authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540021: Authmod debug path is invalid 

Explanation    The authorization mode debug path is invalid.

Recommended Action    If the error message occurs again, disable authentication and enable it again, disable authentication debug and enable it again, and try to reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540022: Authmod debug path not found in the data server 

Explanation    The data server is unable to register the Authmod debug command.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Disable authentication, and enable it again.
2. Disable authentication debug, and enable it again.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540023: Authmod debug path returns an error 

Explanation    The data server returns an error for the authorization mode debug path.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Disable authentication, and enable it again.
2. Disable authentication debug, and enable it again.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540024: Authmod debug log is invalid 

Explanation    The authorization mode debug log is invalid.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Disable authentication, and enable it again.
2. Disable authentication debug, and enable it again.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540025: Authmod debug log not found in the data server 

Explanation    The data server has not registered the Authmod debug log command.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Disable authentication, and enable it again.
2. Disable authentication debug, and enable it again.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540026: Authmod debug log returns an error 

Explanation    The data server returns an error for the authorization mode debug log.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Disable authentication and enable it again.
2. Disable authentication debug and enable it again.
3. Reboot the Content Engine.

If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540027: RADIUS enable path not found in the data server 

Explanation    The data server has not registered the radius server enable command.

Recommended Action    Disable RADIUS authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540028: Data server RADIUS enable path returned error 

Explanation    The data server returns an error for the radius enable command.

Recommended Action    Disable RADIUS authentication, and enable it again. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTHMOD-4-540060: Problem with Data Server's item 

Explanation    The authorization mode failed to get or set a data server item.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

AUTHMOD-5

Error Message    CE-AUTHMOD-5-540012: Thread monitor kills one thread 

Explanation    The system has terminated an authorization mode working thread.

Recommended Action    This message indicates a normal authorization mode state. No action is required.

Error Message    CE-AUTHMOD-5-540013: Thread monitor spawns one thread 

Explanation    The system has spawned an authorization mode working thread.

Recommended Action    This message indicates a normal authorization mode state. No action is required.

Error Message    CE-AUTHMOD-5-540029: Pending request timed out 

Explanation    An authentication request, in a pending state, has ended.

Recommended Action    This message indicates a normal authorization mode state. No action is required.

Error Message    CE-AUTHMOD-5-540031: Auth Module got 0 size auth message with the 
client. Process is exiting. 

Explanation    The system did not receive any data from the socket.

Recommended Action    This message indicates a normal authorization mode state. No action is required.

Error Message    CE-AUTHMOD-5-540032: Auth Module returned error to the client 

Explanation    The authorization mode returned an error to the client.

Recommended Action    This messages indicates a normal authorization mode state. No action is required.

Error Message    CE-AUTHMOD-5-540061: Finished initialization of authmod configure 
thread 

Explanation    The system completed initialization of the authorization mode configuration thread.

Recommended Action    No action is required.

Error Message    CE-AUTHMOD-5-540062: Started initialization of authmod configure 
thread 

Explanation    The system started initialization of the authorization mode configuration thread.

Recommended Action    No action is required.

Error Message    CE-AUTHMOD-5-540064: NetBIOS RFCNT session request failure 

Explanation    The NetBIOS RFCNT session request failed.

Recommended Action    No action is required.

Error Message    CE-AUTHMOD-5-540066: Reset a server status string 

Explanation    The authentication server status string is set to default.

Recommended Action    No action is required.

Auto Registration Messages

This section contains auto registration messages.

AUTOREG-2

Error Message    CE-AUTOREG-2-111026: Enabling CMS failed even after <num> retries.

Explanation    Enabling CMS failed after <num> attempts.

Recommended Action    Attempt to enable CMS again. If the problem persists, contact Cisco TAC.

AUTOREG-3

Error Message    CE-AUTOREG-3-111000: Can't read auto registration config. Quitting.

Explanation    The system could not find an internal data structure, which is necessary for auto registration to function.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111001: Failed to get default autoregistration interface.

Explanation    The system failed to get the default interface on which auto registration is enabled.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111002: Failed to remove dhclient pid file: <error>.

Explanation    A temporary data file could not be removed.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111006: Error while starting up DHCP client (num, num).

Explanation    Starting up the DHCP client failed.

Recommended Action    Attempt, once again, to startup the DHCP client. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTOREG-3-111007: Can't read device mode. Disabling 
autoregistration.

Explanation    The system was unable to identify the device mode. As a precaution, auto registration is not enabled on this system.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111008: Failed to disable auto registration on the 
default interface (num, num).

Explanation    Auto registration did not become disabled on the default interface.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111010: Auto registration on the default interface failed 
(num, num).

Explanation    Auto registering failed on the default interface.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111011: Auto registration enabled on the default 
interface.

Explanation    Auto registration was enabled on the default interface.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-3-111013: CE/CR deregistration (cms disable) failed (num, 
num).

Explanation    Failed to disable CMS.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111015: CE/CR deregistration (cms deregister) failed 
(num, num).

Explanation    The system failed to deregister CMS.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-3-111017: Insufficient parameters to cfg_bin_runcms.

Explanation    The program cfg_bin_autoreg_runcms did not receive a required parameter.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111019: Primary interface configuration failed (num, 
num).

Explanation    Configuring the primary interface failed.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111021: Could not get startup-config to check for cdm ip. 
Assuming it to be present.

Explanation    The system failed to get the startup configuration when trying to check if CDM configuration is present.

Recommended Action    Contact Cisco TAC.

Error Message    CE-AUTOREG-3-111023: CDM hostname configuration failed (num, num).

Explanation    The system failed to configure the CDM hostname that was received through the vendor option information from DHCP server.

Recommended Action    Attempt to configure CDM host name again. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTOREG-3-111024: CDM hostname configuration successful.

Explanation    The CDM hostname was successfully configured.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-3-111025: Enable CMS failed (num, num). Retrying.. (num).

Explanation    The system failed to enable CMS. The system is still trying to enable CMS.

Recommended Action    Attempt to enable CMS again. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTOREG-3-111028: Failed to save the running-config to 
startup-config (num, num).

Explanation    The system failed to save the configuration to the non-volatile flash storage.

Recommended Action    Contact Cisco TAC.

AUTOREG-4

Error Message    CE-AUTOREG-4-111003: DHCP server could not be contacted. Using a cached 
lease.

Explanation    The system was unable to contact a DHCP server. It is using a lease that was obtained earlier but which is still valid.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-4-111004: DHCP server could not be contacted will retry 
after 5 minutes.

Explanation    The system was unable to contact a DHCP server. The system will keep retrying every five minutes to contact the DHCP server.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-4-111005: Usable CDM hostname not found in DHCP server 
response.

Explanation    The response from the DHCP servers did not contain the vendor option information.

Recommended Action    Check the configuration on the DHCP server.

AUTOREG-5

Error Message    CE-AUTOREG-5-111009: Auto registration disabled on the default 
interface.

Explanation    The system disabled auto registration on the default interface.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-5-111012: Auto registration configuration found in 
startup-config. Quitting.

Explanation    The system found auto registration configuration in the startup configuration, so the system did not apply the default configuration.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-5-111014: CE/CR deregistration (cms disable) successful.

Explanation    The system disabled CMS before reenabling it with the new CDM IP.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-5-111016: CE/CR deregistration (cms deregister) successful.

Explanation    The system deregistered the Content Engine and registered it with the new CDM.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-5-111018: Auto registration is disabled. Ignore vendor 
option information.

Explanation    Auto registration is disabled, so the vendor option information received in the DHCP server response was ignored.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-5-111020: Primary interface configuration successful.

Explanation    The primary interface was successfully configured.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-5-111022: CDM IP found in startup-config/dataserver. 
Quitting.

Explanation    The CDM IP address was found in the startup-config or data server, and no configuration changes were made.

Recommended Action    No action is required.

Error Message    CE-AUTOREG-5-111027: CDM hostname configuration removed (num, num).

Explanation    Enabling CMS with the CDM failed. The CDM hostname configuration was removed.

Recommended Action    Attempt to enable CMS with the CDM again. If the problem persists, contact Cisco TAC.

Error Message    CE-AUTOREG-5-111029: CE/CR successfully registered with the CDM.

Explanation    The Content Engine was registered with the CDM.

Recommended Action    No action is required.

Bandwidth Messages

This section contains bandwidth messages.

BANDWD-3

Error Message    CE-BANDWD-3-115001: Failed to bind to [item] error number [x].

Explanation    The bandwidth module failed to bind [item] in the dataserver. The error number for the bind is [x].

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115002: The failed operation will be retried in two 
seconds.

Explanation    The bandwidth module will retry the failed operation in two seconds.

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115003: Failed verification registration with dataserver 
with error [x].

Explanation    The bandwidth module failed to register with data server for verification. The error number is [x].

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115005: Bandwidth setting failed.

Explanation    The bandwidth module failed to set bandwidth because the module is invalid.

Recommended Action    If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115008: Bandwidth module got error [x] from dataserver.

Explanation    The bandwidth module encountered an error [x] while trying to receive the whole message from the data server.

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115009: Bandwidth module lost connection to dataserver.

Explanation    The bandwidth module lost the connection with the data server. It will attempt to reestablish the connection.

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115010: Bandwidth module got error [x] on 
ds_verification_info().

Explanation    The bandwidth module was unable to retrieve verification information from the data server.

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115011: Bandwidth module got error [x] on 
ds_build_verification_ack().

Explanation    The bandwidth module was unable to build the verification acknowledgement for the data server.

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115012: Bandwidth module got error [x] on 
ds_send_whole_ack().

Explanation    The bandwidth module was unable to send verification acknowledgement to the data server.

Recommended Action    The system should recover from the error automatically. If this persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115013: Bandwidth module  got bad type [x] on 
ds_receive_whole_msg().

Explanation    The bandwidth module got error [x] while receiving a message from the dataserver.

Recommended Action    The system should recover from the error automatically. If this persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115014: Bandwidth module got socket error and is 
restarting.

Explanation    The bandwidth module got a socket error and will be restarting.

Recommended Action    The system should recover from the error automatically. If this persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115017: Failed notification registration with dataserver 
with error [x].

Explanation    The bandwidth module failed to register with data server for notification. The error number is [x].

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115018: Bandwidth module got error [x] on 
ds_notification_info().

Explanation    The bandwidth module was unable to retrieve notification information from the data server for a WMT license.

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115019: Bandwidth module could not update bandwidths of 
sprayers.

Explanation    Upon receiving a message from the data server, the bandwidth module updates sprayer bandwidths through pthread. In this case, the bandwidth module was unable to create a thread.

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-3-115020: Bandwidth module could not update bandwidth of 
sprayer.

Explanation    The bandwidth module failed to set the bandwidth for module [name] to [value].

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

BANDWD-4

Error Message    CE-BANDWD-4-115004: Failed to create a thread for notification.

Explanation    The bandwidth module failed to create a thread for notification from the database. It will be restarted by the node manager.

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

BANDWD-5

Error Message    CE-BANDWD-5-115007: Error [x] retrieving item [name] from dataserver.

Explanation    The bandwidth module failed to get [name] from the dataserver. The error number is [x].

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

Error Message    CE-BANDWD-5-115015: Bandwidth module failed to connect to the 
Multicast Sender.

Explanation    The bandwidth module failed to send a message to the Multicast Sender.

Recommended Action    The system should recover from the error automatically. If this persists or occurs frequently, contact Cisco TAC.

BANDWD-6

Error Message    CE-BANDWD-6-115006: Set bandwidth for module [name] to [value].

Explanation    The bandwidth for the module [name] was set to the value [value].

Recommended Action    No action is required. It is just an informational message.

Error Message    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.

Explanation    The bandwidth module is setting the WMT value to [y], which is lower than the configured value [x]. The configured bandwidth license allows for a lower value.

Recommended Action    This message is informational and explains the difference between the actual value of bandwidth available and the configured value.

Boomerang Messages

This section contains boomerang messages.

BMRNG-2

Error Message    CE-BMRNG-2-550004: Can't create log directory for boomerang's translog 
(<error>) 

Explanation    The boomerang module failed to make a directory for logs.

Recommended Action    Contact Cisco TAC.

Error Message    CE-BMRNG-2-550005: boom_agent: can't talk to dataserver. 

Explanation    The boomerang module was unable to connect to the data server.

Recommended Action    Contact Cisco TAC.

BMRNG-3

Error Message    CE-BMRNG-3-550002: <function>: Memory allocation problem: <data> -or- 
Can not allocate memory -or- error allocating Boomerang transaction log! 

Explanation    The boomerang module is out of memory.

Recommended Action    Disable and reenable the module. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-BMRNG-3-550003: select err on boom_cli_vensock fd <number> 
(<error>) 

Explanation    The boomerang module was unable to connect to the data server.

Recommended Action    Contact Cisco TAC.

Error Message    CE-BMRNG-3-550006: sorry, NTP mode isn't supported in this boom-client 
port 

Explanation    The boomerang module does not support NTP mode.

Recommended Action    No action is required.

Error Message    CE-BMRNG-3-550007: sendto failed to send <number> bytes to <address> 
(<error>) 

Explanation    The boomerang module failed to send the required number of DNS rates.

Recommended Action    Check the network configuration and the DNS rate destination.

Error Message    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> 

Explanation    The boomerang module received an invalid domain name.

Recommended Action    Check the boomerang server configuration.

Error Message    CE-BMRNG-3-550009: <name> is an alias of another domain 

Explanation    The domain name is an alias of another domain.

Recommended Action    Check the boomerang configuration, or use a different name.

Error Message    CE-BMRNG-3-550010: No domain <name> 

Explanation    The boomerang module is trying to remove a domain that does not exist.

Recommended Action    Check the supplied domain name.

Error Message    CE-BMRNG-3-550011: Error [<function> at <line>] looking up parent 
domain <name> 

Explanation    The boomerang module is trying to create an alias for a domain that does not exist.

Recommended Action    Check the supplied domain name.

Error Message    CE-BMRNG-3-550012: Invalid encryption type: <number> 

Explanation    The encryption type is not supported.

Recommended Action    Contact Cisco TAC.

Error Message    CE-BMRNG-3-550013: Socket error in file <file> at line <line> (<error>) 

Explanation    The boomerang module failed to create a socket.

Recommended Action    Contact Cisco TAC.

Error Message    CE-BMRNG-3-550014: No origin-server or content-server configured for 
<domain>, request dropped by DNS Boomerang 

Explanation    The boomerang module dropped the request because there is no origin-server or content-server configured.

Recommended Action    Configure an origin-server or content-server.

Error Message    CE-BMRNG-3-550015: Boomerang logging sem lock failed. Internal error 
-or- <function>: pthread_mutex_lock failed! 

Explanation    The boomerang module failed to obtain a lock.

Recommended Action    Contact Cisco TAC.

Error Message    CE-BMRNG-3-550016: Boomerang logging sem unlock failed. Internal error 
-or- <function>: pthread_mutex_unlock failed! 

Explanation    The boomerang module failed to release the lock.

Recommended Action    Contact Cisco TAC.

Error Message    CE-BMRNG-3-550017: Boomerang logging: Cannot open file <name> 
(<error>) 

Explanation    The boomerang module failed to open the log file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-BMRNG-3-550018: Domain not added 

Explanation    The boomerang module failed to add a new domain name.

Recommended Action    Check the domain name.

Error Message    CE-BMRNG-3-550019: DNS A-Record misses 

Explanation    A DNS record is missing.

Recommended Action    Contact Cisco TAC.

Error Message    CE-BMRNG-3-550020: Error! bad pTrig->mode <number> at file <file> line 
<line> 

Explanation    The mode is not supported.

Recommended Action    Contact Cisco TAC.

BMRNG-7

Error Message    CE-BMRNG-7-550001: <various messages> 

Explanation    These are debug messages from the boomerang module.

Recommended Action    No action is required.

Buffer Manager Messages

This section contains buffer manager messages.

BUFMGR-2

Error Message    CE-BUFMGR-2-560001: Http cache buffer manager: out of type <type> 
memory 

Explanation    There is either a buffer leak, or the buffer manager code has bugs.

Recommended Action    Divert http traffic and reboot. If the problem persists, contact Cisco TAC with syslog and errorlog.

Error Message    CE-BUFMGR-2-560003: Http cache buffer manager: shmget error <error> 
<string> 

Explanation    The cache buffer manager was unable to initialize the memory. The system may be low on memory.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-BUFMGR-2-560004: Http cache buffer manager: failed to clean up 
resources <error> 

Explanation    The cache buffer manager was unable to initialize the memory. The system failed to clean up previous shared memory.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

BUFMGR-4

Error Message    CE-BUFMGR-4-560002: Thread <thread> memory really low (<count>), data 
free <free>, header free <free> 

Explanation    The HTTP cache buffer manager is low on memory. The system may be overloaded.

Recommended Action    Reduce HTTP caching load.

BUFMGR-6

Error Message    CE-BUFMGR-6-560005: Http cache buffer manager uses <number> bytes 

Explanation    The cache buffer manager has started. The cache buffer manager and print out memory size will be initialized.

Recommended Action    No action is required.

Bypass Messages

This section contains bypass messages.

BYPS-0

Error Message    CE-BYPS-0-130000: BYPASS: System going out of Bypass mode.

Explanation    The load on the Content Engine may have reduced, and the system is switching out of bypass mode.

Recommended Action    No action is required.

BYPS-1

Error Message    CE-BYPS-1-130006: BYPASS: Module [module] is unable to handle the load.

Explanation    The specified module is heavily overloaded and is in a critical state.

Recommended Action    Reduce the load on the Content Engine. A reboot may be required to make sure the Content Engine has not become unstable.

BYPS-4

Error Message    CE-BYPS-4-130002: BYPASS: System going into Bypass mode.

Explanation    The load on the box may have gone above its maximum limit. The device will bypass new connections.

Recommended Action    Reduce the load or add additional Content Engines to handle the load. The Content Engine may become unstable if it gets overloaded.

Error Message    CE-BYPS-4-130003: BYPASS: sysdb_item_set() failed: return value is 
[error].

Explanation    The overload state could not be saved in the data server. The device state could be incorrectly displayed.

Recommended Action    If this message appears frequently, contact Cisco TAC.

Error Message    CE-BYPS-4-130004: BYPASS: Module [module] not registered due to bad 
name.

Explanation    The specified module could not register its overload state. The module state could be displayed incorrectly.

Recommended Action    If this problem occurs frequently, contact Cisco TAC.

Error Message    CE-BYPS-4-130005: BYPASS: Module [module] not registered successfully.

Explanation    The specified module could not register its overload state. The module state could be displayed incorrectly.

Recommended Action    If this problem occurs frequently, contact Cisco TAC.

BYPS-5

Error Message    CE-BYPS-5-130001: BYPASS: System going Offline BYPASS: reload to 
return to Online state.

Explanation    The Content Engine is going offline because of overload.

Recommended Action    Reboot the Content Engine to bring it back to a stable state.

BYPS-6

Error Message    CE-BYPS-6-130007: OVERLOAD: Preload did not receive overload message. 
But Preload seems to be running.

Explanation    Preload was not informed of an overload condition. The Content Engine could become overloaded if preload begins.

Recommended Action    If preload is not running or is not configured, ignore this message. If preload is enabled and running, call Cisco TAC.

Cache Messages

This section contains cache messages.

CACHE-2

Error Message    CE-CACHE-2-140001: HTTP proxy fails at startup: [failure description].

Explanation    A critical error occurred at startup when the HTTP proxy requested system ID resources.

Recommended Action    HTTP proxy will be restarted automatically. If the problem persists, reboot the Content Engine. Collect technical support information, and contact Cisco TAC.

Error Message    CE-CACHE-2-140002: HTTP proxy fails at startup: [failure description].

Explanation    A critical error occurred at startup when the HTTP proxy requested virtual address space.

Recommended Action    HTTP proxy will be restarted automatically. If the problem persists, reboot the Content Engine. Collect technical support information, and contact Cisco TAC.

Error Message    CE-CACHE-2-140003: HTTP proxy fails at startup: [failure description].

Explanation    A critical error occurred at startup when the HTTP proxy requested virtual memory resources.

Recommended Action    HTTP proxy will be restarted automatically. If the problem persists, reboot the Content Engine. Collect technical support information, and contact Cisco TAC.

Error Message    CE-CACHE-2-140004: HTTP proxy fails at binding to tcp ports: [failure 
description].

Explanation    A critical error occurred at startup when the HTTP proxy failed to bind on specific ports.

Recommended Action    HTTP proxy will not accept requests from ports that have the problem. HTTP continues to run and serve traffic on other ports. Reboot the Content Engine. If the problem persists, collect technical support information, and contact Cisco TAC.

Error Message    CE-CACHE-2-140006: HTTP proxy fails on call to socket listen on a tcp 
port.

Explanation    A critical error occurred at startup when the HTTP proxy failed to start listening on a specific port.

Recommended Action    HTTP proxy will not accept requests from ports that have the specified problem. The proxy continues to run and serve traffic on other configured ports (if any). Enter the show services ports <port-number> command to see which application is using the particular port, and modify the configuration accordingly.

CACHE-3

Error Message    CE-CACHE-3-140005: HTTP proxy failed to load third party plugin 
library.

Explanation    A third party plugin library failed to load because the proxy failed to listen to a port and add the plugin.

Recommended Action    The HTTP proxy will restart but without the third party plugin. The plugin function will not be available to the HTTP proxy. Collect technical support information, and contact Cisco TAC.

Content Delivery Network File Server Messages

This section contains content delivery network file server (CDNFS) messages.

CDNFS-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-CDNFS-n-480000: [message] 

Explanation    Information relating to CDNFS file handling is being logged. Many of these messages are informational only. Depending on the specific message and severity, a problem may be occurring.

Recommended Action    Most messages do not require any action. If specific problematic behavior is seen (such as channel content not being replicated or not being served), then contact Cisco TAC.

Error Message    CE-CDNFS-n-480001: [message] 

Explanation    An internal URL-specific metadata file on disk was found to be truncated (possibly of length 0).

Recommended Action    The system should recover automatically. If content fails to replicate, enter the cdnfs cleanup. If the problems persists, contact Cisco TAC.

Error Message    CE-CDNFS-n-480002: [message] 

Explanation    An internal URL-specific metadata file was opened using a particular lookup file. When the file was opened, the URL stored in the file did not match the look up URL. File system could be corrupted.

Recommended Action    If content fails to replicate or fails to be playable, contact Cisco TAC.

Error Message    CE-CDNFS-n-480003: hit limit on number of UNS-UFM table entries... 

Explanation    Too many CDNFS entries were created. The limit is currently 1 million files. However, certain internal features also create CDNFS entries on an automated basis, and, possibly due to a bug in the code for these other features, too many CDNFS entries have been created and not cleaned up.

Recommended Action    Ensure that customer website channels do not contain over 1 million URLs. If the problem persists, contact Cisco TAC.

Error Message    CE-CDNFS-n-480004: less than <number> bytes of unreserved space... 

Explanation    The available disk space is insufficient for creating a CDNFS entry (a URL).

Recommended Action    Ensure that there is sufficient CDNFS disk space assigned for the channels in use. Check that no disk drives have failed. Enter the show statistics cdnfs command for more information on current CDNFS usage. If the problems persists, for example, if channel content fails to replicate, contact Cisco TAC.

Error Message    CE-CDNFS-n-480005: count not find a usable filesystem... 

Explanation    No file system is available for storing a CDNFS entry (a URL).

Recommended Action    Ensure that sufficient CDNFS disk space is assigned for the channels in use (enter the show statistics cdnfs and show disks commands for current information). Verify that no disk drives have failed. If the problem persists, contact Cisco TAC.

Error Message    CE-CDNFS-n-480006: xact_replay: [message] 

Explanation    An ongoing transaction is being replayed to completion upon startup of the UNS-server subsystem. This message is informational.

Recommended Action    No action is required.

Error Message    CE-CDNFS-<severity>-480007: [message] 

Explanation    At startup, information about CDNFS file systems is printed. These messages are informational.

Recommended Action    No action is required.

Error Message    CE-CDNFS-n-480008: unsfs.c: non-zero sequence number... 

Explanation    The system encountered an internal metadata file with a non-zero sequence number in its filename. This situation may indicate file system corruption.

Recommended Action    If CDNFS content fails to replicate, content is not properly servable. Contact Cisco TAC.

Common Internet File System Server Messages

This section contains common internet file system server (CIFSS) messages.

CIFSSVR-3

Error Message    CE-CIFSSVR-3-207501: CDNFS must be configured to enable Windows 
sharing (CIFS) server.

Explanation    A content delivery network filesystem (CDNFS) needs to be configured and available for use for the CIFS server feature of ACNS to be enabled.

Recommended Action    Configure CDNFS before enabling CIFS server.

Cleanup Messages

This section contains cleanup messages.

CLEAN-AD-2

Error Message    CE-CLEAN-AD-2-210101: Failed to make Database connection 

Explanation    The system was unable to connect to a database during Active Directory (AD) cleanup.

Recommended Action    Troubleshoot the database: review errorlogs and enter the show cms database commands. Check the overall system status and retry to connect to the database.

Error Message    CE-CLEAN-AD-2-210102: Problem with UNS operation. [Error] 

Explanation    The system was unable to connect to the unified name server (UNS) during AD cleanup.

Recommended Action    Troubleshoot CDNFS using related debug commands (such as show stat cdnfs commands). Also, review the syslog to see if disk hardware and/or RPC system has any problem. Fix problem and retry the UNS operation.

Error Message    CE-CLEAN-AD-2-210103: Error with Database tables 

Explanation    Some of the tables that were accessed by AD do not exist.

Recommended Action    Troubleshoot the database (check errorlogs) for missing tables. Possible reasons for the error in database tables include upgrade/downgrade issues, disk problems, or error in communicating with CDM. Fix the problems and retry connecting to the database.

Error Message    CE-CLEAN-AD-2-210104: Error during Memory allocation 

Explanation    The malloc operation failed while cleaning up the AD.

Recommended Action    Attempt to clean up AD later. If the problem persists, reboot the Content Engine and retry the operation.

Error Message    CE-CLEAN-AD-2-210107: Error getting list of channels for orphan 
content [Error] 

Explanation    While cleaning up AD the system detected orphaned content that did not have corresponding channels.

Recommended Action    This message is a log alert. Check the specific database error, and take action accordingly. Possible action includes checking DB errorlogs, and performing CMS database maintenance and recovery.

Error Message    CE-CLEAN-AD-2-210108: Error in AD process. [INFO] 

Explanation    The system was unable to start or stop the AD process.

Recommended Action    This message is a log alert. Use the acquisition-distribution stop command and try the AD process again.

Error Message    CE-CLEAN-AD-2-210109: AD Cleanup called with incorrect argument. 
[INFO] 

Explanation    An AD cleanup command was executed with an incorrect argument.

Recommended Action    This message is a log alert. Check the arguments entered, and retry.

Error Message    CE-CLEAN-AD-2-210110: AD-UNS Cleanup completed 

Explanation    AD-UNS cleanup was completed successfully.

Recommended Action    This message indicates log information. No action is required.

Error Message    CE-CLEAN-AD-2-210111: UNS operation error. [INFO] 

Explanation    An error occurred during a UNS operation.

Recommended Action    This message indicates a log alert. If the problem persists, check the specific CDNFS error returned, troubleshoot CDNFS (for example, check if CDNFS is running out of space, if the UNS server is down, or if the disk is corrupted), and take action accordingly and retry the operation.

Error Message    CE-CLEAN-AD-2-210112: Error restarting AD 

Explanation    An error occurred when trying to restart the AD process.

Recommended Action    This message indicates a log alert. Check the errorlog/cli-util-errorlog.current file for details about the error. Take the required action, and try again.

Command Line Interface Messages

This section contains command line interface messages.

CLI-2

Error Message    CE-CLI-2-170001: [Procedure]: opendir([dirname]).

Explanation    The opendir() function failed in the Exec mode.

Recommended Action    Log out and login again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170002: [Procedure]: opendir(<dirname>).

Explanation    The opendir() function failed in the Exec.

Recommended Action    Log out and login again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170008: CLI:sysdb_bind failed in cfs_clear error = [dec]. 

Explanation    The command could not establish a connection with the data server.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170009: CLI:sysdb_bind failed in cfs_sync, error = [dec].

Explanation    The command could not establish a connection.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170010: CLI:sysdb_bind failed in cfs_mount, error = [dec].

Explanation    The command could not establish a connection.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170011: CLI:sysdb_bind failed in cfs_unmount, error = [dec].

Explanation    The command could not establish a connection.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170016: [str]: failed to pick up startup-configuration: [cmd] 
= ([dc],[dc]).

Explanation    The system was unable to retrieve the startup-configuration.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CLI-2-170017: Can not open interface stat file to read.

Explanation    The interface statistics file is missing.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170018: Error when extracting interface status for [dc].

Explanation    The system was unable to retrieve statistics for a specific interface.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170019: failed when reading interface stat file <str>.

Explanation    The system failed to read the interface statistics file.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170020: [str].

Explanation    The message states the error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CLI-2-170026: Failed to delete old gateway from route table (no, 
no).

Explanation    The software failed when the system attempted to remove the previously configured default gateway.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CLI-2-170027: Failed to configure the default gateway (no, no).

Explanation    The software failed when the system attempted to configure the new default gateway.

Recommended Action    Verify that the default gateway is valid and correct. Attempt to reconfigure the gateway. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170028: Failed to modify default gateway in sysconfig (no).

Explanation    The software failed when the system attempted to configure the new default gateway.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CLI-2-170029: Failed to stop evaluation for <string>, ret <number>.

Explanation    The system could not stop evaluation for application. The application is usually WMT, RealProxy, RealSubscriber, or Multicast.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170033: populate_ds: verifier registration failed for 
<string> error = <num> (errno = <num>/<string>).

Explanation    Some commands are invalid. Invalid commands will not work.

Recommended Action    If this problem appears frequently, contact Cisco TAC.

Error Message    CE-CLI-2-170036: rule_operation_ds_rule(): rule table is NULL, Cannot 
read any rules.

Explanation    Rules could not be read.

Recommended Action    Try again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170037: rule_operation_ds_pattern(): Invalid rules pattern, 
pattern structure corrupted.

Explanation    There is an error in the rules pattern.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170038: rule_item_action_string(): Invalid rules action, 
Action structure corrupted.

Explanation    The rules action could not be determined.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170039: print_valid_patterns(): Invalid rules action, action 
structure corrupted.

Explanation    The rules action could not be determined.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170040: rule_action_string(): Invalid rules action, action 
structure corrupted.

Explanation    The rules action could not be determined.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170041: rule_pattern_string(): Invalid rules pattern, pattern 
structure corrupted.

Explanation    An error occurred involving the rules pattern.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170042: rule_item_pattern_string(): Invalid rules pattern, 
pattern structure corrupted.

Explanation    An error occurred involving the rules pattern.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170054: running-config has <num> line(s).

Explanation    An error occurred in generating the running configuration. This error could be the result of entering the copy running-config command or similar commands.

Recommended Action    Try entering the show running-config command again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170057: running-config is not text /tmp/last_running_config:) 

Explanation    An error occurred in generating the running configuration. This error could be result of entering the show running-config command or similar command.

Recommended Action    Make sure there are no non-ASCII characters in the running-configuration. Try to enter the copy running-config command again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-2-170058: get_config: failed to (pickup | save) initial (disk 
| CLI) configurations (num, num). 

Explanation    The system encountered errors when applying the configurations specified at bootup.

Recommended Action    All configurations that are generated should be available on the disk. Compare the saved configuration and the running-configuration, and reconfigure the commands that are missing from the running-configuration. Then, save the configuration to the flash by entering the copy running-config startup-config command.

Error Message    CE-CLI-2-170069: Memory size (<num> bytes) is too small, expected 
<num>.

Explanation    The physical memory size on the system is smaller than expected. This condition usually means that a memory DIMM module is faulty.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CLI-2-170074: ver_port_channel_load: Can not open bond_mode file.

Explanation    The load balancing method configuration for a port channel has failed.

Recommended Action    Remove and reconfigure the port channel load balancing method. If the problem persists after a reboot, contact Cisco TAC.

CLI-3

Error Message    CE-CLI-3-170000: Can't bind to SysDB at "ENABLE_CFG_PREFIX" error 
<str>.

Explanation    The command could not connect to the data server.

Recommended Action    Log out and log in again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170003: File [filename] has problem: <error>.

Explanation    File operations (open, write) failed.

Recommended Action    Log out and log in again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170006: Can not open [filename] file, errno: [dc].

Explanation    The system failed to open memory configuration template file.

Recommended Action    Retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170012: CLI:Copy [str] to SS failed. status = ([dec],[dec]). 
Ignore if you didn't change RealProxy config. 

Explanation    Safe manager could not copy files.

Recommended Action    If the RealProxy configuration has not changed, ignore this message. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170013: [cmd] failed: status = ([dc],[dc]).

Explanation    The command failed.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170014: Your file system is unmounted, but [str] is not empty.

Explanation    The system was unable to delete the mount point.

Recommended Action    Reboot the Content Engine and retry the operation. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170015: General error when deleting [str], errorno = [dc].

Explanation    The system was unable to delete the mount point.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170020: Can't read memory.config, so memory cap for Real Proxy 
is default <str>.

Explanation    The system was unable to read Mmemory.config.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170021: Can't open file [filename] for reading: [error].

Explanation    The file failed to open for reading.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170022: CDP platform is unknown.

Explanation    The expected CDP information could not be found.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170023: Can't open file [filename] for writing.

Explanation    The file failed to open for writing.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170024: Hostname string length is incorrect.

Explanation    The hostname string length is incorrect.

Recommended Action    Ensure that the length of the hostname is within the specified limits and retry the operation.

Error Message    CE-CLI-3-170031: writing to mediafs split file failed. Can't open file.

Explanation    The system was unable to write new WMT and Real ratios into history file (in mediafs).

Recommended Action    If the problem appears frequently, contact Cisco TAC.

Error Message    CE-CLI-3-170034: NOTE: populate_ds: unable to set default value via 
verifier for <string>, rc = <num>; continuing.

Explanation    The default value of some configuration items could not be set.

Recommended Action    If the problem appears frequently, contact Cisco TAC.

Error Message    CE-CLI-3-170043: ver_webserver: SIGTERM received.

Explanation    The process received a termination signal received by process.

Recommended Action    If the problem appears frequently, contact Cisco TAC.

Error Message    CE-CLI-3-170044: ver_webserver: signal(SIGTERM, ...) failed. 

Explanation    The process could not issue a SIGTERM.

Recommended Action    If the problem appears frequently, contact Cisco TAC.

Error Message    CE-CLI-3-170052: Failed to recreate etc_hosts <num, num>.

Explanation    The system failed to recreate an important internal file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CLI-3-170055: Copy running-config to startup-config failed. 
status(<num>.<num>). 

Explanation    An error occurred in copying the running-configuration to the startup-configuration.

Recommended Action    Enter the copy running-config command again. This problem is mostly transient. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170056: Show running couldn't access dataserver rc=<num>.

Explanation    An error occurred in retrieving the running-configuration.

Recommended Action    Enter the copy running-config command again. This problem is mostly transient. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170059: [application] could not open temp file (errmsg).

Explanation    The specified application could not open a temporary file. The reason is given in the message.

Recommended Action    Retry the operation (configuration). If the reason for the error is that a volume is full, try to clean up the disk volume.

Error Message    CE-CLI-3-170060: Default Gateway CLI retry proc failed during route 
config (%d, %d).

Explanation    The background process that configures the default gateway experienced an error when attempting to configure a route. Error codes are given in the message.

Recommended Action    Unconfigure and reconfigure the ip default-gateway command.

Error Message    CE-CLI-3-170061: Netrcm callback could not be invoked due to fork 
failure. 

Explanation    Internal processes could not be notified of default gateway IP changes.

Recommended Action    Unconfigure and reconfigure the ip default-gateway command.

Error Message    CE-CLI-3-170062: CLI [identifier] will be retried in the background.

Explanation    The [identifier] command was not configurable but will be retried in the background. The problem occurs if the command has a dependency that is not satisfied at the time of configuration but may be satisfied at a later time, for example, network connectivity.

Recommended Action    No action is required.

Error Message    CE-CLI-3-170063: Fork Failed - [additional info].

Explanation    An internal command process could not start another process and may be unable to complete an operation. This operation can be identified by the additional information included in the syslog message. This problem could occur due to system resource constraints.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Unconfigure and reconfigure the associated command for the feature to work correctly.
2. Some other process may be using system resources. Verify correct operation of that process.
3. Inspect syslog and technical support information.

Error Message    CE-CLI-3-170064: Ipchains modification failed: [message]. 

Explanation    A change in a WCCP service or l4-switch configuration could not be completed because an internal packet redirection rule could not be added or deleted. More specific information is available in the message.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Unconfigure and reconfigure the WCCP or l4-switch service.
2. If the problem persists, disable and enable WCCP.
3. If the problem persists, try rebooting the Content Engine and reconfiguring the CLI.

Error Message    CE-CLI-3-170066: CLI [cli] is deprecated [message]. 

Explanation    The command entered is deprecated in this release. The command is accepted, but it is being translated to the new format. The [message] will give more specific information for the command entered.

Recommended Action    Enter the show running-config command to make sure the translation is the same as the information that is mentioned in [message]. If not, contact Cisco TAC.

Error Message    CE-CLI-3-170067: Could not open <filename> for reading/writing: 
<error>.

Explanation    A system file that needs to be updated to modify an IP configuration could not be opened.

Recommended Action    Try the command again. If the problem persists, reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170071: Failed to allocate/deallocate port for the 
application].

Explanation    Port failed to be allocated or deallocated for the particular application. The port may already be in use.

Recommended Action    Try the command again. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-CLI-3-170072: Unknown application.

Explanation    An unknown application was encountered.

Recommended Action    Try the command again. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-CLI-3-170073: Unlock/lock operation on the file [filename] failed. 

Explanation    The specified file could not be locked or unlocked.

Recommended Action    Log out and log in again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170076: [cli component]: Failed to execute the command due to 
accounting problem.

Explanation    The AAA accounting of the command could not be performed. So the command could not be executed.

Recommended Action    Verify that the accounting server is operating correctly and that it can be reached by the device. Try the command again. If the problem persists, reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-3-170078: ip route CLI retry proc failed during route config 
(%d, %d) 

Explanation    The background process that configures the static route, experienced an error while attempting to configure a route. Error codes are included in parenthesis.

Recommended Action    Unconfigure and reconfigure the IP route CLI.

Error Message    CE-CLI-3-170079:   Encountered incorrect advanced bandwidth 
configuration file: ss(%s) 

Explanation    While saving the advanced bandwidth configuration file to safe state disk partition, incorrect configuration file name found.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CLI-3-170500:   Print Services running when print-services auth is 
disabled 

Explanation    Print services (Print Spooler and Print Server) are already enabled when print services authentication is about to be disabled from CLI.

Recommended Action    Print services will be automatically disabled.

CLI-4

Error Message    CE-CLI-4-170068: Warning! Old(<num>) != current(<num>) <filename>.

Explanation    The value read from a system file did not correspond to the value stored in the device data repository.

Recommended Action    No action is required.

CLI-5

Error Message    CE-CLI-5-170005: CDP-EV: No more interfaces running CDP - removing CDP 
process.

Explanation    This message gives the CDP status.

Recommended Action    No action is required.

Error Message    CE-CLI-5-170007: Wrong arguments. 

Explanation    The memory configuration program received the wrong number of arguments.

Recommended Action    Retry the command. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-5-170032: Syslog cleared.

Explanation    The syslog was cleared of old entries.

Recommended Action    No action is required.

Error Message    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.

Explanation    Auto registration is currently enabled on this interface, and it needs to be disabled before the IP address or DHCP configuration can be made.

Recommended Action    No action is required.

Error Message    CE-CLI-5-170046: Disabling auto registration.. (num, num).

Explanation    The Content Engine is not registered with the CDM. When carrying out IP address or DHCP configuration, the system disabled auto registration.

Recommended Action    No action is required.

Error Message    CE-CLI-5-170047: Could not load kernel module [module name]. 

Explanation    The specified kernel module could not be loaded. Information provided by a command may be incomplete.

Recommended Action    Try the command again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-5-170048: Could not unload kernel module [module name]. 

Explanation    The specified kernel module could not be unloaded.

Recommended Action    Try the command again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-5-170049: Could not read proc interface for smbios. 

Explanation    The system was unable to read the process interface to smbios. The information provided by the command may be incomplete.

Recommended Action    Try the command again. If the problem persists, contact Cisco TAC.

Error Message    CE-CLI-5-170050: Cisco ACNS starts booting.

Explanation    This message is informational and indicates system reboot in the syslog.txt

Recommended Action    No action is required.

Error Message    CE-CLI-5-170051: create_etc_hosts.sh: <message>.

Explanation    These messages are informational and are displayed when a new IP address, new hostname, or domain name is configured.

Recommended Action    No action is required.

Error Message    CE-CLI-5-170053: Recreated etc_hosts <num, num>.

Explanation    An important internal file was successfully recreated.

Recommended Action    No action is required.

Error Message    CE-CLI-5-170065: Setting <pathname> to be <type> (dhcp=<number>).

Explanation    This message is informational. Interfaces are identified with types and recorded in an internal database.

Recommended Action    No action is required.

Error Message    CE-CLI-5-170070: Memory size (<num> bytes) is too big, expected <num>.

Explanation    The system physical memory size is bigger than expected. This message usually shows up on unsupported pre-FCS systems. The end user should not see it.

Recommended Action    If the problem is seen at customer site, contact Cisco TAC.

Error Message    CE-CLI-5-170077: informational messages to find safestate failures

Explanation    These messages are informational and are displayed when populate_ds is started.

Recommended Action    No action is required.

CLI-6

Error Message    CE-CLI-6-170030: Stopped evaluation for <string>.

Explanation    The system stopped the evaluation for the application.

Recommended Action    No action is required.

Error Message    CE-CLI-6-170075: config.c: Failed to set signal handler for SIGPIPE to 
SIG_IGN. 

Explanation    The initialization of the config shell command experienced difficulties with a standard system call.

Recommended Action    None. This information may be useful for diagnosis in the context of other problems encountered on the device.

CLI-7

Error Message    CE-CLI-7-170025: [CLI debug message] 

Explanation    These messages are informational and are displayed by the debug command.

Recommended Action    No action is required.

Error Message    CE-CLI-7-170035: <various messages>.

Explanation    These messages are informational and are the output of the debug command.

Recommended Action    No action is required.

Content Management Service Messages

This section contains content management service messages.

CMS-0

Error Message    CE-CMS-0-700003: <exception-name> [: <exception-message>]: 
<stacktrace> 

Explanation    An error has caused the program to exit.

Recommended Action    If this problem occurs frequently or under specific circumstances, contact Cisco TAC.

CMS-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-CMS-n-700001: <message> 

Explanation    An event has occurred for which no further explanation has been provided.

Recommended Action    No action for this event has been documented.

Error Message    CE-CMS-n-700002: <exception-name> [: <exception-message>]: 
<stacktrace> 

Explanation    An unhandled problem was encountered.

Recommended Action    If this problem occurs periodically, it can be ignored. If it repeats frequently, contact Cisco TAC.

CMS-4

Error Message    CE-CMS-4-701001: Software image downgrade detected. 

Explanation    A software image downgrade has been detected by the CMS software. A database downgrade is required to enable CMS services.

Recommended Action    Use the cms database downgrade command to perform the database downgrade.

Error Message    CE-CMS-4-701002: Error executing downgrade script. 

Explanation    A CMS downgrade script could not be executed.

Recommended Action    Verify that the specified script is a valid downgrade script. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-701003: Error setting permissions for emdb data and log files 

Explanation    The system was unable to set permissions for database data and log files.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-701004: Synchronization of device local CLI configuration 
with device CDN configuration on CDM has been disabled or enabled 

Explanation    This message is not an error. This message is a result of the exec command cms lcm (enable|disable).

Recommended Action    No action is required.

Error Message    CE-CMS-4-704001: register(): ClassNotFoundException raised - 
[exception] 

Explanation    Java Virtual Machine (JVM) could not find a required unicorn class during ConsumerAdapter.register().

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-704002: No BoxConfig is found in store 

Explanation    The database was not initialized.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-704003: Timeout when setup a rpcConnection to UNS 

Explanation    The UNS server was not up.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705001: Store has not been initialized yet 

Explanation    The store has not yet been initialized.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705002: No CeConfig object for [id] 

Explanation    The CDM does not recognize the node-ID reported by the Content Engine.

Recommended Action    Reregister the Content Engine, by entering the cms deregister force and cms enable commands.

Error Message    CE-CMS-4-705003: No CeStatus object for [ceConfig] 

Explanation    The CDM does not have the status for a Content Engine with ceConfig.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705004: No report is found from CE's getUpdate request message 

Explanation    The getUpdate request from the Content Engine contains no information.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705005: report is null in CE's getUpdate request message 

Explanation    The report in the Content Engine getUpdate request contains no information.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705006: Invalid report: [node-id] [node-gen-id] 

Explanation    The report in the Content Engine getUpdate request is invalid.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705007: No CrConfig object for [id] 

Explanation    The CDM does not recognize the node-ID reported by the Content Router.

Recommended Action    Reregister the Content Router, by entering the cms deregister force and cms enable commands.

Error Message    CE-CMS-4-705008: No CrStatus object for [crConfig] 

Explanation    The CDM does not have the status for a Content Router with crConfig.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705009: No report is found from CR's getUpdate request message 

Explanation    The getUpdate request from the Content Router contains no information.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705010: report is null in CR's getUpdate request message 

Explanation    The report in the Content Router getUpdate request contains no information.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705011: Unable to preserve cli config while changing cdm role 

Explanation    The system was unable to preserve the command configuration while changing the CDM role.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705012: AControllerUtils.getCEStatus encounter Null register 

Explanation    The register has not yet been initialized.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705013: Node [id] claims to have a gen ID [genid] which is 
higher than CDM's [genId] 

Explanation    The Content Engine, Content Router, or standby CDM claim to have some data that is unknown to the primary CDM.

Recommended Action    Enter the following commands: cms database delete, cms database create, and cms enable.

Error Message    CE-CMS-4-705014: Request from an unknown node [id] 

Explanation    The CDM does not recognize the node.

Recommended Action    Find the node, and enter the cms deregister force commands on it.

Error Message    CE-CMS-4-705015: getConfigProperties(): wrong node object: [object] 

Explanation    The getConfigProperties() function received a wrong parameter.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705016: No Upgrade currently in progress for node [id] 

Explanation    The CDM does not have an ongoing upgrade for the node.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705017: CeConfig has no clusterId: [ceConfig] 

Explanation    The CeConfig has no cluster identification.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705018: No cluster exists in store with clusterId [id] 

Explanation    The CDM database does not have a cluster record for ID = id;

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705019: getListUpdates: set size was changed strangely 

Explanation    This messages indicates an internal error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705020: Could not find CE named > [name] 

Explanation    The CDM database does not have the specified Content Engine.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705021: Could not find the CeStatus associated with 
CeConfig#[id] 

Explanation    The CDM database does not have a CeStatus record corresponding to the CeConfig.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705022: Could not find CR named > [name] 

Explanation    The CDM database does not have the specified Content Router.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705023: Could not find the CrStatus associated with 
CrConfig#[id] 

Explanation    The CDM database does not have a CrStatus record corresponding to the CrConfig.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705024: Could not find CDM named > [name] 

Explanation    The CDM database does not have the specified CDM.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705025: Could not find the CdmStatus associated with 
CdmConfig#[id] 

Explanation    The CDM database does not have a CdmStatus record corresponding to the CdmConfig.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705026: ServantUI::whatPasswordsAreDefault received an 
unexpected Class type... 

Explanation    The ServantUI::whatPasswordsAreDefault received an unexpected class type.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705027: Going to be careful and alerting the user that all 
(system and this node) passwords are default 

Explanation    This message is an alert that all (system and this node) passwords are default.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705028: ConfigProperty [name] does not have a 
ConfigPropertyDefinition associated with it. Skipping... 

Explanation    The ConfigProperty is not defined.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705029: Bandwidth obj. get failed. id [id] 

Explanation    The CDM database does not have the specified bandwidth record.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705030: Can find Config Property: [name] 

Explanation    The CDM database does not have the ConfigProperty record.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705031: Attempting to add ConfigProperty [name] with invalid 
nodeType [nodeType] or sendToNode id [sendToNode] 

Explanation    The system is attempting to add the specified ConfigProperty. The ConfigProperty has the specified invalid node type or has the specified invalid send-to-node ID.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705032: address [addr] has no hostname

Explanation    The specified IP address is not reverse-resolvable.

Recommended Action    Make sure that there is a hostname corresponding to this IP address.

Error Message    CE-CMS-4-705034: CeConfig has no clusterId: [ceConfig] 

Explanation    The CeConfig has no cluster identification.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705035: DbUpgrade Backup record status failed to be set 
properly 

Explanation    The system was unable to configure the DbUpgrade backup record.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705036: No current DbUpgrade record found continuing with 
restore 

Explanation    The system could not find the current DbUpgrade record. The system is continuing with restore.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705037: DbUpgrade Table doesn't exist, creating table now. 

Explanation    The DbUpgrade table does not exist. The system is creating a table now.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705038: Error opening log file [exception] 

Explanation    The system cannot open the validation.log for storing the log details.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705039: Test user does not exist 

Explanation    The user does not exist in the database.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705040: Embedded database maintenance failed: 

Explanation    The database fails at maintenance.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705041: No BoxConfig object exists in store 

Explanation    The database has not been initialized.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705042: Unable to get own CdmConfig object with id [id] 

Explanation    The database does not have the specified CdmConfig object.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705043: Unable to find standby CDM's address 

Explanation    The database does not have the IP address of the standby CDM.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705044: No CdmConfig object for [id] 

Explanation    The CDM does not recognize the node-ID reported by the standby CDM.

Recommended Action    Reregister the standby CDM by entering the cms deregister force and cms enable commands.

Error Message    CE-CMS-4-705045: No CdmStatus object for [cdmConfig] 

Explanation    The CDM does not have the status of the standby CDM.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705046: No report is found from CDM's getUpdate request 
message 

Explanation    The getUpdate request from the standby CDM contains no information.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705047: report is null in CDM's getUpdate request message 

Explanation    The report in the CDM getUpdate request contains no information.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705048: No host parameter found in ProbeCdm request message 

Explanation    The CDM probe message contains no parameters.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705049: CDM assuming halted role: Multiple primary CDMs 
detected during probe from primary CDM at [host] 

Explanation    The system detected multiple primary CDMs.

Recommended Action    Select the CDM that should be primary and enter the cdm role primary command.

Error Message    CE-CMS-4-705050: CDM address points to itself, trying to use next 
available backup cdm address 

Explanation    The CDM IP address is configured to point to itself.

Recommended Action    Change the CDM IP address to the correct configuration.

Error Message    CE-CMS-4-705051: Can not get a free distribution message! 

Explanation    A free distribution message was not available.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-705052: Unable to send probe request to CDM [host] [exception] 

Explanation    The CDM was unable to connect to another CDM [host].

Recommended Action    Make sure that a network connection exists between the two CDMs.

Error Message    CE-CMS-4-705060: Unknown Update status: [status] returning false. 

Explanation    The CDM does not recognize the update status.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705061: Encountered a CmdUpdate not linked to either CeConfig 
or CrConfig. 

Explanation    The system encountered a CmdUpdate that is linked to neither the CeConfig nor to the CrConfig.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705062: Can't find object CeStatus.  Invalid ID# [CeStatusId] 

Explanation    The CeStatus object with the given ID does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705063: Can't find object CrStatus. Invalid ID# [CrStatusId] 

Explanation    The CrStatus object with the given ID does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705064: Can't find object CdmStatus. Invalid ID# 
[CdmStatusId] 

Explanation    The CdmStatus object with the given ID does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705065: Invalid nodeType [nodeType] in heartbeat message from 
[hostname]: [message] 

Explanation    The NodeType is not recognized by the CDM.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705066: Invalid number of system messages. 

Explanation    An invalid number of system messages exists.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705067: Cannot connect with URL: [url] 

Explanation    The system cannot connect with the URL.

Recommended Action    Make sure that the URL is valid and reachable.

Error Message    CE-CMS-4-705068: Coverage zone file [file] is not valid [error message] 

Explanation    The coverage zone file is not valid.

Recommended Action    Specify a valid coverage zone file.

Error Message    CE-CMS-4-705069: Unhandled AAADomain.EntityType: [entity type] 

Explanation    The system does not handle the specified AAADomain.EntityType.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705070: Can not store the CLI(CE/CR) update to CDM db. 

Explanation    The system is unable to store the command update on the CDM database.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705071: mgmtType is not valid for MgmtIncomingType enum. 

Explanation    The schema value is invalid.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705072: CDM cannot determine CE IP Address. 

Explanation    The notification failed because the CDM cannot determine the Content Engine IP address.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705073: An error occurred while opening the database update 
log file. 

Explanation    The system was unable to open the database update log file. The system uses the update log file to log upgrade and downgrade issues.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-705074: Version mismatch while processing update from the 
primary CDM. Updates discarded 

Explanation    The standby CDM and the primary CDM need to run on the same software version.

Recommended Action    Install the same ACNS software version on the primary CDM and the standby CDM.

Error Message    CE-CMS-4-706001: Sequence IDSET not found. 

Explanation    During the test for database existence the IDSET object ID generator was not found.

Recommended Action    This problem is an error only if the system fails later to create the database. In case the database is not created, contact Cisco TAC.

Error Message    CE-CMS-4-706002: Sequence GENSET not found. 

Explanation    During the test for database existence the GENSET generation ID generator was not found.

Recommended Action    This problem is an error only if the system fails later to create the database. In case the database is not created, contact Cisco TAC.

Error Message    CE-CMS-4-706003: Table not found. [table] 

Explanation    During the test for database existence the [table] database table was not found.

Recommended Action    This problem is an error only if the system fails to later create the database. In case the database is not created, contact Cisco TAC.

Error Message    CE-CMS-4-706004: Sequence IDSET not found. 

Explanation    During the test for database validity the IDSET object ID generator was not found.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706005: Sequence GENSET not found. 

Explanation    During the test for database validity the GENSET generation ID generator was not found.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706006: Table not found. [table] 

Explanation    During the test for database validity the [table] database table was not found.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706007: Error in ConsumerAdapter: cannot find class [class] 

Explanation    The consumer adapter getAllSince failed to find the specified class object.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706008: Error in ConsumerAdapter: cannot find class [class] 

Explanation    The consumer adapter getAllClass failed to find the specified class object.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706009: Relationship not found when loading [object] 

Explanation    The specified relationship was missing during the database load.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706010: Relationship set to an invalid null [object] 

Explanation    The specified relationship was found to have an unexpected empty value.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706011: Parent Relationship not found when loading [object] 

Explanation    The specified parent relationship was missing during the database load.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706012: Child Relationship not found when loading [object] 

Explanation    The specified child relationship was missing during the database load.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706013: Parent ID reference mismatch [object] 

Explanation    During a parent reference removal the parent object ID did not match the specified object.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706014: Object reference child doesn't contain inverse 
relationship for [object] 

Explanation    During a child reference removal the parent object ID did not match the specified object.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706015: Object reference not found in [object] 

Explanation    During a child reference removal the child object ID was not found.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706016: Object reference not found in [object] 

Explanation    During a child reference removal the child object ID was not found.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-706017: Error while removing table [table] 

Explanation    An error occurred while removing a database table.

Recommended Action    If the problem is anything other than that the table does not exist, contact Cisco TAC.

Error Message    CE-CMS-4-706018: hasExistingStore() did not find table [table] 

Explanation    During the check for an existing database table an exception occurred and the specified table was not found.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707001: Received an update not matching its Id from CDM. 

Explanation    The node ID in the update message does not match the Content Engine ID.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707002: Cannot find the cluster this CE belongs to. 

Explanation    Content Engine database did not have the cluster object to which the Content Engine belongs.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707003: Null Replication Status Handler 

Explanation    The replication status handler was not initialized or was terminated.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707003: Null FileSysHandler 

Explanation    The module FileSysHandler was not initialized or was terminated.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707004: ClassNotFoundException 

Explanation    The system cannot find Class com.cisco.unicorn.schema.ClusterConfig.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707006: Database does not have the BoxConfig object. 

Explanation    The database does not have the BoxConfig object.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707007: Database does not have the CeConfig for this CE. 

Explanation    The CDM has not sent the CeConfig object to the Content Engine.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707008: DiskQuota is null. 

Explanation    The value of the disk quota does not exist.

Recommended Action    Reconfigure the disk quota using the GUI. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-707009: Cannot retrieve legacy value. 

Explanation    The legacy value output from the legacy script is not a long value.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707010: Cannot delete the file. 

Explanation    The system cannot delete the specified file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-707011: Unable to obtain UnsAdapter reference. 

Explanation    The CMS module was unable to obtain a reference to the UnsAdapter module.

Recommended Action    Wait for 30 seconds, and then retry. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-707012: Error while invoking UNS RPC. 

Explanation    An error occurred while invoking a UNS RPC.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-709001: Cannot delete the file. 

Explanation    The system cannot delete the specified file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-709002: Cannot create or write a file. 

Explanation    The system was unable to create or write the specified file.

Recommended Action    Check the disk space. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-709003: ClassNotFoundException 

Explanation    The system could not find the specified class.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-709004: Cannot concatenate two files into a file 

Explanation    The system could not concatenate the specified files.

Recommended Action    Check the disk space. If no space is left, contact Cisco TAC.

Error Message    CE-CMS-4-709005: Cannot rename a file 

Explanation    The system could not rename the specified file.

Recommended Action    Check the disk space. If no space is left, contact Cisco TAC.

Error Message    CE-CMS-4-709006: Cannot copy a file 

Explanation    The system could not copy the specified file.

Recommended Action    Check the disk space. If no space is left, contact Cisco TAC.

Error Message    CE-CMS-4-709007: Box name, IP and/or Keepalive port are undefined 

Explanation    The Content Engine name, IP address and keepalive port are undefined.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-709008: NULL object 

Explanation    An unexpected null object was detected.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-709009: Wrong FileInfo type 

Explanation    Wrong file information type was detected.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-711001: Received async eProbeCdm message, skipping 

Explanation    The system received an incorrect envelope type in the message.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-711011: RMI interface was not bound 

Explanation    The RMI is used internally.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-711012: ConnectException while talking to other node 

Explanation    The system cannot connect to another node using the RMI. The RMI is used internally.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-711013: ConnectIOException while talking to node 

Explanation    An IO error occurred while the system was talking to other nodes using RMI. The RMI is used internally.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-712001: Cannot retrieve a reference to the Store 

Explanation    The system cannot connect to the database

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-712002: [detail of the exception] 

Explanation    An exception has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-712003: Invalid input: [Message] 

Explanation    Unexpected behavior.

Recommended Action    This is a bug. Contact Cisco TAC.

Error Message    CE-CMS-4-712004: RPC to [A&D/acquirer/meta-replicator] failed 

Explanation    The system cannot communicate with acquisition and distribution services. Services may be down.

Recommended Action    If acquisition and distribution services are running and the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-712005: Cannot retrieve a reference to DataFeedAgent 

Explanation    The system cannot connect to an internal module.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-712006: [detailed message] 

Explanation    The system encountered problems with messaging, such as an unexpected message type or content.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-712007: Replication Status Error 

Explanation    The system encountered an error in getting replication status.

Recommended Action    Restart acquisition and distribution using the acquisition-distribution stop command, and then enter the acquisition-distribution start command. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-CMS-4-713001: Unable to unlink file 

Explanation    The PCM module creates log files of changes for recovery purposes. When the current running configuration is written to the startup configuration, these log files are cleared.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713002: Failed to save cli config 

Explanation    Periodically, the management service preserves command configuration.

Recommended Action    Determine if there are other errors related to this problem. Contact Cisco TAC.

Error Message    CE-CMS-4-713003: Cli command failed 

Explanation    The command received from the CDM failed. Possible reasons could be an invalid hostname or an invalid IP address.

Recommended Action    Locate the output related to this command in the cms_* log file. Contact Cisco TAC.

Error Message    CE-CMS-4-713004: transaction log is empty in onRollbackUpdate 

Explanation    In some cases, the management service is unable to complete the transactions.

Recommended Action    Determine if there are related problems that occurred during the same period of time. Contact Cisco TAC.

Error Message    CE-CMS-4-713005: FAILED to clear cli config 

Explanation    When the management service receives a full update from the CDM, it clears existing command settings before applying the new configuration. This operation has failed.

Recommended Action    Determine if there are related problems that occurred during the same period of time. Contact Cisco TAC.

Error Message    CE-CMS-4-713006: ' Invalid property ...' or 'Invalid object...' 

Explanation    The object received from the CDM could not be processed.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713007: The active field of Bandwidth is null 

Explanation    The system received invalid bandwidth settings from the CDM.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713008: CfgFtpMaxttl read from dataserver has changed 
size/format 

Explanation    The data format and code are incompatible.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713009: CfgHttpMaxttl read from dataserver has changed 
size/format 

Explanation    The data format and code are incompatible.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713003: Object is null 

Explanation    A PCM hook executes a command that is related to a null object.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713003: PcmHandler is null 

Explanation    The PCM handler is null when CMS is executing a command.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713003: CLI string is null or blank 

Explanation    The APCM hook executes a null or blank command.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713003: show running-config exits with errors. 

Explanation    The show running-configuration command gives an error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713003: some list is null. 

Explanation    A schema object has a null list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713003: Can not understand CLI: [exception] 

Explanation    The LCM cannot understand the command.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-713016: Error accessing PCM state file: [file name] 

Explanation    The system was unable to access a PCM state file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-13017: CLI Error 

Explanation    The system was unable to execute a local command.

Recommended Action    Make sure that the command values are valid and try again. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-CMS-4-713018: Sprayer Bandwidth Hook Error 

Explanation    The system was unable to set the sprayer bandwidth.

Recommended Action    Ensure that the bandwidth settings are valid, and try again. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-715001: Error setting CDNFS from CE CLI. [exception details] 

Explanation    The CDNFS is set to less than the quota needed for all assigned channel(s).

Recommended Action    Correct the CDNFS settings and delete some channels or unassign the affected Content Engine from some channels.

Error Message    CE-CMS-4-715002: No definition for property [property name] 

Explanation    The configuration property is not defined.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715003: No action for property [property name] 

Explanation    No action has been specified for the configuration property.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715004: Type of a store does not support SqlConnection. 
Therefore not creating DataBase VIEWs! 

Explanation    The store type does not support the SqlConnection. The system was unable to create database views.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715005: [details of the SQL exception] 

Explanation    An SQL exception has occurred.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715006: IP ranges overlapped 

Explanation    Multiple multicast clouds are signed with overlapping IP address ranges.

Recommended Action    If the error is an input error, correct the IP address so that no overlapping exists.

Error Message    CE-CMS-4-715007: Drop user [user name] failed. [details of the 
exception] 

Explanation    The system cannot drop a database user.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715008: Failed Drop table of [table name]. [details of the 
exception] 

Explanation    The system cannot drop a database table.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715009: Store restore failed. 

Explanation    The system cannot restore the database.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715010: Store backup failed. [details of the exception] 

Explanation    The system cannot backup the database.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715011: Error while removing failed store backup. [details of 
the exception] 

Explanation    The system was unable to remove failed store backup.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715012: Could not create temp table for [table name] 

Explanation    The system was unable to create the temporary database table.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715013: Could not create replacement table [table name] 

Explanation    The system was unable to create the replacement database table.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715014: Could not re-insert data into table [table name] 

Explanation    The system was unable to reinsert data into the database table.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715015: Could not drop temp table for [table name] 

Explanation    The system was unable to drop the temporary database table.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715016: Sql Exec ... [sql] 

Explanation    The system was unable to execute the SQL.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715017: Upgrade failed to set not null on field. 

Explanation    The system was unable to set NULL on a field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715018: Failed to create SYS_MESSAGE_LOG index 

Explanation    The system cannot create the index for the system message log.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715019: PSqlStore VACUUM failed 

Explanation    The system cannot vacuum the database.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715020: [details of the error] 

Explanation    The system was unable to assign a Content Engine to a channel.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715021: ClusterConfig RdToClusterMap HashMap was not found 
for [Cluster Config ID] 

Explanation    The mapping file for the cluster is missing.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715022: Channel RdToClusterMap HashMap was not found for 
[Channel ID]

Explanation    The mapping file for the channel is missing.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715023: Unable to create ExpiresRecord for RdToClusterMap: 
[details of the exception] 

Explanation    The system was unable to create the expires record for the Content Engine assignment to channels.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715024: Expires record missing from store.[Channel ID] and 
[Cluster Config ID] 

Explanation    The expires record is missing from the store.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715025: Could not load the node.dat file 

Explanation    The node.dat file is either missing or is invalid.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715026: SchemaSetup: No CdmConfig objects found while trying 
to set CdmConfig Id: [node ID] active. 

Explanation    The system cannot find the CDM that is using the node ID.

Recommended Action    Make sure the CDM is registered. If the problem persists after successful registration, contact Cisco TAC.

Error Message    CE-CMS-4-715027: SchemaSetup: Unable to find CdmConfig object for this 
CDM; id: [node ID] 

Explanation    The system cannot find the CDM that is using the node ID.

Recommended Action    Make sure the CDM is registered. If the problem persists after successful registration, contact Cisco TAC.

Error Message    CE-CMS-4-715028: Could not load the system configuration file 

Explanation    The system is unable to load the system configuration file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715029: Database doesn't exist [database file name] 

Explanation    The system is unable to locate the database.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715030: Address [address] is allocated multiple times, 
deallocating from CE [CE ID] 

Explanation    The system deallocated the Content Engine because of multiple IP addresses.

Recommended Action    No action is required.

Error Message    CE-CMS-4-715031: Address [address] of CE [CE ID] is not in the internal 
subnet [subnet], deallocating 

Explanation    The system deallocated the Content Engine because of an invalid subnet.

Recommended Action    No action is required.

Error Message    CE-CMS-4-715032: This primary IP [primary IP] is not unique across the 
system 

Explanation    The primary IP address set by the command is not unique across the system.

Recommended Action    Correct the primary IP address so that it is unique across the system.

Error Message    CE-CMS-4-715033: The CDM encountered an error while validating 
configuration properties. 

Explanation    The system is unable to validate the configuration properties.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715034: The CDM encountered an error while attempting to close 
a database connection after validating configuration properties. 

Explanation    The system is unable to close a database connection after validating the configuration properties.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715035: The CDM encountered an error while attempting to 
remove a FactoryInfo record. 

Explanation    The system is unable to remove factory information records while creating a new table during the database update process. Factory information records are used for internal data tracking.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-715036: Invalid use-proxy-failover configuration; ignore 

Explanation    The service rule configuration for use-proxy-failover is invalid. Therefore, only the action type was updated from the use-proxy-failover to the use-proxy.

Recommended Action    Manually fix the service rule configuration. Check the syntax in documentation.

Error Message    CE-CMS-4-716001: [detail of the exception] 

Explanation    The system encountered an error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716002: UpdateMonitor's consumer can not be null on 
registration 

Explanation    The UpdateMonitors user is null on registration.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716003: UpdateMonitor's consumer can not be null on 
deregistration 

Explanation    The UpdateMonitor user is null on deregistration.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716004: Store has more than one BoxConfig objects. 

Explanation    The store has more than one BoxConfig object.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716005: BoxConfig is null. 

Explanation    The BoxConfig object contains no information.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716006: CeUpdateMonitor:processPostCommit(): genId is null. 

Explanation    The CeUpdateMonitor:processPostCommit(): genId function returns no information.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716007: Invalid value(s) inside [gStatusFile]. 

Explanation    The system encountered invalid values in the gStatus file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716008: Unable to remove update distribution file: 
[updateFile]. 

Explanation    The system was unable to remove the update distribution file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716009: Unable to connect to Host [host]:[port] [exception] 

Explanation    The system was unable to connect to the host.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716010: Unable to generate certificate hash. 

Explanation    The system was unable to generate the certificate hash.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716011: Certificate hash not found: [certificateHash]. 

Explanation    The system could not find the certificate hash.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716012: Update did not die when told to. 

Explanation    The system could not terminate the update when the command was given.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716013: Failed to retrieve Update after [retryTimes] times. 
Can not update [status]. 

Explanation    The system failed to retrieve an update after n attempts. The system cannot update the status.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716014: Error retrieving Update File. Upgrade Failed. 

Explanation    The system encountered an error while retrieving the update File. The upgrade operation failed.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716015: Software Upgrade/downgrade status: [status] due to 
version mismatch after box reload. 

Explanation    The software upgrade or downgrade operation failed because of a version mismatch after reboot.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716016: Software Upgrade/downgrade status: [status]. 

Explanation    This message displays the status of the software upgrade or downgrade operation.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716017: Error creating CDM IP file: [gCdmIpFilePath] 

Explanation    The system encountered an error while creating the CDM IP address file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716018: Aborting s/w downgrade. 

Explanation    The system is terminating the software downgrade operation.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716019: Software Upgrade/Downgrade: Initiated Command + [cmd] 

Explanation    The system initiated the specified command during the software upgrade or downgrade operation.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716020: Command [cmd] FAILED. 

Explanation    The specified command failed.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716021: Software Upgrade/Downgrade: Initiated reload force 
command 

Explanation    The system initiated the reload force command during a software upgrade or downgrade operation.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716051: Cannot get host address of primary controller from 
node.dat 

Explanation    The node.dat file does not include the IP address of the primary CDM.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716052: Cannot save the inactive CDM IP address to node.dat 

Explanation    The system was unable to save the node.dat file after it was modified.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716053: Error opening file NodeState.xml 

Explanation    The system was unable to open the file NodeState.xml for writing onto the file. A reason could be that the disk space is full.

Recommended Action    No action is required.

Error Message    CE-CMS-4-716054: The number of consecutive store failure excesses 
system limits (10) 

Explanation    The database failed more than the stipulated number of times.

Recommended Action    The system will restart after this failure. If the problem persists, hard reboot the Content Engine.

Error Message    CE-CMS-4-716055: Current primary CDM activation time stamp is older 
than this node's CDM time stamp. 

Explanation    The system clock is not synchronized with the CDM clock.

Recommended Action    Synchronize this node clock with CDM clock.

Error Message    CE-CMS-4-716056: Cannot decode the response from CDM. 

Explanation    The system could not decode the message from the CDM.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716057: Cannot get updates from the backup Controller. 

Explanation    The system could not get the update from the backup controller.

Recommended Action    Ensure that the backup CDM is on and is connected.

Error Message    CE-CMS-4-716058: RPC Exception prevents this machine from getting 
udpate from CDM. 

Explanation    The system could not get the update from the controller because of an RPC error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716059: Module thread failed 

Explanation    The Java thread failed for an unknown reason.

Recommended Action    No action is required. The Content Engine will reboot.

Error Message    CE-CMS-4-716060: Failed to redirect stdout and stderr, using default 

Explanation    The system failed to redirect the stdout and stderr.

Recommended Action    No action is required.

Error Message    CE-CMS-4-716061: Unknown Configure Property 

Explanation    The system received an unknown configuration property from the CDM.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716062: the group property does not have parent. 

Explanation    The group property does not have a parent.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716063: property is a parent, but does not hold a boolean 
value. 

Explanation    The parent property does not have a boolean value.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716064: MAC address is null 

Explanation    The machine has a null MAC address.

Recommended Action    Check the machine network configuration to see if the MAC address is set up. If yes, contact Cisco TAC.

Error Message    CE-CMS-4-716065: Unable to get dns name for primary interface ip. 

Explanation    The DNS name for the primary interface IP cannot be resolved.

Recommended Action    Check the DNS server to make sure that there is an entry for the primary IP address.

Error Message    CE-CMS-4-716066: Unable to FTP file from the remote FTP server 

Explanation    The system is unable to transfer a file from the remote FTP server using FTP. The problem could be because of the following reasons: the FTP server is not a valid server, the username or password is not valid, or the file does not exist.

Recommended Action    Verify the FTP server, and ensure that the username and password are correct. Ensure that the file exists.

Error Message    CE-CMS-4-716067: rpc call to ADCertMgr server failed after certain 
tries. 

Explanation    The ADCertMgr has terminated, or the rpc encountered an error while connecting to the ADCertMgr.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716068: Failed to read certificate from the file 

Explanation    The file does not contain a valid certificate.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-716069: Software Update Error 

Explanation    The system was unable to upgrade or downgrade the software.

Recommended Action    Ensure that the upgrade parameters are valid and that the network does not have any errors. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-716070: DataFeed Error 

Explanation    The system was unable to process a configuration update from the CDM.

Recommended Action    Ensure that the network has no errors. In general, this error is transient. If not, reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-716071: Restart Error 

Explanation    The system has encountered an error and a reboot is required to correct the error.

Recommended Action    If the Content Engine does not reboot itself, reboot the Content Engine.

Error Message    CE-CMS-4-716072: Clock mismatches between the primary CDM and this 
device. 

Explanation    The clock on the primary CDM and the clock on the Content Engine need to be synchronized with each other.

Recommended Action    Fix the clock either on the primary CDM or on the Content Engine.

Error Message    CE-CMS-4-718001: Unable to connect to dataserver 

Explanation    The system was unable to connect to the dataserver.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-718002: Failed to get statistics(...) 

Explanation    The system failed to get content services statistics from the data server.

Recommended Action    Ensure that the required content service is enabled. If the service is enabled and the corresponding show statistics command works, contact Cisco TAC.

Error Message    CE-CMS-4-718003: Invalid configuration value(<configuration parameter 
name>) 

Explanation    The management service received an incorrect configuration parameter.

Recommended Action    Reenable management service and reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-718004: Dataserver access error(...) 

Explanation    The management service was unable to get or to set the information in the data server.

Recommended Action    Reenable management service and reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-718005: Unable to find syslog fifo 

Explanation    The management service could not open the specified pipe to syslog.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-718006: I/O error while accessing syslog fifo file 

Explanation    The management service could not read from the syslog FIFO file.

Recommended Action    Restart the management service. If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-718007: CE [ce_id] clock is wrong or mismatch with CDM 

Explanation    Content Engine clock is wrong or there is a mismatch between the Content Engine and CDM clocks.

Recommended Action    Correct the Content Engine clock or the CDM clock.

Error Message    CE-CMS-4-719001: Store Hook Rollback has caused an exception. 

Explanation    During a CMS store rollback, the system encountered an error because of a store extension.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719002: AConnection.rollback() Rollback in progress ... 

Explanation    The system, while processing a transaction, encountered an error that caused the transaction to be rolled back.

Recommended Action    No action is required.

Error Message    CE-CMS-4-719003: AConnection processClose() caused the follow 
exception. 

Explanation    The system encountered an error while closing the store connection. Verify the exception stack trace in the log.

Recommended Action    No action is required

Error Message    CE-CMS-4-719004: AConnection.transactionThread not set. 

Explanation    A store connection was wrongly used by a processing thread.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719005: AConnection.transactionThread not set. 

Explanation    A store connection was wrongly used by a processing thread.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719006: AConnection.transactionThread not set. 

Explanation    A store connection was wrongly used by a processing thread.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719007: The number of references were less than the expected. 
[reference] 

Explanation    During object validation, the system received less than the specified number of references.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719008: The following number of references were found to be 
invalid.. [reference] 

Explanation    During object validation, the system found the specified references to be invalid.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719009: The following number of references were found to be 
invalid.. [reference] 

Explanation    During object validation, the system found the specified references to be invalid. [reference].

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719010: SQL error executing command [command] 

Explanation    The system encountered an error when terminating the specified SQL command.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719011: Force insert delete failed, [exception] 

Explanation    The system, when executing a command for the forced insertion of an object store, was unable to delete the object.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719012: Exception closing reallocated connection [exception] 

Explanation    The system encountered an error when attempting to close an old connection and reconnect to the database.

Recommended Action    This message is not an error, if the database is able to reconnect.

Error Message    CE-CMS-4-719013: Failed to connect using connect string [connection] 

Explanation    The system is unable to connect to the database.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719014: Trim DELETE_SINCE log failed   [exception] 

Explanation    The system encountered an error when maintaining the number of records in the deleted record log.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719015: Factory not found for [class] 

Explanation    The system, when reporting statistics, could not find the specified schema class factory.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719016: Error opening log file [filename] 

Explanation    The system, when reporting statistics, could not open the XML log file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719017: Error opening log file [filename] 

Explanation    The system, when reporting statistics, could not open the specified XML log file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719018: Object was found to be modified at the end of 
transaction, [objectId] 

Explanation    The system found the specified object in the still to be modified state at the end of a processing transaction.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719019: AStore.testModified() found modified object. 
[objectId] 

Explanation    The system found the specified object in the still to be modified state at the end of a processing transaction.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719020: SqlConnection.commit() found object in modified 
state. [objectId] 

Explanation    The system found the specified object in the still to be modified state at the end of a processing transaction.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719021: SqlConnection.rollback() Rollback in progress ... 

Explanation    The system encountered an error when processing a transaction. This error caused the transaction to be rolled back.

Recommended Action    No action is required.

Error Message    CE-CMS-4-719022: Sql Rollback failed. 

Explanation    The system encountered an error processing a rollback.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719023: Exception closing connection. [exception] 

Explanation    The system encountered an error when closing a connection.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719024: Connection reallocation failed. 

Explanation    The system encountered an error when reallocating a connection.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719025: SqlConnection.generateObjId Failed. [sqlcommand] 

Explanation    The SQL command failed when generating a new unique object ID.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719026: SqlConnection.generateNum Failed. [sqlcommand] 

Explanation    The SQL command failed when generating a new generation ID.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719027: SQL error in [sqlcommand] 

Explanation    The system encountered an error when performing an SQL query.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719028: An error occurred while writing to the database update 
file log. 

Explanation    The system encountered an error when writing to the database upgrade or downgrade log file.

Recommended Action    Contact Cisco TAC.

Error Message    Contact Cisco TAC.CE-CMS-4-719029: An error occurred while calculating 
a database column type. 

Explanation    The system encountered an error when calculating the type of a database column in an internal data structure.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719030: The specified downgrade script does not support the 
installed database version. 

Explanation    A downgrade script that does not support the currently installed database version was invoked.

Recommended Action    Download and execute a downgrade script that supports the previously-installed software version.

Error Message    CE-CMS-4-719031: Downgrade failed. 

Explanation    The system encountered an error occurred when processing a downgrade script. The system log contains additional information.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-719032: Constraint Error 

Explanation    The system encountered an error when processing invalid input values.

Recommended Action    Ensure that the input values are valid, and try again.

Error Message    CE-CMS-4-719033: Store Error 

Explanation    The system encountered an error when executing a transaction with the local data store.

Recommended Action    If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-CMS-4-719034: DeletedSince Id Class type not found, [className] 

Explanation    The system encountered an error when initializing the log of deleted objects.

Recommended Action    No action is required.

Error Message    CE-CMS-4-720001: retrieveMediaFilesInChannel: null channel; using id 
= [id] 

Explanation    The channel assigned to the playlist does not exist.

Recommended Action    No action is required.

Error Message    CE-CMS-4-720002: retrieveMediaFilesInChannel: null root CE; using chid 
= [chId] 

Explanation    The channel assigned to the playlist does not have a root Content Engine.

Recommended Action    Assign a root Content Engine to the playlist and try again.

Error Message    CE-CMS-4-720003: retrieveMediaFilesInChannel: null criteria 

Explanation    The channel assigned to the playlist does not have any criteria.

Recommended Action    No action is required.

Error Message    CE-CMS-4-720004: No RoutingConfigs in CDM. 

Explanation    The CDM database does not contain any RoutingConfig objects.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-720005: Not able to get the IP Address for node [nodeId] 

Explanation    The system is unable to get the IP Address for the device or the node.

Recommended Action    Enter the correct IP Address of the device or the node.

Error Message    CE-CMS-4-720006: [detail of the error] 

Explanation    The system encountered an error.

Recommended Action    No action is required.

Error Message    CE-CMS-4-720007: [detail of the exception] 

Explanation    The system encountered an error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-720008: Invalid parent config property record. UserSelectedId 
[id] should be the same as sendToNodeId [id]. 

Explanation    The parent configuration property record is invalid. The userSelectedId should match the sendToNodeId.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-721001: [error message] 

Explanation    The system encountered an illegal argument error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-721002: RMI connection failure: Rebinding 

Explanation    The system could not bind to the RMI. The system is trying again.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-721003: [path] is not specified in bypass set or 
serviceRightsMap 

Explanation    The system could not find the mapping to the right service map.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-721004: Error during system initialization on attempt [n] of 
[m]. 

Explanation    The system encountered an error during system initialization.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-722001: Error creating the parser 

Explanation    The system is unable to create a parser when executing an API.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-722002: bean lost from session, recreating 

Explanation    This error occurs only if the session data was lost, or the user opened multiple browsers using the same session.

Recommended Action    Close all browser windows accessing the CDM GUI. Open a new browser window. Open only one browser window with the CDM GUI.

Error Message    CE-CMS-4-722003: [detail of exception] 

Explanation    The system encountered an error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-722004: [detail of error] 

Explanation    The system encountered an error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-722005: Cannot receive writer 

Explanation    The system could not receive the writer when executing the API.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-722006: API servlet sendError() received null response 

Explanation    The system encountered an error when running the specified API.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-722007: Caught exception when APIs send an error [exception] 

Explanation    The system encountered an error when running the specified API.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-722008: [pageName] caught [exception] 

Explanation    The system encountered an error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-722009: RMI error communicating with CDM: Rebinding 

Explanation    The system encountered an error when the UI connected to the CDM.

Recommended Action    Ensure that the CMS process is running before accessing the GUI.

Error Message    CE-CMS-4-722010: System command timeout error 

Explanation    The system encountered an error when executing a system command.

Recommended Action    Ensure that there are no errors in the network, and try again. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-CMS-4-723001: [detail of the exception] 

Explanation    The system encountered an error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-723002: Illegal NumberFormatException found for property 
[key] = [value], defaulting to [default] 

Explanation    The number entered is invalid.

Recommended Action    No action is required.

Error Message    CE-CMS-4-723003: Invalid value for boolean property [key] = [value] 

Explanation    The boolean value entered is invalid.

Recommended Action    No action is required.

Error Message    CE-CMS-4-723004: IP_SOURCE_ADDR does not resolve to an IP address 

Explanation    The IP address entered is invalid.

Recommended Action    Correct the IP address.

Error Message    CE-CMS-4-723005: Missing environment variable CISCO_HOME 

Explanation    The environment variable is not set up correctly.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-723006: Missing environment variable NODE_TYPE 

Explanation    The environment variable is not set up correctly.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-723007: [command] passed timeout of [# of seconds], killing. 

Explanation    The system could not execute the command within the specified period.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-723008: Exited badly [command] [exit value] 

Explanation    The command did not execute correctly.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-723009: Unable to read seed from [random File] more than [# 
of bytes] bytes 

Explanation    The system encountered an error when getting a seed for random numbers.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-723010: [details of the SAX exception] 

Explanation    The system encountered a SAX error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-723011: Monitoring API Error 

Explanation    The system encountered an error when providing the monitoring statistics.

Recommended Action    Ensure that the parameters for getting the monitoring statistics are correct, and try again. If the problem persists, reboot the Content Engine.

Error Message    CE-CMS-4-723012: Thread safety release 

Explanation    An internal thread locking check failed, but the system was able to recover by releasing the lock.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-CMS-4-725001: Showing running config returns an error 

Explanation    The show running config command returns an error when doing the LCM.

Recommended Action    Contact Cisco TAC.

Error Message    CE-CMS-4-725002: LCM Error 

Explanation    The system encountered an error when processing the local configuration changes on the device.

Recommended Action    Ensure that the settings are valid, and try again. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

CMS-7

Error Message    CE-CMS-7-700000: <message> 

Explanation    The system has encountered an error.

Recommended Action    No action is required.

Common Extended Data Manager Messages

This section contains common extended data manager (EDM) messages.

COMMONEDM-4

Error Message    CE-COMMONEDM-4-185000: register_verifier: ver reg err (ret = [error 
number]).

Explanation    The common EDM could not register its verifier with the data server.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-COMMONEDM-4-185001: register_notifier: notifier reg err (ret 
=[error number]).

Explanation    The common EDM could not register its notifier with the data server

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-COMMONEDM-4-185002: get verification info err (ret=[error number]).

Explanation    The common EDM could not get information from the data server in the verifier.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-COMMONEDM-4-185003: get notification info err (ret=[error number]).

Explanation    The common EDM could not get information from the data server in the notifier.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-COMMONEDM-4-185004: could not create /tmp/syslogd_cw2kmode (ret = 
[errorcode], [description]).

Explanation    The common EDM could not create the specified flag file. The CiscoWorks 2000 mode of syslogd will remain unchanged.

Recommended Action    Attempt to enable and disable the CiscoWorks 2000 mode again. If the problem persists, contact Cisco TAC.

Error Message    CE-COMMONEDM-4-185005: could not unlink /tmp/syslogd_cw2kmode (ret = 
[errorcode], [description)].

Explanation    The common EDM could not unlink the specified flag file. The CiscoWorks 2000 mode of syslogd will remain unchanged.

Recommended Action    Attempt to enable and disable the CiscoWorks 2000 mode again. If the problem persists, contact Cisco TAC.

Error Message    CE-COMMONEDM-4-185006: could not open /tmp/syslogd_cw2k_timezone for 
writing (ret=[errorcode], [description]).

Explanation    The common EDM could open the timezone information file. The timezone information used by syslogd will remain unchanged.

Recommended Action    Attempt to change the timezone information again. If the problem persists, contact Cisco TAC.

Error Message    CE-COMMONEDM-4-185007: could not write to /tmp/syslogd_cw2k_timezone.

Explanation    The common EDM could not write to the timezone information file. The timezone information used by syslogd will remain unchanged.

Recommended Action    Attempt to change the timezone information again. If the problem persists, contact Cisco TAC.

Content Routing Messages

This section contains content routing messages.

CR-3

Error Message    CE-CR-3-180101: Memory allocation failure.

Explanation    The content routing module failed to allocate memory from the system. This failure can cause the content routing module to function improperly and may affect other software modules in the system. This message appears whenever a memory allocation failure of the content routing module occurs. This problem can be caused by a software error and requires investigation. The system should reboot the content routing module if a crash occurs and reboot the Content Engine, if necessary.

Recommended Action    Enter the show process memory command to confirm that the system memory has been used up. Rebooting the system provides an immediate workaround in most cases. To help debug this problem, collect the output of the show content routing route, show statistics content-routing all, and show process memory commands. Also, enable debug logging by entering the debug content-routing all, and logging disk priority debug commands for a while, when this problem occurs. Send the output of commands and all syslog files to Cisco TAC for further analysis.

Error Message    CE-CR-3-180301: Failed to open a connection to the data server after 
<num> tries. 

Explanation    The content routing module could not communicate with the data server module that stores system-wide configuration data. This can cause commands related to content routing to fail, including the show content-routing*, clear statistics content-routing*, show statistics content-routing*, and debug content-routing * commands. This message requires immediate attention and appears only when the content routing module starts up.

Recommended Action    Send all syslog files to Cisco TAC for further analysis.

Error Message    CE-CR-3-180303: Failed to register notifications at <string> - 
<string>.

Explanation    The content routing module has failed to register with the data server to be notified when any of the debug content-routing commands are executed. After this message appears, the content routing module keeps trying to register once every 60 seconds. This message occurs only when the content routing module starts up. This message is a notice level message if the problem occurs fewer than five times and is escalated to an error level message if it occurs more than five times. Ignoring this error message can cause failure of the debug content-routing commands.

Recommended Action    Restarting the node provides a temporary workaround. Send all syslog files to Cisco TAC for further analysis.

Error Message    CE-CR-3-180305: Failed to receive notifications from the data server 
at <string> - <string>.

Explanation    The content routing module has failed to receive data from the data server when the debug content-routing commands were executed. This error message appears when the debug content-routing commands are executed and an error occurs in the communication process. If this message appears only occasionally, it is an informational message. Otherwise, its appearance requires investigation, and the debug content-routing commands will always fail.

Recommended Action    If the debug content-routing commands always fail, rebooting the system should provide a temporary workaround. Send all syslog files to Cisco TAC for further analysis.

Error Message    CE-CR-3-180306: Failed to create thread at <string>.

Explanation    The content routing module has failed to create a thread. This message appears whenever the content routing module starts up and fails to create a thread. This error can significantly affect normal functioning of the content routing module and requires immediate attention.

Recommended Action    Rebooting the system may provide a temporary workaround. Send all syslog log files to Cisco TAC for further analysis.

Error Message    CE-CR-3-180311: Failed to get CLI action information from data server 
at <string> - <string>.

Explanation    The content routing module has failed to receive data from the data server when executing content routing-related commands other than the debug content-routing commands. This message appears whenever a single content routing-related command other than the debug content-routing command is executed and there is an error in communication. If this message appears only occasionally, it is an information level message. Otherwise, its appearance requires investigation, and content routing-related commands other than the debug content-routing commands will always fail.

Recommended Action    If content routing-related commands other than the debug content-routing commands always fail, rebooting the system should provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    CE-CR-3-180312: Failed to build response to data server at <string> - 
<string>.

Explanation    The content routing module has failed to build a response to the data server when executing content routing-related commands other than the debug content-routing commands. This message appears whenever a content-routing related command, other than the debug content-routing command, is executed and an error occurs in building a response. If this message appears only occasionally, it is an informational message. Otherwise, its appearance requires investigation, and content routing-related commands other than the debug content-routing commands will always fail.

Recommended Action    If content routing-related commands other than the debug content-routing commands always fail, rebooting the system should provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    CE-CR-3-180313: Failed to send response to data server at <string> - 
<string>.

Explanation    The content routing module has failed to send a response to the data server when executing content routing-related commands other than the debug content-routing commands. This message appears whenever a single content routing-related command other than the debug content-routing command is executed and an error occurs in responding to the data server. This error message is informational if it occurs only occasionally. Otherwise, its appearance requires investigation, and content routing-related commands other than debug content-routing will always fail.

Recommended Action    If content routing-related commands other than the debug content-routing commands always fail, rebooting the system should provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

CR-4

Error Message    CE-CR-4-180304: Failed to unregister notifications.

Explanation    The content routing module has failed to unregister from the data server to be notified when the debug content-routing* commands are executed. This error message occurs when the content routing module exits or when it tries to reregister after a communication error has occurred.

Recommended Action    No serious consequences result from this error. Send all syslog files to Cisco TAC for further analysis if some content routing commands cannot be executed.

Error Message    CE-CR-4-180307: Failed to free resources at <string> - <string>.

Explanation    The content routing module has failed to free resources when executing the debug content-routing commands. This message appears every time the debug content-routing commands are executed. The message may indicate failure of those commands and may affect subsequent execution of other content routing-related commands.

Recommended Action    Rebooting the system may provide a temporary workaround. Send the output of the show process memory and all syslog files to Cisco TAC for further analysis.

Error Message    CE-CR-4-180308: Failed to receive entire message at <string> - 
<string>.

Explanation    The content routing module has failed to receive data from the data server when executing commands related to content routing. This message appears whenever content routing-related commands are executed. This may indicate failure of the commands and may affect subsequent execution of other content routing-related commands.

Recommended Action    Rebooting the system may be a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    CE-CR-4-180202: Content Engine '<ce name>' is down (keepalives have 
stopped). 

Explanation    The content routing module has stopped receiving keepalives from the Content Engine specified in the message. The liveness state of the Content Engine changed to 'down' as a result, and no client requests will be routed to it until the content routing module once again receives keepalives from the Content Engine. This message is notice level only and should appear whenever notice level logging is enabled and a Content Engine state change occurs because the content routing module stops receiving keepalives from the Content Engine.

Recommended Action    Check the network connectivity between the Content Engine and the Content Router. Use a sniffer network analyzer to verify that DNS traffic is passing from the Content Engine to the Content Router and is successfully received by the Content Router. If the connectivity is satisfactory, check the state of the Content Engine on the Content Distribution Manager GUI to see if it is online and check the Content Distribution Manager syslog to look for messages that might indicate why the Content Engine went down. Finally, enter the show process memory command on the Content Engine to see if the crka-start.pl process is running. If you can find no reason for the error message, send all syslog information on the Content Engine and the output of the show cms info and show cms database content xml commands to Cisco TAC for further assistance.

Error Message    CE-CR-4-180302: Failed to close a connection to the data server at 
<string> <string>.

Explanation    The content routing module has failed to close a connection to the data server. This message appears only if the content routing module fails to close a connection to the data server. No serious consequences result from this error.

Recommended Action    Send all syslog files to Cisco TAC for further analysis if some content routing- related commands cannot be executed.

Error Message    CE-CR-4-180310: Failed to unregister from data server at <string> - 
<string>.

Explanation    The content routing module has failed to unregister from the data server for content routing-related commands other than the debug content-routing commands. This error message appears when the content routing module exits or when it tries to reregister after a communication error.

Recommended Action    No serious consequences result from this error. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

CR-5

Error Message    CE-CR-5-180102: Routing table has been rebuilt.

Explanation    The routing table of the content routing module has been rebuilt because of configuration changes. This message is informational only and should appear whenever a configuration change has occurred and information level logging is enabled.

Recommended Action    No action is required.

Error Message    CE-CR-5-180201: Content Engine '<ce name>' is up (keepalives have 
Started or resumed). 

Explanation    The Content routing module has started to receive keepalives from the Content Engine specified in the message. The liveness state of the Content Engine has changed as a result. This message is informational only and should appear whenever keepalives are received that cause a change in the liveness state and when information level logging is enabled.

Recommended Action    No action is required.

Error Message    CE-CR-5-180309: Failed to register to with data server - <string>.

Explanation    The content routing module has failed to register with the data server for content routing-related commands other than the debug content-routing commands. The content routing module then tries to register once every 60 seconds. This message appears only when the content routing module starts up. This message should be treated as a notice level message if it appears fewer than five times. It should be escalated to a critical level message if it appears more than five times in a row. Ignoring this error message can cause content routing-related commands other than the debug content-routing commands to fail.

Recommended Action    Rebooting the system may provide a temporary workaround. Send the output of the show process memory command and all syslog files to Cisco TAC for further analysis.

Error Message    CE-CR-5-180314: Receive a content routing API request in wrong format: 
<string>.

Explanation    The content routing module has received a content routing API request in the wrong format. The detail will be given at the end of the message. This message appears whenever the content routing API feature is enabled on the Content Router and a content routing API request in the wrong format is received. This message is informational only.

Recommended Action    Verify the format of the content routing API request. The Content Router functions correctly even when this message appears.

Cisco Streaming Engine Messages

This section contains Cisco streaming engine messages.

CSE-2

Error Message    CE-CSE-2-632000: [Procedure] - System call error: <system call name> 
<err msg> 

Explanation    A system call failed. The system might have an error.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

CSE-3

Error Message    CE-CSE-3-633000: [Procedure] - Unable to establish connection with the 
Data Server <error_message> 

Explanation    The system failed to establish a connection with the data server.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633001: [Procedure] - Unable to release the connection with 
the Data Server <error_message> 

Explanation    The system failed to release the connection with the data server.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633002: [Procedure] - Failed to receive message from the Data 
Server <error_message> 

Explanation    The system failed to receive the message from the data server.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633003: [Procedure] - Failed to get information from EDM 
<error_message> 

Explanation    The system failed to get information from the Extended Data Manager.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633004: [Procedure] - Failed to send acknowledgment to the 
Data Server <error_message> 

Explanation    The system failed to send the acknowledgment for the information received from the data server.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633005: [Procedure] - Failed to register with Data Manager 
<error_message> 

Explanation    The system failed to register with the EDM.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633006: [Procedure] - Failed to unregister Data Manager 
<error_message> 

Explanation    The system failed to unregister with the EDM.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633007: [Procedure] - Failed to release the resource acquired 
by the Data Server <error_message> 

Explanation    The system failed to unregister with the EDM.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633008: [Procedure] - read event failed <error_message> 

Explanation    A read event failed.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633009: [Procedure] CSE received error code <error_message> 

Explanation    The system failed to serve the request by the Cisco Streaming Engine.

Recommended Action    Attempt the request again. If the service fails, contact Cisco TAC.

Error Message    CE-CSE-3-633010: [Procedure] Failed to get Cisco Streaming Engine 
Configuration <error_message> 

Explanation    The system failed to configure the Cisco Streaming Engine.

Recommended Action    Attempt the command again. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633011: [Procedure] Failed to set Cisco Streaming Engine 
bandwidth <bw> <error_message> 

Explanation    The system failed to the change the bandwidth configuration of the Cisco Streaming Engine.

Recommended Action    Attempt the command again. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633012: [Procedure] Failed to start Cisco Streaming Engine 
<error_message> 

Explanation    The system encountered an error when starting the Cisco Streaming Engine.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633013: [Procedure] Failed to stop Cisco Streaming Ennui 
<error_message> 

Explanation    The system encountered an error when stopping the Cisco Streaming Engine.

Recommended Action    Attempt the command again. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633014: [Procedure] Failed to set accesslog filename variable 
in temp file <error_message> 

Explanation    The system was unable to set the accesslog filename in the temp file.

Recommended Action    Attempt the command again. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633015: [Procedure] Failed to move temp file with accesslog 
filename to configuration file <error_message> 

Explanation    The system failed to move the temp file to the configuration file.

Recommended Action    Attempt the command again. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-CSE-3-633016: [Procedure] Failed to build EDM/verification ACK 
<error_mesg> 

Explanation    The system failed to build the verification or the EDM acknowledgment.

Recommended Action    Attempt the command again. If the problem occurs frequently, contact Cisco TAC.

CSE-6

Error Message    CE-CSE-6-636000: [Procedure] Cisco Streaming Engine Started 

Explanation    The Cisco Streaming Engine started and is running.

Recommended Action    No action is required.

Error Message    CE-CSE-6-636001: [Procedure] Cisco Streaming Engine Stopped 

Explanation    The Cisco Streaming Engine stopped.

Recommended Action    No action is required.

CSE-7

Error Message    CE-CSE-7-637000: [Cisco Streaming Engine CLI bin Debug] 

Explanation    This is a debug message for the Cisco Streaming Engine.

Recommended Action    No action is required.

Debug Messages

This section contains debug messages.

DDBG-7

Error Message    CE-DDBG-7-899998: [Description] 

Explanation    These are debug messages generated by various modules.

Recommended Action    No action is required.

Dynamic Host Configuration Protocol Client Messages

This section contains Dynamic Host Configuration Protocol client messages.

DHCP-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-DHCP-n-191000: Description.

Explanation    These messages are generated by the DHCP client.

Recommended Action    If high priority error messages occur frequently, contact Cisco TAC.

DHCP-3

Error Message    CE-DHCP-3-191011:   disk_check_io(<device>): open (<error>) Failed to 
get default dhcp interface. 

Explanation    The system, by default, enables DHCP on the first interface and the software failed to connect to the first interface on the system.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DHCP-3-191013:   Failed to enable DHCP on the default interface 
(num,num) 

Explanation    The system failed while trying to enable DHCP on the first interface.

Recommended Action    Check if the cable is connected and a DHCP server is available on the network. If the problem persists, contact Cisco TAC.

DHCP-5

Error Message    CE-DHCP-5-191010: Default dhcp interface is already configured. 
Skipping dhcp configuration 

Explanation    The system found that the interface on which the DHCP should be enabled by default, has already been configured. The system failed to enable DHCP.

Recommended Action    No action is required.

Error Message    CE-DHCP-5-191012: DHCP enabled on the default interface. 

Explanation    The system enabled DHCP on the fist interface of the system.

Recommended Action    No action is required.

Disk Messages

This section contains disk messages.

DISK-0

Error Message    CE-DISK-0-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. 

Explanation    This message indicates the possibility of a faulty disk00.

Recommended Action    Replace disk00. Enter the disk recover command. Reinstall the software.

Error Message    CE-DISK-0-200024: First disk not in standard configuration. Run 'disk 
recover' command and re-install software. 

Explanation    The first disk does not have the correct partition configuration.

Recommended Action    Enter the disk recover command, and reinstall the software.

Error Message    CE-DISK-0-200029: disk00 is having serious problems. Reloading ... 

Explanation    The disk00 or the disk drive that has SYSFS is faulty. The system rebooted automatically.

Recommended Action    Replace the drive and enter the disk recover or disk configure commands. You may also need to reinstall the software.

Error Message    CE-DISK-0-200032: First disk <name> is marked as bad. 

Explanation    The first disk drive (usually disk00) has been marked as faulty and is not used by the software. The device will lose most of its function without the first disk drive.

Recommended Action    Enter the disk mark command to bring the disk drive online, provided there is no hardware error. See CE-DISK-0-200015 if there is hardware problem.

DISK-1

Error Message    CE-DISK-1-200001: disk_check_io(): fork failed (<error>).

Explanation    The fork() function failed. The system is unstable.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DISK-1-200035: One or more disk partitions have severe file system 
problem. Please reload the system to recover from this failure. 

Explanation    A disk has a serious, but recoverable file system-related problem.

Recommended Action    Reboot the system.

Error Message    CE-DISK-1-200036: <num> disks have failed. Please check syslog for more 
information. 

Explanation    One or more disks have failed.

Recommended Action    Follow these steps in the given order until one of them solves the problem:

1. Scan for errors (using the command, disk scan-errors <disk>).
2. Reformat the disk (using the command, disk reformat <disk>).
3. Replace the drive.

DISK-2

Error Message    CE-DISK-2-200002: disk_check_io(<device>): open (<error>).

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk, and replace the disk.

Error Message    CE-DISK-2-200003: disk_check_io(<device>): seek (<error>).

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk, and replace the disk.

Error Message    CE-DISK-2-200004: disk_check_io(<device>): read (<error>).

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk, and replace the disk.

Error Message    CE-DISK-2-200005: disk_check_io(<device>): bad disk.

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk, and replace the disk.

Error Message    CE-DISK-2-200006: disk_check_io(<device>): waitpid (<error>).

Explanation    A disk could be faulty. Disk operation does not execute.

Recommended Action    Enter the show disks details command to identify the faulty disk, and replace the disk.

Error Message    CE-DISK-2-200008: <diskname> is bad. Check cable or replace it. 

Explanation    A disk could be faulty.

Recommended Action    Replace the faulty disk. Reinstall the software if the faulty disk is disk00.

Error Message    CE-DISK-2-200009: read signature: open device failed: <device> 
<error>.

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk. Replace the faulty disk. Reinstall the software if the faulty disk is disk00.

Error Message    CE-DISK-2-200010: read signature: seek device failed: <device> 
<error>.

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk. Replace the faulty disk. Reinstall the software if the faulty disk is disk00.

Error Message    CE-DISK-2-200011: read signature: read device failed: <device> 
<error>.

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk. Replace the faulty disk. Reinstall the software if the faulty disk is disk00.

Error Message    CE-DISK-2-200012: write signature: open device failed: <device> 
error>.

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk. Replace the faulty disk. Reinstall the software if the faulty disk is disk00.

Error Message    CE-DISK-2-200013: write signature: seek device failed: <device> 
<error>.

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk. Replace the faulty disk. Reinstall the software if the faulty disk is disk00.

Error Message    CE-DISK-2-200014: write signature: write device failed: <device> 
<error>.

Explanation    A disk could be faulty.

Recommended Action    Enter the show disks details command to identify the faulty disk. Replace the faulty disk. Reinstall the software if the faulty disk is disk00.

Error Message    CE-DISK-2-200018: Can not create log directory <dir>: <error>.

Explanation    The system could not create the necessary directory.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DISK-2-200019: Can not create log export directory <dir>: <error>.

Explanation    The system could not create the necessary directory.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DISK-2-200020: Can not symlink from <dir> to <dir>: <error>.

Explanation    The system could not create the symlink directory.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DISK-2-200021: Can not create crash directory <dir>: <error>.

Explanation    The system could not create the necessary directory.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DISK-2-200027: PERC logical drive XX has problems. 

Explanation    RAID5 logical drive on CDM4650 has an error.

Recommended Action    Check the message 200028 to locate the physical drive and replace it. Enter the build command.

Error Message    CE-DISK-2-200028: PERC bad physical drive(s): Adp-00(Ch-X Id-XX): 
TO-XX,Thr-XXX,Par-XXX SCSI- [XX].

Explanation    The RAID5 physical drive has an error. This message always appears with the message 200027. 200027 identifies the logical drive number while 200028 identifies the physical drive slot.

Recommended Action    Replace the drive and enter the raid rebuild command.

Error Message    CE-DISK-2-200030: diskXX is having serious problems. Won't use it after 
reboot. 

Explanation    DiskXX is faulty. The disk is marked as faulty and will not be used after reboot.

Recommended Action    Replace drive and enter the disk add or disk configure commands.

Error Message    CE-DISK-2-200031: There appear to be no SYSFS filesystem(s) present on 
this system. Software requires SYSFS for transaction logging and certain other 
features, and also for logging of internal status information. Please use "disk 
configure" or, if applicable, use the CDM GUI to configure SYSFS disk space for 
this system. 

Explanation    The system has encountered an error.

Recommended Action    Enter the disk configure command.

Error Message    CE-DISK-2-200033: <text>.

Explanation    The system has encountered an error.

Recommended Action    No action is required.

Error Message    CE-DISK-2-200037: open (<file_name>): <error>.

Explanation    The system failed to open one of the critical files that maintains disk quota information for some applications.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DISK-2-200039: fopen (/etc/fsinfo.new): <error>, 
rename(/etc/fsinfo.new, /etc/fsinfo): <error>, cannot create /etc/fsinfo.new: 
<error>.

Explanation    The system failed to open one of the critical files that maintains the file system space allocation information.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DISK-2-200040: handle_unuse_filesystem: fork(): <error>.

Explanation    The system failed to fork a process that stops applications from using a specified file system.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DISK-2-200041: filesystem_server: fs_svr_init() failed. 

Explanation    A critical system program failed to initialize.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DISK-2-200042: statfs('<path>'): <error>.

Explanation    The system failed to retrieve the size of the specified file.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

DISK-3

Error Message    CE-DISK-3-200017: ruby_disk: physical disk setup appears to have 
changed not effecting 'disk config' changes.

Explanation    The system does not use allocation data, created by the disk configure command because the disk setup has changed.

Recommended Action    Enter the disk configure command again.

Error Message    CE-DISK-3-200022: Unknown disk-layout: sw=<num>, swstore=<num>, 
swap=<num>.

Explanation    The system is unable to handle the partition layout.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DISK-3-200023: Unknown acns5 disk layout: sw=<num>, swstore=<num>, 
swap=<num> state=<num>.

Explanation    The system is unable to handle the partition layout.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DISK-3-200034: <text>.

Explanation    The system encountered a memory allocation error.

Recommended Action    If system behavior is not as expected or is deficient in some manner, contact Cisco TAC.

Error Message    CE-DISK-3-200038: assign_fs_space(): internal error, static_mediafs is 
set, should not be called. 

Explanation    A part of the code that should get called only when mediafs is configured to use unused cdnfs space, got invoked even though space for mediafs is allocated statically.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DISK-3-200043: ver_channel_quota.c:verify: v->new_len = <num>, 
expected <num>.

Explanation    An internal check, for the size of the variables failed.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DISK-3-200044: ver_channel_quota.c:verify: ruby_disk fsc 
setquotasum <num> returned <num>.

Explanation    The system failed to adjust the file system allocation based on the channel quota or the subscription change.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

DISK-4

Error Message    CE-DISK-4-200016: ruby_disk: allocation data corrupted <magic> 
<version> < magic 2>.

Explanation    Allocation data, created by the disk configure command is corrupted.

Recommended Action    Enter the disk configure command again. If the problem persists, contact Cisco TAC.

Error Message    CE-DISK-4-200025: diskXX is too small <size>MB (<size>MB is needed).

Explanation    The capacity of the specified disk is less than 2GB. This is usually because the fiber channel configuration is not set correctly.

Recommended Action    Replace with a Cisco disk if the specified disk is a direct attached disk and not a Cisco disk. Reconfigure fiber channel with size > 2GB if it is an FC disk.

DISK-5

Error Message    CE-DISK-5-200026:' Disk configure' command has been [issued|canceled]. 

Explanation    The disk configuration command has been issued or canceled.

Recommended Action    No action is required.

DISK-6

Error Message    CE-DISK-6-200007: disk_check_io(<device>): waitpid (<error>).

Explanation    This message is informational.

Recommended Action    No action is required.

Distribution Messages

This section contains distribution messages.

DIST-2

Error Message    CE-DIST-2-210000: metadata sender failed in database operations: 
[failure description] 

Explanation    The system encountered a critical database error in the meta sender operations.

Recommended Action    The metasender service will be restarted automatically. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-DIST-2-210001: metadata sender failed in channel table operations: 
[failure description] 

Explanation    The system encountered a critical error in meta sender operations on the channel table.

Recommended Action    The metasender service will be restarted automatically. Collect technical support information, and contact Cisco TAC.

Error Message    CE-DIST-2-210002: metadata sender failed in system calls: [failure 
description] 

Explanation    The system encountered a critical error when the meta sender made systems calls (for example, select).

Recommended Action    The metasender service will be restarted automatically. Collect technical support information, and contact Cisco TAC.

Error Message    CE-DIST-2-210003: metadata sender failed in initialization : [failure 
description] 

Explanation    The system encountered a critical error during meta sender initialization.

Recommended Action    The metasender service will be restarted automatically. Collect technical support information, and contact Cisco TAC.

Error Message    CE-DIST-2-211000: metadata receiver failed in database operations: 
[failure description] 

Explanation    The system encountered a critical database error during meta receiver operations.

Recommended Action    The meta receiver service will be restarted automatically. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-DIST-2-211001: metadata receiver failed in uns operations: [failure 
description] 

Explanation    The system encountered a critical UNS error during metadata operations.

Recommended Action    The meta receiver service will be restarted automatically. Collect technical support information, and contact Cisco TAC.

Error Message    CE-DIST-2-211002: metadata receiver failed in system calls: [failure 
description] 

Explanation    The system encountered a critical system call error during meta receiver operations.

Recommended Action    The meta receiver service will be restarted automatically. Collect technical support information, and contact Cisco TAC.

Error Message    CE-DIST-2-211003: metadata receiver failed in initialization: [failure 
description] 

Explanation    The system encountered a critical error during the meta sender starting phase.

Recommended Action    The meta receiver service will be restarted automatically. Collect technical support information, and contact Cisco TAC.

Error Message    CE-DIST-2-211004: metadata receiver full reload failed: 
error[error_no] channel_id[channel_id] | root_ce_id[root_ce_id] 
root_ce_uid[root_ce_uid] 

Explanation    The metadata receiver failed to fully reload the specified channel from the root Content Engine.

Recommended Action    The meta receiver service will be restarted automatically. Collect technical support information, and contact Cisco TAC.

Error Message    CE-DIST-2-211005: metadata receiver saw inconsistent gen id in 
replication [req/claimed/max gen ids]. 

Explanation    The metadata receiver generated inconsistent IDs during meta data replication.

Recommended Action    The meta receiver service will be restarted automatically. Collect technical support information, and contact Cisco TAC.

Error Message    CE-DIST-2-211006: metadata receiver failed since number of job in sync 
queue exceeded maximum limit. 

Explanation    The metadata receiver failed because of a large number of jobs in the sync queue.

Recommended Action    The meta receiver service will be restarted automatically. Collect technical support information, and contact Cisco TAC.

Error Message    CE-DIST-2-212000: unicast sender failed in database operations: 
[failure description] 

Explanation    The unicast data sender service encountered a critical database error.

Recommended Action    Enter the cms database maintenance command. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-DIST-2-212001: unicast sender failed in semaphore operations: 
[failure description] 

Explanation    The unicast data sender service encountered a critical error in the semaphore or mutex deployment for its internal data structure.

Recommended Action    Enter the acquisition-distribution stop and acquisition-distribution start commands and check the syslogs. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-212002: unicast sender failed in uns operations: [failure 
description] 

Explanation    The unicast data sender service encountered a critical error in UNS operations.

Recommended Action    Enter the cdnfs cleanup start command. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-212003: unicast sender failed in bandwidth operations: 
[failure description] 

Explanation    The unicast data sender service countered a critical error in bandwidth control.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DIST-2-212004: unicast sender failed in apache operations: [failure 
description] 

Explanation    The unicast data sender service encountered a critical error in the HTTP server library.

Recommended Action    Enter the acquisition-distribution stop and acquisition-distribution start commands and check the syslogs. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-213000: unicast receiver failed in database operations: 
[failure description] 

Explanation    The unicast data receiver service encountered a critical error in database operations.

Recommended Action    Enter the cms database maintenance command. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-DIST-2-213001: unicast receiver failed in uns operations: [failure 
description] 

Explanation    The unicast data receiver service encountered a critical error in UNS operations.

Recommended Action    Enter the cdnfs cleanup start commands. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-213002: unicast receiver failed in system calls: [failure 
description] 

Explanation    The unicast data receiver service encountered a critical error in system calls (select/rpc).

Recommended Action    Enter the acquisition-distribution stop and acquisition-distribution start commands and check the syslogs. If the problem persists, contact Cisco TAC

Error Message    CE-DIST-2-213003: unicast receiver failed in bandwidth control: 
[failure description] 

Explanation    The unicast data receiver service encountered a critical error in bandwidth control.

Recommended Action    Enter the acquisition-distribution stop and acquisition-distribution start commands and check the syslogs. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-213004: unicast receiver failed in HT operations: [failure 
description] 

Explanation    The unicast data receiver service encountered a critical error in the HTTP client library.

Recommended Action    Enter the acquisition-distribution stop and acquisition-distribution start commands and check the syslogs. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-213005: multicast receiver lose multicast connectivity: 
[failure description] 

Explanation    The multicast receiver did not receive advertisements or heartbeats for more than 30 minutes. It disabled NACK to the multicast sender. The reason for this error could be multicast networking problem between the sender and receiver.

Recommended Action    Enter the multicast connectivity-test command to verify multicast connectivity loss, then fix the multicast networking problem for the receiver Content Engine.

Error Message    CE-DIST-2-215000: multicast sender failed in database operations: 
[failure description] 

Explanation    The multicast file sender service encountered a critical database error.

Recommended Action    Enter the cms database maintenance command. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-DIST-2-215001: multicast sender plug-in failed in database 
operations: [failure description] 

Explanation    The multicast file sender daemon service encountered a critical database error.

Recommended Action    Enter the cms database maintenance command. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-DIST-2-215002: multicast sender failed in rpc operations: [failure 
description] 

Explanation    The multicast file sender service failed to create an rpc server. It is possible that the port the rpc server wants to listen on is used by other services.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-215003: multicast_file_sender failover/fallback service: 
[msg description] 

Explanation    This message is received from the file sender failover or fallback service. The messages could be informational such as change of a sender state (backup sender becomes active) or they could be error messages.

Recommended Action    In case of error condition, check if the network connectivity between the primary and the backup sender is fault-free, and check if the sender service on the primary or the backup sender Content Engine is running without errors. If the sender service is not running, check if the multicast is enabled on the sender Content Engine. If there is no network connectivity problem and the sender services are running on both sender Content Engines, contact Cisco TAC.

Error Message    CE-DIST-2-215004: Multicast sender can not send file in the channel 
since the maximum carousel is reached. : [failure description] 

Explanation    The multicast sender is unable to send the file in the channel because the maximum carousel is reached.

Recommended Action    Increase the maximum carousel of the multicast cloud that is associated with the channel.

Error Message    CE-DIST-2-216000: multicast receiver failed in database operations: 
[failure description] 

Explanation    The multicast file receiver service encountered a critical database error.

Recommended Action    Enter the cms database maintenance command. If the problem persists, reboot the Content Engine. If the problem still persists, contact Cisco TAC.

Error Message    CE-DIST-2-216001: multicast receiver plug-in failed in database 
operations: [failure description] 

Explanation    The multicast file receiver daemon service encountered a critical database error.

Recommended Action    Enter the cms database maintenance command. If the problem persists, reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-216002: multicast receiver failed in rpc operations: 
[failure description] 

Explanation    The multicast file receiver service failed to create the rpc server. The reason for this error could be that the port the rpc server wants to listen on is used by other services.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-216003: multicast receiver plug-in failed in uns operations: 
[failure description] 

Explanation    The multicast file receiver service encountered a critical error in UNS operations. The reason for this error could be that the UNS server failed to start or was busy. Rebooting the Content Engine may solve the problem.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-216004:   McastReceiver has high loss rate 

Explanation    The message class indicates that the multicast file receiver has high loss rate and it may not be getting all the contents from the multicast file sender. This problem may be due to a network-related problem.

Recommended Action    If there is a network-related problem, try to rectify it. If the problem persists, contact Cisco TAC.

Error Message    CE-DIST-2-217000: multicast system call: [failure description] 

Explanation    The multicast file sender or multicast file receiver encountered a critical error in system calls (fork/execvp).

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

DIST-4

Error Message    CE-DIST-4-214001: Channel Routing topology multicast sender transient 
error. 

Explanation    The channel routing module detected that the multicast sender for the receive multicast cloud is the home Content Engine itself.

Recommended Action    The system should recover from this transient error automatically. If the problem persists or occurs frequently, contact Cisco TAC.

DIST-

Error Message    CE-DIST-X-217001: Failed to write in to NAS 

Explanation    The unicast or multicast receiver is unable to write the file to the NAS partition.

Recommended Action    Make sure the NAS device does not have any problem. Check for free space on the file system by entering the show statistics cdnfs command and checking the physical file system space free. If there is no more free space, remove excess files on the file system (but do not remove files in the Content Engine directory), and assign the Content Engine space in line with what is available on the NAS. Ensure that other applications are not filling up the NAS filesystem that the Content Engine is using. If the problem persists in spite of making sure that the NAS device is problem-free and there is sufficient free space on the device, contact Cisco TAC.

Domain Name Server Messages

This section contains domain name server messages.

DNS-1

Error Message    CE-DNS-1-221000: HTTP DNS cache out of memory 

Explanation    The internal HTTP DNS resolution cache service has run out of memory.

Recommended Action    The HTTP DNS resolution module will try to recover, but such a problem is symptomatic of a system-wide memory shortfall. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

DNS-2

Error Message    CE-DNS-2-221001: HTTP DNS cache has no configured nameservers to query 

Explanation    The internal HTTP DNS resolution cache service has no configured DNS name servers to which it can send queries. As a result, the service will be unable to do its job and many services will be disrupted.

Recommended Action    Configure the DNS name servers in the command.

Error Message    CE-DNS-2-221002: HTTP DNS cache has detected an inconsistent internal 
state 

Explanation    The internal HTTP DNS resolution cache service has detected an internal error. Such an error is indicative of memory corruption. The corruption could be because of the hardware or software, which would be known on further investigation.

Recommended Action    The HTTP DNS resolution service will cause the entire proxy caching application to exit and restart. If the problem persists, contact Cisco TAC.

Error Message    CE-DNS-2-221003: HTTP DNS cache unable to open a UDP socket to send 
queries on 

Explanation    The internal HTTP DNS resolution cache service is unable to open an ephemeral UDP socket used to send DNS requests to any of the configured DNS servers.

Recommended Action    The HTTP DNS resolution module will try to recover, but such a problem is symptomatic of a system-wide network resource shortfall. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-DNS-2-221006: Unable to perform Dataserver operations 

Explanation    The system DNS cache needs to be able to get the configuration and changes to the configuration from the dataserver. This message indicates that it cannot do that and is not able to run. This can be indicative of a major system problem if it is persistent.

Recommended Action    No action is required - the cache process will restart in an attempt to recover. If the problem persists, reboot the Content Engine.

Error Message    CE-DNS-2-221008: DNS is not able to listen on address [address] port 
[port] 

Explanation    The system DNS cache has attempted and failed to open a port on which to listen for requests. This could 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 the system is in an indeterminate state.

Recommended Action    Change the listen parameters in the configuration. If this has occurred on the loopback address reboot the Content Engine.

Error Message    CE-DNS-2-221009: DNS is not able to initiate a WCCP liveness 

Explanation    The system DNS cache has attempted and failed to start communicating with WCCP. This could be a system-wide resource issue or an issue with WCCP itself.

Recommended Action    The system DNS cache will restart on this error. If the problem persists, reboot the Content Engine.

DNS-4

Error Message    CE-DNS-4-221007: DNS has not been able to PIN the entries [name] 
requested 

Explanation    The system DNS cache allows users to configure static entries in the DNS cache. The cache has been unable to set this entry.

Recommended Action    Remove and add the entry again in the configuration.

DNS-5

Error Message    CE-DNS-5-221005: Persistent write failure on ephemeral DNS server 
query socket 

Explanation    The HTTP caching DNS service sends resolution requests that it cannot 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 will shut down the socket and attempt to open another. This may be indicative of a greater system-wide networking subsystem problem.

Recommended Action    No action is required, the cache process will attempt to recover automatically.

Error Message    CE-DNS-5-221010: Persistent write failure on ephemeral DNS server 
query socket 

Explanation    The system DNS cache sends resolution requests that it cannot 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 will shut down the socket and attempt to open another. This may be indicative of a greater system-wide networking subsystem problem.

Recommended Action    No action is required, the system DNS cache will attempt to recover automatically.

DNS-6

Error Message    CE-DNS-6-221004: Periodic HTTP DNS statistics report 

Explanation    Every 10 seconds, a LOG_INFO priority message is sent to the SS that 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 had to retry requests because of a configured DNS server not responding.

Recommended Action    No action is required.

Data Server Messages

This section contains data server messages.

DS-0

Error Message    CE-DS-0-231000: *** FATAL ERROR. DS SERVER EXITING *** Message: 
<string> FILE: <filename> LINE: <linenumber> errno = <number> 

Explanation    The Content Engine data server is not working.

Recommended Action    Contact Cisco TAC.

DS-2

Error Message    CE-DS-2-231200: SYSFS is not mounted. 

Explanation    The system does not have a mounted SYSFS. The system cannot dump the stack trace.

Recommended Action    Check if the SYSFS is configured. If not, configure the SYSFS and restart the system.

Error Message    CE-DS-2-231201: Failed to set RLIMIT_AS. 

Explanation    The system failed to set the RLIMIT_AS.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DS-2-231202: Failed to set RLIMIT_RSS. 

Explanation    The system failed to set the RLIMIT_RSS.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DS-2-231203: Dataserver has too many open connections (<number>) 

Explanation    The data server has too many open connections.

Recommended Action    Contact Cisco TAC.

Error Message    CE-DS-2-232200: data server malloc error. 

Explanation    The system encountered a failure in malloc.

Recommended Action    Contact Cisco TAC.

DS-3

Error Message    CE-DS-3-230300: Unexpected msg type, ds client and server out of sync. 

Explanation    The data server client received a wrong message type in the response from the data server. The communication between the data server and the client is out of sync.

Recommended Action    The client process will try to recover. If not, reboot the Content Engine.

Error Message    CE-DS-3-230301: Client read error 

Explanation    The system encounters a read error when reading from the data server.

Recommended Action    The client will try to recover. If it cannot recover, there could be a problem with the data server. Reboot the Content Engine.

Error Message    CE-DS-3-230302: Invalid response header from data server:     

Explanation    The client gets an invalid response header from the data server. The communication between the data server and the client is out of sync, or the data server is running in an abnormal state.

Recommended Action    The client process should try to recover. If it cannot recover, reboot the Content Engine.

Error Message    CE-DS-3-230303: Client timed out on read 

Explanation    The client could not read from the data server.

Recommended Action    If this message persists, the data server has an error. Collect information about the system state, and contact cisco TAC.

Error Message    CE-DS-3-231300: Failed to send verification msg. 

Explanation    The system failed to send a message to the verifier through vensock.

Recommended Action    If this message occurs frequently, reboot the Content Engine.

Error Message    CE-DS-3-231301: DS svr failed to set signal handler for SIGPIPE to 
SIG_IGN. 

Explanation    The DS server failed to set the signal handler of the SIGPIPE to SIG_IGN.

Recommended Action    No action is required.

Error Message    CE-DS-3-232300: connect error 

Explanation    The system failed to establish a connection.

Recommended Action    Reboot the Content Engine.

Error Message    CE-DS-3-232301: select error 

Explanation    The system encountered an error in the select operation.

Recommended Action    No action is required.

Error Message    CE-DS-3-232302: getsockopt error 

Explanation    The Getsockopt operation returned an error.

Recommended Action    No action is required.

Error Message    CE-DS-3-232303: write error 

Explanation    The write operation returned an error.

Recommended Action    If the problem persists, contact cisco TAC.

Error Message    CE-DS-3-232304: read error 

Explanation    The read operation returned an error.

Recommended Action    If the problem persists, contact cisco TAC.

DS-5

Error Message    CE-DS-5-230500: remaining time is 0. 

Explanation    The system encounters an error in the Calc_remaining_time operation. This operation returns a zero.

Recommended Action    The problem could occur frequently, if there is an error in the data server. Reboot the Content Engine.

Firewall Feature Set

This section contains firewall feature set messages.

FFS-5

Error Message    CE-FFS-5-660001: process info: ffs_dumper()  process_id 

Explanation    The message displays the dumper process ID and the pthread ID.

Recommended Action    No action is required.

File Transfer Protocol Messages

This section contains File Transfer Protocol messages.

FTP-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-FTP-n-250000: Description 

Explanation    These messages are generated by FTP.

Recommended Action    If high priority error messages occur frequently, contact Cisco TAC.

File Transfer Protocol Export Messages

This section contains File Transfer Protocol export messages.

FTP_Export-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-FTP_EXPORT-n-251001:  

Explanation    The native ftp_export code shows the error/notice/information.

Recommended Action    If the problem appears frequently, contact Cisco TAC.

File Transfer Protocol Proxy Messages

This section contains File Transfer Protocol Proxy messages.

FTP-PROXY-2

Error Message    CE-FTP_PROXY-2-252013: FTP proxy could not initialize CLI services 
[err]' '[errno]'. 

Explanation    The system encountered an error while initializing the command line interface for FTP proxy.

Recommended Action    Reconfigure the FTP proxy. If the problem persists, reboot the Content Engine.

Error Message    CE-FTP_PROXY-2-252014: FTP proxy could not initialize DNS submodule 
[err]' '[errno]'. 

Explanation    The system encountered an error while initializing the DNS resolution submodule of the FTP proxy.

Recommended Action    Reconfigure the FTP proxy. If the problem persists, reboot the Content Engine.

Error Message    CE-FTP_PROXY-2-252015: FTP proxy could not initialize IPC submodule 
[errno]'. 

Explanation    The system encountered an error when initializing the IPC submodule of the FTP proxy that is used to communicate between the FTP proxy and the caching service module.

Recommended Action    Reconfigure the FTP proxy. If the problem persists, reboot the Content Engine.

Error Message    CE-FTP_PROXY-2-252016: FTP proxy could not configure WCCP Conditional 
Accept services '[err]' '[errno]'. 

Explanation    The system encountered an error when initializing the WCCP conditional accept service for managing the transparently redirected FTP control connections.

Recommended Action    Retry configuring the FTP proxy. If the problem persists, contact Cisco TAC.

Error Message    CE-FTP_PROXY-2-252017: FTP proxy could not confirm WCCP Conditional 
Accept services '[err]' '[errno]'. 

Explanation    The FTP proxy could not confirm correct configuration of the WCCP Conditional Accept service for managing the transparently redirected FTP control connections.

Recommended Action    Retry configuring the FTP proxy. If the problem persists, contact Cisco TAC.

FTP-PROXY-3

Error Message    CE-FTP_PROXY-3-252002: FTP listener startup for port '[port]' failed 
[try number]' '[err]' '[errno]'. 

Explanation    The system could not start the listener for the FTP control connection on port. The port is temporarily in an unbindable state, or is in use by some other application.

Recommended Action    If this feature was newly configured, the program will restart the listener in a few seconds. If this feature was already running and the failure occurred when an attempt was made to change the configuration, try, after two minuets, to change the configuration.

Error Message    CE-FTP_PROXY-3-252003: Socket exception occurred during FTP 
listeninitialization. 

Explanation    The system could not set up the listener socket for an FTP control connection.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-FTP_PROXY-3-252004: Exception occurred during FTP listener 
initialization. 

Explanation    The system could not set up the listener on the FTP control connection.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-FTP_PROXY-3-252005: Giving up on FTP listener initialization for 
port '[port]' after '[number of tries]' [err]' '[errno]'. 

Explanation    The system could not start the listener for the FTP control connection on the specific port after the specified number of tries. The port is temporarily in an unbindable state, or is in use by some other application.

Recommended Action    Retry the command after a couple of minutes. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-FTP_PROXY-3-252007: Failed to configure FTP WCCP listener on 
reserved port '[port]'. 

Explanation    The system could not start the listener for the WCCP-redirected FTP control. The port is temporarily in an unbindable state.

Recommended Action    Disable and reenter the wccp ftp-native command after a couple of minutes. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-FTP_PROXY-3-252009: Failed to configure FTP Proxy-mode listener on 
port '[port]'. 

Explanation    The system could not start the proxy-mode listener for the FTP control connection on the specified port. The port is temporarily in an unbindable state, or is in use by some other application.

Recommended Action    Check whether the port has been configured for use by a different application. If not, reenter the ftp-native incoming proxy command after a couple of minutes. If the problem occurs frequently, contact Cisco TAC.

FTP-PROXY-4

Error Message    CE-FTP_PROXY-4-252012: FTP CLI socket error, '[socket]' '[err]' 
[errno]'. New socket will be created automatically. 

Explanation    The system encountered a transient error on the command line interface socket.

Recommended Action    No action is required. The system will reinitialize the socket. If the problem occurs frequently, reboot the Content Engine.

FTP-PROXY-5

Error Message    CE-FTP_PROXY-5-252018:   Access Denied: '[conn-type]' ftp-native 
connection with source ip address '[src-ip]' rejected due to ftp-native 
access-list in. 

Explanation    The FTP-native proxy denied access to the connection after checking the source IP address of the connection against the inbound access-list configured by the ftp-native access-list-in.

Recommended Action    No action is required.

FTP-PROXY-6

Error Message    CE-FTP_PROXY-6-252006: FTP listener initialization succeeded for port 
'[port]' in '[number of tries]'. 

Explanation    The system started the FTP listener for accepting FTP control connections at the specified port.

Recommended Action    No action is required.

Error Message    CE-FTP_PROXY-6-252008: Successfully configured FTP WCCP listener on 
reserved port '[port]'. 

Explanation    The system started the FTP listener for accepting FTP control connections.

Recommended Action    No action is required.

Error Message    CE-FTP_PROXY-6-252010: Successfully configured FTP proxy-mode listener 
on port '[port]'. 

Explanation    The system started the FTP listener for accepting proxy-mode FTP control connections on the specified port.

Recommended Action    No action is required.

Error Message    CE-FTP_PROXY-6-252011: Removed FTP listener on port '[port]'. 

Explanation    The system terminated the FTP listener on the specified port.

Recommended Action    No action is required.

FTP-PROXY-7

Error Message    CE-FTP_PROXY-7-252001: <debug messages> 

Explanation    The messages are informational.

Recommended Action    No action is required.

Hypertext Transfer Protocol Messages

This section contains Hypertext Transfer Protocol messages.

HTTP-2

Error Message    CE-HTTP-2-270004: System mem low, no buffer for appended req header 

Explanation    The system memory is low.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270006: process_ntlm_type1_msg: malloc error for type1_msg, 
return 

Explanation    The system encountered a memory allocation error.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270007: process_ntlm_type1_msg: malloc error for host_name, 
return 

Explanation    The system encountered a memory allocation error.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270008: process_ntlm_type1_msg: malloc error for 
domain_name, return 

Explanation    The system encountered a memory allocation error.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270009: Unexpected NTLM username length : <number> 

Explanation    The length of the username is greater than the configured limit.

Recommended Action    Check the configured length of the NTLM username. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270010: process_ntlm_type3_msg: unexpected type-3 message, 
ntlm_state=<number> 

Explanation    The system encountered an error in the NTLM state.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270011: process_ntlm_type3_msg: malloc error for type3_msg 

Explanation    The system encountered a memory allocation error.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270012: process_ntlm_type3_msg: malloc error for 
type3_msg->domain_name 

Explanation    The system encountered a memory allocation error.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270013: process_ntlm_type3_msg: malloc error for 
type3_msg->username 

Explanation    The system encountered a memory allocation error.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270014: process_ntlm_type3_msg: malloc error for 
type3_msg->dc_addr 

Explanation    The system encountered a memory allocation error.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270015: process_ntlm_type3_msg: malloc error for 
type3_msg->lm_resp 

Explanation    The system encountered a memory allocation error.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270016: process_ntlm_type3_msg: malloc error for 
type3_msg->nt_resp 

Explanation    The system encountered a memory allocation error.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-3-270017: Recovering from a lost dataserver connection 

Explanation    The cache lost its connection to the data server and is trying to reconnect.

Recommended Action    The system will recover automatically.

Error Message    CE-HTTP-3-270018: Retrying connection to dataserver 

Explanation    The cache lost its connection to the data server and is trying to reconnect.

Recommended Action    No action is required. The system will recover automatically. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-2-270019: Retry of connection to dataserver did not succeed 

Explanation    The cache lost its connection to the data server and failed to reconnect.

Recommended Action    Collect technical support information, and contact Cisco TAC.

Error Message    CE-HTTP-2-270020: Retry of connection to dataserver did not succeed 

Explanation    The cache lost its connection to the data server and failed to reconnect. The cache will be restarted by the node manager.

Recommended Action    If the problem occurs frequently, save technical support information, and contact Cisco TAC.

Error Message    CE-HTTP-2-270021: Failed to get list after 3 retries 

Explanation    The cache failed to get the list from the data server. The system is opening a new connection to get the list.

Recommended Action    If the problem occurs frequently, collect technical support information, and contact Cisco TAC.

Error Message    CE-HTTP-2-270022: Failed to get connect to dataserver after 3 retries 

Explanation    The cache failed to get the list from the data server. The cache will exit and get restarted by the node manager.

Recommended Action    If the problem occurs frequently, collect technical support information, and contact Cisco TAC.

Error Message    CE-HTTP-2-270023: Failed to get list after 3 retries 

Explanation    The cache failed to get the list from the data server. The system is opening a new connection to get the list.

Recommended Action    If the problem occurs frequently, collect technical support information, and contact Cisco TAC.

Error Message    CE-HTTP-7-270024: Rule Sequence not found 

Explanation    The system could not find the rule sequence.

Recommended Action    No action is required.

Error Message    CE-HTTP-7-270025: Rule Item not found in Sequence 

Explanation    The system could not find the rule item in the sequence.

Recommended Action    No action is required.

Error Message    CE-HTTP-2-270026: Invalid switch during rule processing 

Explanation    The system encountered an invalid switch during rule processing.

Recommended Action    Collect support information, and contact Cisco TAC.

Error Message    CE-HTTP-2-270027: Invalid switch during rule processing 

Explanation    The system encountered an invalid switch during rule processing.

Recommended Action    Collect support information, and contact Cisco TAC.

HTTP-

Error Message    CE-HTTP-3/5-270000: Proxy failover service failed in ds ops: [failure 
description] 

Explanation    The outgoing proxy service failed in data server operations.

Recommended Action    If the problem occurs occasionally, it can be ignored. The service itself will retry a few times, or the node manager will restart the service. If the problem occurs frequently, contact Cisco TAC.

HTTP-3

Error Message    CE-HTTP-3-270001: Proxy failover service failed in sys calls: [failure 
description] 

Explanation    The outgoing proxy service fails in system calls (for example, select).

Recommended Action    If the problem occurs occasionally, it can be ignored. The node manager will restart the service (and retry the system calls). If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTP-3-270005: ERROR: xact == NULL when calling close_ntlm_conn 

Explanation    The transaction record contains no information.

Recommended Action    No action is required.

Error Message    CE-HTTPS-3-280000: https config: Host lookup failed 

Explanation    The host lookup failed during HTTPS configuration.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-HTTPS-3-280001: https config: Failed to record the CLI 

Explanation    The system failed to save the HTTPS configuration.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

HTTP-5

Error Message    CE-HTTP-5-270028: Informational message about DSCP processing 

Explanation    This message is informational and is about DSCP processing.

Recommended Action    No action is required.

Interactive Communicating Application Protocol Messages

This section contains Interactive Communicating Application Protocol messages.

ICAP-3

Error Message    CE-ICAP-3-690100:  Error during rpc to ICAP daemon: [failure 
description] 

Explanation    The system encountered an error during rpc communication between the cache process and the ICAP daemon.

Recommended Action    Collect a copy of the cache error log created in the time frame during which the syslog message was seen, and, if the problem persists, contact Cisco TAC.

Error Message    CE-ICAP-3-690110:  Error parsing HTTP header from ICAP daemon: [failure 
description] 

Explanation    The cache process encountered an error while parsing the HTTP headers in the message coming from the ICAP daemon.

Recommended Action    Collect a copy of the cache error log created in the time frame during which the syslog message was seen, and, if the problem persists, contact Cisco TAC.

Error Message    CE-ICAP-3-690120:  Error with ISTag from ICAP daemon: [failure 
description] 

Explanation    The system encountered an error in the ISTag operations from the ICAP daemon.

Recommended Action    Collect a copy of the cache error log created during the time frame the syslog message was seen, and, if the problem persists, contact Cisco TAC.

Internet Cache Protocol Messages

This section contains Internet Cache Protocol messages.

ICP-6

Error Message    CE-ICP-6-296001: heal_open_sock(): fail to bound to port 
<cluster_heal_port> 

Explanation    The system failed to bind to the port <cluster_heal_port> or failed to set the socket option associated with the port <clustter_heal_port>.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-ICP-6-296002: Healing Mode: the corner case happens 

Explanation    The ICP module is attempting to attach two pending requests to the same timer.

Recommended Action    No action is required.

Error Message    CE-ICP-6-296003: heal_set_pending_req(): pending_req is NULL 

Explanation    The pending request list is empty.

Recommended Action    No action is required.

Error Message    CE-ICP-6-296004: heal_init(): init free_index: num_threads = 
<num_threads>, NUM_THREADS = <NUM_THREADS> 

Explanation    The free index array for all working threads is initialized.

Recommended Action    No action is required.

Error Message    CE-ICP-6-296005: heal_init(): No more memory 

Explanation    The system failed to allocate memory for the pending request and the timer arrays.

Recommended Action    No action is required.

Internet Daemon Messages

This section contains Internet daemon messages.

INETD-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-INETD-n-810000: [Description] 

Explanation    These messages are generated by Inetd.

Recommended Action    If high priority error messages occur frequently, contact Cisco TAC.

IP/TV Program Manager Messages

This section contains IP/TV program manager messages.

IPTVPM-3

Error Message    CE-IPTVPM-3-680001:  Cannot open file 

Explanation    The specified file does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-680002:  Cannot open directory 

Explanation    The specified directory does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-680003:  Socket error 

Explanation    The system encountered a socket error.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-680004:  Send error 

Explanation    The system encountered an error in the send operation.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-680005:  receive error 

Explanation    The system encountered an error in the receive operation.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-680006:  Cannot create file 

Explanation    The system could not create a new file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-680007:  Cannot delete program using CDM API 

Explanation    The CDM API could not delete a program.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-680008: CDM API error 

Explanation    The system encountered an error in the CDM API Program Manager.

Recommended Action    Verify the reports and see the CDM documentation.

Error Message    CE-IPTVPM-3-680009: CDM Connection failed 

Explanation    The connection to the CDM API failed for the specified reason.

Recommended Action    Verify the specified message.

Error Message    CE-IPTVPM-3-681001:  Can't send out scoped address 

Explanation    The scoped address is not defined.

Recommended Action    Define the scoped address in the Preference page.

Error Message    CE-IPTVPM-3-681002:  Can't set multicast TTL 

Explanation    The system is unable to set the IP_MULTICAST_TTL.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-681003:  Can't create UDP socket 

Explanation    The system is unable to create the UDP socket.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-681005:  Invalid IP address 

Explanation    The IP address format is invalid.

Recommended Action    Enter IP address in the valid format.

Error Message    CE-IPTVPM-3-681006:  Can't close socket 

Explanation    The system was unable to close the socket.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-681007:  Cannot select a packet 

Explanation    The system could not select an SDR packet.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-681008:  Invalid SDP format 

Explanation    The SDP format is invalid and could not be processed.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-681009:  Session ID in use 

Explanation    The session ID is in use by another program, channel or recordings.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-683003:  Question is out of sync 

Explanation    The question list is out of sync.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-683004:  Cannot create question file 

Explanation    The system could not create the question file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-683005:  Invalid delete type 

Explanation    The delete type is invalid.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-683006:  Bad question number 

Explanation    The question number is wrong.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-683007:  Keepalive timed out 

Explanation    The keepalive timed out.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-683008:  Cannot accept connection 

Explanation    The system could not accept a new connection.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-683009:  Receive illegal status change 

Explanation    The system received an invalid status change.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-683010:  Receive illegal delete request 

Explanation    The system received an invalid request.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-3-683011:  Unknown request type 

Explanation    The system received an invalid request.

Recommended Action    Contact Cisco TAC.

IPTVPM-4

Error Message    CE-IPTVPM-4-684001:  Program's CDN channel has been deleted 

Explanation    The CDN channel, over which a schedule program is to be delivered, has been deleted.

Recommended Action    Edit the program, and select a different CDN channel. If a suitable channel is not available, request for a new channel from the CDN Administrator.

Error Message    CE-IPTVPM-4-684002:  Program's CDN channel has been modified 

Explanation    The CDN channel, over which a schedule program is to be delivered, has been modified.

Recommended Action    No action is required.

IPTVPM-5

Error Message    CE-IPTVPM-5-681000:  SDR Daemon started 

Explanation    The SDR daemon was started.

Recommended Action    No action is required.

Error Message    CE-IPTVPM-5-682000:  FTP Daemon started 

Explanation    The FTP daemon was started.

Recommended Action    No action is required.

Error Message    CE-IPTVPM-5-682700: Internal system call error 

Explanation    A system call failed.

Recommended Action    Contact Cisco TAC.

Error Message    CE-IPTVPM-5-683000:  Question Manager started 

Explanation    The question manager was started

Recommended Action    No action is required.

IPTVPM-6

Error Message    CE-IPTVPM-6-680010: Audio format is not supported 

Explanation    The selected audio format is not supported in the current release.

Recommended Action    No action is required.

Error Message    CE-IPTVPM-6-681004:  Rebuilding TVGuide Error 

Explanation    The system cannot rebuild the TVGuide periodically.

Recommended Action    Contact Cisco TAC.

IPTVPM-7

Error Message    CE-IPTVPM-7-680000:  <various messages> 

Explanation    These messagea are IPTV/CM Perl debug messages that are logged to syslog.

Recommended Action    No action is required.

Common Library Messages

This section contains common library messages.

LIBCMN-2

Error Message    CE-LIBCMN-2-520003: platform.c:platform_internal_type: can't open 
etc/MODEL: <error> 

Explanation    The Content Engine is not able to read the system cookie.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LIBCMN-2-520004: platform.c:platform_internal_type: can't figure 
out model from /etc/MODEL 

Explanation    The Content Engine failed to recognize the system cookie.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LIBCMN-2-520018: Could not get the memory size 

Explanation    The Content Engine failed to read the amount of memory available on the system. The Content Engine may operate in a degraded mode in such a case.

Recommended Action    If the problem persists after a reboot, contact Cisco TAC.

Error Message    CE-LIBCMN-2-520021: uudecode_binary(): malloc error for out buffer, 
return NULL 

Explanation    The Content Engine failed to obtain the memory required to perform a uudecode.

Recommended Action    If the problem persists after a reboot, contact Cisco TAC.

LIBCMN-3

Error Message    CE-LIBCMN-3-520002: Errorlog directory can't be created/accessed, 
errno = <number> 

Explanation    The error log module failed to create or access the directory where it places all the log messages.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LIBCMN-3-520005: The standby group <group no> could not be brought 
down 

Explanation    The interface of the group that failed could not be brought down.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LIBCMN-3-520006: Error while removing arp entries <error> 
CE-LIBCMN-3-520006: Could not remove the arp entry for <address> 

Explanation    The Content Engine could not remove the ARP entries associated with the failed interface.

Recommended Action    The stale ARP entries will eventually be timed out, and the fresh ones will be cached. If the problem occurs everytime a failover happens, contact Cisco TAC.

Error Message    CE-LIBCMN-3-520011: Error while trying to reach the gateway <error>. 

Explanation    The Content Engine encountered a problem when trying to reach the gateway.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LIBCMN-3-520012: Error opening socket for checking link status 
<erroCE-LIBCMN-3-520012: SIOCDEVPRIVATE on <interface> failed while checking link 
status <error> 

Explanation    The Content Engine encountered a problem when trying to check the interface link status.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LIBCMN-3-520013: Route <net_ip> <netmask> <gateway> could not be 
removed/added 

Explanation    The Content Engine encountered a problem when trying to add or remove the static IP routes after a failover link status.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LIBCMN-3-520022: fork_and_detach: [operation] failure: [error info] 

Explanation    The specified operation failed due to the error information specified. This is most likely a resource issue.

Recommended Action    If the problem persists after a reboot, contact Cisco TAC.

Error Message    CE-LIBCMN-3-520023: get_ext_ip: Got NULL pointer from DataServer, 
item_name= [object name] 

Explanation    The specified object could not be retrieved from the data server. These operations are usually performed as part of a command.

Recommended Action    Try the command again. If the problem persists after a reboot, contact Cisco TAC.

Error Message    CE-LIBCMN-3-520025: validate_url_signature <message describing error> 

Explanation    An error occurred when validating the URL signature, so the request for this URL failed.

Recommended Action    No action is required.

LIBCMN-5

Error Message    CE-LIBCMN-5-520001: Errorlog - messed up file name: <file name> 

Explanation    The error log file-naming code caused an error.

Recommended Action    Delete all the files in the /localX/errorlog directory.

Error Message    CE-LIBCMN-5-520009: Standby group <group no> is up on interface 
<interface> 

Explanation    The Content Engine found the <interface> to be usable and brought up the standby group on this interface.

Recommended Action    No action is required.

Error Message    CE-LIBCMN-5-520010: No interface of the standby group <group no> are 
usable. 

Explanation    The Content Engine could not find any usable interface in the standby group.

Recommended Action    Check if any of the member interfaces of the standby group are up. If not, check for cabling, Content Engine interface configuration, and switch configuration. If any of these areas has a problem then the standby feature has a problem, contact Cisco TAC.

Error Message    CE-LIBCMN-5-520014: Could not load kernel module [module name]. 

Explanation    The specified kernel module could not be loaded.

Recommended Action    Try the command again. If the problem persists after a reboot, contact Cisco TAC.

Error Message    CE-LIBCMN-5-520015: Could not unload kernel module [module name]. 

Explanation    The specified kernel module could not be unloaded.

Recommended Action    Try the command again. If the problem persists after a reboot, contact Cisco TAC.

Error Message    CE-LIBCMN-5-520016: Could not read proc interface for smbios. 

Explanation    The process interface to smbios could not be read.

Recommended Action    Try the command again. If the problem persists after a reboot, contact Cisco TAC.

Error Message    CE-LIBCMN-5-520017: Could not read proc interface for cpuinfo. 

Explanation    The process interface to cpuinfo could not be read.

Recommended Action    Try the command again. If the problem persists after a reboot, contact Cisco TAC.

Error Message    CE-LIBCMN-5-520019: Could not read proc interface for TVOut pci 
information. 

Explanation    The process interface used to access the TVOut pci information could not be read.

Recommended Action    Try the command again. If the problem persists after a reboot, contact Cisco TAC.

LIBCMN-6

Error Message    CE-LIBCMN-6-520007: Could not reach the default gateway on <interface> 

Explanation    The Content Engine could not reach the configured default gateway through the spiffiest interface. This message is informational.

Recommended Action    No action is required.

Error Message    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 

Explanation    The Content Engine could not bring up the specified interface when searching for a usable interface. This message is informational.

Recommended Action    No action is required.

LIBCMN-7

Error Message    CE-LIBCMN-7-520020: system() return value is > 255 

Explanation    system() returned a value greater than 255.

Recommended Action    No action is required.

Error Message    CE-LIBCMN-7-520024: <debug_print message> 

Explanation    This message is informational.

Recommended Action    No action is required.

Logging Messages

This section contains logging messages.

LOGGING-1

Error Message    CE-LOGGING-1-580005: Sysfs space dangerously low. Either remove some 
files on the SYSFS manually, or increase the SYSFS space. 

Explanation    The SYSFS is necessary for various critical functions of the system, and the system has found that the free space on the SYSFS is very low.

Recommended Action    Either remove some files on the SYSFS manually to make some free space available, or increase the size of the SYSFS.

Error Message    CE-LOGGING-1-580006: Kernel crash dumps were found. Immediate 
attention required. 

Explanation    Kernel crashes happened in this system earlier.

Recommended Action    Contact Cisco TAC.

LOGGING-2

Error Message    CE-LOGGING-2-580001: Could not create/attach/detach shared memory 
area. Debug commands may not work: <error> 

Explanation    The Content Engine failed to set up a critical shared memory area.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LOGGING-2-580002: Could not access/attach/detach shared memory 
area. Debug commands may not work: <error> 

Explanation    The Content Engine failed while accessing a critical shared memory area.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LOGGING-2-580003: table pointer NULL. Module: <module> 

Explanation    The module does not have access to a critical shared memory area.

Recommended Action    Contact Cisco TAC.

Error Message    CE-LOGGING-2-580004: Could not access/attach shared memory area. Debug 
commands may not work 

Explanation    The module failed while accessing a critical shared memory area.

Recommended Action    Contact Cisco TAC.

Label Switch Routing Messages

This section contains label switch routing messages.

LSR-2

Error Message    CE-LSR-2-642000: Generic Error 

Explanation    A generic error caused a process failure. The system might be unstable.

Recommended Action    If this problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Minimal Getty Messages

This section contains minimal getty messages.

MINGETTY-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-MINGETTY-n-810010: [Description] 

Explanation    These messages are generated by Mingetty.

Recommended Action    If high priority error messages appear frequently, contact Cisco TAC.

Module Utilities Messages

This section contains module utilities messages.

MODUTILS-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-MODUTILS-n-810020: [Description] 

Explanation    These messages are generated by module utilities.

Recommended Action    If high priority error messages appear frequently, contact Cisco TAC.

Network Attached Storage Messages

This section contains network attached storage messages.

NAS-0

Error Message    CE-NAS-0-205035: A&D prescan failed during NAS detachment process. 

Explanation    The prepositioned content database needs to be updated after the NAS detachment. An update failure occurred, rendering the database out of sync.

Recommended Action    Enter the acquisition-distribution database-cleanup command to clean up the prepositioned content database. This command could take a while to complete and should preferably be entered during off-peak hours.

NAS-1

Error Message    CE-NAS-1-205003: NAS was preempted by another CE. 

Explanation    The NAS was preempted by the Content Engine B when it was being used by Content Engine A. The Content Engine A will be forced to stop using the NAS to avoid NAS usage conflict, which may disrupt Content Engine A's normal operation. NAS preemption is NOT a recommended action.

Recommended Action    No action is required. Ensure that Content Engine B preempting the NAS is a planned operation.

NAS-2

Error Message    CE-NAS-2-205001: NAS signature was missing. 

Explanation    The NAS signature represents the NAS owner ship by the Content Engine. The signature was lost, possibly due to a NAS disk failure.

Recommended Action    Check for NAS disk access failure on the NAS device. NAS will not be attached to the ACNS Content Engine devices if the signature cannot be properly written to the NAS device.

NAS-3

Error Message    CE-NAS-3-205002: NAS signature was missing but was rewritten. 

Explanation    The NAS signature represents the NAS owner ship by the Content Engine. The signature was lost, possibly because the customers removed it by accident.

Recommended Action    Do not touch the NAS content after it is used by ACNS.

Error Message    CE-NAS-3-205004: NAS program can't read from stdin. 

Explanation    The NAS program was unable to access stdin, and thus was unable to get the yes/no input. Default input is yes.

Recommended Action    Check if the NAS command is running in a proper environment such that it can accept user inputs. Contact Cisco TAC if the command is manually entered.

Error Message    CE-NAS-3-205005: Can't retrieve max NAS share value. 

Explanation    The system cannot retrieve the maximum NAS share allowed on the Content Engine.

Recommended Action    Try to reload the device or reinstall the ACNS image.

Error Message    CE-NAS-3-205006 NAS file I/O error. 

Explanation    File operations on the NAS file failed.

Recommended Action    Check NAS network connection or NAS disk.

Error Message    CE-NAS-3-205007: / etc/nasinfo file content error.

Explanation    This message indicates an internal error.

Recommended Action    Reboot the Content Engine.

Error Message    CE-NAS-3-205008: FS-manager was terminated by signal. 

Explanation    The FS-manager was terminated by the system or user interrupt.

Recommended Action    No action is required.

Error Message    CE-NAS-3-205009: FS-manager failed. 

Explanation    This message indicates an internal error.

Recommended Action    Check the error message. Reboot the Content Engine, if necessary.

Error Message    CE-NAS-3-205010: NAS can't be removed because cdnfs quota exceeds cdnfs 
size. 

Explanation    The NAS volume could not be removed since the quota of all assigned channel(s) exceeds the remaining CDNFS space.

Recommended Action    Increase CDNFS space and modify the assigned channel(s).

Error Message    CE-NAS-3-205011: Failed to umount NAS. 

Explanation    The system could not detach the NAS volume.

Recommended Action    Check the error message.

Error Message    CE-NAS-3-205012: Failed to mount NFS NAS. 

Explanation    The system could not attach the NAS volume through NFS.

Recommended Action    Check the error message.

Error Message    CE-NAS-3-205013: Failed to mount CIFS NAS. 

Explanation    The system could not attach the NAS volume through the CIFS.

Recommended Action    Check the error message.

Error Message    CE-NAS-3-205014: Attempted to mount NAS twice. 

Explanation    The system attempted to attach the same NAS volume twice.

Recommended Action    Do not attach the same NAS volume twice.

Error Message    CE-NAS-3-205015: Can't retrieve eth0 mac address 

Explanation    The system could not retrieve the eth0 MAC address.

Recommended Action    Check the Eth0 hardware.

Error Message    CE-NAS-3-205017: NAS signature file content is invalid. 

Explanation    The NAS signature file is corrupted or has been altered.

Recommended Action    Check the NAS disk. Do not touch the NAS content when it is being used by ACNS.

Error Message    CE-NAS-3-205018: Multiple CEs tried to use same NAS at the same time. 

Explanation    Multiple Content Engines tried to access the NAS at the same time.

Recommended Action    No action is required. Only one Content Engine will succeed.

Error Message    CE-NAS-3-205019: Can't find unique NAS mount point. 

Explanation    The system could not find a unique NAS mount point.

Recommended Action    Try again.

Error Message    CE-NAS-3-205020: Content of NAS mntpnt file is invalid. 

Explanation    The NAS mntpnt file is corrupted or has been altered.

Recommended Action    Check the NAS disk. Do no touch the NAS content when it is being used by ACNS.

Error Message    CE-NAS-3-205021: Specified NAS disk size is invalid. 

Explanation    The specified NAS disk size exceeds its total volume size.

Recommended Action    Check the NAS disk size configuration.

Error Message    CE-NAS-3-205022: NAS was not really attached to the device. 

Explanation    The NAS was specified in the UI, but it was not attached to the device.

Recommended Action    Reattach the NAS and check the error message.

Error Message    CE-NAS-3-205024: NAS status was updated and fs-manager is notified

Explanation    The NAS status was updated because it had failed or was just recovered back online.

Recommended Action    No action is required

Error Message    CE-NAS-3-205033: Internal software error. 

Explanation    This message indicates an internal software error. The software is running abnormally.

Recommended Action    Reconfigure NAS. If reconfiguration fails, reboot the Content Engine.

Error Message    CE-NAS-3-205037: Invalid NAS configuration: server-ip, share-name, or 
network-configurations such as default-gw,domain-name-server, etc. 

Explanation    A previously configured NAS command was found to be invalid. A reason could be that a previously configured NAS hostname was not resolvable at a later time due to loss of network connectivity.

Recommended Action    Check the NAS and the network-related configuration on the device.

NAS-4

Error Message    CE-NAS-4-205016: Found alien signature on NAS volume. 

Explanation    The NAS volume is used by another Content Engine.

Recommended Action    No action is required.

Error Message    CE-NAS-4-205023: NAS status was updated. 

Explanation    The NAS status was updated either because NAS was attached or detached or because the network connection was up or down.

Recommended Action    Do not configure NAS on ACNS devices other than Content Engines.

Error Message    CE-NAS-4-205031: A&D object scan will occur as a result of NAS 
detachment. 

Explanation    An acquisition and distribution object scan aims at synchronizing the system database before a NAS volume is detached. It may take long if there are many objects in the NAS volume.

Recommended Action    No action is required. Do not interrupt the scan process.

Error Message    CE-NAS-4-205032: mediafs apps will be restarted due to NAS detachment. 

Explanation    The streaming applications using mediafs will be restarted due to NAS mediafs detachment.

Recommended Action    Schedule streaming applications beforehand, if you do not want the streaming services to be disrupted.

NAS-5

Error Message    CE-NAS-5-205025: Perform NAS preemption upon request from UI.

Explanation    The system performed a NAS preemption upon request from the UI.

Recommended Action    No action is required.

Error Message    CE-NAS-5-205026: Maximum allowable NAS shares exceeded. 

Explanation    Cannot add new NAS since max allowable NAS shares exceeded.

Recommended Action    Do not configure more NAS than the allowed number.

Error Message    CE-NAS-5-205027: Failed to register NAS health probe. 

Explanation    Internal error. Unable to register NAS health probe.

Recommended Action    Reboot the Content Engine.

Error Message    CE-NAS-5-205028: NAS is not supported in certain device mode. 

Explanation    NAS is supported only on Content Engines.

Recommended Action    No action is required.

Error Message    CE-NAS-5-205029: Previous NAS attachment process has not finished yet.

Explanation    You cannot detach a NAS before a previous attachment command on the NAS was finished.

Recommended Action    Wait for previous NAS attachment to finish before detaching NAS.

Error Message    CE-NAS-5-205030: Previous NAS detachment process has not finished yet.

Explanation    You cannot detach a NAS before a previous detachment command on the NAS was finished.

Recommended Action    Wait for previous NAS detachment to finish before attaching it.

Error Message    CE-NAS-5-205036: Signature file on <NAS> updated with hostname 
<hostname> 

Explanation    The hostname assigned to the device was changed. A signature file on the specified NAS was updated to reflect the change

Recommended Action    No action is required.

NAS-6

Error Message    CE-NAS-6-205034: [debug message] 

Explanation    These messages are used for debugging the NAS feature of ACNS software.

Recommended Action    No action is required.

Node Manager Messages

This section contains node manager messages.

NODEMGR-0

Error Message    CE-NODEMGR-0-330009: Nodemgr Exiting. 

Explanation    This message could be generated by a large set of unrecoverable error conditions. This message should be preceded by a more specific error message.

Recommended Action    Reboot Content Engine to recover. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-0-330011: Rebooting the device because of fatal system 
error. 

Explanation    A system call made by node manager was unsuccessful This message would be preceded by a system call failed message.

Recommended Action    No action is required, Content Engine will reboot shortly.

Error Message    CE-NODEMGR-0-330012: Could not fork process while attempting to 
reload: [errno]. 

Explanation    Forking of a process was unsuccessful during an attempted reboot.

Recommended Action    Content Engine will reboot. Power down the system if Content Engine fails to reboot. Attempt a reboot again after power up. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-0-330014: Hard reboot the device now due to timeout. 

Explanation    The Content Engine is going to reboot.

Recommended Action    No action is required. Content Engine should reboot. Power down if all else fails. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-0-330016: Rebooting the device because of unrecoverable 
error. 

Explanation    An unrecoverable system error has occurred. This message would be preceded by a more specific message about the system error. The device will reboot itself.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-0-330034: fork failed while stopping service [service 
name]. 

Explanation    The node manager could not fork a child process while attempting to stop a service.

Recommended Action    No action is required. Content Engine will reboot.

Error Message    CE-NODEMGR-0-330045: Rebooting the device because service [service] is 
dead 

Explanation    A critical service stopped. The only way to recover is by rebooting the Content Engine.

Recommended Action    No action is required, the Content Engine should reboot shortly. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-0-330096: REBOOT BOX NOW FROM WITHIN nodemgr_clt!!! 

Explanation    A reload request was made to the node manager client.

Recommended Action    The Content Engine will reboot. No action is required.

Error Message    CE-NODEMGR-0-330101: Nodemgr appears to have got restarted. Rebooting 
the system to avoid further damage, and to stabilize the system. 

Explanation    Node manager appears to have got restarted. Node manager restarts will be associated with multiple instances of same services running on the system, and this would result in various weird problems. Rebooting to stabilize the system.

Recommended Action    No action is required, but if the problem occurs frequently, contact Cisco TAC.

NODEMGR-1

Error Message    CE-NODEMGR-1-330064: [frame]: [function name]([arg1], [arg2], [arg3], 
[arg4],.... 

Explanation    The node manager has received a critical signal and will quit. The information displayed is a backtrace of the calls made by the node manager.

Recommended Action    Node manager should restart automatically and the device may run in an unstable mode. A reboot is recommended.

Error Message    CE-NODEMGR-1-330065: nodemgr: signal [signal no] received 

Explanation    The node manager has received a critical signal. A backtrace should follow this message and the node manager will most likely exit.

Recommended Action    Node manager should restart automatically and the device may run in an unstable mode. A reboot is recommended.

NODEMGR-2

Error Message    CE-NODEMGR-2-330008: Wait flash device timeout. Forcing a reboot 
now... 

Explanation    In case a reboot is requested when a flash operation is in progress, reboot is delayed till flash operation is completed. This message implies that the flash device was not free even after 15 minutes. Content Engine will be rebooted.

Recommended Action    No action is required. Content Engine should reboot soon.

NODEMGR-3

Error Message    CE-NODEMGR-3-330001: Memconfig: Can not get the config from flash 
[errno]

Explanation    Memconfig tool could not get saved configuration flash.

Recommended Action    Try reloading the device. If problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330002: Memconfig: Can not get the cookie info [errno] 

Explanation    Memconfig tool could not read the cookie.

Recommended Action    Try rebooting the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330003: Memconfig: Can not determine platform! Assume it 
is CE507! 

Explanation    Memconfig tool, could not determine the hardware device type. It is safe to assume lowest end platform CE507.

Recommended Action    Try rebooting the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330004: Memconfig: Can not open [template] file, [errno] 

Explanation    Memconfig tool, could not open the memconfig template file for reading.

Recommended Action    Try rebooting the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330005: Memconfig: Can not open [memconfig file] for 
write, [errno] 

Explanation    Memconfig tool could not open the memconfig file for writing.

Recommended Action    Try rebooting the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330010: system call '[system call]' failed, ret: [return 
code] errno: [error no] at [filename:lineno] 

Explanation    A system call made by node manager was unsuccessful. A more specific error message would precede this message.

Recommended Action    Refer to the recommended action of the preceding error message.

Error Message    CE-NODEMGR-3-330017: open failed("/dev/null", O_RDONLY) returned 
[retcode], errno = [errno] 

Explanation    An attempt to open the null device for reading failed. This signifies a more general system-level failure. This message should be accompanied by other messages explaining the failure.

Recommended Action    The Content Engine is in an unstable condition. If it fails to reboot itself, power cycle it. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330018: open [filename] failed: [errno] 

Explanation    The node manager failed to open a file for logging a service messages.

Recommended Action    No action is required, the messages will not be logged. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330019: dup failed: [errno] 

Explanation    The node manager could not duplicate a file descriptor to redirect the messages from application or service to log file.

Recommended Action    No action is required, the messages will not be logged. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330022: setrlimit for RLIMIT_CORE failed: [errno] 

Explanation    Node manager could not set the core dump limit.

Recommended Action    No action is required. The core dump size may not be limited. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330023: exited pid [process id] not my direct child 

Explanation    A process was terminated but was not directly spawned by the node manager.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-3-330025: Service [program name] died due to signal [signal 
no]:[signal name] 

Explanation    The specified service started by node manager stopped unexpectedly due to the specified signal.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330026: Service [program name] died abnormally with 
status [status no] 

Explanation    The specified service started by node manager stopped because of some abnormal condition.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330029: Someone is trying to kill with pid of [process 
id]. 

Explanation    An attempt was made to terminate a process with a zero or non-negative process id.

Recommended Action    If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330031: Can not kill process with pid: [process id] 

Explanation    Node manager attempted to terminate the specified process using SIGKILL.

Recommended Action    If a service is affected, try disabling and enabling the service. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330035: Service [service name] can not be successfully 
stopped. 

Explanation    The node manager was unable to stop the specified service.

Recommended Action    No action is required. Content Engine will reboot.

Error Message    CE-NODEMGR-3-330037: execve error while trying to stop service: 
[error]. 

Explanation    The node manager could not execute the stop command to stop a service.

Recommended Action    No action is required. The node manager will directly try to terminate the process.

Error Message    CE-NODEMGR-3-330038: Start service fork failed: [error]. 

Explanation    The node manager could not fork a process to start a service.

Recommended Action    No action is required. An attempt will be made again after a while, to start the service.

Error Message    CE-NODEMGR-3-330039: Service [service] has not returned within [sec] 
seconds. Will try stopping it. 

Explanation    The node manager started a service but the service has not responded for the specified number of seconds. It is probably waiting for some resource.

Recommended Action    No action is required. The node manager will stop the process and try to restart it later.

Error Message    E-NODEMGR-3-330041: Start Service execve error: [error]  

Explanation    The node manager tried to start a service but the execve command failed. Restart of the service will be attempted.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-3-330042: Service start program [program] does not exist? 
err: [errorno] 

Explanation    While checking service support binaries, the node manager could not find a specific binary to start a service.

Recommended Action    The installation of software could be incomplete or corrupt. Try reinstallation using copy ftp install or installation commands. Refer to software upgrade or install documentation.

Error Message    CE-NODEMGR-3-330043: Service stop program [program] does not exist? 
err: [errorno] 

Explanation    While checking services support binaries, the node manager could not find a specific binary to stop a service.

Recommended Action    The installation of software could be incomplete or corrupt. Try reinstallation using copy ftp install or installation commands. Refer to software upgrade or install documentation.

Error Message    CE-NODEMGR-3-330044: Service health_probe program [program] does not 
exist? err: [errno]  

Explanation    While checking services support binaries, the node manager could not find a specific binary to stop a service.

Recommended Action    The installation of software could be incomplete or corrupt. Try reinstallation using copy ftp install or installation commands. Refer to software upgrade or install documentation.

Error Message    CE-NODEMGR-3-330046: Stopping the service [service] because it is 
restarting too often. 

Explanation    The specified service has had to be restarted by Node manager more often than normally required.

Recommended Action    Check the related config or the related show commands to see why the service could not run normally. Check if there is coredump generated in /local1/ directory. If problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330047: Rebooting the device because service [service] 
keeps restarting 

Explanation    The Node Manager has restarted the specified service more often that normally required. The recommended way out of this problem is to reboot the device.

Recommended Action    No action is required. Box will reboot automatically. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330050: Fork for health_probe failed: [error] 

Explanation    The node manager could not fork to run a health probe.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330055: Health probe for service [service] failed, ret 
code: [error]. 

Explanation    The health probe for the specified service failed. The node manager will stop and restart the service if needed.

Recommended Action    No action is required. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330056: Health probe exit with a signal [signal] 

Explanation    A health probe started by the node manager exited with a specified signal. The node manager will stop the service and restart it, if needed.

Recommended Action    No action is required. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330057: Health_probe for service [service] died 
abnormally with status [error] 

Explanation    A health probe started by the node manager exited in an abnormal fashion. Node manager will stop the service and restart it, if needed.

Recommended Action    No action is required. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330060: waitpid returns error: [error no]. 

Explanation    The node manager was interrupted by an error when waiting in waitpid.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-3-330061: no child alive. 

Explanation    The node manager was waiting in waitpid and was restarted because all child process of the node manager were terminated

Recommended Action    No action is required.

Error Message    CE-NODEMGR-3-330063: Putenv error adding new path [path] 

Explanation    The node manager could not set the path environment variable. The node manager may not be able to start services properly.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330066: Failed to open [error], ret: [ret code], errno: 
[error no] 

Explanation    The node manager could not open the specified file. The node manager may not be able to get information about local disks and services may be affected.

Recommended Action    System may be in unstable condition, a reboot is recommended.

Error Message    CE-NODEMGR-3-330067: Too many local disks 

Explanation    Node manager found too many disks attached to the system. You are probably using an unsupported configuration.

Recommended Action    Check disk configuration. Disconnect any unsupported drives and then reboot.

Error Message    CE-NODEMGR-3-330076: Reboot requested by [reboot source]. 

Explanation    Reboot was requested by the specified source.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-3-330087: Error in read the req, errno: [error] 

Explanation    The node manager server could not read a request.

Recommended Action    The requesting application would display a separate error, which will specify the action to be carried out.

Error Message    CE-NODEMGR-3-330088: Failed to set NONBLOCK for new_fd, ret [status], 
errno [error code] 

Explanation    The node manager could not set the NONBLOCK attribute for a new file descriptor. The corresponding request will not be processed by the node manager.

Recommended Action    The requesting application would display a separate error, which will specify the action to be carried out.

Error Message    CE-NODEMGR-3-330089: Check request, select: ret = [status], errno = 
[error] 

Explanation    Select call failed while checking a request in the node manager server. The request will not be processed.

Recommended Action    The requesting application would display a separate error, which will specify the action to be carried out.

Error Message    CE-NODEMGR-3-330092: Program error, cancel NULL timer 

Explanation    A call was made to cancel a timer that does not exist.

Recommended Action    No action is required. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330093: Program error, cancel failed 

Explanation    The node manager was called to cancel a timer. However, the timer was not found in the node manager's internal structures. This problem could be because of memory corruption.

Recommended Action    Reboot the Content Engine. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330094: killtilldead: iteration count reached 60, bailing 
out (trying to kill [process]...) 

Explanation    The node manager was unable to successfully disable the specified process. The process could still be running and may interfere with normal device operations.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330095: parse_get_str: Can not allocate more memory! 

Explanation    The node manager could not allocate memory while parsing the configuration file.

Recommended Action    Do not reboot the Content Engine. Contact Cisco TAC.

Error Message    CE-NODEMGR-3-330100: nodemgr_accept_req: accept(...): [error] 

Explanation    The accept(2) system call failed unexpectedly.

Recommended Action    No action is required. If problems occur on the device, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330102: Could not create a flag to indicate that the 
nodemgr has been started. This may result in nodemgr deaths going undetected. 

Explanation    The software maintains a flag to detect node manager crashes. This flag could not be created. With this problem, in case node manager gets restarted, several instances of various services would run and this would result in strange problems.

Recommended Action    Reboot the Content Engine, and verify that the error message does not appear on reboot. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-3-330103: Raise alarm fail <service name> <alarm ID> 
(retcode) 

Explanation    The node manager detected a problem but could not raise an alarm.

Recommended Action    Check syslogs for other alarm-related failures. Alarm information on the device could be inconsistent and a reboot of the Content Engine may be required for recovery.

Error Message    CE-NODEMGR-3-330104: Raise alarm fail <service name> <alarm ID> 
(retcode) 

Explanation    The node manager could not clear an alarm.

Recommended Action    Check syslogs for other alarm-related failures. Alarm information on the device could be inconsistent and a reboot of the Content Engine may be required for recovery.

Error Message    CE-NODEMGR-3-330105: Keepalive problem: <description> [retcode] 

Explanation    The node manager had a problem while sending keepalives to the node health manager. The description will provide specific details.

Recommended Action    Check the syslogs for other alarm-related failures. A reboot is recommended if the keepalive alarm has been raised.

NODEMGR-4

Error Message    CE-NODEMGR-4-330021: chdir to [directory] failed: [errno] 

Explanation    Node manager could not change directory for changing directory attributes.

Recommended Action    No action is required. The core dump size may not be limited. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-4-330020: chmod for [directory] failed: [error] [errno] 

Explanation    Node manager could not change access permissions on the core dump directory while starting an application or service.

Recommended Action    No action is required. If the application causes a core dump, the core dump may not be logged.

Error Message    CE-NODEMGR-4-330070: nodemgr:touch_service_enabled_flag_file: could 
create /tmp/service_enabled ([service]) 

Explanation    The node manager could not create a flag file for the specified service.

Recommended Action    This could be a transient problem. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-4-330071: nodemgr:touch_service_enabled_flag_file: could 
not open [filename] ([error]) 

Explanation    The node manager could not open a flag file for the specified service.

Recommended Action    This could be a transient problem. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-4-330072: nodemgr:delete_service_enabled_flag_file: could 
not unlink [filename]  ([error]) 

Explanation    The node manager could not delete the flag file for the specified service.

Recommended Action    This could be a transient problem. If the problem persists, contact Cisco TAC.

NODEMGR-5

Error Message    CE-NODEMGR-5-330006: External Flash operation completed. 

Explanation    In case reboot is requested when a flash operation is in progress, reboot is delayed till flash operation is completed. This messages is to specify that the flash operation completed sucessfully and the device will reboot shortly.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330007: Flash device is busy, a software image upgrade 
might be under way, waiting for it to finish. 

Explanation    In case reboot is requested when a flash operation is in progress, reboot is delayed till flash operation is completed.

Recommended Action    No action is required, wait for flash device to be free.

Error Message    CE-NODEMGR-5-330013: Child failed to reload successfully. 

Explanation    The child process forked to invoke reboot was unsuccessful.

Recommended Action    Content Engine will reboot. Power down the system if Content Engine fails to reboot. Attempt a reboot again after powerup. If the problem persists, contact Cisco TAC.

Error Message    CE-NODEMGR-5-330015: DEVICE WILL BE REBOOTED SOON. 

Explanation    A reboot has been requested and Content Engine will be undergoing a reboot soon.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330024: Service [program name] exited normally with code 
[status]

Explanation    The specified service has exited as expected.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330027: pid [process id] exits 

Explanation    A process has exited.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330028: healthprobe pid [process id] exits 

Explanation    A health probe process has exited.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330030: Process [process id] killed with SIGTERM does not 
return within [millisecond] ms, trying to use SIGKILL. 

Explanation    The node manager attempted to terminate a process using SIGTERM, but the process did not return in the specified time.

Recommended Action    The process will be terminated using SIGKILL. If the problem occurs periodically, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-5-330032: Stopping service: [service name]. 

Explanation    The node manager is stopping the specified service.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330033: Service [service name] is already stopped. 

Explanation    An attempt was made to stop a service which is already stopped.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330036: Stop service [service name] using: [command] with 
pid: [process id] 

Explanation    This message is a notification from the node manager that the specified service is being stopped.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330040: Started service [service] using: [cmd] with pid: 
[pid] 

Explanation    The node manager has started the specified service.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330048: DEBUG: respawn_count = [count], period: [secs] 

Explanation    The node manager had to restart a process. This is the start of the process. The process was restarted within [secs] no of seconds.

Recommended Action    No action is required. Node manager may restart certain processes. However, if a process restarts very often, contact Cisco TAC.

Error Message    CE-NODEMGR-5-330051: Start health_probe for service [service] using: 
[cmd] with pid: [pid] 

Explanation    The node manager has started a heath probe service

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330054: DEBUG: service health probe took [sec] seconds to 
return 

Explanation    The health probe started by node manager was completed in [sec] seconds.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330059: "Switching to run level [runlevel no] 

Explanation    This is a debug message displayed by node manager. The node manager is switching its run level and will start services based on the new run level.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330068: personality_allows_service called for [service] 

Explanation    The personality_allows_service was called for the specified service.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330069: Device personality: [device personality], Service 
personality = [service personality] 

Explanation    The device personality and the service personality are displayed for debugging purposes.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330074: No personality found, setting default personal\ 
ity: CE.

Explanation    The node manager could not determine the device type. The type Content Engine will be assumed.

Recommended Action    Contact Cisco TAC.

Error Message    CE-NODEMGR-5-330075: Reboot requested by CLI. 

Explanation    Reboot was requested using the reload command.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330077: Reload config requested by [source]. 

Explanation    A request was made by the specified source to reload the node manager configuration file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-NODEMGR-5-330078: "Stop all services (except mingetty) requested by 
[source]. 

Explanation    A request was made by the specified source to the node manager to stop all services.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330079: Shutdown requested by [source]. 

Explanation    The specified source has requested the device to be shutdown.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330080: [source] requests start service [service] 

Explanation    The specified source has requested the node manager to start the specified service.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330082: [source] requests stop service [service]. 

Explanation    The specified source has requested the node manager to stop the service.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330084: [source] requests restart service [service]. 

Explanation    The specified source has requested the node manager to restart the specified service.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330085: [source] requests forcestart service [service] 

Explanation    The specified source has requested the node manager to start the specified service irrespective of the device mode.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-5-330091: ERROR: Not enough timer allocated, should never 
happen 

Explanation    The node manager has run out of timer resources. The device may be under heavy load. Additional memory will be allocated for the timer.

Recommended Action    It may be safer to reduce the load on the device. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NODEMGR-5-330099: Service log cleanup: [error] 

Explanation    There was a problem while cleaning up service logs. Node manager may not be able to clean up the service logs, but they will be taken care of by the logging monitor.

Recommended Action    No action is required.

NODEMGR-6

Error Message    CE-NODEMGR-6-330049: Service [service] is dead, do nothing according 
to the config. 

Explanation    The specified service has become inoperational and according to specifications should not be restarted.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-6-330097: Created codecoverage directory [dir path] 

Explanation    Codecoverage directory is created for a process. This should only be seen when running an instrumented image.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-6-330098: Error while creating codecoverage directory [dir 
path] 

Explanation    Codecoverage directory could not be created successfully for a process. This should only be seen for an instrumented image. If this message is seen, the process will not work properly.

Recommended Action    Contact code coverage change owner for investigating the problem.

NODEMGR-7

Error Message    CE-NODEMGR-7-330058: nodemgr: entering start_loop 

Explanation    The node manager has started running its main code loop.

Recommended Action    No action is required.

Error Message    CE-NODEMGR-7-330062: loop_counter = [count], child_pid = [pid] 

Explanation    Information used mainly for development purposes.

Recommended Action    No action is required.

Network Time Protocol Messages

This section contains Network Time Protocol messages.

NTP-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-NTP-n-340000: [failure-description] 

Explanation    Native Linux NTP code exposes error/notice/information.

Recommended Action    If the problem occurs, check NTP configuration or device configuration. If the problem occurs frequently, contact Cisco TAC.

NTP-3

Error Message    CE-NTP-3-340004: failed to open ntp [drift|config] file: [file-name] 

Explanation    NTP service failed to open NTP driftfile or configfile.

Recommended Action    Check NTP configuration. Check device status. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NTP-3-340005: nodemgr failed to start/stop ntpd 

Explanation    NTP command failed since the node manager could not start or stop NTPD.

Recommended Action    Check device status. Reboot the Content Engine. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-NTP-3-340006: failed to retrieve configuration from data-server, 
error=[err_code] 

Explanation    NTP command failed since the NTP binary could not retrieve configuration from the data server.

Recommended Action    Check device status. Reboot the Content Engine. If the problem occurs frequently, contact Cisco TAC.

NTP-5

Error Message    CE-NTP-5-340001: [host-ip/name]: not a valid host address 

Explanation    An invalid NTP server host address was specified.

Recommended Action    Retry with correct NTP server host address.

Error Message    CE-NTP-5-340002: Maximum NTP servers reached. 

Explanation    Maximum NTP server limit has been reached.

Recommended Action    Do not configure more NTP servers than the maximum limit.

Error Message    CE-NTP-5-340003: Must configure NTP servers before enabling NTP 
service. 

Explanation    No NTP server was configured so NTP service cannot be enabled.

Recommended Action    Configure at least 1 NTP server before enabling NTP service.

Error Message    CE-NTP-5-340008: failed to pre-sync system time and calendar. 

Explanation    Configured NTP servers fail to synchronize system time.

Recommended Action    Check whether the configured NTP servers are valid and reachable. Manually run ntpdate [ntp_server] to find out reasons for failure.

NTP-7

Error Message    CE-NTP-7-340007: [NTP debugging message] 

Explanation    NTP debugging information.

Recommended Action    No action is required.

Port to Application Mapping Messages

This section contains port to application mapping messages.

PAM-2

Error Message    CE-PAM-2-345008: Can not create directory for pam module <reason> 

Explanation    System does not have a configured tmp directory.

Recommended Action    System has severe software image setup or configuration problems. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-2-345010: Can not create log directory for pam module 

Explanation    System does not have a configured tmp directory.

Recommended Action    System has severe software image set up or configuration problems. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-2-345013: Failed to lock authentication statistical file 

Explanation    System fails to set software lock for request authentication statistical file to reset statistics. The statistical information of request authentication cannot be cleared.

Recommended Action    Check condition of the disks. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-2-345014: Can not create log directory for pam module 

Explanation    System does not have a configured tmp directory.

Recommended Action    System has severe software image setup or configuration problems. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-2-345022: Failed to lock authentication statistical file 

Explanation    System fails to lock the authentication statistical file to display statistics.

Recommended Action    Check condition of the disks. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

PAM-3

Error Message    CE-PAM-3-345000: Wrong authentication method to get authentication 
debugging 

Explanation    Wrong authentication method has been selected for debugging.

Recommended Action    Reconfigure authentication method parameters, check the disk condition, and set debug option again by running the command debug authentication... If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345001: Can't open file (TACACS+) 

Explanation    System fails to open configuration file etc/pam.d/ce_http_tacacs_config for request authentication via TACACS+ protocol. The authentication parameters cannot be saved.

Recommended Action    Check TACACS+ protocol configuration. Check the disk condition. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345002: Can't open file (RADIUS) 

Explanation    System fails to open configuration file etc/pam.d/ce_http_radius_config for request authentication via RADIUS protocol. The authentication parameters cannot be saved.

Recommended Action    Check RADIUS protocol configuration. Check disk condition. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345003: Can't open file (NTLM) 

Explanation    System fails to open configuration file etc/pam.d/ce_http_ntlm_config for request authentication via NTLM protocol. The authentication parameters cannot be saved.

Recommended Action    Check NTLM protocol configuration. Check disk condition. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345004: Can't open file (LDAP) 

Explanation    System fails to open configuration file etc/pam.d/ce_http_ldap_config for request authentication via LDAP protocol. The authentication parameters cannot be saved.

Recommended Action    Check LDAP protocol configuration. Check disk condition. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345005: Wrong option to set authentication debugging 

Explanation    Wrong authentication method has been set for debugging.

Recommended Action    Reconfigure authentication method parameters, check the disk condition, and set debug option again by executing command debug authentication. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345006: can't open /tmp/user_authenticate_debug file to set 
debugging information 

Explanation    System fails to open configuration file tmp/user_authenticate_debug file to set debugging information.

Recommended Action    Check the disk condition and set debug option again by running the command debug authentication... If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345007: can't open /tmp/request_authenticate_debug file to 
set debugging in formation 

Explanation    System fails to open configuration file tmp/request_authenticate_debug file to set debugging information.

Recommended Action    Check disk condition and set debug option again by running the command debug authentication... If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345009: Can't open /etc/pam.d/content_engine_config file 

Explanation    System fails to open configuration file etc/pam.d/content_engine_config for user authentication. The authentication parameters cannot be saved.

Recommended Action    Check user authentication configurative. Check disk condition. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345011: can't open /tmp/user_authenticate_stats file 

Explanation    System fails to open authentication statistical file /tmp/user_authenticate_stats to reset statistics. The statistical information of authentication cannot be cleared.

Recommended Action    Check disk condition. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345012: can't open /tmp/user_authenticate_stats file to 
report statistics 

Explanation    System fails to open authentication statistical file /tmp/user_authenticate_stats to update statistics. The statistical information of authentication is lost.

Recommended Action    Check disk. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345015: can't open /tmp/user_ldap_stats file 

Explanation    System fails to open LDAP authentication statistical file /tmp/user_ldap_stats to reset statistics. The statistical information of LDAP authentication cannot be cleaned.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345016: can't open /tmp/user_radius_stats file 

Explanation    System fails to open RADIUS authentication statistical file /tmp/user_radius_stats to reset statistics. The statistical information of RADIUS authentication cannot be cleaned.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345017: can't open /tmp/user_tacacs_stats file 

Explanation    System fails to open TACACS+ authentication statistical file /tmp/user_tacacs_stats to reset statistics. The statistical information of TACACS+ authentication cannot be cleaned.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345018: can't open /tmp/user_ntlm_stats file 

Explanation    System fails to open NTLM authentication statistical file /tmp/user_ntlm_stats to reset statistics. The statistical information of NTLM authentication cannot be cleaned.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345019: Failed to write authentication statistical file 

Explanation    System failed to write the authentication statistical file to reset statistics. The statistical information of authentication method cannot be cleaned.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345020: Failed to close authentication statistical file after 
writing 

Explanation    System fails to close the authentication statistical file after statistics is cleared.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345021: Failed to lock authentication statistical file 

Explanation    System fails to lock the authentication statistical file after statistics is cleared.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345023: Unknown authentication method 

Explanation    Wrong authentication method selected.

Recommended Action    Reconfigure authentication method parameters. Check disk condition. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345024: Filed to open statistical file for authentication 

Explanation    System fails to open authentication statistical file. Authentication method statistics cannot be displayed.

Recommended Action    Check authentication method configuration. Check disk condition. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345025: Statistical file is corrupted 

Explanation    Authentication statistical file has incorrect or corrupted information.

Recommended Action    Check authentication method configuration. Check disk condition. Clear authentication statistical information. Display statistical information again. If the statistical file is corrupted, contact Cisco TAC, otherwise continue to authenticate the users.

Error Message    CE-PAM-3-345026: Failed to close authentication statistical file after 
reading 

Explanation    System fails to close the authentication statistical file after statistics is displayed.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345027: A field of Statistical file is corrupted 

Explanation    Authentication statistical file has incorrect or corrupted information in one of the fields.

Recommended Action    Check authentication method configuration. Check disk condition. Clear authentication statistical information. Display statistical information again. If the statistical file is still corrupted, contact Cisco TAC, otherwise continue to authenticate the users.

Error Message    CE-PAM-3-345028: Failed to read authentication statistical file 

Explanation    System fails to read the authentication statistical file to display statistics.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345029: tmp directory doesn't exist 

Explanation    System does not have a configured tmp directory.

Recommended Action    System has a severe software image setup or configuration problem. Contact Cisco TAC.

Error Message    CE-PAM-3-345030: Failed to lock authentication statistical file 

Explanation    System fails to lock the authentication statistical file to display statistics.

Recommended Action    Check disk condition. Check if the system /tmp directory exists. If the problem persists, contact Cisco TAC.

Error Message    CE-PAM-3-345031: Can't open /etc/pam.d/print_services file 

Explanation    System failed to open configuration file etc/pam.d/print_services for print service authentication. The parameters of authentication could not be saved.

Recommended Action    If error message occurs, check print service's authentication configuration, check a condition of the disks. If the message repeats, contact Cisco TAC.

Parser Messages

This section contains parser messages.

PARSER-2

Error Message    CE-PARSER-2-350035: parser_server reconnect failed. 

Explanation    Shell failed to connect to parser server.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

PARSER-3

Error Message    CE-PARSER-3-350000: sysdb_bind failed: <str> 

Explanation    Parser server failed to establish connection with the data server, which contains the configuration registry.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350001: Bad arguments to parser_malloc 

Explanation    Parser attempted to allocate zero-size memory.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350002: Bad pointer to parser_free 

Explanation    Parser got null memory pointer to be freed.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350003: parser_free before parser_malloc called 

Explanation    Parser attempted to free the memory that was never allocated.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350004: Bad magic in parser free 1 

Explanation    Unexpected magic number detected in the memory block.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350005: Bad magic in parser free 2 

Explanation    Unexpected magic number detected in the memory block.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350006: sysdb_item_set of uint32 <str><dc><str> 

Explanation    Could not set an item in the data server

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350007: wrong sysdb datatype at <str>, <dc>, expect <dc> 

Explanation    Did not received expected type of data from the data server.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350008: sysdb_directory_get_last: '<error>' 

Explanation    sysdb_directory_get_last() failed.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350009: sysdb_item_set of packed <str>: <str> 

Explanation    Error occurred while retrieving data from the data server.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350010: sysdb_iterator_create: <str> 

Explanation    Error occurred while setting an option in the data server.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350011: sysdb_iterator_next_data() failed <str> 

Explanation    Error occurred in a data server operation.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350012: sysdb_iterator_free: <str> 

Explanation    Error occurred in a data server operation.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350013: <str> option Not Present:<str>, <str>, 

Explanation    Expected options are not present.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350014: <str>: new_cmd buffer null <function name> 

Explanation    Expected options are not present.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350015: <str> No endcoption mark for <hex>: <str> 

Explanation    No endcoption mark found.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350016: <str> Incomplete endcoption mark for <hex>: <str> 

Explanation    Incomplete endcoption mark found.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350017: <str>: invalid input (no 'B'): '<str>' 

Explanation    Invalid option found.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350018: <str>: bgcoption missing ',' after id: '<str>' 

Explanation    bgcoption is missing.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350019: <str>: bgcoption missing ',' after type: '<str>' 

Explanation    bgcoption is missing.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350020: <str>: bgcoption missing ',' after path count: 
'<str>' 

Explanation    bgcoption is missing.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350021: <str>:no nxcoption:'<str>' 

Explanation    An expected nxcoption is missing.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350022: <str>: incorrect nested coption:'<str>' 

Explanation    Incorrect nested ctoption is found.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350023: <str>: invalid NXCOPTION mark:'<str>' 

Explanation    Incorrect NXCOPTION mark is found.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350024: <str>: missing '=' in sysdb string <str> for 
command '<str>' 

Explanation    Missing = in sysdb string.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350025: <str>: Possible loop detected in command '<str>' 

Explanation    Loop detected in the command.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350026: <str>: missing equal '<' in sysdb string '<str>' 
for command '<str>' 

Explanation    Missing equal (=) symbol in sysdb string.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350027: <str>: Unknown object type <dec> in nvgen_command 

Explanation    Unknown object type found.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350028: <str>: Unknown object type <dec> in replace_type 

Explanation    Unknown object type found.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350029: Invalid object format '<str>' 

Explanation    Invalid object type found.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350030: <str>: debug registration failed: <dc> 

Explanation    Debug registration failed.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350031: sysdb_bind: <str> 

Explanation    Error occurred while establishing the connection with the data server.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350033: Shell failed to write msg to parser server. 

Explanation    Shell failed to write message to parser server.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350034: parser_server reconnect succeeded 

Explanation    Shell process was able to reconnect to parser server.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350036: Endoption doesn't match! <dec> 

Explanation    Syntax error: Endoption does not match.

Recommended Action    Retry the command. If the problem persists, reboot the Content Engine. If the problem persists even after rebooting, contact Cisco TAC.

Error Message    CE-PARSER-3-350038: Too many parser jobs from the shells. Have to 
restart. 

Explanation    Parser server process has been terminated as the number of concurrent parsing requests exceeded the maximum limit of 34.

Recommended Action    Limit the number of login sessions to 34.

PARSER-4

Error Message    CE-PARSER-4-350037: Too many parser jobs from the shells. Please save 
your work and exit some shells. 

Explanation    Number of sessions that concurrently submitted the parsing requests have reached 34 or more.

Recommended Action    Limit the number of login sessions to 34 or less.

PAC File Server Messages

This section contains PAC file server messages.

PFS-3

Error Message    CE-PFS-3-690010: Memory allocation failure 

Explanation    The PAC file server module has failed to allocate memory from the system. This failure can cause the PAC file server module to function improperly and may affect other software modules in the system. This problem can be caused by a software error and requires investigation. The system should restart the module if a crash occurs and reboot the Content Engine automatically if necessary.

Recommended Action    Run the show process memory command to confirm that the system memory has been used up. Restarting the system should provide an immediate workaround in most cases. To help debug this problem, gather the output of the show pac-file server info, show statistics pac-file server, and show process memory commands. Also, turn on debug logging by running the debug pac-file server all and logging disk priority debug commands for a while when this problem occurs. Send output from commands and all syslog files to Cisco TAC for further analysis.

Error Message    CE-PFS-3-690011: Cannot open file <filename> 

Explanation    The PAC file server module has difficulty opening internal data files when obtaining a configuration update. This failure can cause the PAC file server to run without a configuration or without configuration update, so that it functions improperly. This message may be caused by disk failure. This error message should appear whenever a configuration update occurs and the PAC file server cannot obtain the update.

Recommended Action    Run the show disk detail command to check the system disks. If a disk failure has occurred, contact Cisco TAC to replace the hardware. If there is no disk problem, turn on debug logging by running the debug pac-file server all and logging priority debug commands for a while when this problem happens. Send all syslog files to Cisco TAC for further analysis.

PFS-5

Error Message    CE-PFS-5-690001: PAC file server routing tables have been rebuilt 

Explanation    The routing table of the PAC file server module has been rebuilt because of configuration changes. This message is informational only and should appear whenever a configuration change in PAC files occurs and when information level logging is enabled.

Recommended Action    No action is required.

Error Message    CE-PFS-5-690002: PAC file server CE IP Address map has been rebuilt 

Explanation    The Content Engine name to IP address map has been rebuilt because of a configuration change. This message is informational only and should appear whenever a configuration change occurs in the Content Engine name to IP address mapping and information level logging is enabled.

Recommended Action    No action is required.

Preferences Module Messages

This section contains preferences module messages.

PM-3

Error Message    CE-PM-3-682601: memory allocation failed 

Explanation    Memory resource is exhausted.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682602: Preferences file does not exist 

Explanation    The preferences file containing the default information set by the administrator does not exist.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682603: cannot open <file> 

Explanation    The system cannot open the mentioned file, the file system is busy.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682604: cannot read <file> 

Explanation    The system cannot read the mentioned file, the file system is busy.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682605: Invalid Preferences file 

Explanation    The preferences file containing the default information is invalid or corrupted.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682606: Missing CDN information in Preference file 

Explanation    The preferences file containing the default information does not have all required CDN information.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682607: CDM <name/IP address> not responding 

Explanation    The preferences module is not able to establish a connection with the CDM.

Recommended Action    Verify if CDM is alive and reachable.

Error Message    CE-PM-3-682608: cannot resolve CDM hostname <name> 

Explanation    The CDM hostname cannot be resolved to an IP address by the preferences module.

Recommended Action    Verify that the correct hostname has been supplied in the Preferences page, verify DNS server is alive and reachable.

Error Message    CE-PM-3-682609: CDM information tag too long 

Explanation    The information returned by the CDM contains unrecognized field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682610: missing Origin FQDN field in info returned by CDM 

Explanation    The information returned by the CDM does not contain a required field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682611: No Id tag in CDM response 

Explanation    The information returned by the CDM does not contain a required field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682612: No Name tag found in CDM response 

Explanation    The information returned by the CDM does not contain the website name field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682613: No Fqdn tag found in CDM response 

Explanation    The information returned by the CDM does not contain the Fully Qualified Domain Name field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682614: missing WebSite Id field in CDM response 

Explanation    The information returned by the CDM does not contain the website identifier field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682615: Cannot find channel ID in CDM answer 

Explanation    The information returned by the CDM does not contain the channel identifier field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682616: Cannot find Channel Name tag in CDM answer 

Explanation    The information returned by the CDM does not contain the channel name field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682617: Cannot find Manifest URL in CDM answer 

Explanation    The information returned by the CDM does not contain the manifest URL field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682618: Cannot find RootCE in CDM answer 

Explanation    The information returned by the CDM does not contain the root Content Engine field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682619: cannot find CE status Id field in CDM answer 

Explanation    The information returned by the CDM does not contain the Content Engine status identifier field required to find the root Content Engine assigned to a CDN channel.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682620: cannot find CE IP address in CDM answer 

Explanation    The information returned by the CDM does not contain the root Content Engine IP address field.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682621: unrecognized reply for CE IP address in CDM answer 

Explanation    The information returned by the CDM contains an invalid or unrecognized format, the preferences module cannot extract the root Content Engine IP address of a given CDN channel.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682624: CDM Record size too long 

Explanation    The information returned by the CDM contains a record that is too large.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682625: Invalid CDM username and/or password 

Explanation    The preferences module is not able to connect with the CDM because the username and/or password in the Preferences page is incorrect for this CDM.

Recommended Action    Modify the CDM username or password with the one expected by the CDM.

Error Message    CE-PM-3-682626: Connection to CDM at <name/IP address> on port <port 
number> refused 

Explanation    The preferences module is not able to establish a connection with the CDM.

Recommended Action    Verify the connectivity with the CDM and if the CDM is functioning properly.

Error Message    CE-PM-3-682627: Error <number> returned from CDM at <name/IP address> 
on port <port number> 

Explanation    The CDM returned the HTTP error code <number>.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682628: Unknown answer from CDM at <name/IP address> on port 
<port number> 

Explanation    The information returned by the CDM is not recognized by the preferences module.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682629: CDMIM backend PID probe file cannot be created 

Explanation    File system is busy. The preferences module could not create a mandatory system file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682633: CDM reply not recognized 

Explanation    The reply from the CDM cannot be recognized.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682636: CDM <name/IP address> returned empty reply 

Explanation    The reply from the CDM API was invalid.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682637: CDM <name/IP address> returned invalid reply: 
<message> 

Explanation    The reply from the CDM API was not recognized.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682638: sendfetchnow failed: <message> 

Explanation    The command to indicate to the CDM to get the new or update the existing manifest file or program file failed.

Recommended Action    See CDM documentation.

Error Message    CE-PM-3-682639: <program> called with no parameters 

Explanation    An internal function was called with a wrong number of parameters.

Recommended Action    Contact Cisco TAC.

Error Message    CE-PM-3-682640: <program> called with invalid type 

Explanation    An internal function was called with an invalid parameter.

Recommended Action    Contact Cisco TAC.

PM-6

Error Message    CE-PM-6-682630: Skipping CDN channel <name> because of Null manifest 
file 

Explanation    The identified CDN channel does not have a manifest file URL linked with it, therefore it is useless.

Recommended Action    Add a manifest file URL if the CDN channel is required to export VoD programs to the CDN.

Error Message    CE-PM-6-682631: Skipping CDN channel <name> because it does not have 
a Root CE 

Explanation    The identified live CDN channel does not have a root Content Engine assigned to it and therefore cannot be used by this preferences module.

Recommended Action    If the CDN channel is required, assigne a root Content Engine on the CDM.

Error Message    CE-PM-6-682632: Skipping CDN channel <name> because it does not have 
an IP address for Root CE. 

Explanation    The preferences module was not able to get the root Content Engine IP address of the identified live CDN channel and therefore cannot use it.

Recommended Action    If this channel is required, ensure that a root Content Engine is assigned to this CDN channel and that it is alive.

Error Message    CE-PM-6-682634: CDM reply reports Request failed! (<message>) 

Explanation    The reply from the CDM API was not successful. The <message> contains the reply.

Recommended Action    See CDM documentation.

Error Message    CE-PM-6-682635: cdmim started 

Explanation    The CDM interface module has been activated

Recommended Action    No action is required.

Postgres Server Messages

This section contains postgres server messages.

POSTGRE-1

Error Message    CE-POSTGRE-1-661001: Lower free disk space on STATEFS partition: 
[failure description] 

Explanation    Database is filling the STATEFS partition. A&D content replication is temporarily stopped.

Recommended Action    To reclaim disk space on STATEFS, run the command cms database maintenance regular and cms database maintenance full, or schedule database maintenance more frequently. Database maintenance will impact certain services on Content Engine like live stream splitting and CMS Content Engine. If the free disk space on STATEFS is still less than 10% after database maintenance, it is possible that too much content has been replicated to the Content Engine. Contact Cisco TAC.

Error Message    CE-POSTGRE-1-661002: Unique index violation: [failure description] 

Explanation    Database server failed to validate for unique index and allowed insertion of duplicate key values into unique index.

Recommended Action    Run the command cms database maintenance. If the problem persists, then reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-POSTGRE-1-661003: Foreign key referential integrity violation: 
[failure description] 

Explanation    Database server failed to validate for foreign key and allowed insertion of a record with a foreign key not found in master table. Database could be corrupted.

Recommended Action    Contact Cisco TAC.

Error Message    CE-POSTGRE-1-661005: Unable to create Database connection: [failure 
description] 

Explanation    Database client unable to connect with the backend server. Possible reasons are Postgres server process could have been terminated, or could be hanging, or all database connections could be out.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-POSTGRE-1-661007: Failed to do full vacuuming: [failure 
description] 

Explanation    Postgres server returned error when vacuum daemon executed vacuum full SQL statement.

Recommended Action    Contact Cisco TAC.

Error Message    CE-POSTGRE-1-661008: Database reindexing is started: 

Explanation    A&D content replication is temporarily stopped until the reindexing is complete.

Recommended Action    Wait for reindexing to be completed.

Error Message    CE-POSTGRE-1-661009: Database full vacuuming is started: 

Explanation    A&D content replication is temporarily stopped until the vacuuming is complete.

Recommended Action    Wait for vacuuming to be completed.

Error Message    CE-POSTGRE-1-661010: Delete database records with non-unique value for 
primary key: 

Explanation    Detected and deleted the bad database records with duplicate value for primary key.

Recommended Action    Check if any content is missing for the channel with command show distribution channels. If some contents are missing, run command distribution refresh meta-data channel-name to recover metadata for the channel for receiver Content Engine, or run command acquirer stop-channel and then acquirer start-channel for root Content Engine.

Preload Messages

This section contains preload messages.

PRELD-2

Error Message    CE-PRELD-2-362001: Preload CLI sysdb bind error 

Explanation    Failed to bind to the system-wide configuration database.

Recommended Action    Reload the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-PRELD-2-362002: Preload notification registration failed 

Explanation    Notification registration for the preload proxy module failed.

Recommended Action    Reload the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-PRELD-2-362003: Preload select returned less than zero 

Explanation    The select call on preload socket descriptors failed.

Recommended Action    No action is required. If the problem occurs frequently, contact Cisco TAC.

PRELD-3

Error Message    CE-PRELD-3-363001: preload_threads_invoke(): Unable to start preload 
thread-[<thread_index>] 

Explanation    Failed to create the preload thread for the concurrent session with identity <thread_index>

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-PRELD-3-363002: preload_threads_invoke(): Unable to join preload 
thread-[<thread_index>] 

Explanation    Failed to join the preload for the concurrent session with identity <thread_index>

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-PRELD-3-363003: [preload] mms stream files won't be preloaded as 
wmt is not enabled. 

Explanation    WMT is not enabled, so MMS stream files will not be preloaded.

Recommended Action    Enable WMT. If the problem persists, contact Cisco TAC.

Error Message    CE-PRELD-3-363004: Error setting preload dscp: <item>, ret=<error_no:> 

Explanation    The DSCP setting for description of <item> http or WMT failed with error <error_no>.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

PRELD-5

Error Message    CE-PRELD-5-365001: preload: error <error_no> in bind to sysdb 

Explanation    Preload failed to bind to sysdb and returned the error <error_no>.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-PRELD-5-365002: <meta_info> 

Explanation    Preload meta information.

Recommended Action    No action is required.

Error Message    CE-PRELD-5-365003: Preloading is disabled 

Explanation    User has entered - no preload enable command.

Recommended Action    No action is required.

Router Blade Configuration Protocol Messages

This section contains Router Blade Configuration Protocol messages.

RBCP-1

Error Message    CE-RBCP-1-590019: RBCP: Nodemgr failed to reload in 60sec. Forcing a 
reload 

Explanation    The NM-CE failed to reload the node manager in a graceful manner.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

RBCP-3

Error Message    CE-RBCP-3-590003: IP Address configuration failed (type: <num>, sense 
= <num>, ip = <ip>, mask = <mask>) 

Explanation    IP address configuration on the NM-CE interface failed.

Recommended Action    Reconfigure the IP address on the router. If the error persists, contact Cisco TAC.

Error Message    CE-RBCP-3-590005: do_set_ip(): sendto: <message> 

Explanation    NM-CE failed while sending IP address configuration result to the router.

Recommended Action    Reconfigure the IP address on the router. If the error persists, contact Cisco TAC.

Error Message    CE-RBCP-3-590007: Default gateway configuration failed <default gw> 

Explanation    Default gateway configuration on the NM-CE failed

Recommended Action    Reconfigure the default gateway on the router. If the error persists, contact Cisco TAC.

Error Message    CE-RBCP-3-590009: do_set_defaultgw(): sendto: <message> 

Explanation    NM-CE failed while sending default gateway configuration result to the router.

Recommended Action    Reconfigure the default gateway on the router. If the problem persists, contact Cisco TAC.

Error Message    CE-RBCP-3-590011: do_shutdown(): sendto: <message> 

Explanation    NM-CE failed while sending the shutdown response to the router.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RBCP-3-590012: recvfrom <message> 

Explanation    NM-CE failed while receiving RBCP messages.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RBCP-3-590020: <name>: Error while opening socket: <error> 

Explanation    NM-CE failed while creating a socket.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RBCP-3-590021: <name>: Error in bind: <error> 

Explanation    NM-CE failed while binding a socket.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RBCP-3-590022: rbcpd: cannot fork: <error> 

Explanation    NM-CE failed while forking a process.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RBCP-3-590023: rbcp_register: exec_show_hardware return ret = 
<num>, ret1=<num>, ret2=<num> 

Explanation    The NM-CE failed while getting status information

Recommended Action    Contact Cisco TAC.

Error Message    CE-RBCP-3-590024: rbcp_register: can not open <name>: <error> 

Explanation    NM-CE failed while opening a file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RBCP-3-590025: rbcp_register: error while reading <name>: <error> 

Explanation    NM-CE failed while reading a file.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RBCP-3-590026: Error while sending registration message: <error> 

Explanation    NM-CE failed while sending registration message.

Recommended Action    Contact Cisco TAC.

RBCP-5

Error Message    CE-RBCP-5-590002: IP Address configuration successful (type: <num>, 
sense = <num>, ip = <ip>, mask = <mask>) 

Explanation    IP address configuration on the NM-CE interface was successful.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590004: Sending ip address configuration response. 

Explanation    Sending IP address configuration result to the router.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590006: default gateway configuration successful <default 
gw> 

Explanation    Default gateway configuration on the NM-CE was successful.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590008: Sending defaultgw configuration response. 

Explanation    Sending default gateway configuration result to the router.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590010: Sending shutdown complete message 

Explanation    NM-CE sending the shutdown complete message to the router.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590013: RBCP Registration ACK from <num>. 

Explanation    NM-CE received registration ack from router.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590014: RBCP Registration Request from <num>. 

Explanation    NM-CE received registration request message from router.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590015: RBCP IP address set message from <num> 

Explanation    NM-CE received IP address set message from router.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590016: RBCP default gateway set message from <num> 

Explanation    NM-CE received default gateway set message from router.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590017: RBCP shutdown message from <num> 

Explanation    NM-CE received shutdown message from router.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590018: RBCP reload message from <num> 

Explanation    NM-CE received reload message from router.

Recommended Action    No action is required.

Error Message    CE-RBCP-5-590027: rbcp_register: Registration message successfully 
sent. 

Explanation    NM-CE sent the registration message successfully.

Recommended Action    No action is required.

RBCP-7

Error Message    CE-RBCP-7-590001: <various messages> 

Explanation    Debug messages.

Recommended Action    No action is required.

RealProxy Messages

This section contains RealProxy messages.

REALPXY-2

Error Message    CE-REALPXY-2-382001: Failed to open CscoCache/Ruby disk 

Explanation    Failed to open CscoCache/Ruby disk.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

REALPXY-3

Error Message    CE-REALPXY-3-383001: [Procedure] Failed to set Real Proxy 
<incoming|outgoing> bandwidth <bw> <error_message> 

Explanation    Failed to change the bandwidth configuration of Real Proxy.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-REALPXY-3-383002: Failed to get [property_name] Property 

Explanation    The plugin failed to get the specified property.

Recommended Action    No action is required.

Error Message    CE-REALPXY-3-383003: Plugin Error 

Explanation    The error message should be descriptive.

Recommended Action    No action is required.

Error Message    CE-REALPXY-3-383004: Operation on [file] file failed 

Explanation    The operation failed on the given file.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-REALPXY-3-383005: Real Media Caching is disabled. 

Explanation    RealMedia caching is disabled by configuration.

Recommended Action    Enable using the GUI:Real Proxy->Caching, if needed.

Error Message    CE-REALPXY-3-383006: Failed to bind/unbind or get [info] information 
from the DS. 

Explanation    Failed to bind or unbind or get information from the data server as indicated by the message.

Recommended Action    Try the command again. If the problem occurs frequently, contact Cisco TAC.

REALPXY-4

Error Message    CE-REALPXY-4-384001: Warning 

Explanation    The message should be informative.

Recommended Action    No action is required.

REALPXY-7

Error Message    CE-REALPXY-7-387001: Real Proxy <incoming|outgoing> bandwidth set to 
<bw> 

Explanation    RealProxy bandwidth configurations.

Recommended Action    No action is required.

Error Message    CE-REALPXY-7-387002: Plugin debug messages 

Explanation    Plugin debug message.

Recommended Action    No action is required.

RealSubscriber Messages

This section contains RealSubscriber messages.

REALSRV-3

Error Message    CE-REALSRV-3-393010: [Procedure] Failed to set Real Subscriber 
bandwidth <bw> <error_message> 

Explanation    Failed to change the bandwidth configuration of RealSubscriber.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

REALSRV-7

Error Message    CE-REALSRV-7-397002: Real Subscriber bandwidth set to <bw> 

Explanation    RealSubscriber bandwidth configurations.

Recommended Action    No action is required.

Remote Proxy Caching Messages

This section contains remote proxy caching messages.

RPC-2

Error Message    CE-RPC-2-620000: Usage: [failure description] 

Explanation    Incorrect usage while invoking the program.

Recommended Action    Check the usage and try again. If the problem occurred without any intervention from user, contact Cisco TAC.

Error Message    CE-RPC-2-620001: Malloc failed: [failure description] 

Explanation    Malloc failed.

Recommended Action    Check errorlog for more information. The program will be restarted by node manager. If the problem persists, contact Cisco TAC.

Error Message    CE-RPC-2-620002: Failed to create [server description] server 

Explanation    Failed to create a unirpc server for inter-process communication.

Recommended Action    Check errorlog for more information. The program will be restarted by node manager. If the problem persists, contact Cisco TAC.

Error Message    CE-RPC-2-620003: Child process [pid] was killed unexpectedly with 
signal [signal number] 

Explanation    A dispatcher process trying to communicate outside the box stopped unexpectedly. This is a very rare situation.

Recommended Action    The dispatcher will recover automatically. If this happens on a CDM and if an item that was being configured at the time did not reach its intended destination, redo the configuration. Check CMS errorlog to see if it has any more information. If this happens on a non-CDM device, check appropriate interbox modules (e.g. distribution or CMS errorlogs) to see if you find any information. If there is no effect on the system, the error may be ignored, as some inter-box messages are not reliable and system will continue to function. If the problem persists, contact Cisco TAC.

Remote Shell Protocol Messages

This section contains Remote Shell Protocol messages.

RSH-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-RSH-n-810030: [Description] 

Explanation    These messages are generated by rsh.

Recommended Action    If high priority error messages occur frequently, contact Cisco TAC.

RealServer Manager Messages

This section contains RealServer manager messages.

RSM-2

Error Message    CE-RSM-2-402200: [register_verification] - Verifier register failed. 

Explanation    Registration with data server for verification failed.

Recommended Action    RSM will retry.

Error Message    CE-RSM-2-402201: [set_rlimit] - setrlimit() failed 

Explanation    Could not increase the file descriptors for RealServer process.

Recommended Action    RealServer performance would be affected. Contact Cisco TAC.

RSM-3

Error Message    CE-RSM-3-402300: [rsm_loop] - Error in processing VEN msg 

Explanation    RealServer manager was not able to process VEN msg.

Recommended Action    RealServer manager should reinitialize itself.

Error Message    CE-RSM-3-402301: [rsm_loop] - Health Probe failed for RS 

Explanation    None.

Recommended Action    RealServer manager should restart Real Server.

Error Message    CE-RSM-3-402302: [rsm_ds_bind] - Cannot bind to data server 

Explanation    Non.e

Recommended Action    RealServer manager should retry.

Error Message    CE-RSM-3-402303: [register_notification] - Register Notification 
failed 

Explanation    RealServer manager will not get notified by data server for this item.

Recommended Action    User may require to manually restart RealServer after IP address change.

Error Message    CE-RSM-3-402304: [unregister_verification] - Verifier unregister 
failed 

Explanation    Verifier unregister with data server failed.

Recommended Action    Check for rc value. No action is required.

Error Message    CE-RSM-3-402305: [start_real_server] - fork () or exec() failed 

Explanation    Content Engine may be out of system resources.

Recommended Action    RealServer manager will restart. Try enabling RealServer again.

Error Message    CE-RSM-3-402306: [get_rsm_pid] - Failed to read pid from pid file 

Explanation    NETRCM callback cannot send SIGUP to RealServer manager without its process ID.

Recommended Action    Try changes on the interface again, especially if you have changed the IP address.

Error Message    CE-RSM-3-402307: [rsm_loop] - Received SIGHUP from NETRCM callback 

Explanation    RealServer will be started or stopped after receiving SIGHUP.

Recommended Action    Need to start or stop RealServer from CDM.

Error Message    CE-RSM-3-402308: System call error: <system call name> <err msg> 

Explanation    System call failed. System might be in weird state.

Recommended Action    Try reenabling the service that caused this. Reboot if it does not work. If the problem persists, contact Cisco TAC.

Error Message    CE-RSM-3-402309: - Real Server Manager could not write to pid file 

Explanation    RealServer manager could not write to process ID file.

Recommended Action    Reenable the service that caused this problem. Reboot the Content Engine. If the problem persists, contact Cisco TAC.

RSM-4

Error Message    CE-RSM-4-402400: [main] - RSM restarted while Real Server is running 

Explanation    RealServer manager restarted. If RealServer is enabled playback will be affected. RealServer should restart itself.

Recommended Action    Check RealServer status using the command show rtsp server. Enable RealServer.

Error Message    CE-RSM-4-402401: [handle_signal] - Real Server died 

Explanation    RealServer process terminated. It can be a normal or an abnormal termination.

Recommended Action    RealServer manager should take action automatically depending on the enable status.

Error Message    CE-RSM-4-402402: [procedure] - INFO 

Explanation    None.

Recommended Action    No action is required.

Error Message    CE-RSM-4-402403: [rsm_loop] - RSM select() call returned error 

Explanation    None.

Recommended Action    Look up the errno variable value. No action is required.

Error Message    CE-RSM-4-402404: [unregister_notification] - Notifier unregister 
failed 

Explanation    Notifier unregister with data server failed.

Recommended Action    Check for rc value. No action is required.

Error Message    CE-RSM-4-402405: [verification_ack] - Verification ACK failed 

Explanation    Failed to build/send ACK to data server for verification message.

Recommended Action    Check for rc value. RealServer enable command changes would not take effect. RealServer manager will restart. Try the command again. If problem persists, contact Cisco TAC.

Error Message    CE-RSM-4-402406: [process_notification] - Get notifier info failed 

Explanation    Failed to get notification information from data server.

Recommended Action    RealServer manager should restart. Need to manually start/stop RealServer after IP address change.

Error Message    CE-RSM-4-402407: [process_notification] - Free Ven resources 

Explanation    Failed to free notification information.

Recommended Action    RealServer manager should restart. Need to manually start/stop RealServer after IP address change.

Error Message    CE-RSM-4-402408: [process_ven_msg] - Failed to process ven msg 

Explanation    None.

Recommended Action    RealServer manager should restart. Need to start/stop RealServer again.

RSM-6

Error Message    CE-RSM-6-402600: [process_notification] - 

Explanation    None.

Recommended Action    No action is required.

RSM-7

Error Message    CE-RSM-7-402700: [Procedure] - Debug MSG 

Explanation    None.

Recommended Action    No action is required.

Real Time Streaming Protocol Messages

This section contains Real Time Streaming Protocol messages.

RTSP-3

Error Message    CE-RTSP-3-403000: [Procedure] System call error: <system call name> 
<err msg> 

Explanation    System call failed. System might be in weird state.

Recommended Action    Reenable the service that caused the problem. If the problem persists, contact Cisco TAC.

Error Message    CE-RTSP-3-403001: [Procedure] RTSP [service] user license agreement 
not accepted <mesg> 

Explanation    RTSP Proxy or Subscriber user license agreement not accepted.

Recommended Action    Accept the license agreement and try enabling RTSP services.

Error Message    CE-RTSP-3-403002: [Procedure] Could not set Real [service] Logpath 
variable in temp file <mesg> 

Explanation    Failed to set the Real [service] logpath variable in temp file.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403003: [Procedure] Failed to move temp file with accesslog 
path variable to Real Proxy configuration file <error_message> 

Explanation    Failed to move the temp file to the configuration file.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403004: [Procedure] External/Fast Ethernet/Gigabit Ethernet 
IP not configured. Using the local host IP 

Explanation    External/Fast Ethernet/Gigabit Ethernet IP not available.

Recommended Action    Configure External/Fast Ethernet/Gigabit Ethernet IP and retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403005: [Procedure] Failed to disable Real [service] 
evaluation. on entering valid license key 

Explanation    Failed to disable Real Proxy/Subscriber evaluation. on entering valid license key.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403006: [Procedure] Failed to start/stop Real Subscriber 
<error_mesg> 

Explanation    Failed to start/stop RealSubscriber.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403007: [Procedure] Failed to disable Real [service] 
<error_mesg> 

Explanation    Failed to disable Real Proxy/Subscriber.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco

TAC.

Error Message    CE-RTSP-3-403008: [Procedure] Failed to enable Real [service] 
evaluation <error_msg> 

Explanation    Failed to enable Real Proxy/Subscriber.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403009: [Procedure] Failed to create symbolic link for Real 
Subscriber VOD <error_mesg> 

Explanation    Failed to create symbolic link for Real Subscriber VOD.

Recommended Action    Retry the command. If ithe problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403010: [Procedure] Failed to set Real Subscriber 
default/maximum archive file size 

Explanation    Failed to set RealSubscriber default/maximum archive file size.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403011: [Procedure] Failed to get Real [service] 
Configuration <error_mesg> 

Explanation    Failed to get Real Proxy/Subscriber configuration.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403012: [Procedure] Failed to execute IP address check 
script <error_mesg> 

Explanation    Failed to execute the script which checks for IP address.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403013: [Procedure] Host name not configured <error_mesg> 

Explanation    Host name configuration is not available.

Recommended Action    Configure the hostname and retry the command.

Error Message    CE-RTSP-3-403014: [Procedure] Real Server needs hostname other than 
local host <error_mesg> 

Explanation    RealServer needs host name other than local host.

Recommended Action    Configure the host name other than local host and retry the command.

Error Message    CE-RTSP-3-403015: [Procedure] No IP address available in /etc/hosts. 
<error_mesg> 

Explanation    No IP address available in /etc/hosts file.

Recommended Action    Configure the IP address and retry the command.

Error Message    CE-RTSP-3-403016: [Procedure] Unknown return status from IP address 
check script 

Explanation    Invalid return status received from the IP address check script.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403017: [Procedure] Real Proxy enable. 

Explanation    Could not create symbolic link for MEDIAFS mount point. Real Proxy would go in PASS THROUGH mode.

Recommended Action    Check current disk configuration for MEDIAFS partition. To enable real proxy, you must first configure MEDIAFS partition.

Error Message    CE-RTSP-3-403018: [Procedure] Failed to set [sprayer] bandwidth to 
[bandwidth] 

Explanation    Failed to set streaming sprayer bandwidth.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-3020: [Procedure] Failed to send sighup signal to [pid] 

Explanation    Failed to send sighup signal to the sprayer process.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403021: Number of MEDIAFS partitions exceed the max limit of 
[no] partitions. 

Explanation    The number of MEDIAFS partitions exceed the max limit and RealMedia cached content will not be cleared on certain MEDIAFS partitions.

Recommended Action    No action is required.

Error Message    CE-RTSP-3-403022: Real Server license directory was not set/invalid 

Explanation    Failed to set the real license directory or it is NULL.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-3-403021: Number of MEDIAFS partitions exceed the max limit of 
[no] partitions. 

Explanation    The number of MEDIAFS partitions exceed the max limit and RealMedia cached content will not be cleared on certain MEDIAFS partitions.

Recommended Action    No action is required.

Error Message    CE-RTSP-3-403022: Real Server license directory was not set/invalid 

Explanation    Failed to set the real license directory or it is NULL.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

RTSP-6

Error Message    CE-RTSP-6-406001: [Procedure] Disabled Real [service] evaluation on 
entering valid license key 

Explanation    Disabled Real Proxy/Subscriber evaluation.

Recommended Action    No action is required.

Error Message    CE-RTSP-6-406002: [Procedure] Maximum file size for Real Subscriber 
archiving <size> 

Explanation    RealSubscriber file size information.

Recommended Action    No action is required.

Error Message    CE-RTSP-6-406003: [Procedure] Started/Stopped the Real Subscriber 

Explanation    Started/Stopped the RealSubscriber.

Recommended Action    No action is required.

Error Message    CE-RTSP-6-406004: [Procedure] Enabled Real [service] evaluation 

Explanation    Enabled Real Proxy/Subscriber evaluation.

Recommended Action    No action is required.

Error Message    CE-RTSP-6-406005: [Procedure] [Interface type] IP not available using 
Interface type] IP 

Explanation    External/Fast Ethernet/Gigabit Ethernet IP not available.

Recommended Action    No action is required.

Error Message    CE-RTSP-6-406006: [Procedure] real proxy enable 

Explanation    RealProxy mount point information.

Recommended Action    No action is required.

RTSP-7 

Error Message    CE-RTSP-7-407001: [RTSP CLI Bin Debug Msg] 

Explanation    Debug message.

Recommended Action    No action is required.

Error Message    CE-RTSP-7-407002: [Procedure] Failed to get correct PID [pid] 

Explanation    Failed to get PID of the sprayer.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSP-7-407003: [Procedure] Application is not enabled 

Explanation    Application is not enabled.

Recommended Action    No action is required.

Error Message    CE-RTSP-7-407004: [RTSP Debug Msg] 

Explanation    Debug messag.e

Recommended Action    No action is required.

Real Time Streaming Protocol Gateway Messages

This section contains Real Time Streaming Protocol gateway messages:

RTSPG-2

Error Message    CE-RTSPG-2-408200: [Procedure] - RTSP Gateway error log init failed <error_mesg> 

Explanation    RTSP gateway error log initialization failed.

Recommended Action    If this message appears periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSPG-2-408201: [Procedure] - Failed to generate RTSP Gateway error 
log config file <mesg> 

Explanation    Failed to generate RTSP gateway error log configuration file when RTSPG debug level is changed.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSPG-2-408202: [Procedure] - Memory allocation failed during 
errorlog initialization for RTSP Gateway 

Explanation    Memory allocation failure. Attempted to allocate zero size memory.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-RTSPG-2-408203: [Procedure] - Failed to create/open RTSP Gateway 
errorlog client configuration file: <file_path> 

Explanation    Failed to create/open RTSP Gateway configuration file.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSPG-2-408204: [Procedure] - Failed to initialize debug library 
for RTSP Gateway 

Explanation    Failed to initialize debug library.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSPG-2-408205: [Procedure] - Interface IP address not configured 

Explanation    RTSPG failed to start. It requires interface IP address. RTSPG will remain idle for 15 seconds and exit.

Recommended Action    Configure interface IP address.

RTSPG-3

Error Message    CE-RTSPG-3-408300: [Procedure] - Failed to set item <mesg> 

Explanation    Failed to set item in the data server.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSPG-3-408301: [Procedure] - Unable to signal self to get errlog 
config <mesg> 

Explanation    Unable to send signal to self to get errlog configuration.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSPG-3-408302: [Procedure] - Failed to restart RTSPG after incoming port change 

Explanation    Failed to restart RTSPG after incoming port change.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RTSPG-3-408303: Failed to get/set item [name] in dataserver 

Explanation    The RTSP Gateway module has failed to get/set item [name] from the data server. The error number for the get/set is [x].

Recommended Action    The system should recover from the error automatically. If the problem persists or occurs very frequently, contact Cisco TAC.

Rules Messages

This section contains rules messages. These rules are used for filtering URLs.

RULES-2

Error Message    CE-RULES-2-412001: <procedure>: invalid switch 

Explanation    Encountered an invalid pattern or action type.

Recommended Action    Check rule configuration. If the problem persists, contact Cisco TAC.

Error Message    CE-RULES-2-412002: <procedure>: rule is NULL 

Explanation    The argument rule passed a NULL pointer.

Recommended Action    Check rule configuration. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RULES-2-412003: rule_del(): <parameter> entry not found 

Explanation    Tried to remove a parameter which is not configured.

Recommended Action    Use show rule all command to check for configured parameters.

Error Message    CE-RULES-2-412004: default switch in <procedure> 

Explanation    Encountered an invalid pattern type.

Recommended Action    Check rule configuration. If the problem persists, contact Cisco TAC.

Error Message    CE-RULES-2-412005: <procedure> error: invalid else 

Explanation    Pattern type is neither SRC_IP nor DST_IP.

Recommended Action    Check rule configuration. If the problem persists, contact Cisco TAC.

Error Message    CE-RULES-2-412006: error allocating new pattern table 

Explanation    System failed to allocate memory for the new pattern table.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-2-412007: Error allocating new action table 

Explanation    System failed to allocate memory for the new action table.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-2-412008: error allocating new Rule table 

Explanation    System failed to allocate memory for the new rule table.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-2-412009: rule_of_port_sort() error: NULLP 

Explanation    The argument passed for sorting is a null pointer.

Recommended Action    Check rule configuration for configured destination ports. If the problem persists, contact Cisco TAC.

Error Message    CE-RULES-2-412010: Rule:pattern_match_request: failed to alloc memory 

Explanation    System failed to allocate memory for the new pattern list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-2-412011: rule_show_stat(); Internal error 

Explanation    Rule statistics entry is NULL.

Recommended Action    Check rule configuration. If the problem persists, contact Cisco TAC.

RULES-3

Error Message    CE-RULES-3-413001: <procedure>: Can't create new list 

Explanation    System failed to allocate memory for the new list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413002: rule_add_port(): new_list_head is NULL 

Explanation    System failed to allocate memory for the new port list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413003: rule_add_port(): cur_list NULL 

Explanation    System failed to allocate memory for the new port list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413004: rule_create_port_list(): failed to malloc 
new_list_head 

Explanation    System failed to allocate memory for the new port list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413005: rule_create_ip_list() new_list is NULL 

Explanation    System failed to allocate memory for the new IP list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413006: rule_del_ip(): error creating new list 

Explanation    System failed to allocate memory for the new IP list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413007: rule_add_regex(): failed to create new list 

Explanation    System failed to allocate memory for the new regex list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413008: rule_create_regex_list(): memory allocation failed 

Explanation    System failed to allocate memory for the new regex list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413009: rule_create_regex_list() can't allocate regex 

Explanation    System failed to allocate memory for new regex list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413010: rule_del_regex(): failed to create new list 

Explanation    System failed to allocate memory for the new regex list.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413011: ctype is null 

Explanation    The ctype member in the response header may have null value.

Recommended Action    No action is required. The system deliberately checks for the null value.

Error Message    CE-RULES-3-413012: error allocation new action table 

Explanation    System failed to allocate memory for the new action table.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413013: Malloc for action_sel failed 

Explanation    System failed to allocate memory.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413014: rule_process_verif_msg(): <filename> <line_no> 
<ds_get_verification_info call failed> errno = <error_no> 

Explanation    The ds_get_verification_info call failed with error no <error_no> in file <filename> line <line_no>.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413015: register_verifier(): <filename> <line_no> 
<register_verifier failed for item> <item> 

Explanation    The register_verifier call failed for item <item> in file <filename> line <line_no>.

Recommended Action    Contact Cisco TAC.

Error Message    CE-RULES-3-413016: rule_server_main(): ERROR request processing timed 
out 

Explanation    Request timed out.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RULES-3-413017: rule_server_rpc_main(): RpcUdsServer_new() 
returned NULL server 

Explanation    Launching of new rule_server might have failed.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-RULES-3-413018: rules_daemon : RpcUdsServer_accept returned a NULL 
client 

Explanation    The RpcUdsServer_accept returned a null client.

Recommended Action    No action is required. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RULES-3-413019: rules_daemon() client_thread_create failed err = 
<error_no> 

Explanation    Creation of new client thread failed with error no <error_no>.

Recommended Action    No action is required. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RULES-3-413020: rule_init_cfg() Failed to bind to sysdb 

Explanation    Failed to bind to data server. The cache process will be restored automatically.

Recommended Action    No action is required. If the message appears frequently, contact Cisco TAC.

Error Message    CE-RULES-3-413021: rule_init_cfg() Failed to get the list from sysdb 

Explanation    Failed to get the list from the data server. A new connection will be opened to retry the operation.

Recommended Action    No action is required. If the problem occurs frequently, contact Cisco TAC.

RULES-5

Error Message    CE-RULES-5-415001: Ignoring invalid URL rewrite original URL=<old_url> 
new URL=<new_url> 

Explanation    Invalid URL rewrite ignored.

Recommended Action    No action is required

Error Message    CE-RULES-5-415002: Ignoring invalid URL transformation URL=<old_url> 
new URL=<new_url> 

Explanation    Invalid URL transformation ignored.

Recommended Action    No action is required.

Error Message    CE-RULES-5-415003: rule_show_stat(); Error opening tty 

Explanation    Failed to open the terminal for writing rules statistics.

Recommended Action    No action is required.

RULES-6

Error Message    CE-RULES-6-416001: rule_del_port(): old_list is NULL 

Explanation    The old port list may be empty.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416002: send_verif_ack(): error building ack, error = 
<error_no> 

Explanation    Error in building the acknowledgment message.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416003: rule_process_verif_msg(): unknown event = 
<sysdb_info.event> 

Explanation    Unknown event encountered while receiving rule process verification message.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416004: rule_process_notif_msg(): <file_name> <line_no> 
<ds_get_notification_info call failed> errno = <error_no> 

Explanation    Error <error_no> occurred in file <file_name>, line <line_no> while receiving rule process notification message.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416005: rule_process_notif_msg(): <file_name> <line_no> 
ds_free_ven_resource failed 

Explanation    Error occurred in file <file_name>, line <line_no> when the data server tried to free the resource.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416006: Failed to get the full message from the ds 

Explanation    Rule process failed to receive the complete message from the data server.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416007: rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_action_notif_tuple> Err <error_no> 

Explanation    Error <error_no> occurred in file <file_name>, line <line_no> for item <rule_action_notif_tuple> when the rule process registered notification.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416008: rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_pattern_notif_tuple> 

Explanation    Error occurred in file <file_name>, line <line_no> for item <rule_pattern_notif_tuple> when the rule process registered notification.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416009: rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_pattern_delta_tuple> 

Explanation    Error occurred in file <file_name>, line <line_no> for item <rule_pattern_delta_tuple> when the rule process registered notification.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416010: rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_debug_notif_tuple> 

Explanation    Error occurred in file <file_name>, line <line_no> for item <rule_debug_notif_tuple> when the rule process registered notification.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416011: rule_register_notifier(): <file_name> <line_no> 
<rule_register_notifier failed for item> <rule_action_delta_tuple> 

Explanation    Error occurred in file <file_name>, line <line_no> for item <rule_action_delta_tuple> when the rule process registered notification.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416012: Rule Item Not found in the Sequence 

Explanation    Rule item not found in the fetched sequence.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416013: rule_daemon: Bind failed in sysdb 

Explanation    Data server failed to bind the socket.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-RULES-6-416014: send_verif_ack(): error sending ack, error = 
<error_no> 

Explanation    Error in message acknowledgment.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416015: rule_process_notif_msg (): Unknown Event 

Explanation    Unknown event occurred when sending rule process notification message.

Recommended Action    No action is required.

Error Message    CE-RULES-6-416016: gui_rules: Length of pattern exceeds the limit 
(dislpay_str) 

Explanation    Contet Engine GUI does not display this pattern.

Recommended Action    No action is required.

Scheduler Messages

This section contains scheduler messages.

SCHED-2

Error Message    CE-SCHED-2-189000: Missing scheduler working thread.

Explanation    One of the worker threads, to which the scheduler assigns work, has unexpectedly terminated. The Content Engine web proxy cache will attempt to recover by restarting itself.

Recommended Action    Contact Cisco TAC.

SCHED-4

Error Message    CE-SCHED-4-189002: Scheduler CLI memory allocation failure.

Explanation    A memory resource allocation failed, which may result in some commands failing.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-SCHED-4-189003: Scheduler CLI file open failure.

Explanation    A file could not be opened, which may result in some commands failing.

Recommended Action    If the problem persists, contact Cisco TAC.

SCHED-5

Error Message    CE-SCHED-5-189001: Reporting of thread and process identifiers.

Explanation    Upon startup, the Content Engine scheduler reports the internal process and thread identifiers. Such information may be useful in debugging problems.

Recommended Action    No action is required.

SMART Disk Messages

This section contains SMART disk messages.

SMARTD-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-SMARTD-n-435000: [failure-description]

Explanation    Native Linux SMARTD code exposes error/notice/information.

Recommended Action    SMARTD log messages mean disk health-related attributes have changed. These changes may indicate possible disk failure in the near future. When seeing SMARTD error messages, backup data on the concerned disks.

Simple Network Management Protocol Messages

This section contains Simple Network Management Protocol messages.

SNMP-2

Error Message    CE-SNMP-2-430001: bind_dataserver_sock() failed: <return value> 

Explanation    Could not connect to the data server.

Recommended Action    SNMP agent will not be able to accept configurations from the command, send traps or retrieve any CISCO-CONTENT-ENGINE-MIB statistics. Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-2-430008: [filename] has more data than SNMP Agent 
expects:possible kernel version and SNMP Agent application code mismatch. 

Explanation    Unexpected number of data fields found in a /proc file.

Recommended Action    Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-2-430009: Incorrect number of data items found in [filename] 

Explanation    Unexpected number of data fields found in a /proc file.

Recommended Action    Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-2-430010: / proc/net/snmp header line has unexpected format. 
Possible kernel version and SNMP Agent application code mismatch. 

Explanation    Unknown header information found in /proc/net/arp.

Recommended Action    Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-2-430011: / proc/net/snmp sscanf parsing error STAT_NET_ICMP 
entry.num_items read = <dc>, num_items expected = 26 

Explanation    Unknown number of data fields found in /proc/net/snmp.

Recommended Action    Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    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. 

Explanation    Unknown number of data fields found in /proc/net/snmp.

Recommended Action    Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-2-430013: snmp Agent process terminated. 

Explanation    SNMP agent process terminated because of the failure in data server connection.

Recommended Action    SNMP agent process will be restarted by the node manager process. Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-2-430018: SNMP server: malloc error. <size> <function_name>. 

Explanation    Memory allocation error.

Recommended Action    Try to reenable SNMP. Also try rebooting the Content Engine. If the problem persists, contact Cisco TAC.

SNMP-3

Error Message    CE-SNMP-3-430005: [Procedure]:Failed open [filename]. errno: [dc], 
[str] 

Explanation    Error occurred while opening [filename] file.

Recommended Action    Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-3-430006: [Procedure]: Failed to read [filename]. errno: [dc], 
[str] 

Explanation    Encountered an error while reading a /proc file.

Recommended Action    Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-3-430007: [Procedure]: Failed to read [filename]. End-of-file. 

Explanation    Encountered unexpected end-of-file in a /proc file.

Recommended Action    Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-3-430014: SNMP server could not set Contact data item in 
Dataserver (error code). 

Explanation    A change was made in the SNMP server contact information, but the change could not be recorded in the data server.

Recommended Action    Try setting the contact data item again. Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-3-430015: SNMP server could not set Location data item in 
Dataserver (error code). 

Explanation    A change was made in the snmp server Location information, but the change could not be recorded in the data server.

Recommended Action    Try setting the location data item again. Try to reenable SNMP. If the error persists, contact Cisco TAC.

SNMP-5

Error Message    CE-SNMP-5-430002: ds_edm_register() failed: <item name return value> 

Explanation    EDM registration failed with the data server <return value>.

Recommended Action    SNMP agent recovers from it automatically. Run the show snmp event to see if this command is functioning properly. Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-5-430003: ds_verification_register() failed: <str> 

Explanation    Verification registration with the data server failed.

Recommended Action    You will not be able to configure SNMP related features. Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-5-430004: ds_notification_register() failed: <str> 

Explanation    Notification registration with the data server failed.

Recommended Action    SNMP agent may not be able to generate traps. Try to reenable SNMP. If the problem persists, contact Cisco TAC.

Error Message    CE-SNMP-5-430016: SNMP server is resetting the connection with the 
Dataserver.

Explanation    SNMP Server will reset the data server connection because of data server communication error, .

Recommended Action    No action is required.

Error Message    CE-SNMP-5-430017: SNMP server is resetting the connection with the Node 
Health Manager. 

Explanation    SNMP server will reset the connection with the node health manager because of node health manager error.

Recommended Action    No action is required.

Secure Shell Messages

This section contains Secure Shell (SSH) messages.

SSHD-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-SSHD-n-440000: [failure-description] 

Explanation    Native Linux SSHD code exposes error/notice/information.

Recommended Action    Check SSHD configuration or device configuration. If problem occurs frequently, contact Cisco TAC.

SSHD-3

Error Message    CE-SSHD-3-440001:  read [ssh_session_file] failed, 
errno=[err_code]([failure-description]). 

Explanation    SSH service failed in reading ssh_session_file.

Recommended Action    If this problem occurs occasionally, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-SSHD-3-440002: write [ssh_session_file] failed, 
errno=[err_code]([failure-description]). 

Explanation    SSH service failed in writing ssh_session_file.

Recommended Action    If this problem occurs occasionally, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-SSHD-3-440003: lseek [ssh_session_file] failed, 
errno=[err_code]([failure-description]). 

Explanation    SSH service failed in seeking ssh_session_file.

Recommended Action    If this problem occurs occasionally, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-SSHD-3-440004: can't open [ssh_session_file], 
errno=[err_code]([failure-description]). 

Explanation    SSH service failed in opening ssh_session_file.

Recommended Action    If this problem occurs occasionally, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-SSHD-3-440005: can't create [ssh_session_file], 
errno=[err_code]([failure-description]). 

Explanation    SSH service failed in creating ssh_session_file.

Recommended Action    If this problem occurs occasionally, it can be ignored. If it occurs frequently, contact Cisco TAC.

Error Message    CE-SSHD-3-440006: failed to start /usr/sbin/sshd, 
[failure-description]. 

Explanation    SSH service failed in starting SSHD process.

Recommended Action    Retry the related SSH command. Restart SSH service. Reboot the Content Engine. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-SSHD-3-440007: usr/sbin/sshd did not exit, [failure-description]. 

Explanation    SSH service failed because SSHD process did not exit.

Recommended Action    Retry the related SSH command. Restart SSH service. Reboot the Content Engine. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-SSHD-3-440008: ssh session failed, possibly because of incorrect 
login. 

Explanation    SSH session failed, possibly because of incorrect login, or because of internal SSHD errors.

Recommended Action    Retry SSH login with correct username/password.

Error Message    CE-SSHD-3-440009: ssh session succeeded. 

Explanation    SSH session proceeded successfully.

Recommended Action    No action is required.

Error Message    CE-SSHD-3-440010: Internal error: Could not change owner (error) 

Explanation    SSH could not be enabled because of an internal error.

Recommended Action    Contact Cisco TAC.

Streaming Server Messages

This section contains streaming server messages.

SSRV-3

Error Message    CE-SSRV-3-678300: Error occurred in Streaming Server. <error msg> 

Explanation    Error occurred in streaming server.

Recommended Action    No action is required.

Statistics Messages

This section contains statistics provider application messages.

STATS-3

Error Message    CE-STATS-3-600004: Failed to open /proc/net/netstat. 

Explanation    The statistics provider application could not open the process interface.

Recommended Action    Try the command again. If the problem persists, contact Cisco TAC.

Error Message    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]. 

Explanation    The /proc/net/netstat format and the format expected by the statistics provider application vary.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600006: / proc/net/netstat had sscanf parsing error. 
num_items read = %d, num_items expected = 65 

Explanation    The /proc/net/netstat format and the format expected by the statistics provider application vary.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600007: Failed to open /proc/net/snmp. errno: [error], 
[description] 

Explanation    The statistics provider application could not open the process interface.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600008: Failed to read /proc/net/snmp. errno: [error], 
[description] 

Explanation    The statistics provider application could not read the process interface.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600009: Failed to read /proc/net/snmp. End-of-file. 

Explanation    The statistics provider application could not read the process interface. No data was read.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600010: / proc/net/snmp has more data than cache expects: 
possible kernel version and cache application code mismatch 

Explanation    Format of /proc/net/snmp interface varies from expected format.

Recommended Action    Contact Cisco TAC.

Error Message    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] 

Explanation    Format of /proc/net/snmp interface varies from expected format.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600012: / proc/net/snmp sscanf parsing error STAT_NET_IP 
entry. num_items read = %d, num_items expected = 19 

Explanation    Format of /proc/net/snmp interface varies from expected format.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600013: / proc/net/snmp sscanf parsing error STAT_NET_ICMP 
entry. num_items read = %d, num_items expected = 26 

Explanation    Format of /proc/net/snmp interface varies from expected format.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600014: / proc/net/snmp sscanf parsing error STAT_NET_TCP 
entry. num_items read = %d, num_items expected = 21 

Explanation    Format of /proc/net/snmp interface varies from expected format.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600015: / proc/net/snmp sscanf parsing error STAT_NET_UDP 
entry num_items read = %d, num_items expected = 4 

Explanation    Format of /proc/net/snmp interface varies from expected format.

Recommended Action    Contact Cisco TAC.

Error Message    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 

Explanation    Format of /proc/net/snmp interface varies from expected format.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STATS-3-600017: malloc for fds failed. 

Explanation    Could not allocate memory.

Recommended Action    If problem persists, contact Cisco TAC.

Error Message    CE-STATS-3-600022: Failed to create Content Router statistics thread 

Explanation    The Content Router statistics thread could not be created for some reason. Statistics will not be gathered.

Recommended Action    The machine should be restarted as such a problem may be indicative of a system-wide memory shortfall. If the problem persists, contact Cisco TAC.

STATS-4

Error Message    CE-STATS-4-600000: register_edm: edm reg err (ret = [error_code]) 

Explanation    The statistics provider application could not register with the data server.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STATS-4-600001: ds_connect: ds connect err (ret = [error_code]) 

Explanation    The statistics provider application could not connect to the data server.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STATS-4-600002: msg get err (ret=[error_code]) 

Explanation    The statistics provider application could not retrieve a message from the data server.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STATS-4-600003: get edm info err (ret=[error_code]) 

Explanation    The statistics provider app could not retrieve information from the dataserver.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

STATS-5

Error Message    CE-STATS-5-600020: Statistics thread startup notice 

Explanation    Logs the thread and process IDs of the Content Router statistics thread.

Recommended Action    No action is required.

Error Message    CE-STATS-5-600021: Statistics thread stack space notice 

Explanation    Logs the location of the thread stack space for the statistics thread of the Content Router.

Recommended Action    No action is required.

STATS-6

Error Message    CE-STATS-6-600018: Returning IP/ICMP/UDP/TCP stats. 

Explanation    Statistics for the specified protocol were returned.

Recommended Action    No action is required.

Error Message    CE-STATS-6-600019: Clearing IP/ICMP/UDP/TCP stats. 

Explanation    Statistics for the specified protocol were cleared.

Recommended Action    No action is required.

Standby Messages

This section contains standby messages.

STDBY-3

Error Message    CE-STDBY-3-522001: Standby item protection semaphore 
open/write/signal/close error. 

Explanation    Standby process encountered a problem while trying to access the semaphore that protects the standby data server item.

Recommended Action    Contact Cisco TAC.

Error Message    CE-STDBY-3-522006: Standby group <group no> can't be brought up. 

Explanation    No member interfaces can be brought up in the specified standby group.

Recommended Action    Check syslogs for failures on the related member interfaces.

Error Message    CE-STDBY-3-522007: Error <err no> when raising alarm <alarm 
item>(<alarm description>). 

Explanation    Standby process failed to raise the specified alarm.

Recommended Action    Check syslogs for other alarm-related failures. Alarm information on the device could be inconsistent and a reboot of the device may be required for recovery.

Error Message    CE-STDBY-3-522008: Error <err no> when clearing alarms in module 
<module name>. 

Explanation    Standby process failed to clear raised alarms in the group. The standby group name is represented in <module name>.

Recommended Action    Check syslogs for other alarm-related failures. Alarm information on the device could be inconsistent and a reboot of the device may be required for recovery.

Error Message    CE-STDBY-3-522009: Error <err no> when binding to nodehealthds. 

Explanation    Standby process failed to bind to node health monitor database.

Recommended Action    Check syslogs for more specific failures on the node health monitor database.

STDBY-4

Error Message    CE-STDBY-4-522002: Interface <interface> is down 

Explanation    Standby process has found that the interface <interface> is down.

Recommended Action    Check the cable, switch configuration, and the Content Engine interface configuration for any problems. Try "shut" and "no shut" on the Content Engine interface. If the interface is still down, contact Cisco TAC.

Error Message    CE-STDBY-4-522003: Unable to reach the gateway 

Explanation    Standby process has found that the Content Engine is no longer able to reach the default gateway.

Recommended Action    Try accessing the default gateway manually. If ping does not work, look for any network problems, and check the router configuration. If ping works fine, contact Cisco TAC.

Error Message    CE-STDBY-4-522004: Interface <interface> has seen more errors than 
allowed 

Explanation    Standby process has found that the currently active interface is experiencing excessive input/output errors.

Recommended Action    Look for problems in the switch, check Content Engine interface configurations. If the configurations are okay, contact Cisco TAC.

STDBY-7

Error Message    CE-STDBY-7-522005: Standby group <group no> is up on <interface> 

Explanation    Standby group is currently active on the interface <interface>.

Recommended Action    No action is required.

Stream ing Cache Messages

This section contains streaming cache messages.

STREAMCACHE-3

Error Message    CE-STREAMCACHE-3-673000: [Procedure] Invalid options passed 

Explanation    Options passed in are invalid.

Recommended Action    Pass the correct arguments and retry the command.

Error Message    CE-STREAMCACHE-3-673001: [Procedure] Must pass in Real Proxy and RTSP 
Redirector binary path 

Explanation    Invalid path specified. Must pass RealProxy and RTSP Redirector binary path.

Recommended Action    Pass the correct binary path and retry the command.

Error Message    CE-STREAMCACHE-3-673002: [Procedure] Failed to execute IP address 
check script <error_mesg> 

Explanation    Failed to execute the script, which checks for IP address.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673003: [Procedure] Host name not configured 
<error_mesg> 

Explanation    Host name configuration is not available.

Recommended Action    Configure the hostname and Retry the command.

Error Message    CE-STREAMCACHE-3-673004: [Procedure] Real Proxy needs hostname other 
than local host <error_mesg> 

Explanation    Real Proxy needs host name other than local host.

Recommended Action    Configure the hostname other than localhost and retry the command.

Error Message    CE-STREAMCACHE-3-673005: [Procedure] No IP address available in 
/etc/hosts. <error_mesg> 

Explanation    No IP address available in /etc/hosts file.

Recommended Action    Configure the IP address and retry the command.

Error Message    CE-STREAMCACHE-3-673006: [Procedure] Unknown return status from IP 
address check script 

Explanation    Invalid return status received from the IP address check script.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673007: [Procedure] Failed to spawn a process/thread 
<error_mesg> 

Explanation    Failed to spawn a process/thread.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673008: [Procedure] MonitorMediaConfigAndWaitProcess 
failed 

Explanation    MonitorMediaConfigAndWaitProcess failed.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673009: [Procedure] Failed to set the resource limit 
<error_mesg> 

Explanation    Failed to set the resource limit.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673010: [Procedure] Failed to bind to sysdb 
<error_mesg> 

Explanation    Failed to bind to sysdb.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673011: [Procedure] Failed to initialize the status 
collector <error_mesg> 

Explanation    Failed to initialize the status collector.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673012: [Procedure] - Unknown read event 
<error_message> 

Explanation    Unknown read event. This can be due to the internal error.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673013: [Procedure] - Failed to [action] 
[directory_name] directory <error_mesg> 

Explanation    Failed to create/open/change directory. This can be due to the internal error.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673014: [Procedure] - Failed to get IP address of 
media proxy 

Explanation    Failed to get IP address of media proxy.

Recommended Action    Check the IP address configuration. If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673015: [Procedure] - Failed to get item <error_mesg> 

Explanation    Failed to get item.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673016: [Procedure] - Failed to start a new session 
<error_mesg> 

Explanation    Failed to start a new session.

Recommended Action    Retry the command. It the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673017: [Procedure] - Failed to start a new session 

Explanation    Failed to start a new session.

Recommended Action    Retry the command. It the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673018: [Procedure] - System call failed: <system 
call> <error_mesg> 

Explanation    System call failed. System might be in weird state.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673019: [Procedure] - Program <program name> died 
quickly during restart. Stop spawning 

Explanation    The child process failed immediately after it started last time. Stop spawning it to avoid spawning crashing processes.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673020: [Procedure] - Failed to restart a process 
<process name> 

Explanation    Failed to restart a process.

Recommended Action    If this message occurs periodically, it can be ignored. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673021: [Procedure] - WaitProcess failed 

Explanation    WaitProcess failed.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673022: [Procedure] - Program <program name> died due 
to signal <signal number> 

Explanation    Program exited due to a signal.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673023: [Procedure] - Program <program name> died 
abnormally with status <status code> 

Explanation    Program exited abnormally.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673024: [Procedure] - Unexpected value of item <item 
name> 

Explanation    Received unexpected value of item.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673025: [Procedure] - Failed to get notification info 

Explanation    Failed to get notification info.

Recommended Action    If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673026: [Procedure] Failed to unbind from sysdb 
<error_mesg> 

Explanation    Failed to bind from sysdb.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673027: [Procedure] Failed to Register [action] 
<error_mesg> 

Explanation    Failed to Register Verification/Notification.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673028: [Procedure] Failed to get [action] 
information <error_mesg> 

Explanation    Failed to get verification/notification information.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673029: [Procedure] Failed to free ven resources 
<error_mesg> 

Explanation    Failed to free ven resources.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673030: [Procedure] Failed to build EDM/verification 
ACK <error_mesg> 

Explanation    Failed to build verification/EDM acknowledgment.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673031: [Procedure] Item [fields] is NULL 
<error_mesg> 

Explanation    Item name/new value/old value is empty.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673032: [Procedure] Unexpected sysdb type/item length 
<error_mesg> 

Explanation    Unexpected sysdb type/item length.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673033: [Procedure] Failed to receive whole message 
<error_mesg> 

Explanation    Failed to receive whole message.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673034: [Procedure] Received unexpected message type 
<error_mesg> 

Explanation    Received unexpected message type.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673035: [Procedure] Failed to send ACK <error_mesg> 

Explanation    Failed to send acknowledgment.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673036: [Procedure] Failed to get EDM information 
<error_mesg> 

Explanation    Failed to get EDM information.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673037: [Procedure] EDM List not supported 
<error_mesg> 

Explanation    EDM List is not implemented.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673038: [Procedure] EDM [action] failed <error_mesg> 

Explanation    EDM registration/unregistration failed.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673039: [Procedure] Failed in RTSP reconfiguration 
<error_mesg> 

Explanation    Error occurred during RTSP reconfiguration.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673040: [Procedure] [Resource] operation <operation 
name> failed <error_mesg> 

Explanation    Error occurred during file/pipe operation.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673041: [Procedure] Unknown EDM item <item name> 
failed <error_mesg> 

Explanation    Unknown EDM item.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673042: [Procedure] gethostbyname failed 
<error_mesg> 

Explanation    Failed to get host details by name.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673043: [Procedure] Failed to get local IP address <error_mesg> 

Explanation    Failed to get local IP address.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673044: [Procedure] Failed to register as stats EDM 

Explanation    Failed to register as stats Extended Data Manager.

Recommended Action    Retry the command. If the problem occurs frequently, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673045: [Procedure] Could not open pid file 

Explanation    Could not open PID file.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-STREAMCACHE-3-673046: Generic message 

Explanation    The error message must be descriptive.

Recommended Action    No action is required.

STREAMCACHE-5

Error Message    CE-STREAMCACHE-5-675001: [Procedure] Memory value in Real Proxy -m option 

Explanation    Amount of Physical memory that will be used by Real Proxy.

Recommended Action    No action is required.

STREAMCACHE-6

Error Message    CE-STREAMCACHE-6-676000: [Procedure] Hostname check in /etc/hosts is successful 

Explanation    Successfully checked the host name in /etc/hosts file.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-6-676001: [Procedure] Shutting down, no spawning of child anymore 

Explanation    Shutting down is in progress. No spawning of child process.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-6-676002: [Procedure] Process with PID <PID> exited 

Explanation    Process exited.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-6-676003: [Procedure] PID <pid> not my direct child 

Explanation    This process is a grandchild.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-6-676004: [Procedure] Program <Program name> exited normally with code <status code> 

Explanation    Program exited normally.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-6-676005: [Procedure] Killing all processes related to <Path> 

Explanation    Terminating all the process which are descendents of this process.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-6-676006: [Procedure] Failed to unregister [service] <error_mesg> 

Explanation    Failed to unregister verification/notification.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-6-676007: [Procedure] System call failed: <system call> 

Explanation    System call failed.

Recommended Action    No action is required.

STREAMCACHE-7

Error Message    CE-STREAMCACHE-7-677001: [get_physical_memory] Memory 

Explanation    Amount of physical memory.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-7-677002: [write_pid_to_file] 

Explanation    Written pid to pid-file.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-7-677003: [get_mcm_pid] 

Explanation    Got MCM pid from pid-file.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-7-677004: [process_notification] 

Explanation    Send signal SIGUSR1 to MCM process.

Recommended Action    No action is required.

Error Message    CE-STREAMCACHE-7-677005: debug message 

Explanation    Debug message.

Recommended Action    No action is required.

System Messages

This section contains system messages.

SYS-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-SYS-n-900000: [Kernel Message] 

Explanation    This class of messages is generated by the Kernel and may be useful for debugging a problem that is encountered. More severe priorities, (0 is the highest, 7 the lowest), are more likely to be of concern.

Recommended Action    Contact Cisco TAC and pass on these messages along with details of the problem that was encountered.

SYS-5

Error Message    CE-SYS-5-900001: [system bootup messages] 

Explanation    These are system boot up messages.

Recommended Action    Mostly informational, but could be of help when debugging certain boot up problems.

Error Message    CE-SYS-5-900002: [system bootup messages] 

Explanation    These are system boot up messages (from system initialization till syslogd is started).

Recommended Action    Mostly informational, but could be of help when debugging certain boot up problems.

Error Message    CE-SYS-5-900003: [Kernel crash analysis messages] 

Explanation    These messages indicate that the kernel crashed in the past and contain information that may help in diagnosing the problem.

Recommended Action    Contact Cisco TAC.

System Monitor Messages

This section contains system monitor messages.

SYSMON-1

Error Message    CE-SYSMON-1-445012: disk%02d has a serious file system problem. Please 
reload the system to recover from this failure. 

Explanation    A disk has a serious, but recoverable file system related problem.

Recommended Action    Reload the system.

SYSMON-3

Error Message    CE-SYSMON-3-445000: Error in read the req, errno: [error] 

Explanation    The system fault monitor could not read a request. Request will be skipped.

Recommended Action    No action is required.

Error Message    CE-SYSMON-3-445001: Failed to set NONBLOCK for new_fd, ret [status], 
errno [error no]. 

Explanation    The system fault monitor could not set the NONBLOCK attribute on a request. Request will be skipped.

Recommended Action    No action is required.

Error Message    CE-SYSMON-3-445002: select: ret = [status], errno = [error no] 

Explanation    The select call within the system fault monitor failed.

Recommended Action    If this message appears frequently, contact Cisco TAC.

Error Message    CE-SYSMON-3-445003: Incorrect system id [system identifier] 

Explanation    An unknown system identifier was received by the system fault monitor.

Recommended Action    Contact Cisco TAC.

Error Message    CE-SYSMON-3-445004: Incorrect device id [device id] 

Explanation    An unknown device identifier was received by the system fault monitor.

Recommended Action    Contact Cisco TAC.

Error Message    CE-SYSMON-3-445005: Incorrect timestamp [timestamp] 

Explanation    An improper timestamp was received by the system fault monitor.

Recommended Action    Contact Cisco TAC.

Error Message    CE-SYSMON-3-445006: Incorrect severity [severity level] 

Explanation    An unknown severity level was received by the system fault monitor.

Recommended Action    Contact Cisco TAC.

Error Message    CE-SYSMON-3-445007: error [error code] when binding to dataserver 

Explanation    The system fault monitor could not make a connection to the data server. A fault may not be reported.

Recommended Action    Reboot the Content Engine. If the error persists, contact Cisco TAC.

Error Message    CE-SYSMON-3-445008: error [error code] when setting [data item name] 

Explanation    The system fault monitor could not set a value for the specified data server item name. A fault may not be reported.

Recommended Action    Reboot the Content Engine. If the error persists, contact Cisco TAC.

Error Message    CE-SYSMON-3-445010: Fault detected: [description] 

Explanation    The system fault monitor has detected a fault.

Recommended Action    Take corrective action to fix the fault. If no fault actually exists, contact Cisco TAC.

Error Message    CE-SYSMON-3-445013: Failed to turn off journaling on num:num. 

Explanation    A disk has a serious, but recoverable file system related problem.

Recommended Action    Reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-SYSMON-3-445014: Could not add num:num to the list of failed 
partitions(s) 

Explanation    A disk has a serious, but recoverable file system related problem.

Recommended Action    Reload the system.

SYSMON-5

Error Message    CE-SYSMON-5-445009: sysmon: entering start_loop 

Explanation    The system fault monitor is starting up.

Recommended Action    No action is required.

Error Message    CE-SYSMON-5-445011: Fault cleared: [description] 

Explanation    The system fault monitor has cleared a fault.

Recommended Action    No action is required.

System Utilities Messages

This section contains system utilities messages.

SYSUTL-1

Error Message    CE-SYSUTL-1-800001: RAM disk is full. 

Explanation    System will become unusable soon.

Recommended Action    Rebooting the Content Engine will fix it. Report to Cisco as soon as possible. Include syslog messages following 800001 for detailed analysis.

SYSUTL-3

Error Message    CE-SYSUTL-3-800002: RAM disk usage is growing. 

Explanation    Root file system is getting full.

Recommended Action    Watch for %CE-SYSUTL-1-800001.

SYSUTL-5

Error Message    CE-SYSUTL-5-800003: <username> login on <ttyname> from <host> 

Explanation    A privileged user has logged in.

Recommended Action    No action is required.

Error Message    CE-SYSUTL-5-800006: File removed <filename> And other <number> file(s) 
removed Core file(s) removed <filename> ... 

Explanation    SYSFS space is low. System starts to remove certain files automatically.

Recommended Action    Run "show sysfs volumes" to check SYSFS usage. Remove some old files if it's over 80% used.

SYSUTL-6

Error Message    CE-SYSUTL-6-800004: <username> login on <ttyname> from <host> 

Explanation    A non-privileged user has logged in.

Recommended Action    No action is required.

Error Message    CE-SYSUTL-6-800005: Console at <ttyname> by <username> 

Explanation    A user has logged in from console line.

Recommended Action    No action is required.

Sysvinit Messages

This section contains system V initialization messages.

SYSVINIT-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-SYSVINIT-n-810040: [Description] 

Explanation    These messages are generated by sysvinit.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

Telnet Messages

This section contains telnet messages.

TELNET-n


Note When no severity level exists, the actual number for the severity level is generated at run time and determined by the condition that generated the error.


Error Message    CE-TELNET-n-810050: [Description] 

Explanation    These messages are generated by telnet.

Recommended Action    If high priority error messages frequently occur, contact Cisco TAC.

Trivial File Transfer Protocol Messages

This section contains Trivial File Transfer Protocol messages.

TFTP-2

Error Message    CE-TFTP-2-450014: tftpd: can't drop root privileges: <error details> 

Explanation    TFTP daemon has to keep root privileges to allow creation of files.

Recommended Action    If problem persists, contact Cisco TAC.

TFTP-3

Error Message    CE-TFTP-3-450002: tftpd: Cannot create transaction logs: <error_code> 

Explanation    System could not create a TFTP transaction-log socket.

Recommended Action    No action is required.

Error Message    CE-TFTP-3-450003: tftpd: Unable to send transaction log data: return= 
<return-code> errno= <error-no> errstr= <error-string> 

Explanation    System was unable to send the data to the TFTP transaction-log socket.

Recommended Action    Check if the transaction log command is enabled; if not enable it.

Error Message    CE-TFTP-3-450004: tftp main(): Failed to bind to SysDB-Root with error 
<error_code>. 

Explanation    System was unable to bind to the data from SysDB.

Recommended Action    If problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450005: tftp main(): SYSDB returned NULL tftp_ptr. 

Explanation    System was successful in reading the item from SysDB, but the item has NULL value assigned to it.

Recommended Action    No action is required.

Error Message    CE-TFTP-3-450006: tftp main(): Item not found on the data server. 

Explanation    System was unable to find the data on SysDB. sysdb_itm_get() failed with return code as SYSDB_ERROR_NOTFOUND.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450007: tftp main(): sysdb_item_get failed with error code 
<error_code>. 

Explanation    sysdb_item_get() failed with the error code.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450011: tftpd: ioctl call failed: <error details> 

Explanation    TFTP demon ioctl(FIONBIO) call to open config file failed.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450012: tftpd: recvfrom() failed: <error details> 

Explanation    TFTP demon call to recvfrom() returned an error.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450013: tftpd: fork failed: <error details> 

Explanation    TFTP demon call to fork() failed.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450015: tftpd: socket creation to peer failed: <error 
details> 

Explanation    TFTP demon call to socket() failed.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450016: tftpd: socket bind to peer failed: <error details> 

Explanation    TFTP demon call to bind() failed.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450020: tftpd: sento error: <error details> 

Explanation    TFTP demon error. TFTP failed to send the data to the client.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450021: tftpd: ACK read error: <error details> 

Explanation    TFTP demon error while reading the ACK sent by the client.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450022: tftpd: ACK send error: <error details> 

Explanation    TFTP demon error while sending the ACK to the client.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450023: tftpd: Read error: <error details> 

Explanation    TFTP demon error while reading the data from client.

Recommended Action    If the problem persists, contact Cisco TAC.

Error Message    CE-TFTP-3-450024: tftpd: NAK error: <error details> 

Explanation    TFTP demon error while sending the NAK(negative acknowledgment).

Recommended Action    If the problem persists, contact Cisco TAC.

TFTP-4

Error Message    CE-TFTP-4-450017: tftpd: Cannot access base filesystem. 

Explanation    TFTP demon could not access the /local directory.

Recommended Action    No action is required.

Error Message    CE-TFTP-4-450018: tftpd: Invalid default directory: <default 
directory> 

Explanation    TFTP demon could not access the default directory to search the requested file for.

Recommended Action    Check if the default directory exists, and create it if it does not.

Error Message    CE-TFTP-4-450019: tftpd: Blocked illegal request for <filename> 

Explanation    TFTP daemon can not access the parent directory.

Recommended Action    No action is required.

TFTP-5

Error Message    CE-TFTP-5-450008: NO TFTP-access-list is configured: A <read or write> 
request denied for client <client-ip> for file <file-name>. 

Explanation    For TFTP to be functional a tftp-server access-list needs to be configured on the Content Engine.

Recommended Action    Configure tftp-server access-list and Standard Access List on the Content Engine.

Error Message    CE-TFTP-5-450009: NO Valid access-list is configured for access-list# 
<#> A <read or write> request denied for client <client-ip> for file <file-name>. 

Explanation    A Standard Access List is needed for TFTP to be functional.

Recommended Action    Configure Standard Access List for TFTP on the Content Engine.

Error Message    CE-TFTP-5-450010: Failed to open tftp config file. 

Explanation    TFTP daemon could not open /etc/tftpd.conf file.

Recommended Action    If the problem persists, contact Cisco TAC.

TFTP-7

Error Message    CE-TFTP-7-450001: tftpd: <various tftpd debug messages> 

Explanation    This debug ID is used for debugging TFTP code.

Recommended Action    No action is required.

Translog Messages

This section contains translog messages.

TRNSLG-2

Error Message    CE-TRNSLG-2-460008: TRANSLOG: system mem low. Clean up mem alloced 

Explanation    System memory is low.

Recommended Action    No action is required.

Error Message    CE-TRNSLG-2-460009: TRANSLOG: system mem low. Buffer allocation 
aborted. 

Explanation    Buffer allocation failed.

Recommended Action    No action is required.

TRNSLG-3

Error Message    CE-TRNSLG-3-460001: TRANSLOG: tlog_begin_mark(): write failed, 

Explanation    Write failed.

Recommended Action    No action is required.

Error Message    CE-TRNSLG-3-460002: Unable to open transaction log file: 

Explanation    Unable to open transaction log file.

Recommended Action    No action is required.

Error Message    CE-TRNSLG-3-460003: TRANSLOG: tlog_commit():write failed, errno = 

Explanation    Write failed.

Recommended Action    No action is required.

Error Message    CE-TRNSLG-3-460004: Log directory non-existent -transaction logging 
terminated: 

Explanation    Log directory non-existent.

Recommended Action    Check to see if log directory exists.

Error Message    CE-TRNSLG-3-460005: Log path is not a directory - transaction logging 
terminated: 

Explanation    Log path is not a directory.

Recommended Action    Check to see if log path is a directory.

Error Message    CE-TRNSLG-3-460006: Logging filesystem nearly full and unable to 
delete: 

Explanation    Logging file system nearly full.

Recommended Action    No action is required.

Error Message    CE-TRNSLG-3-460007: TRANSLOG: translog_set_trap(): sysdb_item_set 
failed 

Explanation    Item set failed.

Recommended Action    No action is required.

Error Message    CE-TRNSLG-3-460010: TRANSLOG: tlog_end_mark(): write failed, errno =  

Explanation    Write failed.

Recommended Action    No action is required.

Error Message    CE-TRNSLG-3-460014:  

Explanation    Failed to send translog message remote syslog host: <error details>.

Recommended Action    No action is required.

Error Message    CE-TRNSLG-3-460015:  

Explanation    Failed to send whole translog message to remote syslog host: <error details>.

Recommended Action    No action is required.

Error Message    CE-TRNSLG-3-460016:  

Explanation    Failed to create socket for sending to remote syslog host <error details>.

Recommended Action    If rebooting the Content Engine does not help, contact Cisco TAC.

TRNSLG-5

Error Message    CE-TRNSLG-5-460011: process info: tlog_logger_init() process_id 

Explanation    Process ID and pthread ID.

Recommended Action    No action is required.

TRNSLG-6

Error Message    CE-TRNSLG-6-460012: <translog formatted message> 

Explanation    HTTP/FTP transaction log message sent to syslog host configured in transaction-logs logging host config command.

Recommended Action    No action is required

Error Message    CE-TRNSLG-6-460013:  

Explanation    Dropped %d translog messages to syslog log host due to configured rate limit of <rate-limit>.

Recommended Action    No action is required.

TV Out Messages

This section contains TV out messages.

TVOUT-2

Error Message    CE-TVOUT-2-470041: Daemon failed: [system error] 

Explanation    TV-out service failed to run as a background process and has exited. TV-out service may be automatically restarted.

Recommended Action    If message persists and/or TV-out service is no longer running, reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-2-470042: Exit in main after [type]: [exception] 

Explanation    The specified exception was detected, causing the Tv-out service to immediately exit. TV-out service may be automatically restarted.

Recommended Action    If message persists and/or TV-out service is no longer running, reboot the Content Engine. If the problem persists, contact Cisco TAC.

TVOUT-3

Error Message    CE-TVOUT-3-470002: Unable to determine TV-out hardware: [error] 

Explanation    An error occurred accessing data about the type of TV-out hardware installed on the device.

Recommended Action    Try to reenable the TV-out service. If message persists, reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470003: TV-out hardware was not detected: [error] 

Explanation    TV-out hardware was not detected to be installed on the device. Either the hardware itself was not detected, or the detection software failed to run after the last device reload.

Recommended Action    Verify that a supported A/V decoder card is properly installed and reboot the Content Engine. If the problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470005: Cannot allocate memory for [target] 

Explanation    General memory allocation failure for the specified target. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If the problem persists, reboot the Content Engine. Since this message may be due to low memory conditions, try reducing the overall number of services enabled. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470006: Unable to determine stream type: [error] 

Explanation    An error occurred processing the stream type to be decoded. System may be in an undefined state.

Recommended Action    Check log for additional messages and further action. If no other messages found, try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470008: Cannot open <file>: [system error] 

Explanation    Cannot open the specified file due to system error. System may be in an undefined state.

Recommended Action    Verify that channel replication status and the cdnfs are stable. Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470011: AV-001: Unable to open MPEG device interface 

Explanation    Failed to open the control interface to the MPEG device driver. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470013: AV-001: Unable to setup decode: [error] 

Explanation    An error was encountered setting up the decode of a stream through the device driver.

Recommended Action    Verify that media file parameters are valid as detailed in the 'ACNS Software Deployment and Configuration Guide.' Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470015: [sysdb error message] 

Explanation    Class of sysdb error messages for the TV-out service.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470018: Unable to connect to cms database: Cannot check 
[target] 

Explanation    Unable to connect to cms database so the specified target cannot be retrieved.

Recommended Action    Verify that cms is enabled and running normally. Try re-enable of the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470019: Failed query of cms database: [target] not found - 
[action] 

Explanation    In query of the cms database, the specified target could not be found. This often indicates incomplete or missing data.

Recommended Action    Verify that cms is enabled and running normally. Take specified action, if any. Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470020: Unable to decode <file path> on <playlist>: [error] 

Explanation    Decode of the specified file path on the specified playlist failed due to error encountered. Partial decode may have occurred. System may be in an undefined state.

Recommended Action    Check for additional messages and further action. Try re-enable of the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470027: Unable to connect to uns for resolve of <url> on 
<playlist> 

Explanation    TV-out service was unable to connect to the uns service to determine the local file path for the specified url on the specified playlist. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470034: Unable to register as statistics EDM for <subtree> 

Explanation    An unspecified error occurred when attempting to register as the External Data Manager for tvout statistics. TV-out service statistics may be unavailable.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470039: Device manager returned no devices so playback 
cannot be attempted 

Explanation    Since no device interfaces could be sucessfully initialized, playback will not be attempted. TV-out service will be in idle mode.

Recommended Action    Check log for additional messages and further action. Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470040: Device manager cannot init <number>: <status> 

Explanation    One or more device interfaces failed to be initialized.

Recommended Action    Check log for additional messages and further action. Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470053: Uns unable to provide file path for playable <url> 

Explanation    The local file path could not be determined for the specified url due to a problem encountered with a uns object.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470055: Uns rpc failed for [action]: [status] 

Explanation    Unable to request the specified action due to failure in the remote procedure call to uns. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470061: Socket failure for [target]: [system error] 

Explanation    A failure occurred in socket communications for the specified target due to a system error. System may be in a undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470062: Unable to launch <playlist>: [error] 

Explanation    The specified playlist could not be launched due to the error encountered. System may be in a undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470064: Failed to send term signal to child <pid>: [system 
error] 

Explanation    A system error was encountered after requesting termination of the child process at the specified pid. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470068: AV-002: sem_init error: <errno> 

Explanation    Semaphore initialization operation failed. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470069: AV-002: Unable to open w/o memory 

Explanation    Initialization failed to obtain memory. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470070: AV-002: Unable to open control interface: <status> 

Explanation    Initialization failed to obtain a control interface handle to the driver. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470071: AV-002: Unable to configure PUSH: <inputType> 

Explanation    Initialization failed to put the interface into push mode. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470072: AV-002: Unable to get push handle: <status> 

Explanation    Initialization failed to get proper access to the driver. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470073: AV-002: setupDecode - Unsupported stream type 
specified: <streamType> 

Explanation    Interface was requested to setup for a stream type that it does not support.

Recommended Action    Contact Cisco TAC since this problem indicates a problem with the higher layers of the software.

Error Message    CE-TVOUT-3-470074: AV-002: setupDecode - SetDemuxPUSH error: <status> 

Explanation    An error occurred when setting up the interface for the stream type. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470075: AV-002: setupDecode - PlayPUSH error: <status> 

Explanation    An error occurred when entering the interface into play mode. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470076: AV-002: decode - GetBuffer error: <status> 

Explanation    An error occurred when attempting to get a buffer for the stream data. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470077: AV-002: decode - PushBuffer error <status> when 
writing <bytesDecoded> of <streamLength> bytes 

Explanation    An error occurred when attempting to push a buffer of stream data to the driver. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470078: AV-002: pauseDecode - PausePUSH error: <status> 

Explanation    The driver interface failed to enter into pause mode as requested. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470079: AV-002: resumeDecode - PlayPUSH error: <status> 

Explanation    The driver interface failed to enter into play mode as requested. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470080: AV-002: stopDecode - EOS PushBuffer error: <status> 

Explanation    An error occurred when attempting to push an End Of Stream indication to the driver. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470081: AV-002: stopDecode - StopPUSH error: <status> 

Explanation    The driver interface failed to enter into stop mode as requested. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470082: CARIBBEAN called RMPanic with status=<reason>. 
Exiting 

Explanation    The driver interface callback indicated a Panic condition. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470084: AV-002: callbackRMF - StopPush error: <errno> 

Explanation    The driver interface callback failed to enter into stop mode as requested. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470085: AV-002: Unable to get OSD/RUA handle: <num> 

Explanation    The driver interface failed to get OSD/RUA control handle. OSD will not work.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470086: AV-002: OSD is not initialized 

Explanation    The driver interface failed initialize OSD. OSD will not work.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470098: Failed to record the determined TV-out hardware: 
[error] 

Explanation    An error occurred recording data about the type of TV-out hardware installed on the device.

Recommended Action    Try to reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-3-470100: ver_tvout: Error encountered [stopping | starting] 
TV-out service 

Explanation    An error occurred when interacting with the node manager to either start or stop the TV-out service.

Recommended Action    Try to disable or enable the TV-out service again. If message persists, reload the device. If problem persists, contact Cisco TAC.

TVOUT-4

Error Message    CE-TVOUT-4-470007: On file close: [system error] 

Explanation    Close of a file descriptor generated a system error. System may be in an undefined state.

Recommended Action    Try to re-enable the TV-out service. If message persists, reload the device. If problem persists, contact Cisco TAC.

Error Message    CE-TVOUT-4-470009: Unable to process overlay image: [error] 

Explanation    Failed to process an overlay image for on screen display due to the error encountered.

Recommended Action    Verify any overlay image files are valid and m