Dear Galaxy community,
I'm currently testing cross-platform compatibility with our Galaxy instance
- [on PROD environment] Galaxy service runs on a RedHat 6.5 server (using
python2.6 installed in a virtualenv) and submits jobs on cluster nodes also
in RedHat 6.5/python2.6 (default version installed on the system).
- [on TEST environment] I changed the configuration of our Galaxy TEST
instance (still RedHat 6.5 / python 2.6) to submit jobs on cluster nodes in
CentOS7/python2.7 (default version installed on the system).
- Galaxy installations (test and prod) and virtualenv folders are located
in a volume mounted on Galaxy servers and all cluster nodes.
On TEST environment python tools (like the internal Galaxy tool "upload1",
or the NCBI BLAST toolkit) if submitted on the cluster failed with the
following message :
"python: error while loading shared libraries: libpython2.6.so.1.0: cannot
open shared object file: No such file or directory"
I guess the problem lies in the shared library libpython2.6.so.1.0 located
in /usr/lib64/libpython2.6.so.1.0 on the Galaxy server and absent from the
cluster nodes (it should be something like
Is it possible to integrate this shared library in the Python virtualenv
and use a specific configuration to indicate Galaxy to use it when
submitting jobs on the cluster ?
Thanks in advance,
Show replies by date