Specifications

A-26
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Appendix A Troubleshooting
Ingest Issues
Database Monitoring
To monitor a stuck database thread problem, use the following command:
netstat –an | grep 9999
Two connections for each Vault and Streamer should be listed with a status of “ESTABLISHED.” If
two-way connection does not exist, run db_shutdown on all servers including the CDSM, then start the
database using the following commands:
# su – isa
$ arroyo start avsdb
If the database is stuck and db_shutdown does not take effect, use ps –ef | grep avsdb to query the
process ID (PID), then use the kill -9 {pid} command to kill the avsdb process, and lastly restart the
database.
Ingest Issues
This section includes the following ingest issues:
• Ingest Interface
• Bad Content
• Network
Ingest Interface
This section includes the following topics on troubleshooting the ingest interface:
• General Tips
• Common Ingest Problems
• CDS Is Not Registered to the Name Service
• Restarting the ISA Services
General Tips
Following are some general troubleshooting tips for ingest issues:
• Use the ifstats command to monitor ingests.
• Ping the FTP device, which is either a catcher or an FTP server.
• Manually FTP to the catcher or FTP server.
Common Ingest Problems
Following are some possible causes of ingest issues:
• FTP server is not reachable (server is down, routes are incorrect, network partition).
• Incorrect URL for the content file.
• ContentStore file system is full.