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

--light client stuck at #2088992 #8148

Closed
drandreaskrueger opened this issue Mar 18, 2018 · 9 comments
Closed

--light client stuck at #2088992 #8148

drandreaskrueger opened this issue Mar 18, 2018 · 9 comments
Labels
M2-config 📂 Chain specifications and node configurations. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.

Comments

@drandreaskrueger
Copy link

I'm running:

parity --light ui
2018-03-18 22:39:56 UTC Starting Parity/v1.9.4-beta-6f21a32b2-20180228/x86_64-linux-gnu/rustc1.23.0

on Debian Linux ; installed from latest github release. Mainnet. Yes, tried restarting.


--light client is stuck at #2088992

see bottom half of issue 8145 comment #8145 (comment)

@drandreaskrueger
Copy link
Author

drandreaskrueger commented Mar 20, 2018

solution was: Wait 2 days, then try again.

2018-03-20 09:38:19 UTC Syncing #2089248 22bd…ac3c    51 hdr/s      0+    0 Qed  #2089248   15/50 peers   167 KiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-03-20 09:38:24 UTC Syncing #2090784 af66…9fa0   307 hdr/s      0+    0 Qed  #2090784   18/50 peers   1 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-03-20 09:38:29 UTC Syncing #2092553 4ad5…9c16   353 hdr/s  29970+    0 Qed  #2092553   24/50 peers   2 MiB cache 25 MiB queue  RPC:  0 conn,  0 req/s,   0 µs
2018-03-20 09:38:34 UTC Syncing #2097251 456c…d81b   939 hdr/s  29882+    0 Qed  #2097251   25/50 peers   5 MiB cache 25 MiB queue  RPC:  0 conn,  0 req/s,   0 µs

what are possible reasons for the light client to get stuck for hours?

what can I do in such a situation?

what could you do to make it less likely?

thanks.

@Tbaut
Copy link
Contributor

Tbaut commented Mar 20, 2018

In such cases, restarting the light client would help.
This issue will be worked around with #8075

@Tbaut Tbaut closed this as completed Mar 20, 2018
@drandreaskrueger
Copy link
Author

drandreaskrueger commented Mar 20, 2018

Oh, misunderstanding. Of course I had restarted parity, and several times:

Yes, tried restarting.

You see that in my log cited over there in the other issue, look at the ... and the datetimes.

But restarting did not help.

What did help was waiting 2 days, and now trying again.
Synced now, thanks a lot.

@5chdn 5chdn added Z1-question 🙋‍♀️ Issue is a question. Closer should answer. M2-config 📂 Chain specifications and node configurations. labels Mar 23, 2018
@5chdn 5chdn added this to the 1.11 milestone Mar 23, 2018
@drandreaskrueger
Copy link
Author

I have given up on that.

Instead I have now helped myself to a bootstrap file

For now, I keep a cloud machine running, so that I can always zip & download a synced chain. Download time is 3 hours - but that is better than never ever getting it synced again.

@Tbaut
Copy link
Contributor

Tbaut commented Apr 24, 2018

As stated before, Parity v1.11 should solve this problem.

@drandreaskrueger
Copy link
Author

when stable?

@Tbaut
Copy link
Contributor

Tbaut commented Apr 24, 2018

Will go live next week as beta (light mode is experimental for 1.9 and 1.10 too).

@drandreaskrueger
Copy link
Author

drandreaskrueger commented Apr 24, 2018

Great. Looking forward to light being stable, and incl. token balances & transfers.

Until that dream becomes reality *g* --> https://gist.github.com/drandreaskrueger/88cf4e27c69272e68d44076aaf9a8844

@drandreaskrueger
Copy link
Author

is the token balances & transfer now working in the light client?
Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
M2-config 📂 Chain specifications and node configurations. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Projects
None yet
Development

No branches or pull requests

3 participants