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

Parity Sync Freezes midway! #8729

Closed
rasarasan opened this issue May 29, 2018 · 7 comments
Closed

Parity Sync Freezes midway! #8729

rasarasan opened this issue May 29, 2018 · 7 comments
Labels
M4-core ⛓ Core client code / Rust. P5-sometimesoon 🌲 Issue is worth doing soon. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Milestone

Comments

@rasarasan
Copy link

I'm running:

Which Parity version?: Parity v1.11.1-20180515 beta
Which operating system?: MacOS
How installed?: via installer
Are you fully synchronized?: no
Which network are you connected to?: ethereum
Did you try to restart the node?: yes

I have my storj tokens in my parity wallet. But it has been syncing for days/weeks now. After a while it freezes with no progress or end in sight :( Please see the attached screenshot. Will appreciate a quick response as I have spent too much on time on this already !

parity-sync-issue

@Tbaut Tbaut added Z1-question 🙋‍♀️ Issue is a question. Closer should answer. P5-sometimesoon 🌲 Issue is worth doing soon. M4-core ⛓ Core client code / Rust. labels May 30, 2018
@Tbaut Tbaut added this to the 1.12 milestone May 30, 2018
@Tbaut
Copy link
Contributor

Tbaut commented May 30, 2018

I'm sorry to hear you're having problems getting in sync. Syncing with warp is tricky these days because of several issues we're working on. To give us the best chances to succeed, you should learn how to launch parity with the command line. Here are my rules of thumb :

  1. make sure parity UI is shut down an no parity process is running.
  2. delete your database using parity db kill (in the terminal)
  3. start parity again with the flag parity --warp-barrier 5680000
  4. if the node starts downloading snapshots, you're good, let it do the warp sync. If the node starts syncing showing block numbers (and not the snapshots) it means failed to warp sync.
  5. stop parity and start it again -> jump back to 2.
  6. if after 4-5 attempts you never get the warp sync.. then stop the process, grab a coffee and try later

Here is an extensive explanation of what the command line output means: https://wiki.parity.io/FAQ-CLI,-Mining,-and-Networks.html#what-does-paritys-command-line-output-mean
This is not per se a parity problem, just some challenges brought by the growing network, it's a good thing :)

@rasarasan
Copy link
Author

Followed your steps. Let me know if this is right. (attached screenshot)
parity-sync2

@Tbaut
Copy link
Contributor

Tbaut commented May 30, 2018

Yes, this looks good. Just need to wait for the warp sync to end and the latest blocks to sync. Depending on your connection it can take ~3h overall.

@pro-respirator
Copy link

Is it just pure luck as to whether it works or not? I've tried this process with variations at least 50 times with no success whatsoever, the warp sync never gets beyond 15% before it fails normally and running with the --warp-barrier flag prevents it from syncing at all, it just sits at 0 forever. Is there anything else I can do that might help matters?

@Tbaut
Copy link
Contributor

Tbaut commented Jun 4, 2018

We've found some issues in the v1.11.1 related to the sync (#8710 #8544 #8658) that will be resolved in the next minor release (should come this week). From this point, warp sync should be more reliable.

@Tbaut Tbaut closed this as completed Jun 4, 2018
@rasarasan
Copy link
Author

rasarasan commented Jun 5, 2018

My node is almost synced and I am able to see my tokens now. When I try to transfer I get this error now. :( I dont have any local key file :(
paritysenderror

@Tbaut
Copy link
Contributor

Tbaut commented Jun 6, 2018

This is not a related issue @rasarasan. Please open a new one (in https://github.com/Parity-JS/shell/issues if related to the UI).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
M4-core ⛓ Core client code / Rust. P5-sometimesoon 🌲 Issue is worth doing soon. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Projects
None yet
Development

No branches or pull requests

3 participants