Getting errors on dashboard #6128
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
|
Hopefully you have command line access to the server this is happening on? If you do, then (in theory) you should be able to extract the error message info from the backend logs. The exact process for doing that though can vary. Any idea how your Redash was installed? eg Docker containers vs something else (etc) 😄 |
Beta Was this translation helpful? Give feedback.
-
|
This kind of error is generally caused by a timeout or an error encountered during SQL operation that has not been handled friendly. You can post your log, and the community will help solve it |
Beta Was this translation helpful? Give feedback.
-
|
It seems that redash did not display the sql error return in the error message due to nginx timeout, and uniformly returned a service error problem. |
Beta Was this translation helpful? Give feedback.

Ahhh. I'm not personally familiar with the Amazon AMI version of Redash, so might not be super helpful here.
If it's something that uses Docker for running the Redash pieces though, then we might be ok.
With a Docker based approach, most of the time Redash gets installed into the
/opt/redashdirectory.So, you could change into that directory then run
docker-compose logs > somefile.txtto capture the logs to a file you can do stuff with.For example, you can then search that file for the string "error" with a timestamp of about when it happened. The file should contain the error messages for whatever happened on the back end. 😄
If the Amazon AMI doesn't use a docker based approach though.…