Pages:
Author

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

legendary
Activity: 1540
Merit: 1060
May the force bit with you.
Hey Tranz, I have a problem with 1.5.2.0. It crashes on start up.

hobonickels-qt: src/kernel.cpp:372: unsigned int GetStakeModifierChecksum(const CBlockIndex*, bool): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.
Aborted

If I comment out that line in the code, it dies anyway.

Code:
2017-07-15 14:40:59 HoboNickels version v1.5.2.0-gf46fa0c-V1.5 (2017-06-27 00:03:06 -0400)
2017-07-15 14:40:59 Using OpenSSL version OpenSSL 1.0.1t  3 May 2016
2017-07-15 14:40:59 Default data directory /home/ph4nt0m/.HoboNickels
2017-07-15 14:40:59 Used data directory /home/ph4nt0m/.HoboNickels
2017-07-15 14:40:59 init message: Verifying database integrity...
2017-07-15 14:40:59 dbenv.open LogDir=/home/ph4nt0m/.HoboNickels/database ErrorFile=/home/ph4nt0m/.HoboNickels/db.log
2017-07-15 14:41:00 splitthreshold set to 100000000
2017-07-15 14:41:00 combinethreshold set to 200000000
2017-07-15 14:41:00 Bound to [::]:7372
2017-07-15 14:41:00 Bound to 0.0.0.0:7372
2017-07-15 14:41:00 init message: Loading block index...
2017-07-15 14:41:00 Opening LevelDB in /home/ph4nt0m/.HoboNickels/txleveldb
2017-07-15 14:41:00 Transaction index version is 70600
2017-07-15 14:41:00 Opened LevelDB successfully
2017-07-15 14:42:43 ERROR: CTxDB::LoadBlockIndex() : Failed stake modifier checkpoint height=0, modifier=0x0000000000000000

If I delete the chain data and sync again, it gets stuck at 90-something days ago. Restart and the same crap happens.


Please move to 1.5.3.(0 or 1).  That version messed up the txleveldb  and blk0001.dat versions. You get that version and then grab the block chain from hobonickels.info.
hero member
Activity: 591
Merit: 501
Scavenger of Crypto Sorrow
Hey Tranz, I have a problem with 1.5.2.0. It crashes on start up.

hobonickels-qt: src/kernel.cpp:372: unsigned int GetStakeModifierChecksum(const CBlockIndex*, bool): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.
Aborted

If I comment out that line in the code, it dies anyway.

Code:
2017-07-15 14:40:59 HoboNickels version v1.5.2.0-gf46fa0c-V1.5 (2017-06-27 00:03:06 -0400)
2017-07-15 14:40:59 Using OpenSSL version OpenSSL 1.0.1t  3 May 2016
2017-07-15 14:40:59 Default data directory /home/ph4nt0m/.HoboNickels
2017-07-15 14:40:59 Used data directory /home/ph4nt0m/.HoboNickels
2017-07-15 14:40:59 init message: Verifying database integrity...
2017-07-15 14:40:59 dbenv.open LogDir=/home/ph4nt0m/.HoboNickels/database ErrorFile=/home/ph4nt0m/.HoboNickels/db.log
2017-07-15 14:41:00 splitthreshold set to 100000000
2017-07-15 14:41:00 combinethreshold set to 200000000
2017-07-15 14:41:00 Bound to [::]:7372
2017-07-15 14:41:00 Bound to 0.0.0.0:7372
2017-07-15 14:41:00 init message: Loading block index...
2017-07-15 14:41:00 Opening LevelDB in /home/ph4nt0m/.HoboNickels/txleveldb
2017-07-15 14:41:00 Transaction index version is 70600
2017-07-15 14:41:00 Opened LevelDB successfully
2017-07-15 14:42:43 ERROR: CTxDB::LoadBlockIndex() : Failed stake modifier checkpoint height=0, modifier=0x0000000000000000

If I delete the chain data and sync again, it gets stuck at 90-something days ago. Restart and the same crap happens.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.

