V12 Testing Thread

yea proposals on Mainnet that can be seen on a webpage or it would be nice to see them inside of the Dash wallet, maybe make a tab for it.
 
  • Like
Reactions: AjM
bluebit said:
yea proposals on Mainnet that can be seen on a webpage or it would be nice to see them inside of the Dash wallet, maybe make a tab for it.
Click to expand...
If you get on Testnet and type this on the console you will see the proposals on Testnet: mnbudget show.
or from the commandline: dash-cli mnbudget show
 
If anyone wonders what "dash-tx.exe" does... Because Dash is now a fork from Bitcoin, here's the answer for it:

https://bitcoin.stackexchange.com/q...bitcoin-core-v0-10-0-bitcoin-tx-createrawtran

This can also answer "what's the difference between dashd and dash-qt":

https://bitcoin.stackexchange.com/q...en-bitcoind-and-bitcoin-qt-different-commands

Answers for test_dashd and a test_dash-qt:

https://bitcoin.stackexchange.com/questions/35548/what-are-test-bitcoin-exe-and-test-bitcoin-qt-exe

Difference between dash-tx, dash-cli, and dashd:

https://bitcoin.stackexchange.com/q...e-between-bitcoin-tx-bitcoin-cli-and-bitcoind
 
Last edited by a moderator:
I think there is a string overflowing on the automated backup... See screen shot...

auto-backup.jpg
 
Here's a good one. Updated a cold masternode.

E5BIYk3.png


Can't stop using ./dash-cli stop, so I kill -9 the process. Here is the end of the debug.log:

jENrLRD.png


Any clues for me?
 
oaxaca said:
Here's a good one. Updated a cold masternode.

E5BIYk3.png


Can't stop using ./dash-cli stop, so I kill -9 the process. Here is the end of the debug.log:

jENrLRD.png


Any clues for me?
Click to expand...
I guess the node is still in process indexing, height 232800 is only 87% - give it some time to complete to height 320000
 
Not sure whether to call this an issue or a feature:

When using: Menu -> Tools -> Wallet Repair -> Salvage wallet, all Labels & Addresses consolidate into one default address.
Here are before and after screenshots of using: Menu -> File -> Receiving addresses... :

Before:
capture_003_17082015_012637.jpg


After:
capture_004_17082015_013208.jpg
 
Since updated to V.45 approx 24 hrs ago I have kept 3 wallets running, and have had different ones at different times lose sync with the blockchain - it always seems to happen at Superblocks budget cycle blocks (or whatever they're called) eg. stuck on 84349, stuck on 85299. Using -reindex (with or without deleting everything) doesn't seem to help - get "Synchronization failed..." ; however, -reindex, then -salvage wallet does the trick...
Thx again crowning for those menu options!

Edit: I beleive they're called "budget cycle block"
 
Last edited by a moderator:
Testnet running v0.12.0.45-b2b2cef win32. MN wallets were updated and synced, then shut down for a few hours. When restarted, wallets got to the current block height then got the message "Synchronization failed". These are the last line in one of the debug logs:

"2015-08-17 12:39:56 ProcessNewBlock : ACCEPTED
2015-08-17 12:39:56 UpdateTip: new best=00000042cfa50dad4de35e58107a9a6b0fb34572109be4481b8c25f5e4c87da4 height=85668 log2_work=43.557896 tx=116660 date=2015-08-17 12:39:39 progress=0.999999 cache=346
2015-08-17 12:39:56 ProcessNewBlock : ACCEPTED
2015-08-17 12:39:59 CMasternodeSync::process - ERROR - Sync has failed, will retry later
2015-08-17 12:40:09 CMasternodeMan::AskForMN - Asking node for missing entry, vin: CTxIn(COutPoint(66eb54fc004c69c3ee0c9688a9f0910c3b5504565bda9094b7a08a5747ff5510, 0), scriptSig=)
2015-08-17 12:40:09 mnb - Got NEW Masternode entry - 2b732c9fbaf5134f9828cc85b10bc1bca75417bde1ee7be5ea329202030017b5 - 107.170.146.58:19999 - CTxIn(COutPoint(66eb54fc004c69c3ee0c9688a9f0910c3b5504565bda9094b7a08a5747ff5510, 0), scriptSig=) - 1439518015 "

EDIT: On the other hand, another MN wallet in the same scenario just got synced through fine, no problem.....

EDIT: Deleting peers.dat and mncache.dat fixed the sync problem.
 
Last edited by a moderator:
buster said:
No problem. I'll try to get it done before I leave on Wednesday for a few days. cant make any promises. It's gonna be a short one though, just a few commands using the dash-cli. And it wont be any masternode commands. Does that work?
Click to expand...
Sure. That will be great. Thank you! :)
 
Hmm... I haven't seen that with my wallet.. i've been opening and shutting it down. Just opened it again and let it sit and see... but haven't seen anything. I haven't tested the encryption though.
 
moli said:
Hmm... I haven't seen that with my wallet.. i've been opening and shutting it down. Just opened it again and let it sit and see... but haven't seen anything. I haven't tested the encryption though.
Click to expand...

God, I hate Microsoft...

A long time ago, I used to be a "software breaker". We would try anything to make our code explode. When we were ready to release something, my boss would proclaim it to be sailor-proof. The meaning was that even a drunken sailor running the software couldn't crash it.

Microsoft products always gave me the hardest time...
 
Last edited by a moderator:
thelazier said:
I just did a quick search on google and found same problem occurred with bitcoin wallet as well. They identified this as wallet file corrupted and can be solved with -salvagewallet.
Click to expand...

That's what I thought. Thanks. Now, I'll see if I can "corrupt" another wallet. Just for fun you understand.
 
You must log in or register to reply here.
Back
Top