Specifications

A-6
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Appendix A Troubleshooting
General Information and Issues
/arroyo/log/protocoltiming.log.<date>—Provides information about any network interface issues
and any disk issues.
/arroyo/log/avsdb.log.<date>—Provides information about any database issues.
/arroyo/log/avsdb-err.log.<date>
/arroyo/log/statsd.log.<date>—Provides system statistics information.
/arroyo/log/stresstest.log.<date>—Provides CPU uptime information.
/root/avslauncher.log.<date>—Provides information about the startup of the avslauncher module.
Other CServer log files that may be useful are the following:
/arroyo.log/controlblocktiming.log.<date>
/arroyo.log/debug.log.<date>
/arroyo.log/decommissioned.log.<date>
/arroyo.log/deleted.log.<date>
/arroyo.log/executiontiming.log.<date>
/arroyo.log/objectRepair.log.<date>
/arroyo.log/serverinfo.log.<date>
/arroyo.log/streamevent.log.<date>
/arroyo.log/systemstats.log.<date>
Note The files with the extension <date> use the format yyyymmdd. The date is the Coordinated Universal
Time (UTC) date.
CServer Error Codes
CServer error codes that appear in the c2k.log.<date> file do not necessarily mean an error has occurred.
An actual error has “err” listed in the entry, as opposed to “out” or “ntc.” Following is a list of important
CServer error and status codes:
Error Codes
5—Completion of a task.
25—Insufficient resources.
Status Codes
0—Content is okay (cnOK).
1—Stream has ended (cnEnd).
2—Stream has been paused (cnPaused).
3—Error has occurred (cnError).
4—Next element is being processed (cnNextElement).
5—Live content has resumed (cnResumeLive).
6—Next content object is being processed (cnNextContent).
7—Next iteration is being processed (cnNextIteration).
9—There has been a failover (cnFailover) .