# 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. # # 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. Job: SDP-241 Status: closed Project: perforce-software-sdp Severity: C ReportedBy: giles ReportedDate: 2017/08/03 10:30:19 ModifiedBy: tom_tyler ModifiedDate: 2018/09/14 13:58:42 OwnedBy: tom_tyler Description: Update systemd templates to add new wait targets. Per an email from Giles: Just in case anyone else happens to encounter a problem like this: I had a call where a replica would start but not replicate after a reboot of a Centos 7 machine on which it was running (don't ask about the validity of rebooting without shutting the Helix Server down first !). The error thrown for the 'pull' thread was: 'Replica access to P4TARGET server failed. Remote server refused requesst. Please verify that service user is correctly logged in to remote server, then retry. TCP connect to si-perforce:1667 failed. Name or service not known' Using the SDP scripts to stop and restart the replica allowed replication to continue normally. It was found that the system was using systemd to control the start of the replica at bootup; my suspicion was then that the network had not completed its startup before P4D was started, hence the error. This was confirmed by adding some additional parameters to the startup 'p4d_1.service' file to have some control over the order of the startup (full procedure at the end of this email): Requires=network.target NetworkManager-wait-online.service After=network.target NetworkManager-wait-online.service Lo and behold, P4D now waited for the network to come up before it tries to start and replication takes place properly. This may be simple stuff for some of you guys, but I hope that may help some people and save some time in the future; I lay no claim to be anything more than a novice with systemd so if there are experts out there you may be able to provide refining elements to this. See also: SDP-58 Component: core-unix Type: Bug