Question: Galaxy-Encodedb Connection Issues
0
gravatar for Prachi Shah
12.4 years ago by
Prachi Shah20
Prachi Shah20 wrote:
Hi Istvan, It seems the connection between galaxy and encodedb is broken again. Nothing has changed at the ENCODEdb end that may have caused this problem. Here is the traceback error we receive: URL: http://main.g2.bx.psu.edu:8085/async/encode_db1 File 'build/bdist.darwin-8.5.1-i386/egg/paste/exceptions/errormiddleware.py ', line 138 in __call__ File 'build/bdist.darwin-8.5.1-i386/egg/paste/lint.py', line 65 in lint_app File '/var/opt/universe/wsgi-postgres- main/eggs/flup-0.5-py2.4.egg/flup/middlewar e/session.py', line 743 in __call__ File 'build/bdist.darwin-8.5.1-i386/egg/paste/recursive.py', line 54 in __call__ File 'build/bdist.darwin-8.5.1-i386/egg/paste/httpexceptions.py', line 619 in __call__ File 'build/bdist.darwin-8.5.1-i386/egg/paste/wsgilib.py', line 112 in catch_errors_app File '/var/opt/universe/wsgi-postgres-main/galaxy/web/framework.py', line 104 in __call__ body = method( trans, **kwargs ) exceptions.TypeError: default() takes at least 3 non-keyword arguments (2 given) As a way for galaxy to identify where the data request is coming from, you had set up a dedicated link to send params to (.../async/encode_db1). Is that still valid? Thanks Prachi
galaxy • 749 views
ADD COMMENTlink written 12.4 years ago by Prachi Shah20
Please log in to add an answer.

Help
Access

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