HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive

[mmfiore]

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

[Tranz]

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

Not sure how you got on the wrong chain, but the wallet is trying to get back on but is struggling, due to a large number of reconnects.

I would suggest as a quick fix, removing the txleveldb, and blk0001.dat and then either re-syncing with peers. Or you can use this file for a faster fix.

Block Chain Download:
https://bitcointalk.org/index.php?topic=303749.msg8737716#msg8737716

[mmfiore]

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

[mmfiore]

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.

[Tranz]

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.

Did you see my post?  You may need to clear out txleveldb and block001.dat out of the %appdata%/HoboNickels directory then replace it with the file I posted or just re download from peers.


The Checkpoint too old message will go away on the next wallet restart.. You can always check it  as follows.

getinfo
"blocks" : 1244290,

getcheckpoint
{
"synccheckpoint" : "28c6a975c98f5e2f75a50ea885f58615919031ca31c74bf0287573f10bd2219d",
"height" : 1244290,
"timestamp" : "2014-09-24 22:50:02 UTC",
"policy" : "strict"
}

if the height and blocks match you are good.

If you continue to have issues, please feel free to PM me.

[mmfiore]

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.

[Tranz]

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.

Hmmm. Ok Here is something else to try first.

1) shutdown the wallet
2) copy the wallet(s) and database directory, to somewhere safe(just in case)
3) rename the debug.log file to debug.log_old
4) Remove the 2 files(txleveldb and block0001.dat) and put the ones from the download in place.
5) Start the client up with -zapwallettxes

If you are still stuck, please send me the full debug file. There is something at play I am not sure. But we'll figure it out I have no doubt.

Also check if the db.log file has any entries in it..

[kingscrown]

HBN needs a bit of ram on start, but after it starts all goes smooth

[mmfiore]

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.

[Tranz]

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.

Alright if not, don't get too upset.  I don't let my users just hang out to dry, we'll figure it out!

[mmfiore]

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.

[Tranz]

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.

You can try here.
http://www.filedropper.com/

Zip it up and password it(if you want), them PM me the link..

[EGStrategies]

sorry if this has been answered somewhere but is there an up to date hobonickels.conf?

hadnt synced/staked in a few weeks and now I am not getting any connections when i try to sync.

listen=1
daemon=1
server=1
rpcuser=gawminer
rpcpassword=fury
port=7372
rpcport=7373
rpcconnect=127.0.0.1
addnode=5.249.152.30

that is what I had been using that now gets me no connections

thank you

[EGStrategies]

sorry if this has been answered somewhere but is there an up to date hobonickels.conf?

hadnt synced/staked in a few weeks and now I am not getting any connections when i try to sync.

listen=1
daemon=1
server=1
rpcuser=gawminer
rpcpassword=fury
port=7372
rpcport=7373
rpcconnect=127.0.0.1
addnode=5.249.152.30

that is what I had been using that now gets me no connections

thank you

nevermind, got there eventually I'm good

[presstab]

Ahhh my first crypto "home" - HoboNickels.

Tranz not sure if you saw this, or if HBN already has this, but I added S4C flag to the notificator.

https://github.com/presstab/HyperStake/commit/867a7dbc1b68a4d07dd886bc8dd646ecdceb18c9
https://github.com/presstab/HyperStake/commit/15fa632dfecb18c331103ffac9ba81aef3fc64f8

[mmfiore]

I sent you the link in a PM  file via file dropper. I tried reloading from scratch and the wallet hung at about half way through. I then retried using the blockchain you sent a couple of weeks ago. This time I hardwired my PC to the network instead of wireless. Still hangs. I then tried setting up a wireless hotspot using my phone thinking that it might be something wrong with my router or home network. It still would not progress beyond this block number 1241289. This is the last block processed. So far I have eliminated the PC as the problem, I tried it on two PCs. I have eliminated my home network as the problem. I tried it on two networks. I eliminated the wallet as the problem it even sticks with an empty wallet. It appears to me to be a network / code problem where a certain condition occurs and when this condition happens the wallet looses its ability to sync.

There is only one way I can think of to fix this problem without some sort of code change. I will have to obtain a blockchain that is only a few hours old. One that is beyond the block that causes the freeze. This will probably be a temporary fix as this has happened 2 times this month so I am thinking it may happen again until we find what the root cause of this problem is. I used to test software and hardware for a living so let me know if you need some testing help in the future or with this current problem. I like hobonickles and I want to see it be very successful.

