These are chat archives for getredash/redash

Jan 2016
Takahiro Mitsumori
Jan 15 2016 05:23

I had an error. It seems like a query statement had a problem?
How I find the which query from an error log?

[2016-01-15 14:15:54,375: ERROR/MainProcess] Task redash.tasks.execute_query[9aed6265-ed66-4b59-8fd1-f7b2b5e72e3d] raised unexpected: Exception('{\n "error": {\n "errors": [\n {\n "domain": "global",\n "reason": "invalidQuery",\n "message": "Encountered \" \"}\" \"} \"\" at line 22, column 11.\nWas expecting:\n \u003cEOF\u003e \n ",\n "locationType": "other",\n "location": "query"\n }\n ],\n "code": 400,\n "message": "Encountered \" \"}\" \"} \"\" at line 22, column 11.\nWas expecting:\n \u003cEOF\u003e \n "\n }\n}\n',)
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/celery/app/", line 240, in trace_task
R = retval = fun(args, **kwargs)
File "/opt/di.redash/redash/", line 33, in call
return super(BaseTask, self).call(
args, kwargs)
File "/usr/local/lib/python2.7/dist-packages/celery/app/", line 437, in protected_call
File "/opt/di.redash/redash/", line 329, in execute_query
raise Exception(error)
Exception: {
"error": {
"errors": [
"domain": "global",
"reason": "invalidQuery",
"message": "Encountered \" \"}\" \"} \"\" at line 22, column 11.\nWas expecting:\n \u003cEOF\u003e \n ",
"locationType": "other",
"location": "query"
"code": 400,
"message": "Encountered \" \"}\" \"} \"\" at line 22, column 11.\nWas expecting:\n \u003cEOF\u003e \n "

Arik Fraimovich
Jan 15 2016 12:29
@amitkuagrawal from your description, it doesn't sound like it's running. the query runner doesn't use the cache, it just executes the query. the cached is used by the UI only, when there is no recent result. Is it only one query that isn't running or all of them?
@amitkuagrawal also, when you run the query again (click on "execute") the result you get in the end is from a query execution, and not cache. if you try to run it with execute what do you see happen? can you share logs with me (privately)?
@TMit do you see a line that begins with "Executing query:" before the error message?