I will admit I don't understand how the mapper problem is related or why it would occur in monitor_step or custom builds, but I do know there is an important bug fix in release 15.05 from Dannon (https://github.com/galaxyproject/galaxy/pull/198) that multiple people have reported fixing the problem with mapper initialization. It might be worth upgrading or applying the diffs manually to your instance. -John On Wed, May 13, 2015 at 1:48 PM, Shrum, Donald C <DCShrum@admin.fsu.edu> wrote:
Hi all,
I have a public galaxy server here at FSU that is running behind an apache proxy and on our cluster file system so that jobs can be submitted to our hpc cluster.
I have a user that receives an ‘Internal Server Error’ when going to ‘Custom Builds’ This error seems to only occur for the one user and from what I can see it may be the case that there is a single mapper is causing the problem. (Sys-admin here, not a bioinformatics person :)
The errors I pulled from the logs are below. Is it possible there is some mapper causing the problem? If so is there a way I can remove it?
Any help would be appreciated and thanks,
Don Shrum
FSU Research Computing Center
InvalidRequestError: One or more mappers failed to initialize - can't proceed with initialization of other mappers. Original exception was: Class 'kombu.transport.sqlalchemy.Message' is not mapped
galaxy.jobs.handler ERROR 2015-05-13 13:44:25,150 Exception in monitor_step
WSGI Variables
--------------
application: <paste.recursive.RecursiveMiddleware object at 0x8691650>
is_api_request: False
original_wsgi.url_scheme: 'http'
paste.cookies: (<SimpleCookie: __utma='51326654.2116930099.1431360039.1431360039.1431360039.1' __utmz='51326654.1431360039.1.1.utmcsr=directory.fsu.edu|utmccn=(referral)|utmcmd=referral|utmcct=/' _ga='GA1.2.2116930099.1431360039' galaxysession='c6ca0ddb55be603abe1a0bf853fb54302d17fe1509e1ff998221f8b85399eb4a8bcf9d852c6fb740'>, '__utma=51326654.2116930099.1431360039.1431360039.1431360039.1; __utmz=51326654.1431360039.1.1.utmcsr=directory.fsu.edu|utmccn=(referral)|utmcmd=referral|utmcct=/; _ga=GA1.2.2116930099.1431360039; galaxysession=c6ca0ddb55be603abe1a0bf853fb54302d17fe1509e1ff998221f8b85399eb4a8bcf9d852c6fb740')
paste.expected_exceptions: [<class 'paste.httpexceptions.HTTPException'>]
paste.httpexceptions: <paste.httpexceptions.HTTPExceptionHandler object at 0x867ff10>
paste.httpserver.thread_pool: <paste.httpserver.ThreadPool object at 0x8a21f50>
paste.recursive.forward: <paste.recursive.Forwarder from />
paste.recursive.include: <paste.recursive.Includer from />
paste.recursive.include_app_iter: <paste.recursive.IncluderAppIter from />
paste.recursive.script_name: ''
paste.throw_errors: True
request_id: '57170782f99611e4af7a00219ba29ca2'
webob._parsed_query_vars: (MultiDict([]), '')
wsgi process: 'Multithreaded'
___________________________________________________________ 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/