```ERROR: Whoops. Looks like an internal server er...
# orm-help
h
Copy code
ERROR: Whoops. Looks like an internal server error. Search your server logs for request ID: local:cjwhvghbr000b0849nt6jvtno

{
  "data": {
    "addProject": null
  },
  "errors": [
    {
      "message": "Whoops. Looks like an internal server error. Search your server logs for request ID: local:cjwhvghbr000b0849nt6jvtno",
      "path": [
        "addProject"
      ],
      "locations": [
        {
          "line": 2,
          "column": 9
        }
      ],
      "requestId": "local:cjwhvghbr000b0849nt6jvtno"
    }
  ],
  "status": 200
}
this is after I ran
prisma deploy
h
can you please find that log using
docker-compose logs
h
Copy code
docker logs -f abe003780422
2019-06-04 13:54:00.972 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2019-06-04 13:54:00.976 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2019-06-04 13:54:00.988 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-06-04 13:54:01.021 UTC [22] LOG:  database system was interrupted; last known up at 2019-06-04 13:46:56 UTC
2019-06-04 13:54:01.357 UTC [22] LOG:  database system was not properly shut down; automatic recovery in progress
2019-06-04 13:54:01.362 UTC [22] LOG:  redo starts at 0/175FD80
2019-06-04 13:54:01.362 UTC [22] LOG:  invalid record length at 0/175FE60: wanted 24, got 0
2019-06-04 13:54:01.363 UTC [22] LOG:  redo done at 0/175FE28
2019-06-04 13:54:01.378 UTC [1] LOG:  database system is ready to accept connections
2019-06-04 13:54:07.350 UTC [31] ERROR:  database "prisma" already exists
2019-06-04 13:54:07.350 UTC [31] STATEMENT:  CREATE DATABASE "prisma"
2019-06-04 13:56:37.091 UTC [53] FATAL:  canceling authentication due to timeout
2019-06-04 14:01:56.904 UTC [88] ERROR:  duplicate key value violates unique constraint "Project_pkey"
2019-06-04 14:01:56.904 UTC [88] DETAIL:  Key (id)=(default$default) already exists.
2019-06-04 14:01:56.904 UTC [88] STATEMENT:  insert into "Project" (
	  "id",
	  "secrets",
	  "allowQueries",
	  "allowMutations",
	  "functions"
	)
	values (
	  $1,
	  $2,
	  $3,
	  $4,
	  $5
	)
2019-06-04 14:03:52.659 UTC [100] ERROR:  duplicate key value violates unique constraint "Project_pkey"
2019-06-04 14:03:52.659 UTC [100] DETAIL:  Key (id)=(default$default) already exists.
2019-06-04 14:03:52.659 UTC [100] STATEMENT:  insert into "Project" (
	  "id",
	  "secrets",
	  "allowQueries",
	  "allowMutations",
	  "functions"
	)
	values (
	  $1,
	  $2,
	  $3,
	  $4,
	  $5
	)
2019-06-04 14:04:08.131 UTC [108] ERROR:  duplicate key value violates unique constraint "Project_pkey"
2019-06-04 14:04:08.131 UTC [108] DETAIL:  Key (id)=(default$default) already exists.
2019-06-04 14:04:08.131 UTC [108] STATEMENT:  insert into "Project" (
	  "id",
	  "secrets",
	  "allowQueries",
	  "allowMutations",
	  "functions"
	)
	values (
	  $1,
	  $2,
	  $3,
	  $4,
	  $5
	)
2019-06-04 14:19:47.700 UTC [162] ERROR:  duplicate key value violates unique constraint "Project_pkey"
2019-06-04 14:19:47.700 UTC [162] DETAIL:  Key (id)=(default$default) already exists.
2019-06-04 14:19:47.700 UTC [162] STATEMENT:  insert into "Project" (
	  "id",
	  "secrets",
	  "allowQueries",
	  "allowMutations",
	  "functions"
	)
	values (
	  $1,
	  $2,
	  $3,
	  $4,
	  $5
	)`
I deleted the record in the Management table and rerun the script, I solved the problem.
🙌 1
a
Glad you got it. From my experience with prisma deploy it's almost always a psql or mysql error.