Thanks for the support...

[georgidimitrov]

sorry if this has been answered somewhere but is there an up to date hobonickels.conf?

hadnt synced/staked in a few weeks and now I am not getting any connections when i try to sync.

listen=1
daemon=1
server=1
rpcuser=gawminer
rpcpassword=fury
port=7372
rpcport=7373
rpcconnect=127.0.0.1
addnode=5.249.152.30

that is what I had been using that now gets me no connections

thank you

listen=1
daemon=1
server=1
rpcuser=
rpcpassword=
port=7372
rpcport=7373
rpcconnect=127.0.0.1
maxconnections=100
addnode=5.228.253.141
addnode=5.249.152.30
addnode=23.28.66.198
addnode=23.92.80.107
addnode=24.255.246.67
addnode=24.249.152.169
addnode=46.237.89.248
addnode=54.201.183.106
addnode=54.186.69.238
addnode=54.83.3.49
addnode=54.85.17.31
addnode=54.200.138.226
addnode=63.155.67.204
addnode=65.186.210.229
addnode=65.24.235.56
addnode=67.166.0.82
addnode=67.55.10.47
addnode=69.85.86.195
addnode=71.9.234.158
addnode=71.15.25.28
addnode=72.83.4.150
addnode=72.52.231.153
addnode=74.83.19.68
addnode=74.208.97.13
addnode=74.196.48.62
addnode=76.14.215.153
addnode=81.247.105.90
addnode=83.81.97.1
addnode=86.178.61.241
addnode=86.151.253.206
addnode=87.205.193.178
addnode=91.121.177.181
addnode=93.131.188.211
addnode=94.224.109.177
addnode=94.251.132.2
addnode=94.23.31.223
addnode=97.88.160.74
addnode=98.148.179.13
addnode=107.15.231.157
addnode=107.170.101.69
addnode=108.193.130.242
addnode=109.242.36.205
addnode=109.235.190.7
addnode=162.243.28.252
addnode=162.243.123.132
addnode=162.217.249.198
addnode=173.11.82.114
addnode=173.218.212.131
addnode=178.149.57.165
addnode=188.165.223.132
addnode=188.104.141.34
addnode=192.99.44.159
addnode=195.91.216.170
addnode=198.101.10.109
addnode=203.12.171.66
addnode=213.7.8.12

-------------------------------------------------
websitetrafficdelivery[dot]tk - HBN/DOGE/PayPal accepted

[georgidimitrov]

Also, version 1.4.0.1 works flawless for me under WinXP sp3.

[GiorgosK]

my hobo wallet.dat is probably corrupted
I could not start the client with that .dat
and I was forced to erase everything (took a back up of wallet.dat) and restarted with an empty wallet

is there a way to import that wallet ?
wallet has been encrypted

currently waiting for the blockchain to redownload

[Tranz]

I sent you the link in a PM  file via file dropper. I tried reloading from scratch and the wallet hung at about half way through. I then retried using the blockchain you sent a couple of weeks ago. This time I hardwired my PC to the network instead of wireless. Still hangs. I then tried setting up a wireless hotspot using my phone thinking that it might be something wrong with my router or home network. It still would not progress beyond this block number 1241289. This is the last block processed. So far I have eliminated the PC as the problem, I tried it on two PCs. I have eliminated my home network as the problem. I tried it on two networks. I eliminated the wallet as the problem it even sticks with an empty wallet. It appears to me to be a network / code problem where a certain condition occurs and when this condition happens the wallet looses its ability to sync.

There is only one way I can think of to fix this problem without some sort of code change. I will have to obtain a blockchain that is only a few hours old. One that is beyond the block that causes the freeze. This will probably be a temporary fix as this has happened 2 times this month so I am thinking it may happen again until we find what the root cause of this problem is. I used to test software and hardware for a living so let me know if you need some testing help in the future or with this current problem. I like hobonickles and I want to see it be very successful.

Thanks for the support...

Ok got the log, yes your client is rejecting block 1,241,290 I am testing a few things on my end. I'll let you know what I come up with.

Thank you for your help too.