The "new" LSF DRMAA is the old FedStage source code. However the latest
release (v 1.1.1) is claimed to be compatible with LSF 9.1.2 which we are
using. And it does work indeed.
Yes, I've re-built the lib with --enable-debug and confirmed that the
segfault happens on returning from drmaa_run_job back to Python. I'm
talking to Dan Blanchard, Python DRMAA maintainer, so there is a hope this
can get resolved.
I'm doing my debugging on the latest Python DRMAA release - 0.7.6. Galaxy
is still on 0.6 so need to update at some point.
On 16 June 2014 14:35, Nate Coraor <n...@bx.psu.edu> wrote:
> The drmaa library seems suspect here, I am not sure what the current state
> of the Platform/IBM-supplied libdrmaa is but the vendor versions have given
> me problems in the past. Could you try FedStage DRMAA for LSF?:
> This does look a bit older than FedStage/PSNC's other DRMAA
> implementations but the FedStage/PSNC implementations have been known to
> work well in the past, and this library can also have debugging output
> enabled (./configure --enable-debug) if you get segfaults with it (and
> would be useful for producing cores).
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: