Make sure that the Python you're running when you start the server is supported by Galaxy (2.5+) This will tell you what Python version you are using: python -V If that isn't the problem, try deleting the pysam egg and then re-fetching it: python ./scripts/fetch_eggs.py from your Galaxy install dir. Greg Von Kuster On Mar 23, 2012, at 9:52 AM, Leandro Hermida wrote:

Dear all,

I followed the directions in https://main.g2.bx.psu.edu/u/rkchak/p/data-transfer to set up the Galaxy AMQP listener service so that the sample tracking system can transfer datasets. When running

nohup sh run_galaxy_listener.sh &

Traceback (most recent call last): File "scripts/galaxy_messaging/server/amqp_consumer.py", line 33, in <module> from galaxy.web.api.requests import RequestsAPIController File "/gpfshpc/software/pmrdcdb/galaxy/galaxy_dist_dev/lib/galaxy/web/api/requests.py", line 7, in <module> from galaxy.web.base.controller import * File "/gpfshpc/software/pmrdcdb/galaxy/galaxy_dist_dev/lib/galaxy/web/base/controller.py", line 17, in <module> from galaxy.visualization.tracks.data_providers import get_data_provider File "/gpfshpc/software/pmrdcdb/galaxy/galaxy_dist_dev/lib/galaxy/visualization/tracks/data_providers.py", line 11, in <module> pkg_resources.require( "pysam" ) File "/gpfshpc/software/pmrdcdb/galaxy/galaxy_dist_dev/lib/galaxy/eggs/__init__.py", line 415, in require raise EggNotFetchable( str( [ egg.name for egg in e.eggs ] ) ) galaxy.eggs.EggNotFetchable: ['pysam']

But Galaxy runs fine and the pysam eggs are already there for a long time as they are used by Galaxy. What could be the problem?

kind regards, Leandro ___________________________________________________________ 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:

http://lists.bx.psu.edu/