# The form data below was edited by robert_cowham # 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-412 Status: closed Project: perforce-software-sdp Severity: B ReportedBy: vkanczes ReportedDate: 2019/07/18 19:02:10 ModifiedBy: robert_cowham ModifiedDate: 2019/10/03 03:21:50 OwnedBy: vkanczes Description: Backup failing as logs cannot be rotated as the server is too busy. "We try to rotate our server log files daily and several of our depot instances are super busy and when we try to do the log, it fails with the below error: rename-item -path shootercommit.log shootercommit.log.44.20190418-220109 rename-item : The process cannot access the file because it is being used by another process. This is the first step of our backup process and if the log doesn't rotate, the backup doesn't complete. Can you help us understand what we can do to consistently rotate our logs without these errors? I notified them of open job053474 to have ‘p4 logrotate’ rotate the standard log. Request: Will this SIR also make it way back into SDP code for windows so that the daily-backup process will take advantage of it? Is there a workaround that I can implement in the meantime until it gets fixed? Logging into each my of p4 servers every day to rename the logs manually isn't really an option. DevNotes: Component: core-win Type: Bug