Parity-ethereum: How to determine Sync progress?

Created on 17 May 2018  ·  6Comments  ·  Source: openethereum/parity-ethereum

What is " 0+13281 Qed #2438294" in the log mean?

M2-config 📂 Z1-question 🙋‍♀️

All 6 comments

you mean: https://wiki.parity.io/FAQ-CLI,-Mining,-and-Networks.html#what-does-paritys-command-line-output-mean ? :dango:

both of those links have some wrong information: the number which is shown isn't the number downloaded but the number processed.

@rphmeier then let's make it right: https://github.com/paritytech/wiki/pull/110

My logs today:

2018-05-25 13:55:27 UTC Imported #5674662 0x423b…5bb2 (148 txs, 7.97 Mgas, 3081.36 ms, 22.78 KiB)
2018-05-25 13:56:34 UTC Imported #5674665 0x07e9…b339 (121 txs, 7.73 Mgas, 1264.24 ms, 23.62 KiB)
2018-05-25 13:57:39 UTC Imported #5674670 0x0933…dcfe (122 txs, 8.00 Mgas, 3100.51 ms, 27.04 KiB)
2018-05-25 13:58:25 UTC Imported #5674671 0xca9c…5747 (87 txs, 8.00 Mgas, 1064.10 ms, 14.79 KiB)
2018-05-25 13:59:33 UTC Imported #5674676 0x8711…3e60 (95 txs, 4.37 Mgas, 1052.82 ms, 19.08 KiB)
2018-05-25 14:00:23 UTC Imported #5674677 0xa398…200f (153 txs, 7.94 Mgas, 1798.74 ms, 26.67 KiB)
2018-05-25 14:02:17 UTC Imported #5674685 0xd3df…2a5d (214 txs, 7.98 Mgas, 2126.31 ms, 34.73 KiB)
2018-05-25 14:03:10 UTC Imported #5674691 0x7638…f8af (136 txs, 7.98 Mgas, 2511.87 ms, 18.69 KiB)
2018-05-25 14:03:29 UTC         #1    1/25 peers   7 MiB chain 118 MiB db 0 bytes queue 731 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-05-25 14:03:30 UTC         #1    1/25 peers   6 MiB chain 118 MiB db 0 bytes queue 731 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-05-25 14:04:22 UTC         #1    2/25 peers   6 MiB chain 119 MiB db 0 bytes queue 732 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-05-25 14:04:38 UTC Imported #5674698 0x2dca…6452 (138 txs, 8.00 Mgas, 2780.92 ms, 27.63 KiB)
2018-05-25 14:04:57 UTC         #1    2/25 peers   6 MiB chain 119 MiB db 0 bytes queue 732 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-05-25 14:06:11 UTC Imported #5674704 0x0431…eece (137 txs, 8.00 Mgas, 1887.78 ms, 36.45 KiB)
2018-05-25 14:06:12 UTC         #1    3/25 peers   6 MiB chain 120 MiB db 0 bytes queue 732 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-05-25 14:06:12 UTC         #1    3/25 peers   6 MiB chain 120 MiB db 0 bytes queue 732 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2018-05-25 14:06:12 UTC         #1    3/25 peers   6 MiB chain 120 MiB db 0 bytes queue 732 MiB sync  RPC:  0 conn,  0

what does the #1 mean?

This is when your node is downloading and verifying older blocks (in your case, the block #1) after a warp sync. I will add a comment about this in the doc.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

stone212 picture stone212  ·  3Comments

danfinlay picture danfinlay  ·  3Comments

jurijbajzelj picture jurijbajzelj  ·  3Comments

jordipainan picture jordipainan  ·  3Comments

retotrinkler picture retotrinkler  ·  3Comments