Specifications

A-4
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Appendix A Troubleshooting
Troubleshooting Content Acquisition
• Use the show statistics acquirer delivery-service-id or show statistics acquirer
delivery-service-name EXEC command to obtain the detailed acquisition statistics for a given
delivery service. In the following example, there was an error acquiring two items.
SE# show statistics acquirer delivery-service-id 793
Querying Database.......
Statistics for Delivery Service Delivery-service-id :793 Delivery-service-Name
:group01-cifs
---------------------------------------------------------
Manifest:
---------
Fetch Errors :0
Parsing Errors :0
Parsing Warnings:0
Acquisition:
-------------
Total Number of Acquired Objects :2237
Total Disk Used for Acquired Objects :981511280 Bytes
Total Number of Failed Objects :2
Total Number of Re-Check Failed Objects :0
• Use the show statistics acquirer errors delivery-service-id or show statistics acquirer errors
delivery-service-name EXEC command to see the reasons why the errors occurred. In the following
example, one error occurred because there was a problem acquiring the URL. The other error
occurred because the disk quota for the delivery service configured in the Content Distribution
Manager GUI would have been exceeded if the specified URL had been acquired. You can increase
the delivery service disk quota to correct this error.
SE# show statistics acquirer errors delivery-service-id 793
Querying Database.......
Acquisition Errors for the Delivery Service ID:793
-------------------------------------
Crawl job:start-url http://www.mtv.com//
Crawl Errors
---------------
Internal Server Error(500):http://cgi.cnn.com/entries/intl-emailsubs-confirm
Exceeded Disk Quota(703):http://www.cdt.org/copyright/backgroundchart.pdf
• If more detailed troubleshooting of content acquisition is required, you can increase the debug level
of the acquirer using the debug acquirer trace EXEC command. The logs are written to
local1/errorlog/acquirer-errorlog.current.
• To verify that an expected object has been pre-positioned on the Service Engine, use the show
distribution object-status EXEC command, as shown in the following example:
SE# show distribution object-status
http://172.18.81.168/Videos/SM-final%20Innebandy%202003.wmv
========== Website Information ==========
Name: RTPServer5
Origin Server FQDN: 172.18.81.168
Service Routing FQDN: N/A
Content UNS Reference #: 1
========== Delivery Services Information ==========
*** Delivery Service 1903 (name = A_Multicast) ***
Object Replication
------------------