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

Parity doesn't find any peer to sync for Ropsten testnet #13

Closed
framedio opened this issue Jan 9, 2018 · 16 comments

Comments

Projects
None yet
10 participants
@framedio
Copy link

commented Jan 9, 2018

I'm trying to sync with Ropsten testnet via Parity, but the node doesn't start the sync and Parity doesn't find any peer.
I'm running:

  • Parity version: 1.8.5

  • OS: MacOS High Sierra 10.13

I tried to restart the node and delete the db but it doesn't help. The network on the node is working fine. I tried to connect to Ropsten even in these 2 ways:

  • parity --chain ropsten --bootnodes "enode://20c9ad97c081d63397d7b685a412227a40e23c8bdc6688c6f37e97cfbc22d2b4d1db1510d8f61e6a8866ad7f0e17c02b14182d37ea7c3c8b9c2683aeb6b733a1@52.169.14.227:30303,enode://6ce05930c72abc632c58e2e4324f7c7ea478cec0ed4fa2528982cf34483094e9cbc9216e7aa349691242576d552a2a56aaeae426c5303ded677ce455ba1acd9d@13.84.180.240:30303"

  • parity --chain ropsten --reserved-peers ropstenpeers.txt --reserved-only

but the result was the same: it can not find any nodes to connect.
I write down the log:

2018-01-09 17:32:59 State DB configuration: fast
2018-01-09 17:32:59 Operating mode: active
2018-01-09 17:32:59 Configured for Ropsten using Ethash engine
2018-01-09 17:33:00 Updated conversion rate to Ξ1 = US$1203.06 (98954010 wei/gas)
2018-01-09 17:33:00 Public node URL: enode://febfbe472af11566f613dbe8f6963c559ddd013054e7096473d4a643f13d2d080a10c5fe02016c8762f12fe57a837c5ced8a50fbe5c78139a734d2d6cc8ed24b@192.168.1.9:30303
2018-01-09 17:33:34 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:34:05 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:34:35 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:35:05 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:35:35 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:36:05 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:36:35 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs

Kovan works perfect with Parity instead. What's the problem with Ropsten??

@izetex

This comment has been minimized.

Copy link

commented Jan 9, 2018

For me the same:
/home/studnev/parity/target/release/parity --chain ropsten --bootnodes "enode://20c9ad97c081d63397d7b685a412227a40e23c8bdc6688c6f37e97cfbc22d2b4d1db1510d8f61e6a8866ad7f0e17c02b14182d37ea7c3c8b9c2683aeb6b733a1@52.169.14.227:30303,enode://6ce05930c72abc632c58e2e4324f7c7ea478cec0ed4fa2528982cf34483094e9cbc9216e7aa349691242576d552a2a56aaeae426c5303ded677ce455ba1acd9d@13.84.180.240:30303"
2018-01-09 20:29:33 UTC Starting Parity/v1.7.11-unstable/x86_64-linux-gnu/rustc1.21.0
2018-01-09 20:29:33 UTC Keys path /home/studnev/.local/share/io.parity.ethereum/keys/Ropsten
2018-01-09 20:29:33 UTC DB path /home/studnev/.local/share/io.parity.ethereum/chains/test/db/ae90623718e47d66
2018-01-09 20:29:33 UTC Path to dapps /home/studnev/.local/share/io.parity.ethereum/dapps
2018-01-09 20:29:33 UTC State DB configuration: fast
2018-01-09 20:29:33 UTC Operating mode: active
2018-01-09 20:29:33 UTC Configured for Ropsten using Ethash engine
2018-01-09 20:29:33 UTC Updated conversion rate to Ξ1 = US$1230.08 (96780380 wei/gas)
2018-01-09 20:29:38 UTC Public node URL: enode://d883b2f33e6277da77362672dc37404125bf8a06683e1f8017ce8df2ebfbc55bf24b16b97c927885f04f12cdcc6ebcf6efb1214ed10888b55f9adf4f193c4e9a@172.16.3.3:30303
2018-01-09 20:30:03 UTC 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 20:30:33 UTC 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 20:31:03 UTC 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 20:31:33 UTC 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 20:32:03 UTC 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 20:32:33 UTC 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs

