The replication engine logs errors and warnings in the p4dtg/repl folder. For each instance of the replication engine, one log file is created. The log file is named log-mapfile.log, where mapfile is the name of the corresponding mapping.
After you stop an instance of the replication engine, be sure to examine the log file. If you are experiencing problems, check the log file. If you delete the log file, it is recreated the next time the replication engine is started.
If an error occurs during job-defect replication, the replication engine writes an error message to the DTG_ERROR field in the Helix Server job involved. Jobs containing entries in the DTG_ERROR field are not replicated. To re-enable replication, you must clear the DTG_ERROR field.
To list all jobs that have entries in the DTG_ERROR field, issue the following command:
p4 jobs -e "DTG_ERROR=*"
To detect replication problems on an ongoing basis, you can create a script that periodically issues the preceding command and reports any problems it detects.
If the replication engine encounters a problem that prevents it from successfully replicating data, it logs error information to a file named err-mapfile in the repl folder. The replication then exits and cannot be restarted until you resolve the problem and delete the error file.