Would this problem go away if I only used ONE webserver in my proxy setting and not use a balancer?
I may not need it and if it means I could not use the toolshed effectively, it may be worth it not to use balancing..
What i really need is the manager being balanced, since submitting a workflow with 100's of BAM files can take hours just to get started...ANy change we can run multiple managers?

Thanks

On Feb 13, 2013, at 07:59 AM, Nate Coraor <nate@bx.psu.edu> wrote:

On Feb 7, 2013, at 2:43 PM, Anthonius deBoer wrote:

> That's very unfortunate...
> I have a ton of tools and I guess now I have to create a package for them in a local toolshed to update them in a running galaxy server?
>
> In any case...The toolshed installation also does not work for me...I still have to restart galaxy, even after using the toolshed approach to install a tool...It either does not show up at all or give a bunch of errors, about not being able to find the tool...
>
> Is this also related to the fact I have two webservers and am behind a proxy server as well?

Hi Thon,

Essentially yes, there is no way for one web process to communicate with others that it has installed a tool. We'd like to allow for this sort of notification via a message queue, but we don't have a proper message queue in Galaxy right now.

--nate

>
> Thon
>
> On Feb 07, 2013, at 05:29 AM, Dannon Baker <dannonbaker@me.com> wrote:
>
>> Unfortunately not, and with the migration of tools to the toolshed installation mechanism I don't imagine this will be addressed (at least by the team) anytime soon. If you wanted you could probably write a script that would reload a specified tool in each of the separate web processes, or just implement a complete rolling restart of your web processes to avoid service disruption while still loading the tool updates.
>>
>> -Dannon
>>
>>
>> On Feb 6, 2013, at 8:40 PM, Anthonius deBoer <thondeboer@me.com> wrote:
>>
>> > I am indeed using multiple web processes and I guess I am talking about the "old" admine tool reloader...
>> > Is there any other way to do this for your own tools that you just manually place in tools etc.?
>> >
>> > Thon
>> >
>> > On Feb 05, 2013, at 06:22 PM, Dannon Baker <dannonbaker@me.com> wrote:
>> >
>> >> Are you using multiple web processes, and are you referring to the old admin tool reloader or the toolshed reloading interface?
>> >>
>> >> -Dannon
>> >>
>> >> On Feb 5, 2013, at 9:13 PM, Anthonius deBoer <thondeboer@me.com> wrote:
>> >>
>> >> > Hi,
>> >> >
>> >> > I find that reloading a tool's configuration file does not really work.
>> >> > First, you have to click the reload buttow twice to actually have it update the VERSION number (so it does read something)...
>> >> > But when I try to run my tool, the old bug is still there...
>> >> >
>> >> > I am using proxy server so something may still be cached, but I have to restart my server for it actually to pick up the changes...
>> >> >
>> >> > Any ideas?
>> >> >
>> >> > Thon
>> >> > ___________________________________________________________
>> >> > 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/
>> >>
>>
> ___________________________________________________________
> 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/