V12 Release

UdjinM6 crowning
Hi!
Just noticed this, all my masternodes have a quite big debug.logs.
Time scale 4 days and debug.logs are about 165 Mb size.
Logs are mostly filled with this: 2016-01-23 02:50:07 CBudgetVote::SignatureValid() - Unknown Masternode
I can provide debug.log if needed.

UdjinM6 flare

This 'log' problem is still valid after 0.12.0.56 update.
In 4 hours log size is grown to 11 Mb.
Same 2016-01-23 17:14:23 CFinalizedBudgetVote::SignatureValid() - Unknown Masternode fills it.
 
Hi guys! I'm a new member.

My wallet version is v0.12.0.55-c30a0aa (64-bit), how may I update to this new version above? I couldn't find the update button in my Dash Core Wallet.

Thanks!
 
Hi guys! I'm a new member.

My wallet version is v0.12.0.55-c30a0aa (64-bit), how may I update to this new version above? I couldn't find the update button in my Dash Core Wallet.

Thanks!
There is no update button
You have to download V56 from dash.org/downloads
 
Cool, thanks.
Sorry, i didn't bring this earlier, but there is 4 different Unknown Masternode log entry,
can you also check those 3 other, i think all 4 are filling up about equal amount in the log.

2016-01-23 13:59:04 CMasternodePaymentWinner::IsValid - Unknown Masternode xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2016-01-23 13:59:04 mnw - invalid message - Unknown Masternode xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2016-01-23 14:16:10 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, 1), scriptSig=)
2016-01-23 14:16:12 CFinalizedBudgetVote::SignatureValid() - Unknown Masternode

Edit: After 4 hours log size is ~11 Mb, and after 8 hours it is ~15 Mb.
 
Last edited by a moderator:
Cool, thanks.
Sorry, i didn't bring this earlier, but there is 4 different Unknown Masternode log entry,
can you also check those 3 other, i think all 4 are filling up about equal amount in the log.

2016-01-23 13:59:04 CMasternodePaymentWinner::IsValid - Unknown Masternode xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2016-01-23 13:59:04 mnw - invalid message - Unknown Masternode xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2016-01-23 14:16:10 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, 1), scriptSig=)
2016-01-23 14:16:12 CFinalizedBudgetVote::SignatureValid() - Unknown Masternode

Edit: After 4 hours log size is ~11 Mb, and after 8 hours it is ~15 Mb.
First 2 should go away quite fast, last 2 are there for a much longer time since MN is down and both (3 and 4) are in this PR.
 
First 2 should go away quite fast, last 2 are there for a much longer time since MN is down and both (3 and 4) are in this PR.
OK, now 18 hours after update/start, log size is 35 Mb.
So log grow about 2 Mb per hour.
 
28 hours later...

28h_log.png
 
UdjinM6

Does this cure log bloat if i put this to commandline: -debug=alert

Code:
Debugging/Testing options:
  -debug=<category>      Output debugging information (default: 0, supplying <category> is optional)
                         If <category> is not supplied, output all debugging information.
                         <category> can be:
                           addrman, alert, bench, coindb, db, lock, rand, rpc, selectcoins, mempool, net,
                           dash (or specifically: darksend, instantx, masternode, keepass, mnpayments, mnbudget), qt.
 
UdjinM6

Does this cure log bloat if i put this to commandline: -debug=alert

Code:
Debugging/Testing options:
  -debug=<category>      Output debugging information (default: 0, supplying <category> is optional)
                         If <category> is not supplied, output all debugging information.
                         <category> can be:
                           addrman, alert, bench, coindb, db, lock, rand, rpc, selectcoins, mempool, net,
                           dash (or specifically: darksend, instantx, masternode, keepass, mnpayments, mnbudget), qt.
Nope, these options are used to extend log output, not to suppress it
 
Back
Top