OK so I copied over a fresh blockchain
- I deleted the Hobonickels contents from the %appdata% folder
- I started the wallet QT files, It starts the wallet fine, and creates the contents of the HoboNickels folder
- I close the wallet, delete out the 2 Blk..dat files, and the wallet.dat, and the txleveldb dir
- I copy over my wallet.dat, the 2 Blk...dat files, and the txleveldb dir from the new downloaded
- I start the wallet back, and get the same error, I've been getting

Could my wallet.dat be off somehow?  I've got other copies, I can dig out.
Is my process off somewhere?

Is is possible your wallet.dat got corrupted. Have you tried -salvagewallet startup switch ?

OK this seems crazy to me but, here we go ....
I tried the -salvagewallet - still crashes same way
I tried a lower version HoboNickel wallet - dies same way
I tried it with the original wallat.dat - it still dies, OK yea, that got me thinking too
So I tried the same procedures on another computer, another Windows 7 Pro, this one is 64bit - and it comes up fine.

That original computer that it kept crashing on was a freshly formatted PC, with a fresh OS installed.  What in the world could be wrong with that PC?  That is hates the HBN wallet so much?

Well I am glad you got it work. Have you tried to Scandisk on the original computer? It could be lost clusters which cause read errors, or possibly bad memory chip or CPU?  I have burnt out a CPU before, so I know it is possible.  Although most likely is some issue with HDD.

I have 0 (zero) network connections, what am I missing.  (I only rebuild wallets about once a year, so I have to learn most of the stuff all over again)

https://cryptocurrencytalk.com/topic/85150-no-peer-connections-on-wallet/
member
Activity: 159
Merit: 11

OK so I copied over a fresh blockchain
- I deleted the Hobonickels contents from the %appdata% folder
- I started the wallet QT files, It starts the wallet fine, and creates the contents of the HoboNickels folder
- I close the wallet, delete out the 2 Blk..dat files, and the wallet.dat, and the txleveldb dir
- I copy over my wallet.dat, the 2 Blk...dat files, and the txleveldb dir from the new downloaded
- I start the wallet back, and get the same error, I've been getting

Could my wallet.dat be off somehow?  I've got other copies, I can dig out.
Is my process off somewhere?

Is is possible your wallet.dat got corrupted. Have you tried -salvagewallet startup switch ?

OK this seems crazy to me but, here we go ....
I tried the -salvagewallet - still crashes same way
I tried a lower version HoboNickel wallet - dies same way
I tried it with the original wallat.dat - it still dies, OK yea, that got me thinking too
So I tried the same procedures on another computer, another Windows 7 Pro, this one is 64bit - and it comes up fine.

That original computer that it kept crashing on was a freshly formatted PC, with a fresh OS installed.  What in the world could be wrong with that PC?  That is hates the HBN wallet so much?



I have 0 (zero) network connections, what am I missing.  (I only rebuild wallets about once a year, so I have to learn most of the stuff all over again)
sr. member
Activity: 536
Merit: 250
Deposit on cryptopia still off I need money now, want to sale 50000 HBN for 0.17 BTC, PM please.
legendary
Activity: 2114
Merit: 1090
=== NODE IS OK! ==
HBN and HYP had market caps of roughly $30k each at the start of May 2017. I am not buying that the devs finally showing up warrants them to pump up to $1.5mil each. If you all can sustain those higher market caps, more power to you, but the dumps will come as they always do in high PoS coins. Or, hey, if it looks like demand is picking up for the high PoS model again, I am sure iGotSpots will come back and flood the market with clones Grin

I think the coin age and the development activity are important, plus 100% yearly is not that high
legendary
Activity: 2534
Merit: 1129
It's an artificial spike. Not exactly a man made/planned pump. In flow of coins has halted so current coins on market are inflated from demand. It's not a pump by a coin holder by manipulating the market, but a system update based inflation.

As soon as the flood gates/wallet opens, every one with coins will be selling. Very few would be buying.
The value will then drastically drop since the depth isn't there to sustain high value.

I have 389k hbn. I can personally drop the value into the 10-30 satoshi range if I dumped my wallet.


Why would you say that ?

You never know what forces will come into play on price changes, either + or - 
legendary
Activity: 1540
Merit: 1060
May the force bit with you.

