Hi Yan,

I've moved this discussion to the galaxy-dev list since it pertains to a
local installation of Galaxy.

Responses to your questions follow, in-line.

Yan Luo wrote:
> Dear Sir,
> 
> (1)We installed Galaxy, but recently the user can't registered and got the
> following error, how can we fix it?
> 
> Sever error
> An error occurred. See the error logs for more information.(To turn debug on
> to display ...).

Since debug = False in universe_wsgi.ini, you should be able to find a
more detailed error message in the log file.  If starting Galaxy with:

  % sh run.sh --daemon

The default log file is 'paster.log' in Galaxy's root directory.

> (2) Could you please let me know if there is any command to stop galaxy?

If starting with the --daemon flag (as above), you can use:

  % sh run.sh --stop-daemon

If running in the foreground, you can use Ctrl-C to terminate the
process.  There is a recent bug whereby Ctrl-C is ineffective on some
platforms under Python 2.6 - in this case you will have to kill/pkill
the process manually.  We are working on a fix for the latter.

> (3) If I reset universe_wsgi.ini file and want to set an administrator
> user(I can add a line in the above file), how can I get the password? Should
> I stop galaxy(See question 2) first? then run "./setup.sh" and "./run.sh".

setup.sh would have only been necessary prior to running Galaxy the
first time, however, this step has recently been removed.  If you are
referencing documentation that still refers to setup.sh, please let us
know so we can update it - I did notice this was still on the
"Production Server" page, so I removed it from there.

You no longer need to run setup.sh at all.

> (4) If I run "setup.sh", will a new file "universe_wsgi.ini" be generated?
> if I want to change this file,should I edit it before "run.sh" and after
> "setup.sh". Is it right?

setup.sh and its replacements in run.sh and the Galaxy application
itself never overwrite files, they only create files from sample files
if they do not exist.

> (5) I read some of your docs, command "sh setup.sh"(sh run.sh) and
> "./setup.sh"(./run.sh), which one is correct under Linux?

Both syntaxes are effectively the same in most cases.

--nate

> 
> Looking forward to hearing from you.
> 
> Best Wises,
> 
> Yan Luo, Ph.D.
> NIH
> <http://int.ask.com/web?siteid=10000861&webqsrc=999&l=dis&q=By%20the%20way,>

> _______________________________________________
> galaxy-user mailing list
> galaxy-u...@lists.bx.psu.edu
> http://lists.bx.psu.edu/listinfo/galaxy-user

_______________________________________________
galaxy-dev mailing list
galaxy-dev@lists.bx.psu.edu
http://lists.bx.psu.edu/listinfo/galaxy-dev

Reply via email to