Choose the region of demo server hangs


#1

hello I am new to prisma and it seems that the prisma init hangs - no error msg - when “choose the region of demo server” is presented.

Any suggestions?


#2

I too am new to Prisma and am having this same issue when running prisma init - I can choose an option on the "Set up a new Prisma server or deploy to an existing server? " and no matter what option I choose it will take me to the next screen as expected, but then it hangs - I can’t choose any options or exit - I just have to force quit the terminal. Have tried with iTerm, VS-code terminal and the default mac terminal and all of them hang at the same spot.


#3

I have same problem.
How can I fix this??%E1%84%80%E1%85%B3%E1%84%85%E1%85%AE%E1%86%B8%201

My prisma version

  • Prisma CLI version: prisma/1.34.0 (darwin-x64) node-v11.8.0

and I tried node-v10.8.x but same problem happed.


#4

I am also having same problem. May be prisma server is having issue with init


#5

I have the same problem with prisma init.
I am using prisma on Mint Linux 18.3. I have installed Prisma CLI version: prisma/1.34.0 (linux-x64) node-v8.16.0.
It always hangs on the second step.
I hope I am not hijacking the thread.


#6

I’m on Mac OS 10.14.5 and I’ve experienced the same issue when trying to create a demo server. I tried using iTerm and Terminal to no avail.


#7

Same issue for me, hoping to get this resolved.


#8

It hangs even if I want to connect to existing database


#9

I uninstalled prisma and used prisma@1.24 instead of current 1.34 and it is working


#10

Worked for me as well. Thanks !


#11

I used my Ubuntu 18.04 system and I was able to get around the issue.


#12

Awesome, this worked for me too, thank you!


#13

We were busy organising GraphQLConf last week so I am extremely sorry for the late response.

In am unfortunately unable to reproduce this issue. I tried several times as many people are reporting the same issue.

Can anyone of you please share a exact steps to reproduce this, along with system specification :pray:


#14

Hi.
I am running Mint Linux 18.3.
I installed docker (Docker version 18.09.6, build 481bc77) for Ubuntu 16.04 and prisma (Prisma CLI version: prisma/1.34.0 (linux-x64) node-v8.16.0).
This is the output I had after running export DEBUG="*" and prisma init prisma

  command Failed to get the definition file +0ms
  command Error: Couldn’t find `prisma.yml` file. Are you in the right directory? +1ms
  init prisma init workflow called without existing directory. +0ms
  init Error: ENOENT: no such file or directory, scandir '/home/patz/prisma/' +1ms
  Environment FetchError: request to https://api.cloud.prisma.sh/ failed, reason: getaddrinfo EAI_AGAIN api.cloud.prisma.sh
  Environment     at ClientRequest.<anonymous> (/home/patz/.npm-global/lib/node_modules/prisma/node_modules/node-fetch/lib/index.js:1393:11)
  Environment     at ClientRequest.emit (events.js:200:13)
  Environment     at ClientRequest.EventEmitter.emit (domain.js:471:20)
  Environment     at TLSSocket.socketErrorListener (_http_client.js:402:9)
  Environment     at TLSSocket.emit (events.js:200:13)
  Environment     at TLSSocket.EventEmitter.emit (domain.js:471:20)
  Environment     at emitErrorNT (internal/streams/destroy.js:91:8)
  Environment     at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
  Environment     at processTicksAndRejections (internal/process/task_queues.js:84:9) +0ms
  environment FetchError: request to http://localhost:4466/management failed, reason: connect ECONNREFUSED 127.0.0.1:4466
  environment     at ClientRequest.<anonymous> (/home/patz/.npm-global/lib/node_modules/prisma/node_modules/node-fetch/lib/index.js:1393:11)
  environment     at ClientRequest.emit (events.js:200:13)
  environment     at ClientRequest.EventEmitter.emit (domain.js:471:20)
  environment     at Socket.socketErrorListener (_http_client.js:402:9)
  environment     at Socket.emit (events.js:200:13)
  environment     at Socket.EventEmitter.emit (domain.js:471:20)
  environment     at emitErrorNT (internal/streams/destroy.js:91:8)
  environment     at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
  environment     at processTicksAndRejections (internal/process/task_queues.js:84:9) +0ms
  environment FetchError: request to http://localhost:4466/management failed, reason: connect ECONNREFUSED 127.0.0.1:4466
  environment     at ClientRequest.<anonymous> (/home/patz/.npm-global/lib/node_modules/prisma/node_modules/node-fetch/lib/index.js:1393:11)
  environment     at ClientRequest.emit (events.js:200:13)
  environment     at ClientRequest.EventEmitter.emit (domain.js:471:20)
  environment     at Socket.socketErrorListener (_http_client.js:402:9)
  environment     at Socket.emit (events.js:200:13)
  environment     at Socket.EventEmitter.emit (domain.js:471:20)
  environment     at emitErrorNT (internal/streams/destroy.js:91:8)
  environment     at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
  environment     at processTicksAndRejections (internal/process/task_queues.js:84:9) +1ms
  client Sending query to cloud api +0ms
  client https://api2.cloud.prisma.sh +0ms
  client {
  client       me {
  client         id
  client         name
  client         login {
  client           email
  client         }
  client       }
  client     } +0ms
  client undefined +0ms
  client {
  client   headers: {
  client     Authorization: 'Bearer ' +
  client       'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiJjang0bHo1MmM1Nml4MDg2MWg5MzJuZXpqIiwiaWF0IjoxNTYxMDMxNzIzLCJleHAiOj1234568jM2MjM3MjN9.feqo00000PyAPCaoxLROwveW9-dOIeZJC0GVlATx63s'
  client   },
  client   agent: undefined
  client } +1ms
  endpoint-dialog EndpointDialog workflow called without existing directory. +39ms
  endpoint-dialog Error: ENOENT: no such file or directory, scandir '/home/patz/prisma/' +0ms
? Set up a new Prisma server or deploy to an existing server? Use existing datab
ase
? What kind of database do you want to deploy to? (Use arrow keys)
❯ MySQL             MySQL compliant databases like MySQL or MariaDB 
  PostgreSQL        PostgreSQL database 
  MongoDB           Mongo Database 

That’s where the terminal just froze. Couldn’t use the arrows or anything.

I also tried to create a hello-world project from prisma cli quick start guide. A browser window opened, I registered at prisma, and again the terminal window froze at some point before finishing. I rerun prisma init, I chose to set up a demo server and this as far as I got this time:

 ? Set up a new Prisma server or deploy to an existing server? Demo server + MySQ
 L database
 client Sending query to cloud api +15s
 client https://api2.cloud.prisma.sh +0ms
 client {
 client me {
 client id
 client name
 client login {
 client email
 client }
 client }
 client } +0ms
 client undefined +1ms
 client { headers:
 client { Authorization: 'Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiJjang0bHo1MmM1Nml4MDg2MWg5MzJuZXqpiIwiaWF0IjoxNTYxMDMxNzIzLCJleSD0OjE1NjM2MjM3MjN9.feqojVu96PyAPC222LROwveW9-dOIeZJC0GVlATx63s' },
 client agent: undefined } +0ms
 ? Choose the region of your demo server (Use arrow keys)
 ❯ zacharias/demo-eu1 Hosted on AWS in eu-west-1 using MySQL [1061ms
 latency]
 zacharias/demo-us1 Hosted on AWS in us-west-2 using MySQL [1026ms
 latency]

The terminal froze again.

Hope I 've helped.


#15

Still unable to reproduce. From the stack trace it seems it is a network error.

So I need to ask you for your location(you can direct message me on the forum if you prefer).


#17

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.