This is what happens whenever I have tried to -salvagewallet this one

2017-07-14 19:52:55 Renamed wallet.dat to wallet.1500061975.bak
2017-07-14 19:52:55 Error: Salvage found errors, all data may not be recoverable.
2017-07-14 19:52:55 Salvage(aggressive) found no records in wallet.1500061975.bak.

2017-07-14 19:54:03 Failed to rename wallet.dat to wallet.1500062043.bak

and the client exits. I gave up before when this happened because I couldnt figure it out. Is it doing this because the wallet was encrypted?

also, db.log gives me a bunch of errors. heres the last one

wallet.1488662875.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 359/6987529, past end of log at 71/4537095
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment

Hmm A possibly corrupted encrypted wallet.. I am not sure I have dealt with that yet. I will ask the obvious, do you have a backup before it was encrypted, or one that was encrypted but from a while ago?

I don't know if the database dir has much do to with it. But you should attempt to salvage on a clean database dir as well. Under a separate datadir, so you don't mess up your normal wallet.
member
Activity: 121
Merit: 10
HBN <3
It's an artificial spike. Not exactly a man made/planned pump. In flow of coins has halted so current coins on market are inflated from demand. It's not a pump by a coin holder by manipulating the market, but a system update based inflation.

As soon as the flood gates/wallet opens, every one with coins will be selling. Very few would be buying.
The value will then drastically drop since the depth isn't there to sustain high value.

I have 389k hbn. I can personally drop the value into the 10-30 satoshi range if I dumped my wallet.


Naw, there is a bitcoin at 300.  It would eat your 389k.. Also during those huge dumps the bots come out and play and create liquidity as well.
You're right. I was reading the depth chart wrong. There's some decent buys in place, but any human trader watching his stuff should pull out his stops as it falls.

I'd love to see it settle higher than what we were at. It's an OG coin compared to some of the stuff out there now.
newbie
Activity: 38
Merit: 0
I'm having wallet issues as well. I get the following error

Critical error loading wallet "reset" from wallet-reset.dat: CDB() : cant open
database file wallet-reset.dat, error 22

I had renamed this wallet file a long time ago when doing some coin cleanup to rest all my stakes into one large chunk. I can't seem to get this to work, and google isnt helping. Any tips how to remedy an error 22? thanks

There is no easy way currently to run salvagewallet  on a secondary wallet .If you have a wallet-reset.dat backup, try using that one instead. If not try these steps below.

1) Shutdown client
2) rename wallet.dat to noloadwallet.dat
3) rename wallet-reset.dat to wallet.dat
4) Startclient with -salvagewallet
5) Be patient, after fixing keys, it will rescan 5million blocks, this can take a fair amount of time. Possibly hours depending on your computer.
6) After complete, shutdown client
7) rename your wallet.dat (previously wallet-reset.dat) back to wallet-reset.dat
Cool rename your noloadwallet.dat to wallet.dat
9) start client up
10) do more frequent wallet backups!

You can alway monitor that progress by looking at the debug.log file.

I will work on adding an extra switch to salvagewallet to work on a secondary wallet For version 1.6.

Edit: If you are good with startups switches you can also also do this to save time.
1) Shutdown client
2) Create new dir called C:\hbn_fix
3) copy wallet-reset.dat to c:\hbn_fix\wallet.dat
4) startup client with -salavgewallet -datadir=c:\hbn_fix
5) After client is done and wallet is working, shut it down.
6) rename your wallet-reset.dat in your normal datadir %appdata% to brokewallet-reset.dat
7) Copy your wallet.dat form c:\hbn_fix to your normal datadir as wallet-reset.dat

This method may save a bit of time.



This is what happens whenever I have tried to -salvagewallet this one

2017-07-14 19:52:55 Renamed wallet.dat to wallet.1500061975.bak
2017-07-14 19:52:55 Error: Salvage found errors, all data may not be recoverable.
2017-07-14 19:52:55 Salvage(aggressive) found no records in wallet.1500061975.bak.

2017-07-14 19:54:03 Failed to rename wallet.dat to wallet.1500062043.bak

