Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Defect Tracking Gateway Documentation | 2025.1

# Check for replication errors

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, 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 P4 Server job involved. Jobs containing entries in the DTG_ERROR field are not replicated. To re-enable replication, clear the DTG_ERROR field.

To list all jobs that have entries in the DTG_ERROR field:

    p4 jobs -e "DTG_ERROR=*"

To detect replication problems on an ongoing basis, 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 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.

Your search for returned results