[gridengine users] Message in stderr after exceeding resources
chris.jewell at warwick.ac.uk
Thu Mar 3 11:38:26 UTC 2011
On 2 Mar 2011, at 19:32, Reuti wrote:
>> Would it be possible to write to the stderr with an epilogue script, harvesting the same line from the messages file, I wonder?
> My experience is: no. At time of the epilog the entry in the messges file is not written yet, so I decided to put it in the mail wrapper which will be used to send the email after the job has left the node.
> It's of course possible to "abuse" the mail-wrapper to also append the line to the stderr of the job. But the setup is a little bit convoluted, as you have to save the name of the stderr file in a persistent file which will survive the end of the job - after the job you can't retrieve its name any longer. This can be done in a job prolog, and we use it to include some entries of the job context in the email later on. Let me know if you need some directions to set it up.
Okay, thanks for the info. I understand how to set it up. IMHO, we should probably have this issue addressed in GE, as it can save a lot of debugging time to quickly know why your job was killed when it was -- if this information is available to write to the messages file, then I don't see why it shouldn't be possible for the shepherd to append it to the job stderr.
More information about the users