Pinnacle Design 37T100105 manual Troubleshooting, Logs

Chapter 6: Troubleshooting

This Chapter describes basic troubleshooting and the system logs that may assist you in troubleshooting problems. If you have any questions about troubleshooting your system, please contact Pinnacle Technical Support.

Logs

There are three system logs. The ConnectPlus 1000 gateway and the TCS use elogger, which places log files in the directory C:\FSC\Logs. This log contains most information about system- wide problems such as Ethernet, Fibre Channel, file system, or system resource problems. There are also two logs associated with each file transfer:

•transfer id number.log contains a series of status codes describing the transfer. Each state the transfer enters is logged to the end of this file (e.g., “ACCEPTED”, “Transfer in Progress”, “Job is done”). If the state is a failure state, it may be followed by additional information and debugging suggestions, separated by “”. If no such information is available, check Table 1 below for the extended description.

•info_transfer id number.log contains a list of the actual commands sent to each FTP server involved in the transfer, for a normal transfer. For transfers using audio-demux or newcopy functionality, this file contains the output of the process handling the transfer. For a failed transfer, the last line containing a “” describes the cause of the failure. (This line is identical to the last line of transfer id number.log.)

These file transfer logs are located in C:\Program Files\Pinnacle Systems\MMG-server\Joblogs\ and log transfer-specific problems, such as dropped connections or corrupt source files.

Table 1: Transfer Log Status Codes
Status	Description
ERROR: job not found	A job ID was requested that is ether less than 0 or greater
	than the amount of jobs started yet, and is not identified
	as a valid job by the Transfer Control System (TCS).
	Probable cause: The getStateOverview function of the
	MMG client requested more jobs than the TCS has
	registered.
ERROR: source file couldn’t be	The TCS checks if the source file for a transfer is on the
found on source host	source host. If it’s not, the job is reported as having this
	state.
ERROR: destination file already	The TCS has checked source and destination files for a
exists	transfer, and the destination file already exists. Job
	execution cannot continue.