Skip to content
This repository has been archived by the owner on Jul 7, 2022. It is now read-only.

benchmark run issue #169

Open
s083r opened this issue Nov 1, 2021 · 0 comments
Open

benchmark run issue #169

s083r opened this issue Nov 1, 2021 · 0 comments

Comments

@s083r
Copy link

s083r commented Nov 1, 2021

during start via:

node . benchmark -c config/benchmark.finality.local.sample.json 

got the following error:

Initializing nodes...
upgrade --install polkadot-node-0 -f ../deployments/bm1/values/node-0.yaml --version v0.34.1 --namespace bm1 w3f/polkadot
upgrade --install polkadot-node-1 -f ../deployments/bm1/values/node-1.yaml --version v0.34.1 --namespace bm1 w3f/polkadot
Done
Waiting for nodes ready...

*************************************************************
 Websockets endpoint available at ws://127.0.0.1:11003 
*************************************************************
Done
***************************************
 Starting benchmarks with 2 nodes
***************************************
2021-11-01 10:00:44          API-WS: disconnected from ws://127.0.0.1:11003: 1006:: connection failed
2021-11-01 10:00:44          API-WS: disconnected from ws://127.0.0.1:9944: 1006:: connection failed
(node:1521240) UnhandledPromiseRejectionWarning: #<_Event>
(Use `node --trace-warnings ...` to show where the warning was created)
(node:1521240) 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)
(node:1521240) [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.
2021-11-01 10:00:47          API-WS: disconnected from ws://127.0.0.1:9944: 1006:: connection failed
2021-11-01 10:00:49          API-WS: disconnected from ws://127.0.0.1:9944: 1006:: connection failed
2021-11-01 10:00:52          API-WS: disconnected from ws://127.0.0.1:9944: 1006:: connection failed
^C

It gets stuck, netstat -tulpn shows nothing about 9944.
WAIDW?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant