-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Having trouble syncing Parity with Mist+Geth - Cannot Connect to Peers - 0/0/25 loop #2744
Comments
Seems that your node has trouble discovering new peers. Also please open Windows Explorer, go to your home directory and find |
Also make sure your system clock is synced: |
Apologies for the length of this log. I am running parity and am not sure if/where it is looping so I want to be sure I include the information you need. The "target" field reads: "C:\Program Files\Ethcore\Parity\parity.exe" ui --chain=classic --geth -l sync=trace is this correct, or should I modify it? I have attempted to sync my system clock but http://time.is/ reports that I am .2 seconds behind, even immediately after I sync using the "Date and Time" program, under the "Internet Time tab". 2016-10-20 15:02:09 main INFO parity::run Starting Parity/v1.3.8-beta-e0778fc-20161015/x86_64-windows-msvc/rustc1.12.0 I removed the network directories as requested before running parity with the -lsync=trace parameter. Parity is currently still running and seems to be repeating/looping/following the above pattern. |
What kind of network are you on? All your connections end with timeout which indicates either a very low bandwidth or network misconfiguration |
I am on a 10Mbps fiber connection. My network could be improperly configured for parity but I don't seem to have any problems with Firefox connections or high-demand games like Overwatch. When I initially downloaded parity I simply double clicked to start the program and it seemed to be syncing fine and then eventually seemed to stop at a certain block. I never indicated the --chain=classic --geth flags and it seemed like something was happening before, then after applying those flags there seems to be no syncing taking place at all. I have uninstalled parity multiple times and also deleted all data in the .parity folders multiple times. I do however have "Exact" time now as reported by http://time.is/. |
Have been trying a few other variables to isolate the problem. I have done a fresh install on a secondary computer and have installed the latest geth 3.0.1 and the latest parity 1.3.9 Attempting parity without and with geth installed both resulted in the same 0/0/25 peers error. When I attempted to run Parity in the past however without the "--chain=classic" flag there was a connection and activity - blocks were being updated. Do I need to run parity through first without the attached "--chain=classic --geth" flags, or should they be run? At this point I'm a bit concerned that a fresh install has not gotten this to work. My primary objective is to access my mist account well before 10/25/16 so I can ensure I don't run into any problems when the fork occurs. I could search around for ports that might need opening but again, I haven't had problems with running Mist + Geth up until recently after I logged in around a week ago to notice there are almost (or no) nodes running that currently support geth and noticed that Mist wasn't syncing. I'm willing to try solutions. Any and all help is appreciated. At this point I have a fresh install, have installed parity 1.3.9 from the main site and cannot connect to peers using the "--chain=classic --geth" entry at the end of my target field. Have I entered this incorrectly? |
arkpar's advice was accurate. I needed to adjust my port forwarding settings. I sort of glazed over this by assuming things would have been automatically configured but that was not that case. Parity and geth are both synced and I also have synced the Classic Mist Wallet. Patiently awaiting the fork which should occur in <12 hours. Thanks for the help folks. |
@Free-Peace -> what was the procedure you followed to adjust your port forwarding settings? May you please share the steps? Thanks! |
Evening @jjmr007 . I used these two guides to set myself up. Geth, and I'm supposing by extension parity, listen in on port 30303. This port must be open to allow your computer to sync the blockchain with the outside world. If you are having a similar error/issue, logging in to your router (usually by typing 192.168.1.1 and then pressing enter in the address bar) should provide you with the opportunity to adjust your port forwarding settings to permit the connection to come through http://www.howtogeek.com/66214/how-to-forward-ports-on-your-router/ http://www.pcworld.com/article/244314/how_to_forward_ports_on_your_router.html |
Thank you @Free-Peace !!! both guides are good!!! Now I have 22 peers on classic chain!!! |
hey guys, i have the same issue. stuck with 0/0/25... sometimes i get 1/1/25 and then goes back to zero i tried the 2 guides above but couldn't know which port forwarding to open (ranges)..... still stuck |
Default port you need to expose is 30303 for TCP and UDP. Also make sure your system clock is in sync. Check at http://time.is |
Stoped the parity, removed the file nodes.json, restarted the parity, it worked. For linux, the file locates in '/share/io.parity.ethereum/chains/ethereum/network/'. |
Reposted from this thread: https://www.reddit.com/r/EthereumClassic/comments/57v8rv/using_mist_with_parity/
Can anyone lend a hand? It's been around 24 days since I last synced Mist+geth. I checked in a week or so ago and started familiarizing myself with all of the new changes. I have downloaded parity 1.3.8 and don't seem to be able to sync. I am receiving this message:
2016-10-19 22:24:42 Starting Parity/v1.3.8-beta-e0778fc-20161015/x86_64-windows-msvc/rustc1.12.0
2016-10-19 22:24:42 Using state DB journalling strategy fast
2016-10-19 22:24:42 Configured for Ethereum Classic using Ethash engine
2016-10-19 22:24:42 Your chain is an alternative fork. TRANSACTIONS MAY BE REPLAYED ON THE MAINNET!
2016-10-19 22:24:46 NAT mapped to external address 100.14.2.30:59773
2016-10-19 22:24:46 Public node URL: enode://a63be076c3fca1a3c6cac96b671f78832564f4bea236c70db15808838ad221fd8efdfee772aac14e8e342405f3f109fe1ffd0c0a4588ac10cee5e5f73805b42c@100.14.2.30:59773+33375
2016-10-19 22:25:13 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:25:44 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:26:15 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:26:46 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:27:16 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:27:47 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:28:18 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:28:48 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:29:19 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:29:50 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:30:20 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:30:51 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:31:22 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:31:53 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:32:24 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:32:54 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:33:25 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:33:56 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:34:27 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:34:57 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:35:28 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:35:59 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:36:30 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:37:01 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:37:31 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:38:02 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:38:33 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:39:04 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:39:35 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:40:05 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:40:36 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:41:07 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:41:38 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:42:08 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:42:39 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:43:10 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:43:41 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:44:12 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:44:43 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:45:13 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:45:44 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:46:15 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:46:46 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:47:17 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:47:47 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:48:18 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:48:49 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:49:19 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:49:50 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:50:21 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:50:52 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:51:23 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:51:54 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:52:25 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:52:56 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:53:27 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
2016-10-19 22:53:58 0/ 0/25 peers 3 MiB db 7 KiB chain 2 KiB queue 11 KiB sync
I have appended the "--geth --chain=classic" to the end of the "target" field, as instructed in the above video.
Anyone have an idea of what's going on or how to properly connect to peers and get synced? I have uninstalled via Windows uninstall tool and reinstalled and I'm still getting this error.
Running Windows 10 X64.
Any help would be appreciated. Thanks.
The text was updated successfully, but these errors were encountered: