elastic / elastic/observability-examples
movide data loader fails at start
- Dominant language
- JavaScript
- Stars
- 42
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
```
2024-05-17 06:57:44 (node:1) UnhandledPromiseRejectionWarning: ConnectionError: connect ECONNREFUSED 172.19.0.3:9200
2024-05-17 06:57:44 at ClientRequest.onError (/app/node_modules/@elastic/elasticsearch/lib/Connection.js:123:16)
2024-05-17 06:57:44 at ClientRequest.emit (events.js:400:28)
2024-05-17 06:57:44 at TLSSocket.socketErrorListener (_http_client.js:475:9)
2024-05-17 06:57:44 at TLSSocket.emit (events.js:400:28)
2024-05-17 06:57:44 at emitErrorNT (internal/streams/destroy.js:106:8)
2024-05-17 06:57:44 at emitErrorCloseNT (internal/streams/destroy.js:74:3)
2024-05-17 06:57:44 at processTicksAndRejections (internal/process/task_queues.js:82:21)
2024-05-17 06:57:44 (Use `node --trace-warnings ...` to show where the warning was created)
2024-05-17 06:57:44 (node:1) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
2024-05-17 06:57:44 (node:1) [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.
2024-05-17 06:57:44 starting movie indexing
```
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.