Bug 4311 - GRAM error log files
: GRAM error log files
Status: RESOLVED FIXED
: GRAM
general
: 4.0.1
: All All
: P3 enhancement
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2006-03-24 14:58 by
Modified: 2012-09-12 09:07 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2006-03-24 14:58:19
The GT4 implementation of GRAM has changed what information is being written to
the GRAM log files that are created upon error during job submission.
Specifically, the stderr output of the batch submit command is now being
redirected to a special file rather than reported directly in the GRAM log
file. That information is critical in debugging job submission problems. That
special file is removed during a clean up phases and so there is no trace of
the infomration that is written to stderr from the batch submission command.
Either that infomraiton needs to continue to be included in the GRAM log file
or the file containing that information should not be removed on job submission
error.
------- Comment #1 From 2006-03-24 15:02:17 -------
It is currently difficult to corrolate a GRAM error log file with a job
submission when multiple job submissions are made simultaneously. I suggest
that a command line option to GRAM job submission tools be implemented that
would allow a user to provide a name of the GRAM log file. That would enable
the user, or an automated job submission process, to establish a corrolation
between job submissions and GRAM error log files.
------- Comment #2 From 2006-03-24 16:03:05 -------
Adding Joe to the CC list since I don't understand what Doru is talking about.
------- Comment #3 From 2012-09-12 09:07:23 -------
Cleaning up old GRAM bugs. This exists in GRAM5.