[Shake-dev] [EHPweb] PDL sender configuration

[Bruce Worden]

Hi Pete,

The ShakeMap programs bounce around. The initial working directory would be the directory from which the program was called, of course, but transfer, for example, moves into the event's data directories. It's not clear how PDL used to work -- I'm guessing that there was a default that looked for the config file relative to the location where the client code was installed, rather than from where it was invoked.

But I guess none of that matters now that PDL has changed. It looks like everyone is going to have to explicitly specify the config file using the pdl_config parameter in transfer.conf.

FWIW, I didn't know this change was coming -- I added the config parameter for a completely different reason.

B


On Apr 3, 2012, at 1:24 PM, Peter Lombard wrote:

> Bruce,
> 
> Pardon my misuse of the term "current directory". Apparently I should have
> used "working directory"; the result of the "pwd" command or the value of the
> PWD environment variable on most Unix/Linux systems; the quantitiy that
> changes when it calls "chdir()", See for example
> http://en.wikipedia.org/wiki/Working_directory.
> 
> I don't see anything in the programs queue, shake or transfer that define a
> standard "working directory". So I don't know how ProductClient.jar, when
> called by transfer, is supposed to find its config file.
> 
> Pete
> 
> 
> Bruce Worden writes:
>> Hi Pete,
>> 
>> I don't know what is meant by "current directory." My understanding is that
>> the client comes with a default configuration file. Maybe Jeremy can
>> elaborate. 
>> 
>> There is an as-yet unannounced ShakeMap update in the repository. One of
>> the changes is the addition of a parameter "pdl_config" to
>> transfer.conf. The parameter is not documented in transfer.conf (at the
>> moment), but is available for use, and will set the --configFile option for
>> PDL. 
>> 
>> Bruce
>> 
>> 
>> On Apr 3, 2012, at 10:55 AM, Peter Lombard wrote:
>> 
>>> Bruce,
>>> 
>>> Jeremy Fee reports a possible change to the way we are using PDL in
>>> Shakemap. Specifically, he seems to be saying that we should set up a
>>> configuration file when using ProductClient.jar to send products to USGS.
>>> 
>>> It's not clear to me how if we are supposed to do this in ShakeMap; and if so,
>>> how we do it.  According to the help built into ProductClient.jar, there is a
>>> command-line option "--configFile=FILE" to identify the config file. Yet there
>>> is no provision in transfer or transfer.conf for giving the file name. Without
>>> this option, ProductClient attempts to read "config.ini" from the "current
>>> directory". I have no idea what is the current directory when transfer invokes
>>> ProductClient.jar, and I'm pretty sure there is no config.ini in any directory
>>> that transfer might be using.
>>> 
>>> Can you please clarify with Jeremy what ShakeMap producers are supposed to do
>>> regarding ProductClient and its config file?
>>> 
>>> Pete
>>> 
>>> 
>>> Jeremy M Fee writes:
>>>> Hello,
>>>> 
>>>> Several users have reported problems sending products using the new  
>>>> PDL client (version 1.7.3).  If you only receive products using PDL  
>>>> this does not affect you.
>>>> 
>>>> 
>>>> If you send products, please double check that senders and trackerURL  
>>>> are configured explicitly in config.ini:
>>>> 
>>>> - in the globals, set the senders list and trackerURL property:
>>>> 
>>>> senders = ehppdl1, ehppdl2
>>>> trackerURL = http://ehppdl1.cr.usgs.gov/tracker/
>>>> 
>>>> 
>>>> - add sections for each sender
>>>> 
>>>> [ehppdl1]
>>>> type = gov.usgs.earthquake.distribution.SocketProductSender
>>>> host = ehppdl1.cr.usgs.gov
>>>> port = 11235
>>>> 
>>>> [ehppdl2]
>>>> type = gov.usgs.earthquake.distribution.SocketProductSender
>>>> host = ehppdl2.wr.usgs.gov
>>>> port = 11235
>>>> 
>>>> 
>>>> 
>>>> Thanks,
>>>> 
>>>> Jeremy
>>>> 
>>>> _______________________________________________
>>>> EHPweb mailing list
>>>> EHPweb at geohazards.usgs.gov
>>>> https://geohazards.usgs.gov/mailman/listinfo/ehpweb
>>> _______________________________________________
>>> Shake-dev mailing list
>>> Shake-dev at geohazards.usgs.gov
>>> https://geohazards.usgs.gov/mailman/listinfo/shake-dev
>>