> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
>
> > -----Original Message-----
> > From: Testbed Support for GridPP member institutes [mailto:TB-
> >
> > I reviewing the large simulation task we swallowed in the last few
> > days (http://tinyurl.com/kqqu9m), Oxford were having most problems
> > with 3600s timeouts on data staging, which I think they should look
> at
> > (http://tinyurl.com/mzlbl8).
> >
> We don't really understand this one at the moment, but we're hoping to
> get a bit more info if we can catch it in the act with
today/tomorrow's
> test.
>
I'm having a slight technical hitch here; if I go to the HammerCloud
page
at http://gangarobot.cern.ch/hc/540/test/ and pick the 'Backend Reasons'
section I can see that there have been some timeouts at Oxford; if I
then
click on the 'd' (detail?) link to the right I get a 404.
Can someone point me at a way to get the actual detailed job
output/error
messages from somewhere?
Ewan
|