Author

Topic: Slow at "connecting to peers" (Read 798 times)

legendary
Activity: 1358
Merit: 1001
https://gliph.me/hUF
April 01, 2017, 11:16:58 AM
#2
For older versions, deleting / renaming peers.dat (when Core is not running) used to help in situations like this.
newbie
Activity: 1
Merit: 0
March 31, 2017, 06:41:35 PM
#1
Using 0.14, upon initialization, the client sits at "connecting to peers".

Here's a sample from the log:
2017-03-31 12:57:56 Loading addresses from DNS seeds (could take a while)
2017-03-31 12:57:58 119 addresses found from DNS seeds
2017-03-31 12:57:58 dnsseed thread exit
2017-03-31 12:58:03 receive version message: /Satoshi:0.14.0/: version 70015, blocks=459765, us=:64662, peer=1
2017-03-31 12:58:04 receive version message: /Satoshi:0.14.0/: version 70015, blocks=459765, us=:64668, peer=2
2017-03-31 12:58:16 receive version message: /Satoshi:0.13.2/: version 70015, blocks=459765, us=[2001:0:5ef5:79fb:2023:37e6:b5b4:8cb]:64684, peer=3
2017-03-31 12:58:16 receive version message: /Satoshi:0.13.1/: version 70014, blocks=459765, us=:64689, peer=4
2017-03-31 12:58:17 receive version message: /Satoshi:0.13.1/: version 70014, blocks=459765, us=:64690, peer=5
2017-03-31 12:58:29 receive version message: /Satoshi:0.14.0/: version 70015, blocks=459765, us=:64708, peer=6
2017-03-31 12:58:29 receive version message: /Satoshi:0.14.0/: version 70015, blocks=459765, us=:64709, peer=7
2017-03-31 13:04:35 receive version message: /Satoshi:0.13.2/: version 70015, blocks=459767, us=:65386, peer=8

It's on peer 61 and has taken about 10 hours just on this stage alone.

Things I've tried:
  • I've restarted
  • Checked port blocking software (Windows defender is off)
  • Checked CPU usage (it's at 0%)

I've tried to search for this problem but haven't seen much.

Thanks in advance!

Edit: Updated - blew away the entire directory and started from scratch, appears to be working now
Jump to: