-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Parity gets stuck syncing #3635
Comments
I can confirm the issue above, it eventually stops synching |
I am only seeing this on 1.4.5 , 1.4.4 seems ok |
1.4.4 seems to have also issues. edit:
strange thing is, that both nodes runs the same version, but had different block state / number while stucked. |
if you could run with |
@gavofyork hmmm, after waiting 20 mins within a loop of calling getCurrentBlockNumber() on node 2 parity seems to be resynced again... the block number raised from 55629 to 55750 immediately between two calls. sorry, have no clue what magic is happening here. |
@gavofyork issue appears again. last timestamp before issue occured:
Log file attached |
Version: Parity/v1.4.5-beta-a028d04-20161126/x86_64-linux-gnu/rustc1.13.0
OS: Ubuntu 16.04
HD: SSD
System: VPS Digital Ocean
Parity 1.4.4 seemed to be perpetually syncing so I upgraded to 1.4.5 deleted chain data and did a warp sync with the new
--testnet
option. Geth is currently at block52828
.Parity output:
Upon restarting Parity it continues "Importing" in sync with Geth for a short period before returning to a perpetual "Syncing" state.
The text was updated successfully, but these errors were encountered: