Cisco 11503 Administration Guide - Page 147

Chapter 4 Using the CSS Logging Features Interpreting Undeliverable Messages The logging message that follows the logging header defines the error type and the destination, followed by a message as shown in Figure 4-3. Figure 4-3 Logging Message Logging Header Logging Message Communications- Error Type - Dest: Message ... The error type indicates one of the following conditions: • QUEUE FULL - The receiving queue has no room to accept messages • QUEUE DELETED - The CSS was trying to place a message in a valid queue but the queue was destroyed • QUEUE INVALID - A destination message queue handle was not a valid object • QUEUE UNKNOWN - The CSS was trying to determine the destination queue and the lookup failed The destination indicates one of the following: • String decoded name of the destination message queue • Hexadecimal value if the error type is QUEUE DELETED, QUEUE INVALID, or QUEUE UNKNOWN • INTERNAL, which indicates a LOCAL message passed between the tasks on the same processor The Message... section in the logging message provides additional information concerning the problem. The log level for the undeliverable message determines how much information is in the logging message, and how often the message occurs in the log. You can set the log level to Warning-4, Info-6, or Debug-7. By default, the log level for undeliverable messages is Warning-4. These messages occur every two seconds per message queue that is experiencing the problem. The message in the logging messages provides only the following information: Internal Messages Dropped. OL-5647-02 Cisco Content Services Switch Administration Guide 4-27