Hello Peter, What would your suggestion be? Wait until a new version of galaxy is compatible with my Oracle Linux 6 ? Best regards, Edgar Fernandez System Administrator (Linux) Direction Générale des Technologies de l'Information et de la Communication Université de Montréal PAVILLON ROGER-GAUDRY, bureau X-210 I Bur. : 1-514-343-6111 poste 16568 -----Original Message----- From: Peter Cock [mailto:p.j.a.cock@googlemail.com] Sent: May-24-16 2:29 PM To: Fernandez Edgar <edgar.fernandez@umontreal.ca> Cc: galaxy-dev@bx.psu.edu Subject: Re: [galaxy-dev] not sure what I can do about this... Hi Fernandez, We saw something very like that with mixed versions of Linux, specifically our Galaxy head node where pysam was installed had CentOS 7, but the node where Galaxy was trying to run the metadata detection was CentOS 6. Unfortunately I do not have a record of the exact traceback - but from memory it was the same problem in pysam with gzopen64. (We'd already fought problems with Python mis-matches, GLIBC versions, etc and had carefully built Python on CentOS 6 in order to run on both CentOS 6 and 7.) At this point we gave up, and will run the Galaxy node on the same version of Linux as the Cluster - and plan to upgrade the cluster before the Galaxy node. That way all the stuff Galaxy installs (e.g. via the ToolShed) ought to work on the cluster. Peter On Tue, May 24, 2016 at 7:08 PM, Fernandez Edgar <edgar.fernandez@umontreal.ca> wrote:
Hello guys,
I’m still stuck on this error.
I’ve installed a brand new galaxy v16.01
And when I start it, I get the big error mentioned below.
Here’s the last message in the error:
ImportError: /home/galaxy/galaxy-v16.01/.venv/lib/python2.7/site-packages/pysam/lib chtslib.so: undefined symbol: gzopen64
Thanks for your assistance!
Cheers,
Edgar Fernandez