Hi, I’ve tried upgrading my Prisma instance from v...
# orm-helpk
k0ff33
03/01/2019, 11:42 AMHi, I’ve tried upgrading my Prisma instance from v1.25 to v.1.27 hosted on Heroku and ended up probably breaking stuff. New `prisma deploy`s result in
ERROR: GraphQL Error (Code: 503)k0ff33
03/01/2019, 11:44 AMI’ve followed the steps from https://github.com/prisma/prisma-cloud-feedback/issues/202#issuecomment-414095090 when upgrading the Heroku instance.
k0ff33
03/01/2019, 11:45 AMFull error message:
Copy code
ERROR: GraphQL Error (Code: 503)
{
"error": "<!DOCTYPE html>\n\t<html>\n\t <head>\n\t\t<meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n\t\t<meta charset=\"utf-8\">\n\t\t<title>Application Error</title>\n\t\t<style media=\"screen\">\n\t\t html,body,iframe {\n\t\t\tmargin: 0;\n\t\t\tpadding: 0;\n\t\t }\n\t\t html,body {\n\t\t\theight: 100%;\n\t\t\toverflow: hidden;\n\t\t }\n\t\t iframe {\n\t\t\twidth: 100%;\n\t\t\theight: 100%;\n\t\t\tborder: 0;\n\t\t }\n\t\t</style>\n\t </head>\n\t <body>\n\t\t<iframe src=\"//www.herokucdn.com/error-pages/application-error.html\"></iframe>\n\t </body>\n\t</html>",
"status": 503
}d
dpetrick
03/01/2019, 11:48 AMThis is not a descriptive error. You need to check the dyno logs for prisma errors.
k
k0ff33
03/01/2019, 11:53 AMI thought so but there are no error logs, just standard connection ones
k0ff33
03/01/2019, 11:55 AMOr actually…
k0ff33
03/01/2019, 11:55 AM Copy code
2019-03-01T11:54:19.348650+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=POST path="/management" host=<http://awdis-prisma.herokuapp.com|awdis-prisma.herokuapp.com> request_id=96d815c5-5260-4c76-aec9-5ae1425880e4 fwd="77.96.237.217" dyno=web.1 connect=0ms service=30001ms status=503 bytes=0 protocol=httpsk0ff33
03/01/2019, 11:56 AMH12 errors are when requests take more than 30 seconds to complete: https://devcenter.heroku.com/articles/error-codes#h12-request-timeout
k0ff33
03/01/2019, 11:58 AMI’ve tried downgrading to v1.25 and all works fine
k0ff33
03/01/2019, 12:02 PMLet’s see if that is the case with other versions…
k0ff33
03/01/2019, 12:06 PMIf it possible that:
22c83ce: The request timeout for the Prisma Servers has been bumped to 600 seconds to enable running long queries.causes the issue? I believe that Heroku terminates requests after 30 seconds.
k0ff33
03/01/2019, 12:12 PMYup, might be that change, v1.26.5 works perfectly. Gonna fill a github issue
d
dpetrick
03/01/2019, 12:29 PMThanks for reporting!
k
k0ff33
03/01/2019, 12:36 PMHere’s a link to the issue: https://github.com/prisma/prisma/issues/4115
h
Harshit
03/01/2019, 3:20 PM@dpetrick
Can we make this change only in the prisma-heroku image?
Otherwise this might break some other workflows.
d
dpetrick
03/01/2019, 3:21 PMNo.
a
Ahmad
05/20/2020, 6:36 AMsurprisingly 1.26.5 version isn't avaible at all. moved to 1.26.6
Ahmad
05/20/2020, 6:36 AMhopefully it works
Ahmad
05/20/2020, 8:29 AMDidn't work for me
3 Views