Warp sync keeps failing

[FortHart]

i Tried this #5444

and now im getting stuck at 2,398,406/3,529,305 syncing

Info

Parity//v1.6.5-beta-987390f-20170328/x86_64-windows-msvc/rustc1.16.0
Unknown capability

[FortHart]

LOG

2017-04-14 11:08:40
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 8/10/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 4 req/s, 92 µs

2017-04-14 11:08:50
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/ 9/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 4 req/s, 84 µs

2017-04-14 11:08:55
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 9/11/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 4 req/s, 84 µs

2017-04-14 11:09:00
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 9/10/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 88 µs

2017-04-14 11:09:05
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 6/ 7/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 2 req/s, 81 µs

2017-04-14 11:09:10
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 8/ 9/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 84 µs

2017-04-14 11:09:15
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 9/10/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 2 req/s, 84 µs

2017-04-14 11:09:20
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/ 8/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 84 µs

2017-04-14 11:09:25
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 9/10/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 2 req/s, 87 µs

2017-04-14 11:09:30
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/ 8/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 87 µs

2017-04-14 11:09:35
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/ 8/25 peers 194 MiB db 5 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 4 req/s, 85 µs

2017-04-14 11:09:45
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 9/10/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 80 µs

2017-04-14 11:09:55
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/ 8/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 5 req/s, 84 µs

2017-04-14 11:10:00
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 9/10/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 92 µs

2017-04-14 11:10:05
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 5/ 7/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 4 req/s, 91 µs

2017-04-14 11:10:15
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 9/11/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 93 µs

2017-04-14 11:10:25
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 10/12/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 116 µs

2017-04-14 11:10:35
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 6/ 8/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 2 req/s, 88 µs

2017-04-14 11:10:40
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 8/10/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 71 µs

2017-04-14 11:10:50
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 9/11/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 71 µs

2017-04-14 11:10:55
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/ 9/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 2 req/s, 71 µs

2017-04-14 11:11:05
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 8/10/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 5 req/s, 74 µs

2017-04-14 11:11:15
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 9/12/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 5 req/s, 78 µs

2017-04-14 11:11:20
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/10/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 2 req/s, 77 µs

2017-04-14 11:11:25
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 6/ 9/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 6 req/s, 77 µs

2017-04-14 11:11:30
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/10/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 4 req/s, 75 µs

2017-04-14 11:11:35
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 6/ 9/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 2 req/s, 75 µs

2017-04-14 11:11:40
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 5/ 8/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 4 req/s, 84 µs

2017-04-14 11:11:45
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/10/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 3 req/s, 75 µs

2017-04-14 11:11:55
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 7/10/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 4 req/s, 95 µs

2017-04-14 11:12:00
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 8/11/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 6 req/s, 134 µs

2017-04-14 11:12:10
Syncing #2401050 93d8…7d6c 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #2401050 8/10/25 peers 194 MiB db 6 MiB chain 0 bytes queue 60 MiB sync RPC: 1 conn, 9 req/s, 78 µs

2017-04-14 11:12:15

[tomusdrw]

Are you running on HDD? Those blocks may take realy, realy long to process.

Have you tried syncing with --warp? It should sync to the top of the chain in less than 10 minutes.

[FortHart]

Yes running on HDD, ive tryed that parameter actually that log session is running with the parameter on

The number is stuck on 2,401,050/3,534,757 syncing should i keep waiting ? how long do you think it may take?

[tomusdrw]

