Hi Makis,
The thread I posted does have the exact same container.hpp error and
proposes a solution.
Did you try setting your PBS_PYTHON_INCLUDEDIR to point to your
torque/include directory, as mentioned in that thread?
from the thread:
export PBS_PYTHON_INCLUDEDIR=/usr/local/torque/include/
Good day Nicola,
Thank you for the advise on LDAP authentication. Did you need to run Galaxy
on Apache to enable this, or did you simply change some configuration files to
enable this. I think we’ll be able to write some scripts using SLURM commands
to pull data about resource utilization,
David,
Thank you for the valuable feedback. I will look into the galaxy-pulsar server
app and determine how we can implement it to connect our galaxy instance to the
working nodes. Perhaps I’ll direct a few relevant questions while we get on
board with the implementation, if you don’t mind.
Howdy y'all,
I'm building some changes to the IE infrastructure that will fix some
initial hacks we did, however they will be backwards incompatible.
Specifically these changes will fix some of the enterprise deployment
pains (running with an external upstream proxy like apache) and allow
for
Hi Carlos,
next steps might include:
* install slurm drmaa
http://apps.man.poznan.pl/trac/slurm-drmaa
e.g.
curl -#o slurm-drmaa-1.0.7.tar.gz
http://apps.man.poznan.pl/trac/slurm-drmaa/downloads/9
tar -xf slurm-drmaa-1.0.7.tar.gz
cd slurm-drmaa-1.0.7
p=$(which srun)
