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

Ancient blocks are not downloaded #8908

Closed
Jeiwan opened this issue Jun 15, 2018 · 5 comments
Closed

Ancient blocks are not downloaded #8908

Jeiwan opened this issue Jun 15, 2018 · 5 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust.
Milestone

Comments

@Jeiwan
Copy link

Jeiwan commented Jun 15, 2018

I'm running:

  • Which Parity version?: Parity/v1.11.3-beta-a66e36b-20180605/x86_64-linux-gnu/rustc1.26.1
  • Which operating system?: Ubuntu 18.04 and this docker image: https://hub.docker.com/parity/parity
  • How installed?: via installer
  • Are you fully synchronized?: yes
  • Which network are you connected to?: ethereum
  • Did you try to restart the node?: yes

After downloading all the snapshots and waiting for more than 24 hours:

$ geth attach http://localhost:8545
> eth.getBlock('latest')
{...number: 5793554...}
> eth.getBlock(eth.getBlock('latest').number - 31337)
null
> eth.getBlock(100)
null
> eth.getBlock(5000000)
nul
> eth.syncing
{
  currentBlock: 5793573,
  highestBlock: 5793573,
  startingBlock: 5790638,
  warpChunksAmount: null,
  warpChunksProcessed: null
}

The chain folder doesn't grow and stays at 22Gb:

$ du -sh /var/lib/docker/volumes/parity-chain/
22G	/var/lib/docker/volumes/parity-chain/

Also, there are errors (total 47) in the log:

2018-06-15 07:47:54 UTC Error importing ancient block: 0x4034…d034
2018-06-15 07:47:54 UTC Error importing ancient block: 0x16f4…da0e
2018-06-15 07:47:54 UTC Error importing ancient block: 0x99dd…de13
2018-06-15 07:47:54 UTC Error importing ancient block: 0xd19b…9f7b
2018-06-15 07:47:54 UTC Error importing ancient block: 0xa374…9d13

I tried removing the data folder and resyncing 3 times, the last one was using Docker.
I start the container with:

docker run -d -it -v parity-chain:/root/.local/share/io.parity.ethereum/ -p 8545:8545 parity/parity:v1.11.3 --allow-ips=public --no-ui --no-ws --no-ipc --no-dapps --jsonrpc-interface all --base-path /root/.local/share/io.parity.ethereum/

Before trying the Docker image, I ran the node with:

/usr/bin/parity --allow-ips=public --no-ui --no-ws --no-ipc --no-dapps
@Jeiwan
Copy link
Author

Jeiwan commented Jun 16, 2018

12 hours passed. It still takes 22Gb of disk space, and there's no sign of ancient blocks.

@Jeiwan
Copy link
Author

Jeiwan commented Jun 17, 2018

2 days passed. There are still no ancient blocks, the folder takes 23Gb.

@alexcos20
Copy link

Confimed on ropsten also:

Which Parity version?: Parity/v1.11.3-beta-a66e36b-20180605/x86_64-linux-gnu/rustc1.26.1
Which operating system?: Ubuntu 16.04
How installed?: via https://d1h4xl4cr1h0mo.cloudfront.net/v1.11.3/x86_64-unknown-linux-gnu/parity_1.11.3_ubuntu_amd64.deb
Are you fully synchronized?: yes
Which network are you connected to?: ropsten
Did you try to restart the node?: yes
Did you try to delete database and restart ?: yes
Runing like: screen -dmS parity-ropsten /usr/bin/parity --chain ropsten -d=/raid10/coins/parity-ropsten/basedata/ --rpcapi eth,net,web3,personal,parity,parity_set --ipc-apis eth,net,web3,personal,parity --log-file /var/log/parity-ropsten.log --jsonrpc-interface=192.168.244.144

Happens on two machines (almost same hw config, same os , same parity binary.)

2018-06-17 13:17:50 Error importing ancient block: 0x9055…cc57
2018-06-17 13:17:50 Error importing ancient block: 0xa2ff…ad47
2018-06-17 13:17:50 Error importing ancient block: 0x43cb…11e9
2018-06-17 13:17:50 Error importing ancient block: 0x8333…e596
2018-06-17 13:17:50 Error importing ancient block: 0xeb1d…19b3
2018-06-17 13:17:50 Error importing ancient block: 0x8abc…bed1
2018-06-17 13:17:50 Error importing ancient block: 0x5bcb…b8bf
2018-06-17 13:17:50 Error importing ancient block: 0x9640…34b0
2018-06-17 13:17:50 Error importing ancient block: 0xe236…e926
2018-06-17 13:17:50 Error importing ancient block: 0x7587…bf6b
2018-06-17 13:17:50 Error importing ancient block: 0xfc02…79de
2018-06-17 13:17:50 Error importing ancient block: 0x9529…97ec
2018-06-17 13:17:50 Error importing ancient block: 0xeb78…0700
2018-06-17 13:17:50 Error importing ancient block: 0x2a72…5e19
2018-06-17 13:17:50 Error importing ancient block: 0xdf9c…6455
2018-06-17 13:17:50 Error importing ancient block: 0xdc8a…273c
2018-06-17 13:17:50 Error importing ancient block: 0x4156…80e5
2018-06-17 13:17:50 Error importing ancient block: 0x594e…7ca9
2018-06-17 13:17:50 Error importing ancient block: 0xeaa9…2a1e
2018-06-17 13:17:50 Error importing ancient block: 0x5088…c9d8
2018-06-17 13:17:50 Error importing ancient block: 0xc675…3d1b
2018-06-17 13:17:50 Error importing ancient block: 0x9332…e596
2018-06-17 13:17:50 Error importing ancient block: 0xfde8…53b0
2018-06-17 13:17:50 Error importing ancient block: 0x6ac8…3bbc
2018-06-17 13:17:50 Error importing ancient block: 0x2840…8051
2018-06-17 13:17:50 Error importing ancient block: 0x5584…ec36
2018-06-17 13:17:50 Error importing ancient block: 0x7146…b23d
2018-06-17 13:17:50 Error importing ancient block: 0xcc6f…16ad
2018-06-17 13:17:50 Error importing ancient block: 0x0d9a…8824
2018-06-17 13:17:50 Error importing ancient block: 0x7a22…11b3
2018-06-17 13:17:50 Error importing ancient block: 0x7e42…c988
2018-06-17 13:17:50 Error importing ancient block: 0xdda7…04fe
2018-06-17 13:17:50 Error importing ancient block: 0x4198…93b4
2018-06-17 13:17:50 Error importing ancient block: 0xa31f…4acf
2018-06-17 13:17:50 Error importing ancient block: 0xb0f6…4ba6

@Tbaut
Copy link
Contributor

Tbaut commented Jun 18, 2018

There is a bug fixed in #8832 that makes this message get fired actually every time a block is downloaded. It'll be included in the next release.

@Tbaut Tbaut closed this as completed Jun 18, 2018
@Tbaut Tbaut added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. labels Jun 18, 2018
@Tbaut Tbaut added this to the 1.12 milestone Jun 18, 2018
@Jeiwan
Copy link
Author

Jeiwan commented Jun 19, 2018

Anyway, I ran it with --no-warp and it's fine now.

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. M4-core ⛓ Core client code / Rust.
Projects
None yet
Development

No branches or pull requests

3 participants