You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.
Describe the bug
I have set up the Rosetta node using docker command : docker run -d --rm --ulimit "nofile=100000:100000" -v "$(pwd)/klaytn-data:/data" -e "MODE=ONLINE" -e "NETWORK=MAINNET" -e "PORT=8080" -p 8080:8080 -p 30303:30303 rosetta-klaytn:v1.0.5
But the node is not syncing and its stuck at below logs:
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [34] UDP listener up self="kni://1e2ad43bbdaa21ca30a88c7371d254c53b28ed9971c516e205055845f0fb614c0055b4c6d99388a8f5cb76cbea59d1dd902fbd3712709febaedddbc15aac9ae3@[::]:32323?ntype=en"
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [40] Started P2P server id=1e2ad43bbdaa21ca multichannel=false
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [40] RLPx listener up self="kni://1e2ad43bbdaa21ca30a88c7371d254c53b28ed9971c516e205055845f0fb614c0055b4c6d99388a8f5cb76cbea59d1dd902fbd3712709febaedddbc15aac9ae3@[::]:32323?ntype=en"
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [44] Start listening chain head event to update stakingInfoCache.
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [40] IPC endpoint opened url=/data/klay.ipc
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [40] HTTP endpoint opened url=http://127.0.0.1:8551 cors= vhosts=localhost
2023/11/01 11:48:35 ken err INFO[11/01,11:48:35 Z] [34] Removed the node without any response Discover=Simple StorageName=PN NodeID=63f1c96874da8514 NodeType=BN
2023/11/01 11:48:36 ken err INFO[11/01,11:48:36 Z] [34] Removed the node without any response Discover=Simple StorageName=BN NodeID=63f1c96874da8514 NodeType=BN
To Reproduce
Try setting up the node with the command: docker run -d --rm --ulimit "nofile=100000:100000" -v "$(pwd)/klaytn-data:/data" -e "MODE=ONLINE" -e "NETWORK=MAINNET" -e "PORT=8080" -p 8080:8080 -p 30303:30303 rosetta-klaytn:v1.0.5
Expected behavior
Node should be syncing
The text was updated successfully, but these errors were encountered:
Describe the bug
I have set up the Rosetta node using docker command : docker run -d --rm --ulimit "nofile=100000:100000" -v "$(pwd)/klaytn-data:/data" -e "MODE=ONLINE" -e "NETWORK=MAINNET" -e "PORT=8080" -p 8080:8080 -p 30303:30303 rosetta-klaytn:v1.0.5
But the node is not syncing and its stuck at below logs:
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [34] UDP listener up self="kni://1e2ad43bbdaa21ca30a88c7371d254c53b28ed9971c516e205055845f0fb614c0055b4c6d99388a8f5cb76cbea59d1dd902fbd3712709febaedddbc15aac9ae3@[::]:32323?ntype=en"
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [40] Started P2P server id=1e2ad43bbdaa21ca multichannel=false
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [40] RLPx listener up self="kni://1e2ad43bbdaa21ca30a88c7371d254c53b28ed9971c516e205055845f0fb614c0055b4c6d99388a8f5cb76cbea59d1dd902fbd3712709febaedddbc15aac9ae3@[::]:32323?ntype=en"
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [44] Start listening chain head event to update stakingInfoCache.
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [40] IPC endpoint opened url=/data/klay.ipc
2023/11/01 11:48:32 ken err INFO[11/01,11:48:32 Z] [40] HTTP endpoint opened url=http://127.0.0.1:8551 cors= vhosts=localhost
2023/11/01 11:48:35 ken err INFO[11/01,11:48:35 Z] [34] Removed the node without any response Discover=Simple StorageName=PN NodeID=63f1c96874da8514 NodeType=BN
2023/11/01 11:48:36 ken err INFO[11/01,11:48:36 Z] [34] Removed the node without any response Discover=Simple StorageName=BN NodeID=63f1c96874da8514 NodeType=BN
To Reproduce
Try setting up the node with the command: docker run -d --rm --ulimit "nofile=100000:100000" -v "$(pwd)/klaytn-data:/data" -e "MODE=ONLINE" -e "NETWORK=MAINNET" -e "PORT=8080" -p 8080:8080 -p 30303:30303 rosetta-klaytn:v1.0.5
Expected behavior
Node should be syncing
The text was updated successfully, but these errors were encountered: