hedera-local-node
hedera-local-node copied to clipboard
Published
20 hours ago •
hashgraph
hashgraph
Smoke test when testing again relay node deployed by solo
Description
I was able to run smoke test pass when running again local launched hedera-local-node, but could not get smoke test run when running again relay deployed by solo
Solo is using hedera-json-rpc-relay chart version 0.47.0 https://github.com/hashgraph/hedera-json-rpc-relay/tree/main/charts/hedera-json-rpc-relay
Steps to reproduce
These are steps to launch hedera network locally with solo
./test/e2e/setup-e2e.sh
solo node keys --gossip-keys --tls-keys --key-format pfx
solo node setup
solo node start
solo mirror-node deploy
solo relay deploy
kubectl port-forward svc/relay-node0-node1-node2-hedera-json-rpc-relay -n solo-e2e 7546:7546 &
kubectl port-forward svc/haproxy-node0-svc -n solo-e2e 50211:50211 &
kubectl port-forward svc/fullstack-deployment-hedera-explorer -n solo-e2e 8080:80 &
From terminal output as well as K9s I can tell the network /hedera nodes are running, mirror node are running
******************************* Solo *********************************************
Version : 0.24.0
Kubernetes Context : kind-solo-e2e
Kubernetes Cluster : kind-solo-e2e
Kubernetes Namespace : solo-e2e
**********************************************************************************
✔ Initialize [0.1s]
✔ Enable mirror-node [6s]
✔ Prepare address book [0.4s]
✔ Deploy mirror-node [5s]
✔ Check pods are ready [1m10s]
✔ Check Postgres DB [14s]
✔ Check REST API [40s]
✔ Check GRPC [52s]
✔ Check Monitor [1m10s]
✔ Check Importer [1m10s]
✔ Check Hedera Explorer [10s]
******************************* Solo *********************************************
Version : 0.24.0
Kubernetes Context : kind-solo-e2e
Kubernetes Cluster : kind-solo-e2e
Kubernetes Namespace : solo-e2e
**********************************************************************************
✔ Initialize [0.3s]
✔ Prepare chart values
✔ Deploy JSON RPC Relay [17s]
✔ Check relay is ready [26s]
When launched smoke test now, I got this output
Smoke Tests
Relay
1) Should perform a crypto transfer transaction
Websocket server
2) "before all" hook for "Should receive events for subscribed contract"
0 passing (3s)
2 failing
1) Smoke Tests
Relay
Should perform a crypto transfer transaction:
ProviderError: [Request ID: 95f6bc18-0a17-40e0-818c-5b2fb33315c3] Error invoking RPC: queryA and queryAaaa ENODATA fullstack-deployment-rest
at HttpProvider.request (/Users/jeffrey/hedera-local-node/test/smoke/node_modules/hardhat/src/internal/core/providers/http.ts:90:21)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at HardhatEthersProvider.getBalance (/Users/jeffrey/hedera-local-node/test/smoke/node_modules/@nomicfoundation/hardhat-ethers/src/internal/hardhat-ethers-provider.ts:171:21)
at Context.<anonymous> (/Users/jeffrey/hedera-local-node/test/smoke/test/Smoke.js:17:39)
2) Smoke Tests
Websocket server
"before all" hook for "Should receive events for subscribed contract":
ProviderError: [Request ID: fd9de4af-46a1-43da-a47a-df4696f138ed] Unknown error invoking RPC
at HttpProvider.request (/Users/jeffrey/hedera-local-node/test/smoke/node_modules/hardhat/src/internal/core/providers/http.ts:90:21)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at HardhatEthersProvider.getBlockNumber (/Users/jeffrey/hedera-local-node/test/smoke/node_modules/@nomicfoundation/hardhat-ethers/src/internal/hardhat-ethers-provider.ts:134:25)
at HardhatEthersSigner.sendTransaction (/Users/jeffrey/hedera-local-node/test/smoke/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:122:25)
at ContractFactory.deploy (/Users/jeffrey/hedera-local-node/test/smoke/node_modules/ethers/src.ts/contract/factory.ts:111:24)
at Context.<anonymous> (/Users/jeffrey/hedera-local-node/test/smoke/test/Smoke.js:39:16)
And in addition, here is log from relay
[2024-05-08 14:42:21.592 +0000] INFO (rpc-server/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [GET]: /health/readiness 200 0 ms │
│ [2024-05-08 14:42:31.594 +0000] TRACE (relay-eth/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): undefined chainId() │
│ [2024-05-08 14:42:31.594 +0000] INFO (rpc-server/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [GET]: /health/readiness 200 0 ms │
│ [2024-05-08 14:42:31.594 +0000] INFO (rpc-server/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [GET]: /health/liveness 200 0 ms │
│ [2024-05-08 14:42:41.593 +0000] INFO (rpc-server/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [GET]: /health/liveness 200 0 ms │
│ [2024-05-08 14:42:41.593 +0000] TRACE (relay-eth/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): undefined chainId() │
│ [2024-05-08 14:42:41.593 +0000] INFO (rpc-server/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [GET]: /health/readiness 200 0 ms │
│ [2024-05-08 14:42:49.340 +0000] TRACE (relay-eth/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [Request ID: cec16d1c-bbb0-43b2-89db-c4f557f83fa1] chainId() │
│ [2024-05-08 14:42:49.342 +0000] INFO (rpc-server/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [Request ID: cec16d1c-bbb0-43b2-89db-c4f557f83fa1] [POST]: eth_chainId 200 24 ms │
│ [2024-05-08 14:42:49.359 +0000] TRACE (relay-eth/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [Request ID: 86b8ba6d-d7fe-4216-8ef7-377a42280f48] getBalance(account=0xbF8F135840EaE2a4A3710b8F66c │
│ [2024-05-08 14:42:49.486 +0000] TRACE (mirror-node/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): Retry delay 250 ms on 'undefined' │
│ [2024-05-08 14:42:49.738 +0000] TRACE (mirror-node/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): Retry delay 500 ms on 'undefined' │
│ [2024-05-08 14:42:50.240 +0000] TRACE (mirror-node/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): Retry delay 750 ms on 'undefined' │
│ [2024-05-08 14:42:50.994 +0000] ERROR (mirror-node/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [Request ID: 86b8ba6d-d7fe-4216-8ef7-377a42280f48] [GET] accounts/0xbF8F135840EaE2a4A3710b8F66c98 │
│ err: { │
│ "type": "Error", │
│ "message": "queryA and queryAaaa ENODATA fullstack-deployment-rest", │
│ "stack": │
│ Error: queryA and queryAaaa ENODATA fullstack-deployment-rest │
│ at MirrorNodeClient.handleError (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:235:31) │
│ at MirrorNodeClient.<anonymous> (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:206:22) │
│ at Generator.throw (<anonymous>) │
│ at rejected (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:25:65) │
│ at process.processTicksAndRejections (node:internal/process/task_queues:95:5) │
│ } │
│ [2024-05-08 14:42:50.994 +0000] ERROR (relay-eth/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [Request ID: 86b8ba6d-d7fe-4216-8ef7-377a42280f48] Error raised during getBalance for account 0xbF8 │
│ err: { │
│ "type": "MirrorNodeClientError", │
│ "message": "queryA and queryAaaa ENODATA fullstack-deployment-rest", │
│ "stack": │
│ Error: queryA and queryAaaa ENODATA fullstack-deployment-rest │
│ at MirrorNodeClient.handleError (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:224:29) │
│ at MirrorNodeClient.<anonymous> (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:206:22) │
│ at Generator.throw (<anonymous>) │
│ at rejected (/home/node/app/packages/relay/dist/lib/clients/mirrorNodeClient.js:25:65) │
│ at process.processTicksAndRejections (node:internal/process/task_queues:95:5) │
│ "statusCode": 567 │
│ } │
│ [2024-05-08 14:42:50.994 +0000] ERROR (rpc-server/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [Request ID: 86b8ba6d-d7fe-4216-8ef7-377a42280f48] Error invoking RPC: queryA and queryAaaa ENODAT │
│ [2024-05-08 14:42:50.994 +0000] INFO (rpc-server/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [Request ID: 86b8ba6d-d7fe-4216-8ef7-377a42280f48] [POST]: eth_getBalance 500 1636 ms │
│ [2024-05-08 14:42:51.009 +0000] TRACE (relay-eth/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): [Request ID: 30396f04-d099-4e4c-9f7a-bad581aa1817] blockNumber() │
│ [2024-05-08 14:42:51.011 +0000] TRACE (mirror-node/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): Retry delay 250 ms on 'undefined' │
│ [2024-05-08 14:42:51.263 +0000] TRACE (mirror-node/63 on relay-node0-node1-node2-hedera-json-rpc-relay-6c9c4768d9-tbv96): Retry delay 500 ms on 'undefined'
Log from mirror node REST
│ (node:1) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time. │
│ (Use `node --trace-warnings ...` to show where the warning was created) │
│ 2024-05-08T17:51:48.763Z INFO Startup Loaded configuration source: /home/node/app/config/application.yml │
│ 2024-05-08T17:51:48.767Z INFO Startup Loaded configuration source: /usr/etc/hedera/application.yaml │
│ 2024-05-08T17:51:48.769Z INFO Startup Override config with environment variable HEDERA_MIRROR_REST_DB_USERNAME=mirror_rest │
│ 2024-05-08T17:51:48.769Z INFO Startup Override config with environment variable HEDERA_MIRROR_REST_DB_HOST=fullstack-deployment-postgres-postgresql │
│ 2024-05-08T17:51:48.769Z INFO Startup Override config with environment variable HEDERA_MIRROR_REST_DB_PASSWORD=****** │
│ 2024-05-08T17:51:48.769Z INFO Startup Override config with environment variable HEDERA_MIRROR_REST_DB_NAME=mirror_node │
│ bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?) │
│ 2024-05-08T17:51:50.254Z INFO Startup Response compression is enabled │
│ 2024-05-08T17:51:50.259Z INFO Startup stateproof REST API is disabled │
│ 2024-05-08T17:51:50.261Z INFO Startup Server running on port: 5551
Additional context
No response
Hedera network
other
Version
latest
Operating system
macOS
Another question I have is that after started hedera-local-node, mirror node log was flooded with following messages:
2024-05-08 15:33:34 2024-05-08T20:33:34.821Z INFO 7d400abf ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200403-213000000 in 2 ms: 200
2024-05-08 15:33:34 2024-05-08T20:33:34.833Z INFO dc435999 ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200403-113000000 in 2 ms: 200
2024-05-08 15:33:34 2024-05-08T20:33:34.871Z WARN daa708fb ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200404-613000000 in 2 ms: 404 Not found NotFoundError Not found
2024-05-08 15:33:34 2024-05-08T20:33:34.884Z WARN fcd6b5e9 ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200404-113000000 in 1 ms: 404 Not found NotFoundError Not found
2024-05-08 15:33:34 2024-05-08T20:33:34.916Z INFO 109ee28e ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200403-513000000 in 2 ms: 200
2024-05-08 15:33:34 2024-05-08T20:33:34.925Z INFO e8d65c2e ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200403-13000000 in 2 ms: 200
2024-05-08 15:33:34 2024-05-08T20:33:34.971Z WARN 5932c37b ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200404-713000000 in 1 ms: 404 Not found NotFoundError Not found
2024-05-08 15:33:35 2024-05-08T20:33:35.071Z WARN f6bf32b4 ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200404-813000000 in 1 ms: 404 Not found NotFoundError Not found
2024-05-08 15:33:35 2024-05-08T20:33:35.074Z INFO 289d8414 ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200403-413000000 in 2 ms: 200
2024-05-08 15:33:35 2024-05-08T20:33:35.140Z WARN 34067086 ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200404-213000000 in 2 ms: 404 Not found NotFoundError Not found
2024-05-08 15:33:35 2024-05-08T20:33:35.171Z WARN 36635584 ::ffff:172.20.0.9 GET /api/v1/transactions/0.0.2-1715200404-913000000 in 2 ms: 404
Who sent out such requests and how to disable it, since some useful information maybe buried by such flood of request.