 |
 |
hi david, this is from the jobs directory: -rw-r--r-- 1 becms29 becms 28915901 Oct 19 00:15 ORCA_000013.stdout the file shows some abrupt ending, possibly caused by end of proxy. but, other files indicate that the job started around 23:50 yesterday. i'll check the logs to see when the proxy expired. (any hints where to look?) stijn >On Wed, 19 Oct 2005, Stijn De Weirdt wrote: > > > >>i would like to know what is going wrong here (ie where the perl script >>hangs on. i bet on the sleep($wait_time). the job has been like this for >>12h+, giving it already 6 retries. where does the output of the >>log_something ends up anyway?) or what can be done about it. if you need >>more info, let me know. >> >> > >Hi Stijn, > >Apparently the user payload (ie. job) was running until about 11 o'clock >this morning (about 1.5 hours before you wrote), when its proxy ran out. > >Therefore I don't believe it was sitting in exactly the state which you >found it in for 12+ hours, but it's true that now it is attempting to >return the job output (with retires) even though there is no possibility >that it will succeed. It will take several hours to fail. That is clearly >not good - I'll look at it straight away. > >Thanks alot, >David > > >