Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heima collator not finding peers #3262

Open
nfekunprdtiunnkge opened this issue Feb 19, 2025 · 7 comments
Open

Heima collator not finding peers #3262

nfekunprdtiunnkge opened this issue Feb 19, 2025 · 7 comments

Comments

@nfekunprdtiunnkge
Copy link

nfekunprdtiunnkge commented Feb 19, 2025

Hey, after recent restart of our node (using latest version) it cannot find parachain peers anymore. Can you please provide some bootnodes we can use? Thanks

@wangminqi
Copy link
Member

wangminqi commented Feb 20, 2025

Hi, can you provide more info like node running screenshoot/log?
And you may use this tool to check locally if our current bootnodes are available to your machine.
https://github.com/lexnv/subp2p-explorer

@nfekunprdtiunnkge
Copy link
Author

I just tried with fresh install and no luck as well.
Running it with command
./collator --chain=litentry --base-path=/data/collator --state-pruning=archive --rpc-cors=all --rpc-external --rpc-port=9933 --node-key-file=/data/secret_ed25519_parachain -- --chain=polkadot --node-key-file=/data/secret_ed25519_relaychain --sync=Fast

Image

@wangminqi
Copy link
Member

wangminqi commented Feb 20, 2025

Can you share a screenshoot of running command of discover-network in subp2p-explorer on the machine where you run the node?

Guidance here: https://github.com/lexnv/subp2p-explorer?tab=readme-ov-file#discover-network

@nfekunprdtiunnkge
Copy link
Author

nfekunprdtiunnkge commented Feb 20, 2025

Command seems to be stuck
Running `target/debug/subp2p-explorer-cli discover-network --genesis 2fc8bb6ed7c0051bdcf4866c322ed32b6276572713607e3297ccf411b8f14aa9 --timeout 15

Image

@wangminqi
Copy link
Member

wangminqi commented Feb 20, 2025

Just for confirmation. On this same internet environment, you used to have a node connecting to Peer successfully, but find 0 peer after a restart?

@nfekunprdtiunnkge
Copy link
Author

Correct, it was working fine before the restart.
Running verify-bootnodes getting

Image

@wangminqi
Copy link
Member

I just checked on my local machine. I get the same result.
Checking. We will look into it.

Seems weird since not ours, dwellir also gives this error.

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

No branches or pull requests

2 participants