Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Ropsten bootnodes use wrong fork #8845

Closed
melnikaite opened this issue Jun 8, 2018 · 4 comments
Closed

Ropsten bootnodes use wrong fork #8845

melnikaite opened this issue Jun 8, 2018 · 4 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P5-sometimesoon 🌲 Issue is worth doing soon.
Milestone

Comments

@melnikaite
Copy link

I'm running:

  • Which Parity version?: 1.10.6
  • Which operating system?: Linux
  • How installed?: docker
  • Are you fully synchronized?: no
  • Which network are you connected to?: ropsten
  • Did you try to restart the node?: yes

actual
Running with option --warp-barrier 3000000
Last block is 3380734

expected behavior
Block number should grow every minute

steps to reproduce
Stop parity
Remove database folder
Run parity
Wait to be synced

@Tbaut Tbaut added the F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. label Jun 11, 2018
@Tbaut
Copy link
Contributor

Tbaut commented Jun 11, 2018

Parity Bootnode is on the right side of the fork (can be checked here: https://ropsten-stats.parity.io/) but it seems that you were not able to warp sync with it. Checking why now.

To make sure to warp-sync on the right one, you can specify our bootnode enode in a reserved-peer-file and force your node only to connect to this one with : parity --no-ancient-blocks --chain ropsten --reserved-peers reserved-peer-file --reserved-only.

Using the bootnode: enode://6332792c4a00e3e4ee0926ed89e0d27ef985424d97b6a45bf0f23e51f0dcb5e66b875777506458aea7af6f9e4ffb69f43f3778ee73c81ed9d34c51c4b16b0b0f@52.232.243.152:30303

An alternative is to sync with --no-warp. This is of course more time consuming but it'll bring you on the right fork.

@Tbaut Tbaut closed this as completed Jun 11, 2018
@Tbaut Tbaut added the P5-sometimesoon 🌲 Issue is worth doing soon. label Jun 11, 2018
@Tbaut Tbaut added this to the 1.12 milestone Jun 11, 2018
@melnikaite
Copy link
Author

I tried to drop db and sync again and today it was successful. I guess it was related the recent consensus issue. Probably it make sense to add some mechanism to avoid synchronization with old clients. Also in this situation I could edit network.json and leave only geth nodes and latest parity nodes.

@usmananwar
Copy link

usmananwar commented Jun 15, 2018

Hi,
is it related with this issue: (Ropsten synchronization hangs at: 3383693, doesn't work even after restart)

2018-06-15 17:00:18     6/50 peers     63 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  55 µs
2018-06-15 17:00:28  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    7/50 peers     64 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  55 µs
2018-06-15 17:00:39  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    9/50 peers     65 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  55 µs
2018-06-15 17:01:13     7/50 peers     68 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  55 µs
2018-06-15 17:01:29  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    9/50 peers     70 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  4 req/s,  55 µs
2018-06-15 17:02:03     7/50 peers     72 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  55 µs
2018-06-15 17:02:13  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    8/50 peers     73 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  55 µs
2018-06-15 17:02:48     7/50 peers     75 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  55 µs
2018-06-15 17:03:23     8/50 peers     76 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  4 req/s,  59 µs
2018-06-15 17:03:58     7/50 peers     80 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:04:28     8/50 peers     81 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:05:03     6/50 peers     81 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:05:13  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    7/50 peers     81 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:05:23  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    7/50 peers     81 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:05:28  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    7/50 peers     81 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:05:33  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    7/50 peers     81 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:06:03     6/50 peers     81 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:06:38     6/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:07:13     6/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:07:48     6/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:08:18     6/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:08:48  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    8/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:08:53  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    8/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:09:23     7/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:09:58     7/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  59 µs
2018-06-15 17:10:13  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    8/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  3 req/s,  56 µs
2018-06-15 17:10:43     7/50 peers     84 MiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,  56 µs
2018-06-15 17:11:15  Starting Parity/v1.11.3-beta-a66e36b-20180605/x86_64-linux-gnu/rustc1.26.1
2018-06-15 17:11:15  Keys path /applications/parity/ropsten/keys/Ropsten
2018-06-15 17:11:15  DB path /applications/parity/ropsten/node/chains/test/db/ae90623718e47d66
2018-06-15 17:11:15  Path to dapps /applications/parity/ropsten/node/dapps
2018-06-15 17:11:15  State DB configuration: fast +Trace
2018-06-15 17:11:15  Operating mode: active
2018-06-15 17:11:15  Warning: Warp Sync is disabled because tracing is turned on.
2018-06-15 17:11:15  Configured for Ropsten using Ethash engine
2018-06-15 17:11:16  Removed existing file '/applications/parity/ropsten/node/jsonrpc.ipc'.
2018-06-15 17:11:21  Public node URL: enode://225abdc36703eb63b711ee79f64ce6c5775b17212459ff3c3e8e91a84a8973ae12c4b306102a5b514bc8d98dd83a7a2744a90af07d6a20624ed53a68375dff25@10.0.104.193:30300
2018-06-15 17:11:26  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3383662    5/50 peers    241 KiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-06-15 17:11:46  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    5/50 peers    346 KiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s, 349 µs
2018-06-15 17:12:11  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    4/50 peers    364 KiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s, 349 µs
2018-06-15 17:12:31  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    4/50 peers    364 KiB chain   65 MiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,  2 req/s,  70 µs
2018-06-15 17:13:01     3/50 peers    364 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  70 µs
2018-06-15 17:13:36     3/50 peers    364 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:14:07     4/50 peers    364 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:14:41     3/50 peers    509 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:15:11     3/50 peers    509 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:15:46     4/50 peers    509 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:16:16     3/50 peers    509 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:16:51     3/50 peers    626 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:17:21     3/50 peers    626 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:17:56     4/50 peers    626 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:18:01  Syncing #3383693 0xf4c9…88e4     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed  #3381646    4/50 peers    626 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:18:31     4/50 peers    626 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:19:01     4/50 peers    626 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs
2018-06-15 17:19:36     4/50 peers    626 KiB chain   65 MiB db  0 bytes queue   11 KiB sync  RPC:  0 conn,  0 req/s,  61 µs```

@Tbaut
Copy link
Contributor

Tbaut commented Jun 15, 2018

@usmananwar to sync the right chain, please do the following:

  • Make sure you run parity v1.11.3 or 1.10.6 or later.
  • run echo "enode://6332792c4a00e3e4ee0926ed89e0d27ef985424d97b6a45bf0f23e51f0dcb5e66b875777506458aea7af6f9e4ffb69f43f3778ee73c81ed9d34c51c4b16b0b0f@52.232.243.152:30303" > ./ropsten-parity-bootnode to create a file with parity bootnode.
  • parity --chain ropsten db kill to erase your current chain.
  • parity --chain ropsten --reserved-peers ropsten-parity-bootnode --reserved-only to warp sync with our bootnode only.
  • you can then let it run like this or run parity --chain ropsten --no-warp to continue the sync with any peer while making sure you do not warp-sync on the wrong fork.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P5-sometimesoon 🌲 Issue is worth doing soon.
Projects
None yet
Development

No branches or pull requests

3 participants