Author

Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 260. (Read 478852 times)

hero member
Activity: 708
Merit: 502
mixax1 if you continue to have issue, please PM me. I'll see if I can help.


I downloaded hobo on ubuntu vmware
I compiled it and ran
synced blockchain
added wallet-stake - error 22


trying to recover keys:

./pywallet.py --dumpwallet --otherversion=34 --datadir=~/.HoboNickels --wallet=wallet-stake.dat
Traceback (most recent call last):
  File "./pywallet.py", line 5010, in
    db_env = create_env(db_dir)
  File "./pywallet.py", line 1269, in create_env
    r = db_env.open(db_dir, (DB_CREATE|DB_INIT_LOCK|DB_INIT_LOG|DB_INIT_MPOOL|DB_INIT_TXN|DB_THREAD|DB_RECOVER))
bsddb.db.DBNoSuchFileError: (2, 'No such file or directory -- ~/.HoboNickels/__db.001: No such file or directory')
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
I've added this note to the front page until I can get to the bottom of it.

https://bitcointalksearch.org/topic/m.3251468
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
Yes I have a hard shutdown before.

Remove db file and those 2 folders. I get 2 wallet files: default and mining.

Only the wallet-mining.dat file get error message when launching wallet client. I tried copy mining DAT file to somewhere else and "load" that DAT manually. Still get following message:

"Critical error loading wallet xxx.dat:CDB() / error 22"

Is it means this wallet file is currupted?  Huh

Yes I think it does.  Damn.....  My guess is it is the mining wallet. You can tell by using the -usewallet="" switch.  And see if it starts up.

There maybe something not quite right with secondary wallets.

Edit: I see you already pinpointed it to a secondary wallet. Please let me know if you have a backup or not.

I'll start digging through the code and see why the currpotion is only happening on the non default wallets.
full member
Activity: 182
Merit: 100
Yes I have a hard shutdown before.

Remove db file and those 2 folders. I get 2 wallet files: default and mining.

Only the wallet-mining.dat file get error message when launching wallet client. I tried copy mining DAT file to somewhere else and "load" that DAT manually. Still get following message:

"Critical error loading wallet xxx.dat:CDB() / error 22"

Is it means this wallet file is currupted?  Huh
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
I get this error message suddenly when I relanuch wallet



It's the beta 1.4 client. Still get same message when I download the 1.3 client.

Can you tell me if there was a hard shutdown of your computer?  Or recent windows update?

Another friend got this error as well, not sure what is causing it. It can solved by removing the blk0001.dat and  database and txleveldb directories in %appdata%/HoboNickels.

It maybe best to take a quick copy of all files in %appdata%/HoboNickels  first though.

full member
Activity: 182
Merit: 100
I get this error message suddenly when I relanuch wallet



It's the beta 1.4 client. Still get same message when I download the 1.3 client.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
Here is a version what will work with HBN, by default. https://github.com/Tranz5/pywallet

Tried to help another who had a bad wallet but no luck.

Backup all your wallets at least every other months and put a copy offline on a thumb drive, and maybe in the backup directory of your %appdata% folder.  It is worth the 2 minutes it takes!!!!

Version 1.4 will have an auto wallet backup that will take a snapshot every 24 hours or so.  But for now, you are responsible for ensuring you are protected.

mixax1 if you continue to have issue, please PM me. I'll see if I can help.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
Those who have a corrupted wallet, I am working on a version of pywallet that will work with HBN. It should just be --otherversion=34  but you will have to specify the path as well.

For those that are fine. Please take the opportunity to save a wallet off line. And even keep a printed copy. I have added dumpwallet to the rpc commands so it is very easy to print it out and keep it on paper.

hero member
Activity: 708
Merit: 502


--otherversion=OTHERVERSION
                        use other network address type, whose version is
                        OTHERVERSION

I can`t find a version that hobo uses anywhere.
hero member
Activity: 786
Merit: 1000
I had 1k coins stake, but it's not in my transaction list.  I guess I'm confused.  I have a few PoS mined totaling ~40ish.  I would have never known the 1k stake happened if I didn't see it pending on the overview.

Sort your transaction list by date, rather then status.

No change.  The top of the list is the 30 PoS I mined earlier.  Now that I think about it.  When I opened my wallet The 30 PoS mine was 1/6 and the 1k stake was there at the same time.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
I had 1k coins stake, but it's not in my transaction list.  I guess I'm confused.  I have a few PoS mined totaling ~40ish.  I would have never known the 1k stake happened if I didn't see it pending on the overview.

Sort your transaction list by date, rather then status.
hero member
Activity: 786
Merit: 1000
I had 1k coins stake, but it's not in my transaction list.  I guess I'm confused.  I have a few PoS mined totaling ~40ish.  I would have never known the 1k stake happened if I didn't see it pending on the overview.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
Hi Tranz.
Didnt check this thread for a time, and now I see new version 1.3 released.
Does it works with multiwallet form previous version?

Deleted all files except 2 wallet.dat files from previous version (1.2.2) and run the 1.3 version, after chain downloading the client is crushing(

Version 1.3 will work with multi-wallets.

You mean to say the client is crashing? Do you have an error in the debug log?  It could be a corrupt wallet. But hard to say with no other infomation.

One thing to try is to isolate the wallets. So rename your wallets to something like nowallet.dat or nowallet-stake. And then start-up the client. If it doesn't crash, then you have some corruption with one of your wallets.

Let me know if you need further help.

Hi Tranz.

Making nowallet didnt work.
Win7 shows miscrosoft visual c++ runtime library error.
Debug log shows multiple errors of such a kind:

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block ... (different blocks)
connection timeout

May be I should delete an old .conf file with different addnodes, which may be already dont work...I dont know
I have Win7 64, and using windows client 1.3 (P.S. does older 1.2.2 version works now or not?)

You can go back to the old client yes. You will need to remove block chain files and re-sync. Although I am not sure you should have too.

You can move all your files into a new bkup directory and try to go fresh and see what happens. If you get up to speed you can reload the old wallets from the bkup directory and see if they cause a crash.


Ive made a clean install, by deleting all files except the wallet.dat and run the HoboNickels-qt.exe from 1.3.0.0 version, and the client still crush approx after downloading the blockchain.

Going back to 1.2.2

Update: after removing back to 1.2.2, during blockchain downloading (after clean install), got this error:
"Critical error loading wallet "POS" from wallet-POS.dat:CDB() : can't open database file wallet-POS.dat, error 22"

Wallet file was taken from backup, during 1.3 installation I was experimented with "nowallet" thing, could this be the reason? What should I do?

I've had 2 wallets on my multiwallet 1.2.2 system when it was working (wallet.dat and wallet-POS.dat). If i'll take 2nd .dat file (wallet-POS.dat) to another machine and will try to sync 1.2.2 system there, would it work without 1st .dat (wallet.dat)? I'll try and report.

You may try to use the -salvagewallet option. Between 1.2.2 and 1.3 there is no change to the wallet file only the block chain. So if you are having issues with the wallet. Going back a rev most likely won't help.

With a PoS client the wallet is in read/write mode alot more then with only PoW clients, so the operutnity for curroption is much higher. I'll work on some methods to lower this chance.


Please keep a backup of your wallet offline. 

I have done this for every client I have used, and even tough I have currpoted even litecoin wallets, my bakcups have saved me.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
Hey Tranz, got some weird behavior with the Mac client.

I left the Mac client opened to let it stake.  It did but all blocks are orphaned?!? All without exception.. So I fire up my windows client... It stakes perfectly (and it looks like all those block that got orphaned on the Mac client)

It's the same physical machine, windows 7 in VirtualBox. Both v1.3 and the same wallet is used on both instance (actually a copy of the same wallet).
Also, I noted that I normally have less peer connections on the Mac client than on the Windows client

Do you know about this, what could be the problem? Any advice ?

Anybody else having issues staking on Mac?

Thanks

I have very little mac experiecne so I am not sure about the mac. Perhaps other Mac users can comment.  Which mac client did you use for 1.3? There are two on github. Compiled by different people. So I'd like get a base as to which is causing you issues.
hero member
Activity: 708
Merit: 502
Pywallet seems to work only with bitcoin?
hero member
Activity: 708
Merit: 502

#3 after you are sync'd up with chain. Try to quickly load the wallet-stake.dat and then send those coins to another wallet.
#4 if that fails and the client crashes. Rename wallet.dat to wallet-olddef.dat Rename wallet-stake.dat wallet.dat then start client with -salvagewallet -usewallet=""

Maybe a stupid question but you do you have a backup of your wallet-stake.dat?

Let me know.

loading wallet from a freshly synced client shows error 22 - cant open db file

-salvagewallet -usewallet="" - is it exactly as command line should look like?
- I got error during loading:
Runaway exception
fatal error
error opening DBenvironment IO error C:

path/txtleveldb/MANIFEST-004260:this handle is invalid
sr. member
Activity: 476
Merit: 250
I think we need an extremist hobo with more ROI  Wink
sr. member
Activity: 303
Merit: 250
Hi Tranz.
Didnt check this thread for a time, and now I see new version 1.3 released.
Does it works with multiwallet form previous version?

Deleted all files except 2 wallet.dat files from previous version (1.2.2) and run the 1.3 version, after chain downloading the client is crushing(

Version 1.3 will work with multi-wallets.

You mean to say the client is crashing? Do you have an error in the debug log?  It could be a corrupt wallet. But hard to say with no other infomation.

One thing to try is to isolate the wallets. So rename your wallets to something like nowallet.dat or nowallet-stake. And then start-up the client. If it doesn't crash, then you have some corruption with one of your wallets.

Let me know if you need further help.

Hi Tranz.

Making nowallet didnt work.
Win7 shows miscrosoft visual c++ runtime library error.
Debug log shows multiple errors of such a kind:

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block ... (different blocks)
connection timeout

May be I should delete an old .conf file with different addnodes, which may be already dont work...I dont know
I have Win7 64, and using windows client 1.3 (P.S. does older 1.2.2 version works now or not?)

You can go back to the old client yes. You will need to remove block chain files and re-sync. Although I am not sure you should have too.

You can move all your files into a new bkup directory and try to go fresh and see what happens. If you get up to speed you can reload the old wallets from the bkup directory and see if they cause a crash.


Ive made a clean install, by deleting all files except the wallet.dat and run the HoboNickels-qt.exe from 1.3.0.0 version, and the client still crush approx after downloading the blockchain.

Going back to 1.2.2

Update: after removing back to 1.2.2, during blockchain downloading (after clean install), got this error:
"Critical error loading wallet "POS" from wallet-POS.dat:CDB() : can't open database file wallet-POS.dat, error 22"

Wallet file was taken from backup, during 1.3 installation I was experimented with "nowallet" thing, could this be the reason? What should I do?

I've had 2 wallets on my multiwallet 1.2.2 system when it was working (wallet.dat and wallet-POS.dat). If i'll take 2nd .dat file (wallet-POS.dat) to another machine and will try to sync 1.2.2 system there, would it work without 1st .dat (wallet.dat)? I'll try and report.
sr. member
Activity: 504
Merit: 254
Hey Tranz, got some weird behavior with the Mac client.

I left the Mac client opened to let it stake.  It did but all blocks are orphaned?!? All without exception.. So I fire up my windows client... It stakes perfectly (and it looks like all those block that got orphaned on the Mac client)

It's the same physical machine, windows 7 in VirtualBox. Both v1.3 and the same wallet is used on both instance (actually a copy of the same wallet).
Also, I noted that I normally have less peer connections on the Mac client than on the Windows client

Do you know about this, what could be the problem? Any advice ?

Anybody else having issues staking on Mac?

Thanks
Jump to: