Error and Event Messages

Explanation   The HTTP password for a device has been changed. The HTTP password allows administrators to secure access to configuration information for selected devices from the Content Distribution Manager. This password can be changed from the modify screen for a Content Engine or Content Router.

Action No action is required.

Explanation   The root password allows administrators to overwrite the root account password and gain direct, command-line access to the device. This password can be changed from the modify screen for a Content Engine or Content Router.

Action No action is required.

Explanation   Identifies a DNS trace message for the named hosted domain.

Action No action is required. See the "Enabling and Disabling DNS Trace" section for more information on the DNS Trace feature.

Explanation   The Content Distribution Manager was able to successfully review damaged records on the Oracle policy database and mark them invalid. Invalid database records are not loaded with the rest of the Oracle database.

Action Using the store-invalidation tool enables you to quickly bring your policy database (and thus your Content Distribution Manager) online even when errors are encountered during validation. However, you should still attempt to repair any damaged database records. Review the text of the invalidation messages and attempt to resolve damaged records on your Oracle policy database.

Explanation   The Content Distribution Manager's check of the Oracle policy database was completed successfully, without finding any database errors.

Action No action is required.

Explanation   A new Content Engine has registered itself with the Content Distribution Manager.

Action Once a new Content Engine is registered, it must be activated from the Content Distribution Manager before content is routed to the new device. See the "Activating and Defining a Content Engine" section for instructions on activating the new Content Engine.

Explanation   A new Content Router has registered itself with the Content Distribution Manager.

Action Once a new Content Router is registered, it must be activated from the Content Distribution Manager before it is added to the CDN and begins routing requests. See the "Activating and Defining a Content Router" section for instructions on activating the new Content Router.

Explanation   The named device is in the process of shutting down. Shutdown can be initiated from the command-line interface or from the Content Distribution Manager.

Action No action is required. See the "Stopping, Shutting Down, Restarting, and Rebooting a Content Engine" section or the "Stopping, Shutting Down, Restarting, and Rebooting a Content Router" section for more information.

Explanation   The named device is in the process of restarting. Restart operations can be initiated from the command-line interface or remotely from the Content Distribution Manager.

Action No action is required. See the "Stopping, Shutting Down, Restarting, and Rebooting a Content Engine" section or "Stopping, Shutting Down, Restarting, and Rebooting a Content Router" section for more information.

Explanation   An administrator has logged on to the Content Distribution Manager and launched the store-invalidation tool. This tool locates records marked damaged by the store-validation tool and marks them invalid, enabling the Content Distribution Manager to ignore them when loading the policy database.

Action No action is required. The results of the store-invalidation tool review of your policy database—a list of records that have been marked invalid and will not be loaded by the CDN software—are written to the validation.log file, which is stored in the /state directory on the Content Distribution Manager.

Explanation   An administrator has logged on to the Content Distribution Manager and launched the store-validation tool. This tool checks the Oracle policy database for damaged records or internal inconsistencies and outputs its result in a log file, validation.log, located in the /state directory on the Content Distribution Manager.

Action When the tool has completed its review of the Oracle policy database, review the validation.log file and determine whether or not damaged records were located. If damaged records exist, run the store-invalidation tool on the Content Distribution Manager to mark those records invalid and enable the Content Distribution Manager to come online.

Explanation   You are attempting to remove the node (supernode, standalone Content Engine, or Content Engine cluster) from the root location of a hosted domain. When a location is selected as the root location for a hosted domain, it must maintain a minimum of one node.

Action Change the root location for the hosted domain, or assign other nodes from the root location to the hosted domain and then try again to delete or relocate the Content Engine, supernode, or cluster. See the "Modifying Hosted Domains" section for instructions on adding Content Engines to a hosted domain, the "Modifying a Supernode" section or the "Modifying a Cluster" section for instructions on adding Content Engines to a supernode or cluster, or the "Modifying Content Engines" section for instructions on changing the location of a Content Engine.

Explanation   A problem occurred during the loading or processing of cached content. Either the Content Distribution Manager did not pass correct data to the Content Engine or Content Router, or the Content Engine or Content Router did not cache data from Content Distribution Manager correctly.

Action Reboot the device on which the error was generated. If the problem returns, contact Cisco Technical Support.

Explanation   A log file from the named device could not be transferred to your remote logging server.

Action This could be the result of an interruption in service or insufficient resources on your remote logging server to accommodate the new log file. Verify that your remote logging server is online and that it has sufficient disk space to accommodate the log files being transferred to it. Also, review recent remote logging activity, and verify that confirmation (*.ok) files exist for each log file. See the "Setting Up Remote Logging" section for more information.

Explanation   An attempt to configure or reconfigure a Content Services Switch on your CDN has failed.

Action Review configuration procedures in the Cisco Internet CDN Software Configuration Guide and try again to configure your switch. If configuration fails a second time, contact Cisco Technical Support.

Explanation   The CDN device encountered syntax errors in the manifest file.

Action Use the replication log for the selected device as well as the system events log to find detailed information on the nature of the problem with the manifest file. Then use your preferred ASCII text or XML editor to correct the manifest file syntax. See the "Viewing the Status of Content Replication to a Hosted Domain" section for information on viewing the replication log for a Content Engine, and "Creating a Manifest File for Importing Media" section for instructions on the manifest file syntax.

Explanation   Damaged records named by the store-validation tool in the validation.log file could not be marked invalid by the store-invalidation tool. This means that the Content Distribution Manager will not be able to overlook these damaged records when attempting to come online.

Action Review the validation.log file in the /state directory on the Content Distribution Manager for more information on the records that failed, and then contact Cisco Technical Support.

Explanation   An administrator has logged on to the Content Distribution Manager and launched the store-validation tool, which encountered internal inconsistencies in the Oracle policy database during a routine check following startup. There could be a problem with your policy database.

Action Review the validation.log file in the /state directory on your Content Distribution Manager for a list of the database records that failed the store-validation review. In order to bring your Content Distribution Manager online, log on to the Content Distribution Manager and use the store-invalidation tool to mark the problem database records invalid, enabling the Content Distribution Manager to come back online.

Explanation   The manifest file for the hosted domain could not be retrieved from the specified location.

Action Correct the manifest file URL so that it points to a valid manifest file. See the "Replicating Content from the Origin Server to a Hosted Domain" section for instructions on pointing your hosted domain to a valid manifest file.

Explanation   The device has deleted the reported number of system messages from its log in order to make room for new messages.

Action This occurs when the volume of system messages being logged by the device exceeds the limit set by the CDN. Older messages are deleted to enable the device to accommodate the large number of new messages being added. Review the messages being logged and address the problem that is producing the high volume of logged messages.

Explanation   The available disk space on the hosted domain is not adequate to store all the contents named in the manifest file. Some of the contents named by the manifest file will not be pre-positioned.

Action Add more disk space to your hosted domain. After more space is made available, any content that has not been pre-positioned will be replicated. See the "Adding and Removing Content Engines from a Hosted Domain" section for more information.

Explanation   Checks run by the Content Distribution Manager against the Oracle policy database have indicated that the database has been corrupted.

Action Contact Cisco Technical Support immediately for help in resolving this problem.