Please update to latest version 1.6.6, make sure that your time is exact (go to https://time.is) and try --warp syncing again. I think that wiping the blockchain data may actually help (remove C:\Users\<username>\Application Data\Local\Parity\chains\ethereum\db, cause your computer might be under heavy load while processing those particular blocks and it may inhibit warp sync.

[FortHart]

2017-04-14 23:02:54
Starting Parity/v1.6.6-beta-8c6e3f3-20170411/x86_64-windows-msvc/rustc1.16.0
2017-04-14 23:02:54  State DB configuration: fast
2017-04-14 23:02:54  Operating mode: passive
2017-04-14 23:02:54  Configured for Foundation using Ethash engine
2017-04-14 23:02:55  Updated conversion rate to Ξ1 = US$47.85 (2487933700 wei/gas)
2017-04-14 23:03:00  Public node URL: enode://064a6121544918f0d5f34d7c275d0cdf25dde1d1ef314a5c3b17158c64c66194860a1c0d8f9a2e0775e1716795cb50c423a232fbf06f2e8bfc900858f8591adc@127.0.0.1:30303
2017-04-14 23:03:05  Syncing snapshot 0/119 #0 5/ 8/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-04-14 23:03:10  Syncing snapshot 0/119 #0 5/10/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-04-14 23:03:15  Syncing snapshot 0/119 #0 5/10/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-04-14 23:03:20  Syncing snapshot 0/119 #0 5/12/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-04-14 23:03:25  Syncing snapshot 0/119 #0 5/13/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-04-14 23:03:30  Syncing snapshot 0/119 #0 5/14/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-04-14 23:03:35  Syncing snapshot 0/119 #0 5/15/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-04-14 23:03:40  Syncing snapshot 0/119 #0 5/16/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-04-14 23:03:45  Syncing snapshot 0/119 #0 1/12/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 2 conn, 82 req/s, 78 µs
2017-04-14 23:03:50  Syncing #0 d4e5…8fa3 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #0 3/15/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 1 conn, 17 req/s, 76 µs
2017-04-14 23:03:55  Syncing #0 d4e5…8fa3 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #0 3/16/25 peers 3 MiB db 7 KiB chain 0 bytes queue 10 KiB sync RPC: 1 conn, 8 req/s, 96 µs
2017-04-14 23:04:13  Imported #2 b495…98c9 (0 txs, 0.00 Mgas, 0.44 ms, 0.53 KiB) + another 1 block(s) containing 0 tx(s)
2017-04-14 23:04:14  Imported #255 c631…3ff9 (0 txs, 0.00 Mgas, 0.30 ms, 0.53 KiB) + another 1 block(s) containing 0 tx(s)
2017-04-14 23:04:25  1/14/25 peers 4 MiB db 309 KiB chain 0 bytes queue 486 KiB sync RPC: 1 conn, 7 req/s, 136 µs
2017-04-14 23:04:45  Syncing snapshot 0/119 #255 3/14/25 peers 4 MiB db 309 KiB chain 0 bytes queue 199 KiB sync RPC: 1 conn, 16 req/s, 54 µs
2017-04-14 23:04:55  Syncing snapshot 0/119 #255 1/12/25 peers 4 MiB db 309 KiB chain 0 bytes queue 199 KiB sync RPC: 1 conn, 4 req/s, 54 µs
2017-04-14 23:05:05  Syncing snapshot 0/119 #255 5/13/25 peers 4 MiB db 309 KiB chain 0 bytes queue 199 KiB sync RPC: 1 conn, 4 req/s, 96 µs
2017-04-14 23:05:10  Syncing snapshot 0/119 #255 5/13/25 peers 4 MiB db 309 KiB chain 0 bytes queue 199 KiB sync RPC: 1 conn, 4 req/s, 97 µs
2017-04-14 23:05:15  Syncing snapshot 0/119 #255 5/13/25 peers 4 MiB db 309 KiB chain 0 bytes queue 199 KiB sync RPC: 1 conn, 4 req/s, 79 µs
2017-04-14 23:05:25  Syncing snapshot 0/119 #255 5/14/25 peers 4 MiB db 309 KiB chain 0 bytes queue 199 KiB sync RPC: 1 conn, 4 req/s, 96 µs

Parity//v1.6.6-beta-8c6e3f3-20170411/x86_64-windows-msvc/rustc1.16.0 Unknown capability
0.84% warp restore
Starting fresh doing what you just said , lets see how it goes

[rphmeier]

@FortHart You can also run with --snapshot-peers NUM (replace NUM with 10 or 15 or something) to reserve additional slots for warp sync peers, which should help with warp sync success rate.
Right now the logs indicate it's giving up because of not enough peers.

[FortHart]

It took around 12 hours but im finally syncded, Thanks for the help

[5chdn]

I can reproduce this issue with 1.6.6, warp sync keeps failing even with --snapshot-peers 64.

0 ✓ user@alcor ~/.opt/parity $ ./target/debug/parity 
Loading config file from /home/user/.local/share/io.parity.ethereum/config.toml
2017-04-18 12:01:44  Starting Parity/v1.6.6-unstable-a099f549f-20170321/x86_64-linux-gnu/rustc1.16.0
2017-04-18 12:01:44  State DB configuration: fast
2017-04-18 12:01:44  Operating mode: active
2017-04-18 12:01:44  Configured for Foundation using Ethash engine
2017-04-18 12:01:45  Updated conversion rate to Ξ1 = US$49.96 (2382858500 wei/gas)
2017-04-18 12:01:48  Public node URL: enode://2cc6f8b72a7d86d07f79ec76f2c1b2256492bb2c2acd1fabbfbcdfc4d8c6394c1ae0a75be69d0ab9b06830c72cfb721a844c889ccdcf30df7e51cbd2ef36e3b7@192.168.178.70:30303
2017-04-18 12:01:53  Syncing       #0 d4e5…8fa3     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed        #0    0/ 0/256 peers     3 MiB db    7 KiB chain  0 bytes queue 448 bytes sync  RPC:  0 conn,  0 req/s,   0 µs
2017-04-18 12:01:58  Syncing       #0 d4e5…8fa3     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed        #0    0/ 0/256 peers     3 MiB db    7 KiB chain  0 bytes queue 448 bytes sync  RPC:  0 conn,  0 req/s,   0 µs
2017-04-18 12:02:03  Syncing       #0 d4e5…8fa3     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed        #0    0/ 3/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2017-04-18 12:02:08  Syncing snapshot 0/121        #0    6/15/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2017-04-18 12:02:13  Syncing snapshot 0/121        #0    6/15/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
2017-04-18 12:02:18  Syncing snapshot 0/121        #0    6/15/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  2 conn,  0 req/s,   0 µs
2017-04-18 12:02:26  Syncing snapshot 0/121        #0    6/15/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  2 conn,  4 req/s, 639 µs
2017-04-18 12:02:33  Syncing snapshot 0/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  4 req/s, 457 µs
2017-04-18 12:02:38  Syncing snapshot 1/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  7 req/s, 363 µs
2017-04-18 12:02:43  Syncing snapshot 1/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 322 µs
2017-04-18 12:02:48  Syncing snapshot 1/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  6 req/s, 322 µs
2017-04-18 12:02:53  Syncing snapshot 1/121        #0    4/ 7/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  7 conn,  6 req/s, 494 µs
2017-04-18 12:02:58  Syncing snapshot 1/121        #0    2/ 2/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  7 conn,  6 req/s, 330 µs
2017-04-18 12:03:08  Syncing snapshot 0/121        #2    6/21/256 peers     3 MiB db    7 KiB chain    2 KiB queue   60 KiB sync  RPC:  1 conn,  6 req/s, 209 µs
2017-04-18 12:03:13  Syncing snapshot 0/121        #2    6/21/256 peers     3 MiB db    7 KiB chain    2 KiB queue   60 KiB sync  RPC:  1 conn,  6 req/s, 207 µs
2017-04-18 12:03:18  Syncing snapshot 0/121        #2    6/21/256 peers     3 MiB db    7 KiB chain    2 KiB queue   60 KiB sync  RPC:  1 conn,  6 req/s, 241 µs
2017-04-18 12:03:23  Syncing snapshot 0/121        #2    6/21/256 peers     3 MiB db    8 KiB chain  0 bytes queue   60 KiB sync  RPC:  1 conn,  8 req/s, 347 µs
2017-04-18 12:03:28  Syncing snapshot 0/121        #2    5/20/256 peers     3 MiB db    8 KiB chain  0 bytes queue   60 KiB sync  RPC:  1 conn,  9 req/s, 381 µs
2017-04-18 12:03:33  Syncing snapshot 0/121        #2    5/19/256 peers     3 MiB db    8 KiB chain  0 bytes queue   60 KiB sync  RPC:  1 conn,  5 req/s, 375 µs
2017-04-18 12:03:38  Syncing snapshot 1/121        #2    5/19/256 peers     3 MiB db    8 KiB chain  0 bytes queue   60 KiB sync  RPC:  1 conn,  6 req/s, 303 µs
2017-04-18 12:03:43  Syncing snapshot 1/121        #2    5/19/256 peers     3 MiB db    8 KiB chain  0 bytes queue   60 KiB sync  RPC:  1 conn,  5 req/s, 234 µs
2017-04-18 12:03:48  Syncing snapshot 1/121        #2    5/19/256 peers     3 MiB db    8 KiB chain  0 bytes queue   60 KiB sync  RPC:  1 conn,  5 req/s, 222 µs
2017-04-18 12:03:53  Syncing snapshot 1/121        #2    2/ 6/256 peers     3 MiB db    8 KiB chain  0 bytes queue   60 KiB sync  RPC:  1 conn,  5 req/s, 222 µs
2017-04-18 12:04:03  Syncing       #2 b495…98c9     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed        #2    1/ 5/256 peers     3 MiB db    8 KiB chain  0 bytes queue  348 KiB sync  RPC:  1 conn,  4 req/s, 298 µs
2017-04-18 12:04:28  Syncing      #96 3505…1f80     3 blk/s    0 tx/s   0 Mgas/s     25+    0 Qed      #127    6/23/256 peers     4 MiB db   92 KiB chain   55 KiB queue  440 KiB sync  RPC:  1 conn,  7 req/s, 658 µs


2017-04-18 12:04:29  Imported #127 707c…91ed (0 txs, 0.00 Mgas, 9.25 ms, 0.53 KiB) + another 2 block(s) containing 0 tx(s)
^C2017-04-18 12:04:31  Finishing work, please wait...
0 ✓ user@alcor ~/.opt/parity $ ./target/debug/parity db kill
Loading config file from /home/user/.local/share/io.parity.ethereum/config.toml
2017-04-18 12:04:43  Database deleted.
0 ✓ user@alcor ~/.opt/parity $ ./target/debug/parity --snapshot-peers 64
Loading config file from /home/user/.local/share/io.parity.ethereum/config.toml
2017-04-18 12:05:01  Starting Parity/v1.6.6-unstable-a099f549f-20170321/x86_64-linux-gnu/rustc1.16.0
2017-04-18 12:05:01  State DB configuration: fast
2017-04-18 12:05:01  Operating mode: active
2017-04-18 12:05:01  Configured for Foundation using Ethash engine
2017-04-18 12:05:01  Updated conversion rate to Ξ1 = US$50.03 (2379524600 wei/gas)
2017-04-18 12:05:04  Public node URL: enode://2cc6f8b72a7d86d07f79ec76f2c1b2256492bb2c2acd1fabbfbcdfc4d8c6394c1ae0a75be69d0ab9b06830c72cfb721a844c889ccdcf30df7e51cbd2ef36e3b7@192.168.178.70:30303
2017-04-18 12:05:14  Syncing       #0 d4e5…8fa3     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed        #0    0/ 0/256 peers     3 MiB db    7 KiB chain  0 bytes queue 448 bytes sync  RPC:  1 conn,  4 req/s, 152 µs
2017-04-18 12:05:19  Syncing       #0 d4e5…8fa3     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed        #0    0/ 4/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 201 µs
2017-04-18 12:05:24  Syncing snapshot 0/121        #0    6/17/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 249 µs
2017-04-18 12:05:29  Syncing snapshot 0/121        #0    6/19/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 323 µs
2017-04-18 12:05:34  Syncing snapshot 0/121        #0    6/19/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  2 req/s, 323 µs
2017-04-18 12:05:39  Syncing snapshot 0/121        #0    6/19/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  2 req/s, 221 µs
2017-04-18 12:05:44  Syncing snapshot 0/121        #0    6/18/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 215 µs
2017-04-18 12:05:49  Syncing snapshot 0/121        #0    6/18/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 270 µs
2017-04-18 12:05:54  Syncing snapshot 1/121        #0    6/18/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 296 µs
2017-04-18 12:05:59  Syncing snapshot 1/121        #0    6/18/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 296 µs
2017-04-18 12:06:04  Syncing snapshot 1/121        #0    6/18/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 214 µs
2017-04-18 12:06:20  Syncing snapshot 2/121        #0    6/18/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  7 req/s, 210 µs
2017-04-18 12:06:20  Syncing snapshot 2/121        #0    6/18/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  7 req/s, 210 µs
2017-04-18 12:06:20  Syncing snapshot 2/121        #0    6/18/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  7 req/s, 210 µs
2017-04-18 12:06:29  Syncing snapshot 2/121        #0    5/17/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  2 req/s, 210 µs
2017-04-18 12:06:34  Syncing snapshot 2/121        #0    3/15/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 219 µs
2017-04-18 12:06:39  Syncing snapshot 3/121        #0    3/15/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  2 req/s, 219 µs
2017-04-18 12:06:44  Syncing snapshot 3/121        #0    3/15/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 243 µs
2017-04-18 12:06:49  Syncing snapshot 3/121        #0    3/15/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  3 req/s, 214 µs
2017-04-18 12:06:54  Syncing snapshot 3/121        #0    2/12/256 peers     3 MiB db    7 KiB chain  0 bytes queue   10 KiB sync  RPC:  1 conn,  4 req/s, 210 µs
2017-04-18 12:07:09  Syncing       #0 d4e5…8fa3     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed        #0    2/ 3/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  3 req/s, 286 µs
2017-04-18 12:07:14  Syncing snapshot 0/121        #0    6/16/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  3 req/s, 400 µs
2017-04-18 12:07:19  Syncing snapshot 0/121        #0    6/17/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  1 req/s, 400 µs
2017-04-18 12:07:29  Syncing snapshot 0/121        #0    6/17/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  2 req/s, 256 µs
2017-04-18 12:07:34  Syncing snapshot 0/121        #0    6/17/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  5 req/s, 191 µs
2017-04-18 12:07:39  Syncing snapshot 1/121        #0    6/17/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  3 req/s, 191 µs
2017-04-18 12:07:44  Syncing snapshot 1/121        #0    6/17/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  3 req/s, 162 µs
2017-04-18 12:07:49  Syncing snapshot 1/121        #0    6/16/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  3 req/s, 179 µs
2017-04-18 12:07:54  Syncing snapshot 2/121        #0    6/16/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  6 req/s, 196 µs
2017-04-18 12:07:59  Syncing snapshot 2/121        #0    6/16/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  5 req/s, 228 µs
2017-04-18 12:08:04  Syncing snapshot 2/121        #0    6/16/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  2 req/s, 193 µs
2017-04-18 12:08:19  Syncing       #0 d4e5…8fa3     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed        #0    4/11/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  4 req/s, 237 µs
2017-04-18 12:08:24  Syncing snapshot 0/121        #0    6/13/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  5 req/s, 252 µs
2017-04-18 12:08:29  Syncing snapshot 0/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  4 req/s, 252 µs
2017-04-18 12:08:57  Syncing snapshot 0/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  1 req/s, 205 µs
2017-04-18 12:08:57  Syncing snapshot 0/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  1 req/s, 205 µs
2017-04-18 12:08:57  Syncing snapshot 0/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  1 req/s, 205 µs
2017-04-18 12:08:57  Syncing snapshot 0/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  1 req/s, 205 µs
2017-04-18 12:09:04  Syncing snapshot 0/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  5 req/s, 261 µs
2017-04-18 12:09:09  Syncing snapshot 1/121        #0    6/14/256 peers     3 MiB db    7 KiB chain  0 bytes queue   18 KiB sync  RPC:  1 conn,  3 req/s, 338 µs

[5chdn]

2017-04-18 12:11:56  Encountered error during state restoration: Snapshot restoration aborted.

[5chdn]

Was due to slow debug build. release works.

[Corto77]

Hello
I'am new here and i try to run Parity 1.6.6 (installed from the binary release) on a raspberry pi 3
I launched parity with this arguments
$ parity --pruning fast --mode passive --warp -l info --log-file ~/Parity/parity.log &
after several hours the process aborted with this error
' terminate called after throwing an instance of "std::bad_alloc" '
So I restarted Parity adding the argument --pruning-history 64 as recommended here #4694
but after around 5 minutes I got this error
' Encountered error during state restoration : Snapshot restoration aborted '
this error always occurs after a log ./. Syncing snapshot 24/121 ./.

ps : sorry for my mistakes but I am not very fluent in english

[winsvega]

same here

[5chdn]

@Corto77 @winsvega if you want use snapshot synchronization on low-memory devices, you should consider adding sufficient swap. please let me know if this works.