when I try to do `prisma deploy` I get:
```
ERROR:...
# orm-helpc
captaindaylight
05/14/2019, 10:02 PMwhen I try to do
prisma deploy Copy code
ERROR: GraphQL Error (Code: 503)
{
"error": "<html>\r\n<head><title>503 Service Temporarily Unavailable</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>503 Service Temporarily Unavailable</h1></center>\r\n</body>\r\n</html>\r\n",
"status": 503
}h
Harshit
05/15/2019, 12:52 PM@captaindaylight
Are you trying to deploy to the demo servers? Are you still facing this?
c
captaindaylight
05/15/2019, 1:51 PMnope, I followed this tutorial and set something up on fargate https://www.prisma.io/tutorials/deploy-prisma-to-aws-fargate-ct14
h
Harshit
05/15/2019, 2:06 PMCan you tell me on which step you are getting this error?
Harshit
05/15/2019, 2:07 PMPlease check the server logs in cloudwatch > logs in AWS
c
captaindaylight
05/15/2019, 2:34 PMI’m seeing this:
Copy code
Exception in thread "main" java.sql.SQLTransientConnectionException: database - Connection is not available, request timed out after 5000ms.
14:29:54
at com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:548)
14:29:54
at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:186)
14:29:54
at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:145)
14:29:54
at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:83)
14:29:54
at slick.jdbc.hikaricp.HikariCPJdbcDataSource.createConnection(HikariCPJdbcDataSource.scala:14)
14:29:54
at slick.jdbc.JdbcBackend$BaseSession.<init>(JdbcBackend.scala:453)
14:29:54
at slick.jdbc.JdbcBackend$DatabaseDef.createSession(JdbcBackend.scala:46)
14:29:54
at slick.jdbc.JdbcBackend$DatabaseDef.createSession(JdbcBackend.scala:37)
14:29:54
at slick.basic.BasicBackend$DatabaseDef.acquireSession(BasicBackend.scala:249)
14:29:54
at slick.basic.BasicBackend$DatabaseDef.acquireSession$(BasicBackend.scala:248)
14:29:54
at slick.jdbc.JdbcBackend$DatabaseDef.acquireSession(JdbcBackend.scala:37)
14:29:54
at slick.basic.BasicBackend$DatabaseDef$$anon$2.run(BasicBackend.scala:274)
14:29:54
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
14:29:54
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
14:29:54
at java.lang.Thread.run(Thread.java:748)captaindaylight
05/15/2019, 2:37 PMAlso I guess I’m seeing here an alarm on RDS too,
State changed to ALARM at 2019/05/14. Reason: Threshold Crossed: 2 datapointsh
Harshit
05/15/2019, 2:37 PMThis error implies your database is not not taking connections from prisma
Harshit
05/15/2019, 2:38 PMYou used one of our database templated or it is your own db
Harshit
05/15/2019, 2:38 PMIf yes, I think you have a strict rule for connection limit
c
captaindaylight
05/15/2019, 2:38 PMI used prisma’s database template
captaindaylight
05/15/2019, 2:39 PMfor postgres
h
Harshit
05/15/2019, 2:39 PMHmm
Harshit
05/15/2019, 2:39 PMtry deleting and recreating that stacks
Harshit
05/15/2019, 2:39 PMfrom cloudformation
c
captaindaylight
05/15/2019, 2:40 PMjust RDS or the or the ECS cluster too
h
Harshit
05/15/2019, 2:40 PMBoth
c
captaindaylight
05/15/2019, 2:40 PMk
captaindaylight
05/15/2019, 2:41 PMwill report back in 30 or so
captaindaylight
05/15/2019, 3:22 PMI think the issue is that in the fargate.yml has this hardcoded
Copy code
DbConnector:
Type: String
Default: mysqlcaptaindaylight
05/15/2019, 3:22 PMand I was using postgres
h
Harshit
05/15/2019, 3:23 PMI think it is configurable
Harshit
05/15/2019, 3:23 PMIt should ask for that when you create the template
Harshit
05/15/2019, 3:23 PMmysql is the default, you will need to change that to postgres when you apply the template
c
captaindaylight
05/15/2019, 3:29 PMyup you’re right
captaindaylight
05/15/2019, 6:55 PMthe problem that I’m running into now is that I can’t configure the VPC that I want to run on
captaindaylight
05/15/2019, 6:55 PMnot sure how to configure that with this cloudformation script
3 Views