and the client exits. I gave up before when this happened because I couldnt figure it out. Is it doing this because the wallet was encrypted?

also, db.log gives me a bunch of errors. heres the last one

wallet.1488662875.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 359/6987529, past end of log at 71/4537095
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
hero member
Activity: 763
Merit: 534
HBN and HYP had market caps of roughly $30k each at the start of May 2017. I am not buying that the devs finally showing up warrants them to pump up to $1.5mil each. If you all can sustain those higher market caps, more power to you, but the dumps will come as they always do in high PoS coins. Or, hey, if it looks like demand is picking up for the high PoS model again, I am sure iGotSpots will come back and flood the market with clones Grin
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
It's an artificial spike. Not exactly a man made/planned pump. In flow of coins has halted so current coins on market are inflated from demand. It's not a pump by a coin holder by manipulating the market, but a system update based inflation.

As soon as the flood gates/wallet opens, every one with coins will be selling. Very few would be buying.
The value will then drastically drop since the depth isn't there to sustain high value.

I have 389k hbn. I can personally drop the value into the 10-30 satoshi range if I dumped my wallet.


Naw, there is a bitcoin at 300.  It would eat your 389k.. Also during those huge dumps the bots come out and play and create liquidity as well.
member
Activity: 121
Merit: 10
HBN <3
It's an artificial spike. Not exactly a man made/planned pump. In flow of coins has halted so current coins on market are inflated from demand. It's not a pump by a coin holder by manipulating the market, but a system update based inflation.

As soon as the flood gates/wallet opens, every one with coins will be selling. Very few would be buying.
The value will then drastically drop since the depth isn't there to sustain high value.

I have 389k hbn. I can personally drop the value into the 10-30 satoshi range if I dumped my wallet.
newbie
Activity: 14
Merit: 0
Cryptopia still hasn't unfrozen the wallet deposits yet.
Artificial price spike since no one can add coin to the exchange. So the coins on there are "worth more".

Would be amazing is those prices stayed. I could put a down payment on a car Smiley

As soon as the wallet unlocks. Everyone will dump their coins on the price and tank the demand side. Any one not watching their buys will be left holding the bag as it falls. We only have 1.8 BTC in depth before it drops down to 140 satoshi.

A counter argument, to show that it is not a totally cornered market, and would be difficult to corner.

Wallets
471,664 hbn
397,564 hbn
383,744 hbn
150,000 hbn
147,750 hbn
108,455 hbn
100,000 hbn
100,000 hbn
97,276 hbn
89,562 hbn
83,894 hbn
78,619 hbn
74,052 hbn
72,621 hbn
70,948 hbn
68,287 hbn
68,123 hbn
60,380 hbn
56,788 hbn
50,000 hbn
48,309 hbn
47,400 hbn

+ 53 more wallets of at least 10,000 hbn

So if a person tries to take the pump too far they will have to buy a lot of expensive coins.

You are right though, any new person should never buy a coin while deposits are not enabled, because the price can be run up artificially.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
I'm having wallet issues as well. I get the following error

Critical error loading wallet "reset" from wallet-reset.dat: CDB() : cant open
database file wallet-reset.dat, error 22

I had renamed this wallet file a long time ago when doing some coin cleanup to rest all my stakes into one large chunk. I can't seem to get this to work, and google isnt helping. Any tips how to remedy an error 22? thanks

There is no easy way currently to run salvagewallet  on a secondary wallet .If you have a wallet-reset.dat backup, try using that one instead. If not try these steps below.

1) Shutdown client
2) rename wallet.dat to noloadwallet.dat
3) rename wallet-reset.dat to wallet.dat
4) Startclient with -salvagewallet
5) Be patient, after fixing keys, it will rescan 5million blocks, this can take a fair amount of time. Possibly hours depending on your computer.
6) After complete, shutdown client
7) rename your wallet.dat (previously wallet-reset.dat) back to wallet-reset.dat
Cool rename your noloadwallet.dat to wallet.dat
9) start client up
10) do more frequent wallet backups!

You can alway monitor that progress by looking at the debug.log file.

I will work on adding an extra switch to salvagewallet to work on a secondary wallet For version 1.6.

