Question: Internal Server Error on Histories Shared with Me
gravatar for Carlos Gamboa
14 months ago by
Costa Rica / San José / CeNAT
Carlos Gamboa10 wrote:

We have a Galaxy instance installed on a node in our cluster, giving access to all our researchers. Sharing histories seem to work, but when I try to use the Histories shared with Me I got a error page with:

Internal Server Error

Galaxy was unable to successfully complete your request

And the command line log:

paste.expected_exceptions: [< class 'paste.httpexceptions.HTTPException' >]
paste.httpexceptions: < paste.httpexceptions.HTTPExceptionHandler object at 0xf400690 > 'dummy'
paste.httpserver.proxy.scheme: 'http'
paste.httpserver.thread_pool: < paste.httpserver.ThreadPool object at 0xd131ed0 >
paste.recursive.forward: < paste.recursive.Forwarder from /galaxy/galaxy >
paste.recursive.include: < paste.recursive.Includer from /galaxy/galaxy >
paste.recursive.include_app_iter: < paste.recursive.IncluderAppIter from /galaxy/galaxy >
paste.recursive.script_name: '/galaxy/galaxy'
paste.throw_errors: True
request_id: '06a077649d4c11e784ca0cc47ad6b9cc'
webob._parsed_query_vars: (GET([]), '')
wsgi process: 'Multithreaded'

Yes, the path is: /galaxy/galaxy

What could be happening with our installation or configuration? Thanks

error history galaxy share • 316 views
ADD COMMENTlink modified 14 months ago by Jennifer Hillman Jackson25k • written 14 months ago by Carlos Gamboa10
gravatar for Jennifer Hillman Jackson
14 months ago by
United States
Jennifer Hillman Jackson25k wrote:


There was a prior bug where non-ASCII characters in the history name would cause a problem like this. The fix was made over a year ago and applied in Galaxy release 16.01.

First, make sure you are using the latest stable release of Galaxy 17.05.

Once you are using 17.05 stable, and if the problem is still present, try changing the history name to include only ASCII characters to see if that corrects the issue.

If that does not work, please post back the original history name as a comment here and confirm the version of Galaxy in use. We can test and troubleshoot from there.

Thanks! Jen, Galaxy team

ADD COMMENTlink modified 14 months ago • written 14 months ago by Jennifer Hillman Jackson25k
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 183 users visited in the last hour