I ran the experiment you suggested on my other PC. It still hung at the same spot. I tried to send the log inside the PM but it was to big. How can I get you the log file. It definitely has a clear error message sequence in there. Just need to send you the log some how.
|
|
|
I am still loading from scratch, probably will not be done until sometime tomorrow. If that does not work I follow your instructions and see if that works. I will let you know tomorrow. Hopefully it will finish loading by then.
|
|
|
Thanks for the prompt replies tranz. I tried the files you posted twice and it still jams at the same block. I deleted the blockchain files as you suggested and I will attempt to download the entire block chain from the peers and see if that fixes. I even moved everything to another PC and it still sticks at the same spot.
|
|
|
I am also getting an error message in the wallet at the top that says: Warning: Checkpoint is too old. Wait for block chain to download, or notify developers.
|
|
|
Well I am getting depressed at this point. I have invested heavily in this coin and the wallet will not go beyond Block 1241289. I have tried three different versions of the wallet. I've reloaded the block chain from the golden one you provided earlier this month when the wallet failed on about Sept 8. The wallet was repaired and then ran all the way up till this morning.
Is there anything else that I can do to get beyond block 1241289. I am out of ideas and I am worried that I will not be able to salvage my coins. Can I send the coins to another wallet?
I have repaired the wallet but that has not helped. here is the last log:
09/24/14 22:07:13 connection timeout 09/24/14 22:07:14 trying connection 84.173.100.190:7372 lastseen=8.7hrs 09/24/14 22:07:19 connection timeout 09/24/14 22:07:19 trying connection 80.229.249.107:7372 lastseen=95.5hrs 09/24/14 22:07:24 connection timeout 09/24/14 22:07:25 trying connection 84.173.100.184:7372 lastseen=184.9hrs 09/24/14 22:07:27 ProcessSyncCheckpoint: pending for sync-checkpoint dd8b75959822836b42ee1f739aa1082205e90ab28f568212c1c0a7d0602cd145 09/24/14 22:07:30 connection timeout 09/24/14 22:07:31 received block b3ba070d4eb0c3adaaa0 sent from 84.200.17.178:7372 09/24/14 22:07:31 ProcessBlock: ORPHAN BLOCK, prev=0000000009b66922e7da 09/24/14 22:07:31 trying connection 198.144.154.103:7372 lastseen=45.0hrs 09/24/14 22:07:31 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:31 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:31 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:31 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:32 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:32 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:32 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:32 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:32 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:32 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:32 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:33 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:33 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:33 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:34 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:36 connection timeout 09/24/14 22:07:36 trying connection [2001:0:9d38:90d7:1c91:21b0:9a9d:1082]:7372 lastseen=988.7hrs 09/24/14 22:07:41 connection timeout 09/24/14 22:07:42 trying connection 98.215.74.213:7372 lastseen=81.8hrs 09/24/14 22:07:43 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:47 connection timeout 09/24/14 22:07:47 trying connection [2001:41d0:1:f2b5::1]:7372 lastseen=15.5hrs 09/24/14 22:07:49 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000009b66922e7da7847993bf68c570be001f0438307457213cf3e58f5e9 09/24/14 22:07:52 connection timeout 09/24/14 22:07:53 trying connection 70.60.17.66:7372 lastseen=482.4hrs 09/24/14 22:07:57 ProcessSyncCheckpoint: pending for sync-checkpoint b3ba070d4eb0c3adaaa03c0f96bab74374447885ae4cf8ff15153b3481b2681d 09/24/14 22:07:58 connection timeout 09/24/14 22:07:59 trying connection 95.52.2.49:7372 lastseen=1384.3hrs 09/24/14 22:08:02 received getdata (2 invsz) 09/24/14 22:08:04 connection timeout 09/24/14 22:08:04 trying connection 123.176.103.130:7372 lastseen=99.4hrs 09/24/14 22:08:06 received getdata for: block 21152ae4561448407563 09/24/14 22:08:09 connection timeout 09/24/14 22:08:10 trying connection [2001:0:9d38:90d7:2036:fbd:b469:8689]:7372 lastseen=801.9hrs 09/24/14 22:08:15 connection timeout 09/24/14 22:08:16 trying connection [2001:0:9d38:90d7:14d3:2692:9a9d:eee]:7372 lastseen=126.5hrs 09/24/14 22:08:21 connection timeout 09/24/14 22:08:21 trying connection 94.41.180.226:7372 lastseen=553.0hrs 09/24/14 22:08:22 ProcessSyncCheckpoint: pending for sync-checkpoint 7ae60c561023cbd023429ea183797beeafa4fab3c2b009a36ef132ac60ea6f3d 09/24/14 22:08:26 connection timeout 09/24/14 22:08:27 trying connection 198.23.103.90:7372 lastseen=959.6hrs
|
|
|
Well still no luck I have tried three different wallet levels. Loading back up blockchain. I did have errors in the wallet and repaired them but the wallet still refuses to sync. Anyone have any suggestions. See error log below.
09/24/14 19:36:00 Postponing 1774 reconnects 09/24/14 19:36:00 REORGANIZE 09/24/14 19:36:00 REORGANIZE: Disconnect 10 blocks; f528637dd8f754ca2583..bebe4121b0f59a8ec522 09/24/14 19:36:00 REORGANIZE: Connect 13 blocks; f528637dd8f754ca2583..4c42a8c057d2457b5af1 09/24/14 19:36:01 connection timeout 09/24/14 19:36:01 ERROR: ConnectInputs() : 7ae81d70a1 prev tx already used at (nFile=1, nBlockPos=581778185, nTxPos=581778344) 09/24/14 19:36:01 ERROR: Reorganize() : ConnectBlock 000000000c7403f78c10 failed 09/24/14 19:36:01 InvalidChainFound: invalid block=b7693245432e77c5f3d4 height=1243076 trust=7664472959379 date=09/24/14 13:02:33 09/24/14 19:36:01 InvalidChainFound: current best=bebe4121b0f59a8ec522 height=1241299 trust=7643452494209 date=09/24/14 09:14:48 09/24/14 19:36:01 ERROR: SetBestChain() : Reorganize failed 09/24/14 19:36:01 ERROR: AcceptBlock() : AddToBlockIndex failed 09/24/14 19:36:01 ERROR: ProcessBlock() : AcceptBlock FAILED 09/24/14 19:36:01 received block 0000000003ca3121244f sent from 108.38.251.208:7372 09/24/14 19:36:01 Postponing 1775 reconnects 09/24/14 19:36:01 REORGANIZE 09/24/14 19:36:01 REORGANIZE: Disconnect 10 blocks; f528637dd8f754ca2583..bebe4121b0f59a8ec522 09/24/14 19:36:01 REORGANIZE: Connect 13 blocks; f528637dd8f754ca2583..4c42a8c057d2457b5af1 09/24/14 19:36:01 trying connection 73.44.36.214:7372 lastseen=4.5hrs
|
|
|
What's the link for 1.4.8?
|
|
|
@ Tranz My 1.4.1 wallet seems to be locked up as of a few hours ago and will no longer sync to the network. Should I try reloading the block chain. I have a backup of it. Which files do I need to replace? Thanks for your help.
|
|
|
I am guessing it may be needed in an effort to fix the high orphan rate while mining. It is important to fix the high orphan rate or Tekcoin will suffer.
|
|
|
What is the best pool for mining tek. It appears as if Tompool is going to be down for a long time.
|
|
|
AS I understand it if your wallet is encrypted even if they steal your coins they will never be able to spend them. So it is definitely a good idea to encrypt the wallet.
|
|
|
Thanks dollux...
Anybody know where I can get an API that can be used for Tek Coin?
|
|
|
I just checked the POS difficulty at Block 541114 and it is at .000092 is this what you guys are seeing now?
|
|
|
Super good stuff Tranz. I appreciate the links.
|
|
|
The Richlist has been down for weeks I sure would like to see it get fixed. Its a fun tool to use.
|
|
|
If you put a space in the label part it causes a crash when trying to send coin. That is why it would not send. You should be getting some coin soon.
Figured out why the wallet was losing sync. One of the other files not the wallet and not the block chain was in some way corrupt or improper. I replaced them with a back up of some other golden files and that fixed the problem with the wallet losing the sync. Now it is time to backup the golden working files before I have another thunderstorm show up.
|
|
|
Thanks Tranz it worked great. I am using your beta wallet as well seems to be working well so far. Accept that the wallet seems to fall behind after syncing. I tried to send some coin to you but the address I sent it to was not correct somehow. F1TranzWqFGZyFeTMu6iLbtTQgdXuJPsiL
|
|
|
Thanks Tranz. I appreciate it. Learned my lesson its good to backup both the wallet and the block chain.
|
|
|
Anybody have the latest blockchain for downloading?
|
|
|
Help! I am in desperate need of the blockchain for hobo nickels. I tried the wiki link with no luck. I need to download new one to fix my wallet thanks for your help.
|
|
|
|