Author

Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 355. (Read 782375 times)

sr. member
Activity: 1274
Merit: 250
PredX - AI-Powered Prediction Market
v2.1.2.0 is still randomly crashing on Windows 10.........also getting 'Fatal error' whenever I exit the wallet.

I have tried deleting everything (except 3 files).......but no luck. Not good.

I had the same thing.  It corrupted the wallet.dat so I deleted it and replaced it with a backup.  Synced from fresh with no nodes and just the backup wallet, darknet.conf and masternodes.conf.

All is synced, masternodes running and MN payment incoming.

My wallet corruption happened after I tried to unlock the wallet.

Everything seems to be running smoothly for me now.  Give it a go and see if it works for you.

EDIT:  
Just had a crash but no corruption of either the wallet or blockdata

getblockhash 260259

d56608b91036ad724b82f0f272260d5f11e1afc40870fcc8029069f3db6abed1

EDIT:

Seems to be moving along nicely now.  Smiley

getblockhash 260269

b347d97409c802da53d25934e6d31c068305e8ee6006da686790f108646d0852


Thanks for the tip. It worked!

Did you try v2.1.1.0 last night?  I have a feeling it was that release that corrupted the wallet.dat because it would open the file on close.

I might be wrong but anyone that was testing last night on v 2.1.1.0 might want to replace the wallet.dat with a backup just as a precaution.

Yes, I did try v 2.1.1.0.
legendary
Activity: 1078
Merit: 1011
What coin? For 10 days it does not work. The latest version of the purse, does not synchronize, delete the old block, is not helping.

Remove all addnode addresses from darknet.conf
Then delete all but darknet.conf, masternodes.conf and wallet.dat (use a backed up copy if possible) make sure you are using the latest version of the wallet from the 1st page of this ANN.

WALLET VERSION: 1.1.0.1 Huh http://darknet-crypto.com/?page_id=28

All done, is 2.1.1
No synchronization.
Someone even synchronized?
And what happened to this coin that 10 days, developers can not fix?


You are using an old wallet, the correct version is v2.1.2.0

https://github.com/Darknet-Crypto/Darknet/releases
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
What coin? For 10 days it does not work. The latest version of the purse, does not synchronize, delete the old block, is not helping.

Remove all addnode addresses from darknet.conf
Then delete all but darknet.conf, masternodes.conf and wallet.dat (use a backed up copy if possible) make sure you are using the latest version of the wallet from the 1st page of this ANN.

WALLET VERSION: 1.1.0.1 Huh http://darknet-crypto.com/?page_id=28

All done, is 2.1.1
No synchronization.
Someone even synchronized?
And what happened to this coin that 10 days, developers can not fix?
sr. member
Activity: 448
Merit: 250
What coin? For 10 days it does not work. The latest version of the purse, does not synchronize, delete the old block, is not helping.

Remove all addnode addresses from darknet.conf
Then delete all but darknet.conf, masternodes.conf and wallet.dat (use a backed up copy if possible) make sure you are using the latest version of the wallet from the 1st page of this ANN.
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
What coin? For 10 days it does not work. The latest version of the purse, does not synchronize, delete the old block, is not helping.
sr. member
Activity: 448
Merit: 250
v2.1.2.0 is still randomly crashing on Windows 10.........also getting 'Fatal error' whenever I exit the wallet.

I have tried deleting everything (except 3 files).......but no luck. Not good.

Only time I recall seeing this is if there is something wrong with the wallet.dat file, when it goes to write to the wallet on exit..

Restored wallet.dat from backup......works fine now....staking is also active. I guess previous versions corrupted it.

Me too!!! I had the same problem and your tip worked perfectly.

So isn't it time to congratulate the devs for their great work and enjoy?

W(ell)C(oded) devs!

btw now I can compile my own wallet Cool

Compiling wallets is a useful skill to have.  Smiley I think the last week of madness is going to work in our favour.  We now have more community members developing skill sets that will further strengthen the project.  With such a hard working Dev team and dedicated community I think DNET has a very bright future.

