# The form data below was edited by tom_tyler # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a given job is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Doc/Feature/Problem]. Required. # # Bug: is a problem that is fairly well understood, # e.g. one for which there is a reproduction or clear # articulation of the problem. # # Doc: A Documentation fix. # # Feature: An enhancement request, perhaps adding # a new product features, improving maintainability, # essentially any new software improvement other than # a fix to something broken. # # Problem: a suspected bug, or one without a clear # understanding of exactly what is broken. # # Release: Release in which job is intended to be fixed. Job: SDP-563 Status: open Project: perforce-software-sdp Severity: C ReportedBy: ashaikh ReportedDate: 2020/10/30 19:56:46 ModifiedBy: tom_tyler ModifiedDate: 2022/09/28 18:20:36 OwnedBy: ashaikh Description: Enable daily_checkpoint.sh to run on forwarding replicas. The SDP daily_checkpoint.sh script fails on forwarding replicas. The daily_checkpoint.sh script fails on forwarding replicas. It tries to replay journals to the offline_db that do not exist. $ /p4/common/bin/daily_checkpoint.sh 1 Offline journal replay failed. Abort! $ cat /p4/1/logs/checkpoint.log Fri Oct 30 05:07:00 UTC 2020 /p4/common/bin/daily_checkpoint.sh: Start p4_1 Checkpoint Fri Oct 30 05:07:01 UTC 2020 /p4/common/bin/daily_checkpoint.sh: Offline journal number is: 22 Fri Oct 30 05:07:01 UTC 2020 /p4/common/bin/daily_checkpoint.sh: Skipping call to truncate_journal() on edge or replica server. Fri Oct 30 05:07:01 UTC 2020 /p4/common/bin/daily_checkpoint.sh: Replay any unreplayed journals to the offline database. Fri Oct 30 05:07:01 UTC 2020 /p4/common/bin/daily_checkpoint.sh: Replay journal /depotdata/p4/1/checkpoints.replica.1/p4_1.replica.1.jnl.22 to offline db. Recovering from /depotdata/p4/1/checkpoints.replica.1/p4_1.replica.1.jnl.22... real 0m0.027s user 0m0.004s sys 0m0.013s Fri Oct 30 05:07:01 UTC 2020 /p4/common/bin/daily_checkpoint.sh: Replay journal /depotdata/p4/1/checkpoints.replica.1/p4_1.replica.1.jnl.23 to offline db. Recovering from /depotdata/p4/1/checkpoints.replica.1/p4_1.replica.1.jnl.23... real 0m0.023s user 0m0.004s sys 0m0.012s Fri Oct 30 05:07:01 UTC 2020 /p4/common/bin/daily_checkpoint.sh: Replay journal /depotdata/p4/1/checkpoints.replica.1/p4_1.replica.1.jnl.24 to offline db. Recovering from /depotdata/p4/1/checkpoints.replica.1/p4_1.replica.1.jnl.24... Perforce server error: open for read: /depotdata/p4/1/checkpoints.replica.1/p4_1.replica.1.jnl.24: No such file or directory open for read: /depotdata/p4/1/checkpoints.replica.1/p4_1.replica.1.jnl.24: No such file or directory real 0m0.007s user 0m0.003s sys 0m0.004s Fri Oct 30 05:07:01 UTC 2020 /p4/common/bin/daily_checkpoint.sh: ERROR!!! - replica p4_1 /p4/common/bin/daily_checkpoint.sh: Offline journal replay failed. Abort! $ ls -al /p4/1/checkpoints.replica.1/ total 40 drwx------. 2 p4 p4 267 Oct 30 05:08 . drwx------. 6 p4 p4 81 Oct 30 03:44 .. -r--r-----. 1 p4 p4 2838 Oct 30 04:54 p4_1.replica.1.jnl.15 -r--r-----. 1 p4 p4 4126 Oct 30 04:55 p4_1.replica.1.jnl.16 -r--r-----. 1 p4 p4 1940 Oct 30 04:55 p4_1.replica.1.jnl.17 -r--r-----. 1 p4 p4 1940 Oct 30 04:55 p4_1.replica.1.jnl.18 -r--r-----. 1 p4 p4 1940 Oct 30 04:55 p4_1.replica.1.jnl.19 -r--r-----. 1 p4 p4 2838 Oct 30 04:56 p4_1.replica.1.jnl.20 -r--r-----. 1 p4 p4 2838 Oct 30 04:57 p4_1.replica.1.jnl.21 -r--r-----. 1 p4 p4 3228 Oct 30 05:06 p4_1.replica.1.jnl.22 -r--r-----. 1 p4 p4 1940 Oct 30 05:06 p4_1.replica.1.jnl.23 DevNotes: Changed from 'Bug' to 'Feature'. See discussion: https://swarm.workshop.perforce.com/jobs/SDP-563#comments Also changed header line to match that this is a feature request. Component: core-unix Type: Feature