Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unhandled Promise rejection while yarn start

See original GitHub issue

I just followed every step on the guide for the development environments, and when it gets to the yarn start on graphql folder this is what happen:

root@ubuntu:/home/openctidev/opencti/opencti-platform/opencti-graphql# yarn start

yarn run v1.17.3
$ yarn schema --env=development && yarn migrate --env=development && babel-node -r node_modules/dotenv/config ./src/server.js --e development
$ babel-node ./src/schema/schema-init.js --env=development
🚀 OpenCTI started in development mode with embedded file
(node:7082) UnhandledPromiseRejectionWarning: Error: 14 UNAVAILABLE: TCP Write failed
    at Object.exports.createStatusError (/home/openctidev/opencti/opencti-platform/opencti-graphql/node_modules/grpc/src/common.js:91:15)
    at Object.onReceiveStatus (/home/openctidev/opencti/opencti-platform/opencti-graphql/node_modules/grpc/src/client_interceptors.js:1204:28)
    at InterceptingListener._callNext (/home/openctidev/opencti/opencti-platform/opencti-graphql/node_modules/grpc/src/client_interceptors.js:568:42)
    at InterceptingListener.onReceiveStatus (/home/openctidev/opencti/opencti-platform/opencti-graphql/node_modules/grpc/src/client_interceptors.js:618:8)
    at callback (/home/openctidev/opencti/opencti-platform/opencti-graphql/node_modules/grpc/src/client_interceptors.js:845:24)
(node:7082) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:7082) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:7082) UnhandledPromiseRejectionWarning: ConnectionError: socket hang up
    at onResponse (/home/openctidev/opencti/opencti-platform/opencti-graphql/node_modules/@elastic/elasticsearch/lib/Transport.js:220:13)
    at ClientRequest.request.on.err (/home/openctidev/opencti/opencti-platform/opencti-graphql/node_modules/@elastic/elasticsearch/lib/Connection.js:114:9)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketOnEnd (_http_client.js:423:9)
    at emitNone (events.js:111:20)
    at Socket.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
(node:7082) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)