On Oct 18, 2012, at 1:43 AM, Todd Oakley wrote:

> Yes, daemon/stop-daemon is the best way.  However, to stop a process that was 
> not started with --daemon, this is what I do:
> 
>  ps aux | grep galaxy
> 
> Identify the process numbers for 3 Galaxy processes, which will change every 
> time Galaxy is restarted.
> For example this line:
>  galaxy   11638  0.0  0.0  63856   988 ?        S    Nov10   0:00 /bin/sh 
> ./run.sh --reload
> 
> indicates the process has a number of 11638.
> The 3 processes look like:
>       • /bin/sh ./run.sh --reload
>       • python ./scripts/paster.py serve universe_wsgi.ini --reload
>       • /home/galaxy/bin/python ./scripts/paster.py serve universe_wsgi.ini 
> --reload
> Next, kill the three processes with this command:
>  kill -9 <ID1> <ID2> <ID3>

Hi Todd,

Are you unable to Ctrl+C when using --reload?  Using --reload is actually my 
workaround for this problem.

--nate

> 
> 
> 
> 
> 
> On Oct 17, 2012, at 10:17 PM, Enis Afgan wrote:
> 
>> With a certain version of Python there's been an issue stopping Galaxy using 
>> ctrl+C. You can use 'sh run.sh --daemon' to have the process run in the 
>> background and then 'sh run.sh --stop-damemon' to stop it.
>> 
>> Hope this helps,
>> Enis
>> 
>> On Thu, Oct 18, 2012 at 4:12 PM, Sachit Adhikari 
>> <sachit.techner...@gmail.com> wrote:
>> Hello Everyone. Ctrl+C or Ctrl+D doesn't stop the Galaxy server. In local 
>> machine, I need to close the terminal and restart the terminal again. 
>> However, in server I integrated several tools, now I need to restart the 
>> server to test it. I used ./run.sh --reload doesn't restart the server and I 
>> can't stop the server. How can I stop or restart Galaxy in the real working 
>> server? Thanks 
>> ___________________________________________________________
>> The Galaxy User list should be used for the discussion of
>> Galaxy analysis and other features on the public server
>> at usegalaxy.org.  Please keep all replies on the list by
>> using "reply all" in your mail client.  For discussion of
>> local Galaxy instances and the Galaxy source code, please
>> use the Galaxy Development list:
>> 
>>   http://lists.bx.psu.edu/listinfo/galaxy-dev
>> 
>> To manage your subscriptions to this and other Galaxy lists,
>> please use the interface at:
>> 
>>   http://lists.bx.psu.edu/
>> 
>> ___________________________________________________________
>> The Galaxy User list should be used for the discussion of
>> Galaxy analysis and other features on the public server
>> at usegalaxy.org.  Please keep all replies on the list by
>> using "reply all" in your mail client.  For discussion of
>> local Galaxy instances and the Galaxy source code, please
>> use the Galaxy Development list:
>> 
>>  http://lists.bx.psu.edu/listinfo/galaxy-dev
>> 
>> To manage your subscriptions to this and other Galaxy lists,
>> please use the interface at:
>> 
>>  http://lists.bx.psu.edu/
> 
> ___________________________________________________________
> The Galaxy User list should be used for the discussion of
> Galaxy analysis and other features on the public server
> at usegalaxy.org.  Please keep all replies on the list by
> using "reply all" in your mail client.  For discussion of
> local Galaxy instances and the Galaxy source code, please
> use the Galaxy Development list:
> 
>  http://lists.bx.psu.edu/listinfo/galaxy-dev
> 
> To manage your subscriptions to this and other Galaxy lists,
> please use the interface at:
> 
>  http://lists.bx.psu.edu/


___________________________________________________________
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using "reply all" in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

  http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

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

Reply via email to