Edit: If you are good with startups switches you can also also do this to save time.
1) Shutdown client
2) Create new dir called C:\hbn_fix
3) copy wallet-reset.dat to c:\hbn_fix\wallet.dat
4) startup client with -salavgewallet -datadir=c:\hbn_fix
5) After client is done and wallet is working, shut it down.
6) rename your wallet-reset.dat in your normal datadir %appdata% to brokewallet-reset.dat
7) Copy your wallet.dat form c:\hbn_fix to your normal datadir as wallet-reset.dat

This method may save a bit of time.

newbie
Activity: 38
Merit: 0
I'm having wallet issues as well. I get the following error

Critical error loading wallet "reset" from wallet-reset.dat: CDB() : cant open
database file wallet-reset.dat, error 22

I had renamed this wallet file a long time ago when doing some coin cleanup to rest all my stakes into one large chunk. I can't seem to get this to work, and google isnt helping. Any tips how to remedy an error 22? thanks
legendary
Activity: 1540
Merit: 1060
May the force bit with you.

OK so I copied over a fresh blockchain
- I deleted the Hobonickels contents from the %appdata% folder
- I started the wallet QT files, It starts the wallet fine, and creates the contents of the HoboNickels folder
- I close the wallet, delete out the 2 Blk..dat files, and the wallet.dat, and the txleveldb dir
- I copy over my wallet.dat, the 2 Blk...dat files, and the txleveldb dir from the new downloaded
- I start the wallet back, and get the same error, I've been getting

Could my wallet.dat be off somehow?  I've got other copies, I can dig out.
Is my process off somewhere?

Is is possible your wallet.dat got corrupted. Have you tried -salvagewallet startup switch ?
member
Activity: 159
Merit: 11
Getting this error on start up

Runaway exception
A fatal error occurred.  HoboNickes can no longer continue safely ....

EXCEPTION: st9bad_alloc
std::bad_alloc

version 1.5.3.0
Windows 7 Pro 32bit

(taking a guess ... this is a 64bit wallet?)



No, it is 32 bit. Will work on just about every Windows. Likley whatever you did for you block chain download was not correct.

You need to replace both blk001.dat and blk0002.dat and the entire txleveldb folder. If you don't do all 3 of these you will get errors as such.


I've uncompressed the ZIP and re-apply the files, made sure the files were in the right place.  Still getting the same error.
C:\....1.5.3.0\HoboNickels-qt.exe in Runaway exception

I copied over the backup'd wallat.dat before the first start up.


Ok mabye those were bad zip file? You can try the one I am doing to hobonickels.info here in a bit, once it is done. I applied it to another computer and it came right up.

post when it is up, and I'll DL and try again.
(glad I checked in here, who knew I had HBN sitting on Cryptopia I bought almost a year ago, small moral victory)

OK so I copied over a fresh blockchain
- I deleted the Hobonickels contents from the %appdata% folder
- I started the wallet QT files, It starts the wallet fine, and creates the contents of the HoboNickels folder
- I close the wallet, delete out the 2 Blk..dat files, and the wallet.dat, and the txleveldb dir
- I copy over my wallet.dat, the 2 Blk...dat files, and the txleveldb dir from the new downloaded
- I start the wallet back, and get the same error, I've been getting

Could my wallet.dat be off somehow?  I've got other copies, I can dig out.
Is my process off somewhere?
member
Activity: 159
Merit: 11
I'm surprised there was that much depth there in the first place.  I figured it'd be staking, and not sitting on an exchange.  I wish I'd had more there.  I didn't realize I had any there until last night.
member
Activity: 121
Merit: 10
HBN <3
Cryptopia still hasn't unfrozen the wallet deposits yet.
Artificial price spike since no one can add coin to the exchange. So the coins on there are "worth more".

Would be amazing is those prices stayed. I could put a down payment on a car Smiley

As soon as the wallet unlocks. Everyone will dump their coins on the price and tank the demand side. Any one not watching their buys will be left holding the bag as it falls. We only have 1.8 BTC in depth before it drops down to 140 satoshi.
Pages:
Jump to: