[Swift-devel] log

[Mihael Hategan]

1. I asked Nika to enable debugging on that so that I could get a closer
look at what's happening.
2. Yes, but not quite like that. You need to remove the trailing part:
mhategan at viper:/home/nefedova/alamines> cat
MolDyn-244-loops-20070918-1056-g09htdig.log|grep 0-1-224-0
2007-09-18 11:00:47,302 DEBUG vdl:execute2 Job antch-o5j7pehi running in
thread 0-1-224-0 run 20070918-1056-g09htdig
2007-09-18 11:19:24,143 DEBUG TaskImpl Task(type=4,
identity=urn:0-1-224-0-1-1190131081169) setting status to Active
2007-09-18 11:19:24,143 DEBUG TaskImpl Task(type=4,
identity=urn:0-1-224-0-1-1190131081169) setting status to Completed
2007-09-18 11:20:14,360 DEBUG TaskImpl Task(type=1,
identity=urn:0-1-224-0-1190131082238) setting status to Submitted
2007-09-18 11:24:58,541 DEBUG TaskImpl Task(type=1,
identity=urn:0-1-224-0-1190131082238) setting status to Active
2007-09-18 11:25:19,121 DEBUG TaskImpl Task(type=1,
identity=urn:0-1-224-0-1190131082238) setting status to Completed

So there's one message saying what thread a job runs in, and then the
task ID is made of "urn:"<thread>"-"<UID>

If you see more after, say "0-1-224-0" and before the long UID, those
are sub-threads of the job thread, most likely files being staged in or
out.


On Tue, 2007-09-18 at 21:43 +0000, Ben Clifford wrote:
> related,
> 
> these logs lines:
> 
> 2007-09-18 16:38:53,297 DEBUG TaskImpl Task(type=4, 
> identity=urn:0-1-211-0-1-1190150109910) setting status to Completed
> 
> Is there a way to tie them into anything else?
> 
> Running this:
> 
> $ grep urn:0-1-211-0-1-1190150109910 MolDyn-244-loops-20070918-1613-ry2ltpyc.log
> 
> 2007-09-18 16:38:53,296 DEBUG TaskImpl Task(type=4, 
> identity=urn:0-1-211-0-1-1190150109910) setting status to Active
> 
> 2007-09-18 16:38:53,297 DEBUG TaskImpl Task(type=4, 
> identity=urn:0-1-211-0-1-1190150109910) setting status to Completed
> 
> gives fairly uninteresting information, at least without knowledge of what 
> that tast is trying to do.
> 
> Is there a way to tie it to what the task actually is? or perhaps it too 
> could be turned off.
>