Hi Martin,

We haven't upgraded to the March release yet, and I haven't really touched the tools I referred to in my original email since I got them working (despite the duplicate installation records in the admin interface, etc). I've started testing the new release, though, and will take another look after we complete the upgrade. Thanks for following up!


Cheers,

Brian


On Mon, Apr 13, 2015 at 7:27 AM, Martin Čech <marten@bx.psu.edu> wrote:
Hello Brian,

we have made some changes in the past month that might address the issue you are having. Are you still encountering problems? If so could you please try re-installing the tools again?

thank you

Martin

On Tue, Feb 24, 2015 at 5:15 PM Brian Claywell <bclaywel@fredhutch.org> wrote:
Hi Martin,

Thanks for the prompt reply! My responses are inline below.

On Tue, Feb 24, 2015 at 8:26 AM, Martin Čech <marten@bx.psu.edu> wrote:
Are you using Admin UI for installation or API scripts?

The admin UI exclusively.
 
Does the 'installed tool shed repos' page show multiple installations of the same package (with the same changesets)? If so what are the states of these?

Yes -- the iuc package_numpy_1_7 revision a4bdc17eed4a is listed twice, with both showing the green "Installed" status. Interestingly the installed repo page shows that they're installed in different locations:


At one point during the troubleshooting steps I described in my original email, package_pybamparser_0_0_1 and package_pybamtools_0_0_1 showed up in the same way, with two records each having the same revision and a green "Installed" status.

If you check on the filesystem in the {{configured_dependency_dir}}/path/to/duplicated/package do you see any strange stuff/duplication?

I didn't see anything that struck me as out of the ordinary. Here's a gist of the directory structures for the affected packages under both shed_tools and tool_deps:


How big is your Galaxy in terms of installed tools, complexity of setup and traffic?

I don't think it's terribly big -- we have a couple of large tool suites like BEDTools, the gops interval operations suites, GATK 1 and 2, etc, and then maybe 15-20 other tools and their dependencies?

Our setup isn't very complex, either; Galaxy is running with one web process and one handler process behind an nginx reverse proxy, all running on a single machine. Jobs are submitted to our slurm cluster via the SSH CLI runner.

Traffic is pretty low -- we're just now rolling out of beta.


Cheers,

Brian

--
Brian Claywell | programmer/analyst
Matsen Group   | http://matsen.fredhutch.org
Fred Hutchinson Cancer Research Center



--
Brian Claywell | programmer/analyst
Matsen Group   | http://matsen.fredhutch.org
Fred Hutchinson Cancer Research Center