Re: [Opaltoolkit-users] problem launching opal jobs

[Luca C. <lcl...@uc...>]

Malcolm Tobias wrote:
> Wilfred,
> 
> On Thursday 25 June 2009 11:34:03 am Wilfred Li wrote:
>> Looking at your opal.properties file, I'd suggest that you use the
>> ForkJobManager for now to debug your installation, since we haven't figured
>> out how to configure the DRMAAJobManager with PBS yet. We used PBS 4 or 5
>> years ago, but switched to SGE for a number of reasons. You can do this by
>> adding the appConfig entry
>>
>> <jobManagerFQCN>edu.sdsc.nbcr.opal.manager.ForkJobManager</jobManagerFQCN>,
>> or edit your current entry for DRMAAJobmanager.
> 
> This seems like a good suggestion.  I tried using ForkJobManager and it 
> worked!
> 
> [root@agave opal-ws-2.0]# java edu.sdsc.nbcr.opal.GenericServiceClient -l 
> http://agave.wustl.edu:8080/opal2/services/pdb2pqr -r 
> launchJob -a "--ff=amber sample.pdb output.pqr" -f samples/sample.pdb
> 
> Reading command line arguments
> Service URL: http://agave.wustl.edu:8080/opal2/services/pdb2pqr
> Invoking operation: launchJob
> 
> Command line arguments: --ff=amber sample.pdb output.pqr
> Making non-blocking invocation on Opal service -
> Received jobID: app1245958071884
> Current Status:
>         Code: 1
>         Message: Launching executable
>         Output Base URL: http://agave.wustl.edu:8080/app1245958071884
> 
> I'll try to focus on making sure that the user running opal can access the 
> correct queues by default.  
> 
> Malcolm
> 

Malcom,
but if you use fork, Opal will simply fork the job on the node where the 
tomcat is running.

The problem you are experiencing is connected with the libdrmaa.so so if 
you use fork everything is fine.

To update the LD_LIBRARY_PATH try running
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<your path to libdrmaa.so>

Sincerely,
Luca