[Swift-devel] coasters-hosts.pl script

[Jonathan Monette]

An update,

I noticed that the worker logs were not displaying the message connected.  This lead me to believe this circular dependency issue described in the previous email.  So I modified the worker.pl to connect to the service before trying to run a WORKER_INIT_CMD script.  This caused the connected message to appear in the worker logs, however the lines necessary for the coaster-hosts.pl script to work are still not present in the cps log.  This still confuses me, Justin how were you able to get those DEBUG Cpu lines to appear in the cps log?

On Mar 1, 2012, at 7:16 PM, Jonathan Monette wrote:

> Justin,
>   So I have been trying to help Emalayan get the host list file for the worker-init.pl script.  It seems the cps log file is not providing the ip addresses for the coasters-hosts.pl script.  I thought this was maybe because we did not have the correct log4j setting set but we have the Coaster service Cpu set to DEBUG.  So for some reason the workers are not connecting to the service.  When I comment out the export WORKER_ENVIRONEMTN="…" line in the coaster-service.conf file I see the workers connect and the cps log file shows there ip addresses.  However when setting this line it seems they are not connecting.
> 
> Emalayan thought there might be some sort of circular dependency going with the host-list file and the worker.  The worker requires the host-list file so that it can run the worker-init.pl script and then connect but the host-list file cannot be generated because the workers cannot connect.  I noticed in your swift-test directory the cps files did have the ip addresses set and coasters-hosts.pl found the ip addresses and reported them.  Did you try that test with setting the WORKER_ENVIRONMENT variable in the coaster-service.conf file?  Any idea what may be happening?  The job is running when looking under cqstat.
> 
> A side note: At the mosaswift site, your example talks about running the coasters-hosts.pl on the cps log but the example you provide runs it on logs/coasters.log.  This may need to be changed.  Also, should provide the log4j setting that is required to generate the Cpu line with the worker ip address just to clarify that this line should be set for this script to work.
> 
> For reference, this line: log4j.logger.org.globus.cog.abstraction.coaster.service.job.manager.Cpu=DEBUG