I use something similar to Stuart, except I go via the WMS and specify
the queue, so I can decide later one where I dump the output:
glite-wms-job-submit -a -r
ceprod05.grid.hep.ph.ic.ac.uk:8443/cream-sge-grid.q -o ceprod05.log
glite-submit.jdl
and then
glite-wms-job-output --dir [directory where I want the stuff to go] -i
ceprod05.log
(I still need
StdOutput = "stdoutFile";
StdError = "stderrFile";
OutputSandbox = { "stdoutFile", "stderrFile"};
in the jdl)
Daniela
On 4 October 2011 22:43, Stuart Purdie <[log in to unmask]> wrote:
> On 4 Oct 2011, at 21:42, Stephen Jones wrote:
>
>> I'm using glite-ce-job-submit, to show that a prototype emi cream ce
>> works. Fine, it goes through all the job states, and winds up on a
>> worker node. But where does STDOUT/STDERR get hidden? I can't find them,
>> and there's no glite-ce-get-output command. Anybody got a clue where
>> they are, because I don't!
>
> If you're submitting direct to cream, there is no facility for 'collecting' output. Instead, what you must do is put an explicit stage out description in the JDL, telling CREAM what files you want, and where to put them.
>
> To a first approximation, you'll need to run a GridFTP server somewhere for this purpose. Running one on a UI is very convenient, but you'll have to be very careful to make sure you don't expose certificates!
>
> You'll probably want something like:
>
> StdOutput = "stdoutFile";
> StdError = "stderrFile";
> OutputSandbox = { "stdoutFile", "stderrFile", "otherFile" };
> OutputSandboxBaseDestURI = "gsiftp://host.name/path/to/dir";
>
> (If memory serves, the lack of / at the end of the path of OutputSandboxBaseDestURI is important).
>
> The WMS does this, with having a staging area for a output to be left in before collection.
>
--
-----------------------------------------------------------
[log in to unmask]
HEP Group/Physics Dep
Imperial College
Tel: +44-(0)20-75947810
http://www.hep.ph.ic.ac.uk/~dbauer/
|