I am definatly going to be sticking around.  Smiley
full member
Activity: 226
Merit: 100
Sure that it was the previous wallet that corrupted the wallet. right now it works perfectly.

I tried to go there : http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
to cast my vote for the proposal. nothing, seems to be buggy.

then tried in the console:

mnbudget show

and it returned nothing too.

So what's up with the proposal? have they been deleted with the updates?

then there is still a pool tab on the OP: useless now Cheesy.

Yeah, the wallet that provides the data for that masternode info page is down right now, should be back up later on today, I would think.

Good catch. The budget info is saved in budget.dat, with everyone deleting theirs it looks like all budget info is gone. I will see if using one from a backed up data directory will save things, but I am not holding my breath, may have to start from scratch there.

The pool section is useless, another good catch, thanks for keeping us on our toes. It will get removed shortly.

It is looking like you guys have come to the same conclusions and fixes regarding the crashing wallets and corrupted wallet.dat files, good job helping each other out.

If anyone notices anything else let us know, thanks.
hero member
Activity: 728
Merit: 500
crashed again

2016-08-18 17:46:06 getblocks 259960 to end limit 500 from peer=8
2016-08-18 17:46:08 getblocks 259982 to end limit 500 from peer=8
2016-08-18 17:46:08 ERROR: ReadBlockFromDisk(CBlock&, CBlockIndex*) : GetHash() doesn't match index
sr. member
Activity: 854
Merit: 277
liife threw a tempest at you? be a coconut !
Sure that it was the previous wallet that corrupted the wallet. right now it works perfectly.

I tried to go there : http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
to cast my vote for the proposal. nothing, seems to be buggy.

then tried in the console:

mnbudget show

and it returned nothing too.

So what's up with the proposal? have they been deleted with the updates?

then there is still a pool tab on the OP: useless now Cheesy.
hero member
Activity: 525
Merit: 500
I restored an old copy of my wallet.dat file and that fixed it. But it locks up on me when I do the masternode start-missing

You are much better off using start-alias.

Why do I need to unlock my wallet after each time I run the start-alias command?
Thats how it works for security reasons. If you know you need to issue a couple of commands and dont want it to lock right after a privileged command you can do (via Tools  > Debug console)
Quote
walletpassphrase "passphrase" timeout

What do I enter in place of "timeout"?
sr. member
Activity: 448
Merit: 250
v2.1.2.0 is still randomly crashing on Windows 10.........also getting 'Fatal error' whenever I exit the wallet.

I have tried deleting everything (except 3 files).......but no luck. Not good.

I had the same thing.  It corrupted the wallet.dat so I deleted it and replaced it with a backup.  Synced from fresh with no nodes and just the backup wallet, darknet.conf and masternodes.conf.

All is synced, masternodes running and MN payment incoming.

My wallet corruption happened after I tried to unlock the wallet.

Everything seems to be running smoothly for me now.  Give it a go and see if it works for you.

EDIT:  
Just had a crash but no corruption of either the wallet or blockdata

getblockhash 260259

d56608b91036ad724b82f0f272260d5f11e1afc40870fcc8029069f3db6abed1

EDIT:

Seems to be moving along nicely now.  Smiley

getblockhash 260269

b347d97409c802da53d25934e6d31c068305e8ee6006da686790f108646d0852


Thanks for the tip. It worked!

Did you try v2.1.1.0 last night?  I have a feeling it was that release that corrupted the wallet.dat because it would open the file on close.

I might be wrong but anyone that was testing last night on v 2.1.1.0 might want to replace the wallet.dat with a backup just as a precaution.
sr. member
Activity: 854
Merit: 277
liife threw a tempest at you? be a coconut !
v2.1.2.0 is still randomly crashing on Windows 10.........also getting 'Fatal error' whenever I exit the wallet.

I have tried deleting everything (except 3 files).......but no luck. Not good.

Only time I recall seeing this is if there is something wrong with the wallet.dat file, when it goes to write to the wallet on exit..

