training_and_outreach:ticket_system

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
training_and_outreach:ticket_system [2019/04/01 11:06]
meesters
training_and_outreach:ticket_system [2019/04/01 13:03]
meesters [Investigatin a running Job]
Line 14: Line 14:
   * If possible, the whole job //output//, or if it is to big, the relevant output from the batch system (at the beginning and the end) and any //error messages// you encounter.   * If possible, the whole job //output//, or if it is to big, the relevant output from the batch system (at the beginning and the end) and any //error messages// you encounter.
  
-===== Investigatin a running Job =====+===== Investigating a running Job =====
  
 Sometimes particular jobs give issues. Expecting us to investigate a running job, requires a job to be running at working hours and to be tracked at will. This can be accomplished, if you submit your job with the ''--hold'' flag, by amending it on the command line: Sometimes particular jobs give issues. Expecting us to investigate a running job, requires a job to be running at working hours and to be tracked at will. This can be accomplished, if you submit your job with the ''--hold'' flag, by amending it on the command line:
Line 22: Line 22:
 </code> </code>
  
-If you subsequently notify us with a mail to ''hpc@uni-mainz.de'' we can release the job at any time and investigate it. Be sure to give the path to the expected job output, too.+If you subsequently notify us with a mail to [[hpc@uni-mainz.de]] we can release the job at any time and investigate it. Be sure to give the path to the expected job output, too.
  
 <WRAP center round info 90%> <WRAP center round info 90%>