@gpip

This comment has been minimized.

Copy link

commented Jan 14, 2018

It takes some time to find peers after a restart too but it eventually works. You can try adding one of my ropsten nodes as a bootnode: enode://94c15d1b9e2fe7ce56e458b9a3b672ef11894ddedd0c6f247e0f1d3487f52b66208fb4aeb8179fce6e3a749ea93ed147c37976d67af557508d199d9594c35f09@192.81.208.223:30303

@framedio

This comment has been minimized.

Copy link
Author

commented Jan 14, 2018

@gpip I tried to add your node as bootnode and it works!
Thanks!

@Sofoca

This comment has been minimized.

Copy link

commented Jan 15, 2018

@gpip Works, thanks! So apparently something is wrong with the official bootnodes?

@izetex

This comment has been minimized.

Copy link

commented Jan 15, 2018

@gpip - i added your node in the end of official nodes and this did not help

Jan 15 08:52:54 node1 parity[16076]: 2018-01-15 08:52:54 UTC 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC:

for more than 12 hours

@Sofoca

This comment has been minimized.

Copy link

commented Jan 15, 2018

@izetex Try using only the node mentioned by @gpip. That worked for me.

@visa10

This comment has been minimized.

Copy link

commented Jan 23, 2018

@gpip works!
Thanks!

@izetex

This comment has been minimized.

Copy link

commented Jan 23, 2018

@gpip - it works only if ONLY your node is in the list. Thanks

@5chdn

This comment has been minimized.

Copy link
Contributor

commented Feb 1, 2018

Parity Ropsten Bootnode:

enode://6332792c4a00e3e4ee0926ed89e0d27ef985424d97b6a45bf0f23e51f0dcb5e66b875777506458aea7af6f9e4ffb69f43f3778ee73c81ed9d34c51c4b16b0b0f@52.232.243.152:30303

@5chdn 5chdn referenced this issue Feb 1, 2018

Merged

Update Bootnodes #16

@5chdn

This comment has been minimized.

Copy link
Contributor

commented Feb 7, 2018

New EF ropsten bootnodes:

enode://30b7ab30a01c124a6cceca36863ece12c4f5fa68e3ba9b0b51407ccc002eeed3b3102d20a88f1c1d3c3154e2449317b8ef95090e77b312d5cc39354f86d5d606@52.176.7.10:30303
enode://865a63255b3bb68023b6bffd5095118fcc13e79dcf014fe4e47e065c350c7cc72af2e53eff895f11ba1bbb6a2b33271c1116ee870f266618eadfc2e78aa7349c@52.176.100.77:30303

@5chdn 5chdn referenced this issue Feb 7, 2018

Closed

Ropsten Syncing #15

@vieiralc

This comment has been minimized.

Copy link

commented Mar 7, 2018

@gpip how do I add ropsten nodes as a bootnode?

@gabmontes

This comment has been minimized.

Copy link

commented Apr 23, 2018

@vieiralc perhaps the easiest way is to create a text file with each bootnode in a single row and use the --reserver-peers=<filepath> option.

@alextotheroh

This comment has been minimized.

Copy link

commented Aug 7, 2018

@5chdn Is there a central location where working Ropsten bootnodes are maintained? Might be a good way to close the loop on this issue for those stumbling across it on the interwebs like me.

@5chdn

This comment has been minimized.

Copy link
Contributor

commented Aug 18, 2018

This issue is long resolved. Just this repository appears to be unmaintained, see #16

@reiven

This comment has been minimized.

Copy link

commented Aug 18, 2018

Should we clone it and keep it updated?

@5chdn

This comment has been minimized.

Copy link
Contributor

commented Aug 20, 2018

Maybe we can volunteer to maintain it in place? cc @Souptacular

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.