On Fri, May 07, 2010 at 11:31:07AM +0200, Loraine Brillet wrote:
The script being already running , I thought that could be problem (Am I right ?) and tried "run.sh --stop-daemon", which returned me "No PID file exists in paster.pid".
What is the right thing to do ?
Your assessment that another galaxy instance is already running seems correct. Off the top of my head here are a few possible reasons why --stop-daemon might not be working:
1) If the running instance were started in another disk location/copy-of-galaxy you need to be there when stopping the daemon
2) If it was run not as a daemon, (eg "./run.sh") then it's not a daemon and can't be stopped thusly. If that's the case go find the window where it was started and press Ctrl-C in it.
3) If the daemon were started by a user other than you it's possible you're unable to stop their daemon instance and read their .pid file
Some options you have now inlcude:
1) find the python galaxy process and kill it directly:
$ ps auxwww | grep python galaxy 3743 0.0 2.3 332716 72532 ? Sl May05 2:30 python -E ./scripts/paster.py serve --log-file /var/log/galaxy/galaxy.log universe_wsgi.ini --pid-file=/var/lib/galaxy/galaxy.pid --daemon $ kill 3743
or
2) Find out what user+location combo ran the daemon and stop it
or
3) Start the new instance on a different by changing the port= value in universe.wsgi to something ohter than 8080, and update the URL in your browser's address bar thusly.
Sorry if that's too much info, but the cause and fix are likely somewhere in that braindump.