1.3.6.0 and now I am trying 1.3.0 and it loaded, syncing slowly and then the wallet will hang.
(Not Responding)
Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 237. (Read 478852 times)
April 02, 2014, 12:39:19 PM
April 02, 2014, 12:26:26 PM
Thanks, I replace the blockchain with rar files you linked then the wallet said loaded, hung, then crashed.
I will try version 1.3.0.
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: HoboNickels-qt.exe
Application Version: 0.0.0.0
Application Timestamp: 00000000
Hang Signature: 07d1
Hang Type: 0
OS Version: 6.2.9200.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 07d1e93e033b11bb20482d9dfc43571f
Additional Hang Signature 2: 65e8
Additional Hang Signature 3: 65e858b5c52c69c8e7d6c49597c42223
Additional Hang Signature 4: 07d1
Additional Hang Signature 5: 07d1e93e033b11bb20482d9dfc43571f
Additional Hang Signature 6: 65e8
Additional Hang Signature 7: 65e858b5c52c69c8e7d6c49597c42223
I will try version 1.3.0.
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: HoboNickels-qt.exe
Application Version: 0.0.0.0
Application Timestamp: 00000000
Hang Signature: 07d1
Hang Type: 0
OS Version: 6.2.9200.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 07d1e93e033b11bb20482d9dfc43571f
Additional Hang Signature 2: 65e8
Additional Hang Signature 3: 65e858b5c52c69c8e7d6c49597c42223
Additional Hang Signature 4: 07d1
Additional Hang Signature 5: 07d1e93e033b11bb20482d9dfc43571f
Additional Hang Signature 6: 65e8
Additional Hang Signature 7: 65e858b5c52c69c8e7d6c49597c42223
What version of the client were you running?
April 02, 2014, 12:21:55 PM
Thanks, I replace the blockchain with rar files you linked then the wallet said loaded, hung, then crashed.
I will try version 1.3.0.
From 1.3.6.0
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: HoboNickels-qt.exe
Application Version: 0.0.0.0
Application Timestamp: 00000000
Hang Signature: 07d1
Hang Type: 0
OS Version: 6.2.9200.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 07d1e93e033b11bb20482d9dfc43571f
Additional Hang Signature 2: 65e8
Additional Hang Signature 3: 65e858b5c52c69c8e7d6c49597c42223
Additional Hang Signature 4: 07d1
Additional Hang Signature 5: 07d1e93e033b11bb20482d9dfc43571f
Additional Hang Signature 6: 65e8
Additional Hang Signature 7: 65e858b5c52c69c8e7d6c49597c42223
I will try version 1.3.0.
From 1.3.6.0
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: HoboNickels-qt.exe
Application Version: 0.0.0.0
Application Timestamp: 00000000
Hang Signature: 07d1
Hang Type: 0
OS Version: 6.2.9200.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 07d1e93e033b11bb20482d9dfc43571f
Additional Hang Signature 2: 65e8
Additional Hang Signature 3: 65e858b5c52c69c8e7d6c49597c42223
Additional Hang Signature 4: 07d1
Additional Hang Signature 5: 07d1e93e033b11bb20482d9dfc43571f
Additional Hang Signature 6: 65e8
Additional Hang Signature 7: 65e858b5c52c69c8e7d6c49597c42223
April 02, 2014, 12:20:14 PM
Ok I will try that,
and no it was regular transactions this time. What can cause this kind of issue ?
I know that if you send a transaction while not synced, or while having networking issues it can cause this to happen. I had this happen with a different coin a few months ago.
I'm still not sure why this happened, as I did make about 10 transactions before sending the 2 that got "stuck". Maybe they were either too fast, or I had network issues that I wasn't aware of.
The other thing I can say is that I was combining smaller blocks into bigger ones, (I had over 100 blocks sent into one) and the client was a bit laggy while preparing the transaction... Maybe something went wrong during that process.
Anyhow, -salvagewallet cleaned up that mess and I'm all good now. Thanks
EDIT: just did another transaction and never got caught up by the network... I'll redo the -salvagewallet thing but it's a pain and time consuming
here's the log if that could help
Code:
04/02/14 17:47:48 CommitTransaction:
CTransaction(hash=e62f60d62e, nTime=1396460865, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(1f0f651975, 0), scriptSig=3045022100d53b3d7ec7ca92)
CTxOut(nValue=1883.598592, scriptPubKey=OP_DUP OP_HASH160 c1deeb3337900432c207e4a0e55c2278e13fcd56 OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet e62f60d62e new
04/02/14 17:47:49 WalletUpdateSpent found spent coin 1883.599592hbn 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d
04/02/14 17:47:49 NotifyTransactionChanged 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d status=1
04/02/14 17:47:49 NotifyTransactionChanged e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b status=0
04/02/14 17:47:49 NotifyTransactionChanged 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d status=1
04/02/14 17:47:49 CTxMemPool::accept() : accepted e62f60d62e (poolsz 1)
04/02/14 17:47:49 AddToWallet e62f60d62e
04/02/14 17:47:49 NotifyTransactionChanged e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b status=1
04/02/14 17:47:49 AddToWallet e62f60d62e new
04/02/14 17:47:49 NotifyTransactionChanged e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b status=0
04/02/14 17:47:49 Relaying wtx e62f60d62e
04/02/14 17:47:49 NotifyAddressBookChanged EzAbwP8XEDByVXLw6rD58gozmvUaiKKQmi isMine=0 status=0
04/02/14 17:47:50 updateWallet 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d 1
04/02/14 17:47:50 inWallet=1 inModel=1 Index=225-226 showTransaction=1 derivedStatus=1
04/02/14 17:47:50 updateWallet e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b 0
04/02/14 17:47:50 inWallet=1 inModel=0 Index=1611-1611 showTransaction=1 derivedStatus=0
04/02/14 17:47:50 updateWallet 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d 1
04/02/14 17:47:50 inWallet=1 inModel=1 Index=225-226 showTransaction=1 derivedStatus=1
04/02/14 17:47:50 updateWallet e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b 1
04/02/14 17:47:50 inWallet=1 inModel=1 Index=1611-1612 showTransaction=1 derivedStatus=1
04/02/14 17:47:50 updateWallet e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b 0
04/02/14 17:47:50 inWallet=1 inModel=0 Index=0-0 showTransaction=1 derivedStatus=0
04/02/14 17:47:52 Flushing wallet.dat
04/02/14 17:47:52 Flushed wallet.dat 242ms
April 02, 2014, 11:36:03 AM
My wallet is still trying to sync, it stuck on block 1829 and it locking up? I never had so much trouble with a HBN wallet until last week. 
Block 1829 as in block 1829, or 1829 remaining? If block 1829, then I would recommend grabbing the blockchain manually and jumping way further ahead on the download - details here http://wiki.hobonickels.info/index.php?title=Replace_Blockchain
If 1829 remaining - sometimes I have found the QT client in general (not specific to HBN, happened to me with another coin too) will get stuck while trying to sync. This has happened a few times with a different coin, and one time the solution was as easy as restarting the client, another time I had to replace the chain manually.
Right now my Windows VPS with 666mhz ram and tiny cpu is up to the current block 724673 at the moment. I would have expected my VPS with shitty specs to have had more problems that other people are reporting, but it seems to keep up fine. I wonder what the source of the QT client getting stuck mid-sync would be?
I may have found a possible solution, and the underlying cause being boost library version.
April 02, 2014, 10:37:38 AM
My wallet is still trying to sync, it stuck on block 1829 and it is locking up? I never had so much trouble with a HBN wallet until last week.
April 01, 2014, 11:23:40 PM
Foolishly I didnt date the hbn wallet backup like I do with btc. But it is very likely from version 1.3.1.
I wonder if starting the client using -salvagewallet might work? I am running out of ideas real fast. Sorry.
Try repairwallet in the console
Regarding my wallet it has been trying to sync for over 24 hours.
I am using the 1.3.6.0 beta version, are they any extra nodes besides the ones below?5.249.152.30
54.201.183.106
178.33.105.250
123.176.103.130
Repair wallet is actually in the menu now.
You can get more nodes here.
http://hbn.blockx.info/connected-nodes
Cheers, she is trucking along at a 10 blk pace now instead of stalling, getting a bite to eat and a beverage.
April 01, 2014, 10:45:18 PM
Everything works great for me, just a quick blockchain replacement that happened once. Not a big deal in my book 
I have really enjoyed all of the additional features and development that have gone into the wallet. As I continue to learn more and more about crypto-currency development, I realize just how time consuming coin development must be. I am very thankful for all the time that Tranz as well as other members of the community have put into HBN.
I think things will continue to get better and better and that the coin will continue to evolve. Just looking at the amount of hits from all over the world that hobonickels.info gets, it continues to validate that HBN is becoming more widely adopted and popular. Stake for charity is going to be awesome and is another item that makes HBN better than all the other coins out there.
I have really enjoyed all of the additional features and development that have gone into the wallet. As I continue to learn more and more about crypto-currency development, I realize just how time consuming coin development must be. I am very thankful for all the time that Tranz as well as other members of the community have put into HBN.
I think things will continue to get better and better and that the coin will continue to evolve. Just looking at the amount of hits from all over the world that hobonickels.info gets, it continues to validate that HBN is becoming more widely adopted and popular. Stake for charity is going to be awesome and is another item that makes HBN better than all the other coins out there.
April 01, 2014, 09:56:28 PM
Thanks guys!
I do understand that there are some bugs in the HBN wallet and network. Namely the assert failures dealing the blk*.dat files and the error 22 files dealing with wallets.
I haven't had a wallet error 22 myself, so that is a bit more difficult for me to trouble shoot. I do believe this last case (based on what was said here) is the database directory had some bad data, and this caused the wallet to fail to be loaded. The wallet.dat may have been fine. Difficult to tell from this end. I just wonder if strawie had started a fresh directly with only that wallet, which was causing problems, would the error 22 still have happened?
The assert failures I can now (mostly) duplicate. So I will be looking for the root cause and solution. Both of these will be in focus as we get closer to 1.4. I can not promise I will be able to fix both or either of them, but I will continue to look deeper. If there are any other coin developers that may have any ideas I would be glad to brainstorm.
Remember btc has fairly big team with years of development. HBN has me, and I've only been doing this for about 6 months now. I do my best to search through the pull requests of many coins. BTC, PPC, NVC. If anyone sees pull request that deals with either of these, please bring it to my attention, it may help.
I am trying to push the envelope, good or bad, on what can be done with a coin. Some of this will cause bugs.
I plan to complete a bit more work on stake for charity this week, the move on to some of these and other issues.
I hope that in the next year or so HBN could be part of a bigger picture which many sites choose to use this coin for general spending and for charitable giving. Obviously we will have to work some of these issue out as we go. As I understand they can be frustrating and cause people to turn away. Neither of these is satisfactory in my eye. But for now it is what it is.
Thanks all and carry on the good fight.
I do understand that there are some bugs in the HBN wallet and network. Namely the assert failures dealing the blk*.dat files and the error 22 files dealing with wallets.
I haven't had a wallet error 22 myself, so that is a bit more difficult for me to trouble shoot. I do believe this last case (based on what was said here) is the database directory had some bad data, and this caused the wallet to fail to be loaded. The wallet.dat may have been fine. Difficult to tell from this end. I just wonder if strawie had started a fresh directly with only that wallet, which was causing problems, would the error 22 still have happened?
The assert failures I can now (mostly) duplicate. So I will be looking for the root cause and solution. Both of these will be in focus as we get closer to 1.4. I can not promise I will be able to fix both or either of them, but I will continue to look deeper. If there are any other coin developers that may have any ideas I would be glad to brainstorm.
Remember btc has fairly big team with years of development. HBN has me, and I've only been doing this for about 6 months now. I do my best to search through the pull requests of many coins. BTC, PPC, NVC. If anyone sees pull request that deals with either of these, please bring it to my attention, it may help.
I am trying to push the envelope, good or bad, on what can be done with a coin. Some of this will cause bugs.
I plan to complete a bit more work on stake for charity this week, the move on to some of these and other issues.
I hope that in the next year or so HBN could be part of a bigger picture which many sites choose to use this coin for general spending and for charitable giving. Obviously we will have to work some of these issue out as we go. As I understand they can be frustrating and cause people to turn away. Neither of these is satisfactory in my eye. But for now it is what it is.
Thanks all and carry on the good fight.
The effort is certainly appreciated. And the fact you have been able to do great things with the coin in the 6 months as developer just shows that their are some great things in the pipeline for this coin.
April 01, 2014, 09:04:45 PM
Foolishly I didnt date the hbn wallet backup like I do with btc. But it is very likely from version 1.3.1.
I wonder if starting the client using -salvagewallet might work? I am running out of ideas real fast. Sorry.
Try repairwallet in the console
Regarding my wallet it has been trying to sync for over 24 hours.
I am using the 1.3.6.0 beta version, are they any extra nodes besides the ones below?5.249.152.30
54.201.183.106
178.33.105.250
123.176.103.130
Repair wallet is actually in the menu now.
You can get more nodes here.
http://hbn.blockx.info/connected-nodes
April 01, 2014, 08:58:55 PM
Foolishly I didnt date the hbn wallet backup like I do with btc. But it is very likely from version 1.3.1.
I wonder if starting the client using -salvagewallet might work? I am running out of ideas real fast. Sorry.
Try repairwallet in the console
Regarding my wallet it has been trying to sync for over 24 hours.
I am using the 1.3.6.0 beta version, are they any extra nodes besides the ones below?5.249.152.30
54.201.183.106
178.33.105.250
123.176.103.130
April 01, 2014, 07:46:42 PM
Thanks guys!
I do understand that there are some bugs in the HBN wallet and network. Namely the assert failures dealing the blk*.dat files and the error 22 files dealing with wallets.
I haven't had a wallet error 22 myself, so that is a bit more difficult for me to trouble shoot. I do believe this last case (based on what was said here) is the database directory had some bad data, and this caused the wallet to fail to be loaded. The wallet.dat may have been fine. Difficult to tell from this end. I just wonder if strawie had started a fresh directly with only that wallet, which was causing problems, would the error 22 still have happened?
The assert failures I can now (mostly) duplicate. So I will be looking for the root cause and solution. Both of these will be in focus as we get closer to 1.4. I can not promise I will be able to fix both or either of them, but I will continue to look deeper. If there are any other coin developers that may have any ideas I would be glad to brainstorm.
Remember btc has fairly big team with years of development. HBN has me, and I've only been doing this for about 6 months now. I do my best to search through the pull requests of many coins. BTC, PPC, NVC. If anyone sees pull request that deals with either of these, please bring it to my attention, it may help.
I am trying to push the envelope, good or bad, on what can be done with a coin. Some of this will cause bugs.
I plan to complete a bit more work on stake for charity this week, the move on to some of these and other issues.
I hope that in the next year or so HBN could be part of a bigger picture which many sites choose to use this coin for general spending and for charitable giving. Obviously we will have to work some of these issue out as we go. As I understand they can be frustrating and cause people to turn away. Neither of these is satisfactory in my eye. But for now it is what it is.
Thanks all and carry on the good fight.
I do understand that there are some bugs in the HBN wallet and network. Namely the assert failures dealing the blk*.dat files and the error 22 files dealing with wallets.
I haven't had a wallet error 22 myself, so that is a bit more difficult for me to trouble shoot. I do believe this last case (based on what was said here) is the database directory had some bad data, and this caused the wallet to fail to be loaded. The wallet.dat may have been fine. Difficult to tell from this end. I just wonder if strawie had started a fresh directly with only that wallet, which was causing problems, would the error 22 still have happened?
The assert failures I can now (mostly) duplicate. So I will be looking for the root cause and solution. Both of these will be in focus as we get closer to 1.4. I can not promise I will be able to fix both or either of them, but I will continue to look deeper. If there are any other coin developers that may have any ideas I would be glad to brainstorm.
Remember btc has fairly big team with years of development. HBN has me, and I've only been doing this for about 6 months now. I do my best to search through the pull requests of many coins. BTC, PPC, NVC. If anyone sees pull request that deals with either of these, please bring it to my attention, it may help.
I am trying to push the envelope, good or bad, on what can be done with a coin. Some of this will cause bugs.
I plan to complete a bit more work on stake for charity this week, the move on to some of these and other issues.
I hope that in the next year or so HBN could be part of a bigger picture which many sites choose to use this coin for general spending and for charitable giving. Obviously we will have to work some of these issue out as we go. As I understand they can be frustrating and cause people to turn away. Neither of these is satisfactory in my eye. But for now it is what it is.
Thanks all and carry on the good fight.
April 01, 2014, 07:02:18 PM
User scryptographer has offered to keep HBN blockchain archives hosted online for those that need them. The link for the most recent backup (today) is http://cryptotrade.rs/hbn/HBNchain04012014.rar and I will update the wiki to include this file.
Thanks scryptographer for helping the HBN community!
Thanks scryptographer for helping the HBN community!
You're welcome. Happy to help!
April 01, 2014, 06:36:12 PM
User scryptographer has offered to keep HBN blockchain archives hosted online for those that need them. The link for the most recent backup (today) is http://cryptotrade.rs/hbn/HBNchain04012014.rar and I will update the wiki to include this file.
Thanks scryptographer for helping the HBN community!
Thanks scryptographer for helping the HBN community!
April 01, 2014, 05:47:37 PM
Ok I will try that,
and no it was regular transactions this time. What can cause this kind of issue ?
I know that if you send a transaction while not synced, or while having networking issues it can cause this to happen. I had this happen with a different coin a few months ago.
April 01, 2014, 04:22:56 PM
A real quick question... what to do when you send a transaction, the funds are deducted from the sending wallet, it's being posted to the network (the receiving wallet marks it as unconfirmed) but the network never accept the transaction?
It happened to me 3 times now but I am not sure how to "reset" the transaction
Do I need to -salvagewallet on both wallets (sending and receiving)
what's the correct procedure to recover from that?
It happened to me 3 times now but I am not sure how to "reset" the transaction
Do I need to -salvagewallet on both wallets (sending and receiving)
what's the correct procedure to recover from that?
I think repairwallet in rpc should fix this right? As long as you have the latest version of the daemon/client.
Repair wallet will fix missmatched coins, and orphans from stake or mining, But this type of transaction may not go away. Worth a shot though.
Unick was this dealing with multi-signatures. Or just a normal transactions?
You could try resendtx. But I think salvage wallet maybe necessary.
Ok I will try that,
and no it was regular transactions this time. What can cause this kind of issue ?
April 01, 2014, 04:21:37 PM
A real quick question... what to do when you send a transaction, the funds are deducted from the sending wallet, it's being posted to the network (the receiving wallet marks it as unconfirmed) but the network never accept the transaction?
It happened to me 3 times now but I am not sure how to "reset" the transaction
Do I need to -salvagewallet on both wallets (sending and receiving)
what's the correct procedure to recover from that?
It happened to me 3 times now but I am not sure how to "reset" the transaction
Do I need to -salvagewallet on both wallets (sending and receiving)
what's the correct procedure to recover from that?
I think repairwallet in rpc should fix this right? As long as you have the latest version of the daemon/client.
Repair wallet will fix missmatched coins, and orphans from stake or mining, But this type of transaction may not go away. Worth a shot though.
Unick was this dealing with multi-signatures. Or just a normal transactions?
You could try resendtx. But I think salvage wallet maybe necessary.
April 01, 2014, 04:16:23 PM
A real quick question... what to do when you send a transaction, the funds are deducted from the sending wallet, it's being posted to the network (the receiving wallet marks it as unconfirmed) but the network never accept the transaction?
It happened to me 3 times now but I am not sure how to "reset" the transaction
Do I need to -salvagewallet on both wallets (sending and receiving)
what's the correct procedure to recover from that?
It happened to me 3 times now but I am not sure how to "reset" the transaction
Do I need to -salvagewallet on both wallets (sending and receiving)
what's the correct procedure to recover from that?
I think repairwallet in rpc should fix this right? As long as you have the latest version of the daemon/client.
April 01, 2014, 04:12:38 PM
A real quick question... what to do when you send a transaction, the funds are deducted from the sending wallet, it's being posted to the network (the receiving wallet marks it as unconfirmed) but the network never accept the transaction?
It happened to me 3 times now but I am not sure how to "reset" the transaction
Do I need to -salvagewallet on both wallets (sending and receiving)
what's the correct procedure to recover from that?
It happened to me 3 times now but I am not sure how to "reset" the transaction
Do I need to -salvagewallet on both wallets (sending and receiving)
what's the correct procedure to recover from that?
April 01, 2014, 04:04:52 PM
yeah, I've made it through the console commands and figured out how to do that.
Jump to: