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

[Matthew Woitaszek]

Hi Mihael,

Thanks so much for the logging pointers! I have to confess that I'm really
inexperienced with the log4j/Java logging facility, so those details were
exactly what I needed.

I tracked down the Coasters configuration in
cog/modules/provider-coaster/resources/log4j.properties and the two lines
that control what I was interested in were painfully obvious:

log4j.logger.org.globus.cog.abstraction.coaster=INFO
log4j.logger.org.globus.cog.abstraction.impl.common.task.TaskImpl=DEBUG

After copying those over to swift-dist/etc/log4j.properties, the
Submitting|Submitted|Active messages I'm interested in get included when
running Swift with Coasters in the "local" (one JVM) mode.

Thanks again for your help!

Matthew


On Sun, Nov 7, 2010 at 1:08 PM, Mihael Hategan <hategan at mcs.anl.gov> wrote:

> On Fri, 2010-11-05 at 13:54 -0600, Matthew Woitaszek wrote:
> > 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?
>
> You would say something like:
> log4j.logger.org.globus.cog.abstraction=DEBUG
> in log4j.properties.
>
> Which log4j.properties that is depends on how you run this. In one of
> the local modes (i.e. coaster service in the same JVM as swift = coaster
> messages in swift logs) you would edit swift-dist/etc/log4j.properties.
>
> In the remote service case, and assuming you are not using a persistent
> coaster service, you would have to edit
> cog/modules/provider-coaster/resources/log4j.properties and re-compile
> swift. I don't much like this, but it is like that for now.
>
> Mihael
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-user/attachments/20101107/c95ea3ee/attachment.html>