Greetings,

I am trying to upgrade our Galaxy instance to the latest stable code from 
master and now our instance won't start using my /etc/init.d/galaxy script.  
That is:

> sudo service galaxy start

no longer works. It says it does (i.e. prints "[OK]"), but Galaxy isn't running 
and nothing is written to the log. I am using the init.d script from simison 
[1], which is basically the same as the one posted to the Galaxy wiki [2], both 
of which are quite old.

Galaxy does start with:

> sudo su galaxy
> ./run.sh --daemon

so I have left Galaxy running in a screen session for now, but that is less 
than ideal.

I suspect something to do with the .venv as `./run.sh --skip-venv` also fails 
and I don't recall Galaxy being that finicky about a venv being active. Does 
anyone know how I can get the /etc/init.d/galaxy script (i.e. 
start-stop-daemon) to activate the venv for paster.py?

Cheers,
Keith

1. http://simison.com/brian/GalaxyAdmin_notes.html
2. 
https://wiki.galaxyproject.org/Events/GCC2012/TrainingDay/WS5?highlight=%28init.d%29

------------------------------
Research Associate
Department of Computer Science
Vassar College
Poughkeepsie, NY


___________________________________________________________
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:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to