# 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 givenjob 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/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: SDP-623 Status: open Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2021/03/13 10:25:41 ModifiedBy: tom_tyler ModifiedDate: 2021/03/13 10:25:41 OwnedBy: tom_tyler Description: Under heavy load, can't rotate p4d log on Windows, preventing checkpoints. == Sample log Starting Daily Backup 2021/03/13 03:00:03 Logging in to P4 Instance 2021/03/13 03:00:03 c:\p4\2\bin\p4.exe -p 2666 -u perforce login -a < c:\p4\config\adminpass.txt >> c:\p4\2\logs\checkpoint.log 2>&1 Enter password: User perforce logged in. 2021/03/13 03:00:05 Checking offline DB exists 2021/03/13 03:00:05 checking existence of c:\p4\2\offline_db\db.counters 2021/03/13 03:00:05 Ensuring there is no other checkpoint script running 2021/03/13 03:00:05 checking existence of c:\p4\2\checkpoints\ckp_running.txt 2021/03/13 03:00:05 Getting current live journal counter 2021/03/13 03:00:05 c:\p4\2\bin\p4.exe -p 2666 -u perforce counter journal 2021/03/13 03:00:06 110 2021/03/13 03:00:06 Live journal/checkpoint counters 110/111 2021/03/13 03:00:06 Getting offline journal counter 2021/03/13 03:00:06 c:\p4\2\bin\p4d.exe -r c:\p4\2\offline_db -jd - db.counters 2021/03/13 03:00:07 @110@ 2021/03/13 03:00:07 Offline journal counter 110 2021/03/13 03:00:07 Truncating live journal 2021/03/13 03:00:07 Truncating journal... 2021/03/13 03:00:07 c:\p4\2\bin\p4d.exe -r c:\p4\2\root -J c:\p4\2\logs\journal -jj 2021/03/13 03:00:08 Rotating c:\p4\2\logs\journal to c:\p4\2\checkpoints\p4_2.jnl.110... 2021/03/13 03:00:08 Rotating various logfiles 2021/03/13 03:00:08 Rotating master.2.log to master.2.log.110.20210313-030008 2021/03/13 03:01:15 Failed to rename file after 600 retries. 2021/03/13 03:01:15 c:\p4\common\bin\gzip.exe master.2.log.110.20210313-030008 2021/03/13 03:01:16 2021/03/13 03:01:16 failed to gzip file 2021/03/13 03:01:16 Sending email with subject: FAILED: p4d-win10-04 p4_2 Daily Backup log. == process busy ... When attempting to rotate the log manually on the command line, an error is given indicating the service has the file busy so that it can't be moved. == Possible solution? Rethink log rotation. Maybe copy-then-truncate? Component: core-win Type: Bug