Restored wallet.dat from backup......works fine now....staking is also active. I guess previous versions corrupted it.

Me too!!! I had the same problem and your tip worked perfectly.

So isn't it time to congratulate the devs for their great work and enjoy?

W(ell)C(oded) devs!

btw now I can compile my own wallet Cool
sr. member
Activity: 1274
Merit: 250
PredX - AI-Powered Prediction Market
v2.1.2.0 is still randomly crashing on Windows 10.........also getting 'Fatal error' whenever I exit the wallet.

I have tried deleting everything (except 3 files).......but no luck. Not good.

I had the same thing.  It corrupted the wallet.dat so I deleted it and replaced it with a backup.  Synced from fresh with no nodes and just the backup wallet, darknet.conf and masternodes.conf.

All is synced, masternodes running and MN payment incoming.

My wallet corruption happened after I tried to unlock the wallet.

Everything seems to be running smoothly for me now.  Give it a go and see if it works for you.

EDIT:  
Just had a crash but no corruption of either the wallet or blockdata

getblockhash 260259

d56608b91036ad724b82f0f272260d5f11e1afc40870fcc8029069f3db6abed1

EDIT:

Seems to be moving along nicely now.  Smiley

getblockhash 260269

b347d97409c802da53d25934e6d31c068305e8ee6006da686790f108646d0852


Thanks for the tip. It worked!
sr. member
Activity: 1274
Merit: 250
PredX - AI-Powered Prediction Market
v2.1.2.0 is still randomly crashing on Windows 10.........also getting 'Fatal error' whenever I exit the wallet.

I have tried deleting everything (except 3 files).......but no luck. Not good.

Only time I recall seeing this is if there is something wrong with the wallet.dat file, when it goes to write to the wallet on exit..

Restored wallet.dat from backup......works fine now....staking is also active. I guess previous versions corrupted it.
hero member
Activity: 661
Merit: 500
Windows wallet keeps crashing here too Sad

Block database corrupted error.

Same. Have wallet.dat backups but my wallet is jacked up.
hero member
Activity: 728
Merit: 500
2016-08-18 16:40:19 ERROR: ReadBlockFromDisk(CBlock&, CBlockIndex*) : GetHash() doesn't match index
2016-08-18 16:40:19 ERROR: VerifyDB() : *** ReadBlockFromDisk failed at 260365, hash=717090b1f02c717ddc5b03dfae25586a967290b85d8eaf6c5ec488bb202fffe2
2016-08-18 16:40:26 Aborted block database rebuild. Exiting.

wimdows wallet crashing still.
sr. member
Activity: 474
Merit: 252
I restored an old copy of my wallet.dat file and that fixed it. But it locks up on me when I do the masternode start-missing

You are much better off using start-alias.

Why do I need to unlock my wallet after each time I run the start-alias command?
Thats how it works for security reasons. If you know you need to issue a couple of commands and dont want it to lock right after a privileged command you can do (via Tools  > Debug console)
Quote
walletpassphrase "passphrase" timeout
hero member
Activity: 525
Merit: 500
I restored an old copy of my wallet.dat file and that fixed it. But it locks up on me when I do the masternode start-missing

You are much better off using start-alias.

Why do I need to unlock my wallet after each time I run the start-alias command?
member
Activity: 90
Merit: 10
My Win32-QT (latest version) stays syncing forever @ block 259399.

Any tips?

thx,
sr. member
Activity: 448
Merit: 250
v2.1.2.0 is still randomly crashing on Windows 10.........also getting 'Fatal error' whenever I exit the wallet.

I have tried deleting everything (except 3 files).......but no luck. Not good.

Only time I recall seeing this is if there is something wrong with the wallet.dat file, when it goes to write to the wallet on exit..

The last wallet release was doing something to the wallet, it kept opening up the file in notepad++ when I closed the wallet.  The corruption happened just once with the new wallet.

I just had another block corruption which happened the same time my masternode had a disk space error closing ./darknetd

I'll let it resync and wait for Paul to sort out the node before starting it in the desktop wallet.
Jump to: