[Swift-user] Coasters local:pbs and the coasters.log file debug output

[Michael Wilde]

Matthew, thats actually a very *good* question, and I dont know the answer (but we should document it). 


I think you want to set a log4j property in the swift file etc/log4j.properties. Hopefully the message below, from the swift-user list provides a clue. Im not sure this is the exact setting you need, or something similar. 


I think to find the precise answer you'd need to look for the message you want in the source code under provider-coaster and then set the corresponding log4j property to debug. 


See also Justin's posts on simplified logging which may interact with this. 


Mihael can provide the exact answer; Justin is offline at the moment. 


Mike 



----- Forwarded Message ----- 
From: "Justin M Wozniak" <wozniak at mcs.anl.gov> 
To: "Allan Espinosa" <aespinosa at cs.uchicago.edu> 
Cc: "Swift-User" <swift-user at ci.uchicago.edu> 
Sent: Wednesday, October 20, 2010 1:23:41 PM 
Subject: Re: [Swift-user] log4j settings of vdl:* elements 




Try log4j.logger.swift=DEBUG 


See org.griphyn.vdl.karajan.lib.Log for more info. 


On Wed, 20 Oct 2010, Allan Espinosa wrote: 


> Hi, 
> 
> I think I have asked this before, but can't find the previous posts about it. 
> 
> I woud like to set the vdl:execute2 log level to DEBUG. Which 
> package/class path should I adjust in log4j.properties? 
> 
> Thanks, 
> -Allan ----- Original Message -----


Hi Mike, 

I do see some of the Coasters messages in the file, such as the INFO Cpu pull messages. 

With apologies for a dumb question: Can you point me to how to turn on the DEBUG TaskImpl messages? 

Matthew 





On Thu, Nov 4, 2010 at 9:47 PM, Michael Wilde < wilde at mcs.anl.gov > wrote: 




Matthew, 


When the first token in the coaster jobmanager parameter is "local" as in "local:pbs", then the coaster server threads run inside the main swift JVM, and thus log to the main swift log. thats the file with the long name starting with your swift script file name, followed by a timestamp and unique ID, and ending in .log. 


All the log entries that you'd find in the coaster.log file should, I think, be in the main log. 


- Mike 









When running with coasters using the gt2:gt2:pbs provider, an excellent log file pops up in 
~/.globus/coasters/coasters.log 
containing useful lines like: 
DEBUG TaskImpl Task(type=JOB_SUBMISSION, identity=urn:... 

This file isn't generated when using the local:pbs provider, at least out-of-box. 

Is there a way to turn that output log file back on, or to get those debug lines in the Swift job log file, using the local:pbs provider? 

Thanks for your time, 

Matthew 




_______________________________________________ 
Swift-user mailing list 
Swift-user at ci.uchicago.edu 
http://mail.ci.uchicago.edu/mailman/listinfo/swift-user 


-- 
Michael Wilde 
Computation Institute, University of Chicago 
Mathematics and Computer Science Division 
Argonne National Laboratory 





-- 
Michael Wilde 
Computation Institute, University of Chicago 
Mathematics and Computer Science Division 
Argonne National Laboratory 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-user/attachments/20101105/917b4584/attachment.html>