I am re-syncing the blockchain from the Genesis block and try to re-create my wallet. It is not successful. On the DCRD this is my output. I am syncing it for 10 hours now but I have too many " http: TLS handshake error from [::1]:xxxxx: EOF" I am trying to recreate my wallet as well, but after entering the seeds the cmd just stop, waiting forever (waited 15 minjs but nothing happened) and looks frozen. I am running the 0.4.0. The latest from the DCRD: 2016/09/26 06:07:28 http: TLS handshake error from [::1]:61331: EOF 06:07:31 2016-09-26 [INF] BMGR: Lost peer 24.247.20.162:9108 (outbound) 06:07:31 2016-09-26 [INF] BMGR: Syncing to block height 66684 from peer [2604:a880:1:20::250:c001]:9108 06:07:31 2016-09-26 [INF] BMGR: New valid peer [2a01:4f8:141:4144:6438:35ff:fe31:3939]:9108 (outbound) (/dcrwire:0.2.0/dcrd:0.1.6/) 06:08:04 2016-09-26 [INF] BMGR: Lost peer [2604:a880:1:20::250:c001]:9108 (outbound) 06:08:04 2016-09-26 [INF] BMGR: Syncing to block height 66684 from peer [2a01:4f8:141:4144:6438:35ff:fe31:3939]:9108 06:08:25 2016-09-26 [INF] BMGR: New valid peer 92.222.73.115:9108 (outbound) (/dcrwire:0.1.0/dcrd:0.1.4/) 2016/09/26 06:08:28 http: TLS handshake error from [::1]:61338: EOF 06:08:46 2016-09-26 [INF] BMGR: Lost peer [2a01:4f8:141:4144:6438:35ff:fe31:3939]:9108 (outbound) 06:08:46 2016-09-26 [INF] BMGR: Syncing to block height 66684 from peer 92.222.73.115:9108 06:09:25 2016-09-26 [INF] BMGR: Lost peer 92.222.73.115:9108 (outbound) 2016/09/26 06:09:28 http: TLS handshake error from [::1]:61343: EOF 2016/09/26 06:10:28 http: TLS handshake error from [::1]:61352: EOF 2016/09/26 06:11:28 http: TLS handshake error from [::1]:61353: EOF 2016/09/26 06:12:28 http: TLS handshake error from [::1]:61354: EOF 2016/09/26 06:13:29 http: TLS handshake error from [::1]:61355: EOF 2016/09/26 06:14:29 http: TLS handshake error from [::1]:61357: EOF 2016/09/26 06:15:29 http: TLS handshake error from [::1]:61358: EOF 2016/09/26 06:16:29 http: TLS handshake error from [::1]:61359: EOF 2016/09/26 06:17:29 http: TLS handshake error from [::1]:61360: EOF 2016/09/26 06:18:30 http: TLS handshake error from [::1]:61361: EOF 2016/09/26 06:19:30 http: TLS handshake error from [::1]:61363: EOF 2016/09/26 06:20:30 http: TLS handshake error from [::1]:61364: EOF 2016/09/26 06:21:30 http: TLS handshake error from [::1]:61365: EOF 2016/09/26 06:22:30 http: TLS handshake error from [::1]:61366: EOF 2016/09/26 06:23:30 http: TLS handshake error from [::1]:61367: EOF 2016/09/26 06:24:30 http: TLS handshake error from [::1]:61369: EOF 2016/09/26 06:25:31 http: TLS handshake error from [::1]:61370: EOF 2016/09/26 06:26:31 http: TLS handshake error from [::1]:61371: EOF 2016/09/26 06:27:31 http: TLS handshake error from [::1]:61372: EOF 2016/09/26 06:28:31 http: TLS handshake error from [::1]:61373: EOF 2016/09/26 06:29:31 http: TLS handshake error from [::1]:61375: EOF 2016/09/26 06:30:31 http: TLS handshake error from [::1]:61376: EOF 2016/09/26 06:31:31 http: TLS handshake error from [::1]:61377: EOF 2016/09/26 06:32:32 http: TLS handshake error from [::1]:61378: EOF 2016/09/26 06:33:32 http: TLS handshake error from [::1]:61379: EOF 2016/09/26 06:34:32 http: TLS handshake error from [::1]:61381: EOF 2016/09/26 06:35:32 http: TLS handshake error from [::1]:61382: EOF 2016/09/26 06:36:32 http: TLS handshake error from [::1]:61383: EOF 2016/09/26 06:37:32 http: TLS handshake error from [::1]:61384: EOF 2016/09/26 06:38:33 http: TLS handshake error from [::1]:61385: EOF 2016/09/26 06:39:33 http: TLS handshake error from [::1]:61387: EOF 2016/09/26 06:40:33 http: TLS handshake error from [::1]:61388: EOF 2016/09/26 06:41:33 http: TLS handshake error from [::1]:61389: EOF 2016/09/26 06:42:33 http: TLS handshake error from [::1]:61390: EOF 2016/09/26 06:43:33 http: TLS handshake error from [::1]:61392: EOF 2016/09/26 06:44:33 http: TLS handshake error from [::1]:61393: EOF 2016/09/26 06:45:34 http: TLS handshake error from [::1]:61394: EOF 2016/09/26 06:46:34 http: TLS handshake error from [::1]:61395: EOF 2016/09/26 06:47:34 http: TLS handshake error from [::1]:61396: EOF 2016/09/26 06:48:34 http: TLS handshake error from [::1]:61398: EOF 2016/09/26 06:49:34 http: TLS handshake error from [::1]:61399: EOF 2016/09/26 06:50:34 http: TLS handshake error from [::1]:61400: EOF 2016/09/26 06:51:35 http: TLS handshake error from [::1]:61401: EOF 2016/09/26 06:52:35 http: TLS handshake error from [::1]:61402: EOF 2016/09/26 06:53:35 http: TLS handshake error from [::1]:61404: EOF 06:09:25 2016-09-26 [INF] BMGR: Syncing to block height 66684 from peer 81.2.247.82:9108 06:53:52 2016-09-26 [INF] BMGR: New valid peer 128.199.39.144:9108 (outbound) (/dcrwire:0.2.0/dcrd:0.2.0/) 06:53:52 2016-09-26 [INF] BMGR: New valid peer 146.185.145.242:9108 (outbound) (/dcrwire:0.2.0/dcrd:0.1.6/) 06:53:53 2016-09-26 [INF] BMGR: Processed 1 block in the last 52m19.26s (3 transactions, height 66685, 2016-09-26 06:26:24 +0100 BST) 2016/09/26 06:54:35 http: TLS handshake error from [::1]:61405: EOF How could I sort it out, re-create the wallet and go back to solo PoS mining?
After entering seed when you see black CMD window and it looks like nothing is happened wait maybe 1-2 minutes. After that just hit ENTER one more time. You should get message : Wallet was successfully created or something similar. Important: bebore wallet creation sync must be fully completed to the last block! About another problem I have no idea, I just know that since v0.3.0. peers are extremly unstable and I'm loosing peers as crazy, sometime 20x per hour. I think it have some impact to synchronization also. Maybe somebody else will put some light to this matter.
I am still using 0.1.6, usually fine, but just found it was down, probably computer overheated. Please see my signature how to recreate from seed. I posted somewhere how to check dcrd is synced. Once DCRD is all ready, play with dcrwallet.