v0.11.2.x Testing
- Thread starter eduffield
- Start date
crowning
Well-known member
Could be VMware reporting false max sizes to the guest-OS. Or not updating the new size information correctly.
Anyway, I'll check this one with VirtualBox (because I'm already using it for other tests) and if it's not reproducible there I'll install VMware.
Is it just me or do you all also want to see the little "Digital Cash" Tag underneath the logo on start-up. I tend to use the term Digital Cash a lot more outside of this very small cryptoverse. I have also had others inside the cryptoverse say they are confused by Digital Cash.
I'm not sure where the confusion is. Am I correct in calling it either Digital Cash or Dash as they are essentially synonymous? Probably the wrong place to ask this but i've been curious and perhaps we should give the community some clarification.
I'm not sure where the confusion is. Am I correct in calling it either Digital Cash or Dash as they are essentially synonymous? Probably the wrong place to ask this but i've been curious and perhaps we should give the community some clarification.
Also make sure you have the lastest vmware tools as well sometimes people forget to install the tools on linux and so the resolutions don't change up nicely.
Could be, just saying, first time this is happening
Almost but later part is quite the opposite actually :smile: PoSe scores is basically an "Error count". So 1% of network check another 1% of network and applies score accordingly. Once you reach some threshold (now it's 6) you will not be count as enabled and as a result you will not be in payment schedule.
eduffield
Core Developer
******************** TESTNET : 11.2.11 - All Users *********************************
- Masternode fixes - Udjin
- CSS / Styling fixes / overview tx table update - Crowning/Snogcel
- Removed DS limit - Udjin
- nScanningErrorCount / nLastScanningErrorBlockHeight storage fixes - Udjin
** Compiling - if you get a 404 try again in a bit
Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-150/gitian-win-darkcoin-bin/32/dash-qt.exe
Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...1/gitian-osx-dash-dist/dash-0.11.2.11-osx.dmg
Linux 32bit:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-155/gitian-linux-dash-bin/bin/32/dash-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-155/gitian-linux-dash-bin/bin/32/dashd
Linux 64bit
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-155/gitian-linux-dash-bin/bin/64/dash-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-155/gitian-linux-dash-bin/bin/64/dashd
- Masternode fixes - Udjin
- CSS / Styling fixes / overview tx table update - Crowning/Snogcel
- Removed DS limit - Udjin
- nScanningErrorCount / nLastScanningErrorBlockHeight storage fixes - Udjin
** Compiling - if you get a 404 try again in a bit
Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-150/gitian-win-darkcoin-bin/32/dash-qt.exe
Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...1/gitian-osx-dash-dist/dash-0.11.2.11-osx.dmg
Linux 32bit:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-155/gitian-linux-dash-bin/bin/32/dash-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-155/gitian-linux-dash-bin/bin/32/dashd
Linux 64bit
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-155/gitian-linux-dash-bin/bin/64/dash-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-155/gitian-linux-dash-bin/bin/64/dashd
Keep up the great work guys. Been nailing it!
hmm... took 25 secs for me... anyone else?
404. :wink: url should be:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-150/gitian-win-dash-bin/32/dash-qt.exe
:smile:
Having issues with latest win build (url above).
First launch stuck "out of sync" with 0 hours remaining.
Launched with -reindex, hung at 6 weeks ago for over a half hour.
Deleted blocks/chainstate folders, launched, churning with many (windows) "not responding" messages.
This wallet has a LOT of addresses/txns from mining.
Previous builds didn't have this issue.
It's behaving like my 11.1.25 wallet. (which also has a ton of addresses/txns)
First launch stuck "out of sync" with 0 hours remaining.
Launched with -reindex, hung at 6 weeks ago for over a half hour.
Deleted blocks/chainstate folders, launched, churning with many (windows) "not responding" messages.
This wallet has a LOT of addresses/txns from mining.
Previous builds didn't have this issue.
It's behaving like my 11.1.25 wallet. (which also has a ton of addresses/txns)
Also, on linux masternodes, am occasionally (10% of nodes) getting:
Am having to delete mncache.dat and restart.
Code:
2015-03-24 16:39:13 Verifying mncache.dat format...
2015-03-24 16:39:13 ERROR: Read : Deserialize or I/O error - non-canonical ReadCompactSize()
2015-03-24 16:39:13 Masternode cache file mncache.dat has invalid format
2015-03-24 16:39:13 Shutdown : doneAm having to delete mncache.dat and restart.
That's ok, delete mncache.dat once and it should be good (you will need to delete it once again on next release but that should be the last time I believe)
And that is not ok. Delete peers.dat and try again.
PS. look like testnet stuck with no new blocks at low diff ~1hour ago https://test.dashninja.pl/blocks.html#blocksdetail
PPS. I just mined a block with my mid 2010 macbook lol
Also, need to report some linux masternodes hanging.
Having to kill -9 and restart.
(dashd is symlinked to darkcoind)
Nothing telling in logs:
Having to kill -9 and restart.
(dashd is symlinked to darkcoind)
Nothing telling in logs:
Code:
ubuntu@node-71:~/testnet$ ./darkcoind -datadir=. getinfo
^C
ubuntu@node-71:~/testnet$ tail testnet3/debug.log
2015-03-24 17:42:42 dsq - new Darksend queue object - 107.170.242.110:19999
2015-03-24 17:42:51 CDarksendPool::Check() - entries count 0
2015-03-24 17:43:01 CDarksendPool::Check() - entries count 0
2015-03-24 17:43:03 dsee - Got NEW Masternode entry 172.245.5.168:19999
2015-03-24 17:43:03 dsee - Accepted Masternode entry -1 -1
2015-03-24 17:43:03 CMasternodeMan: Adding new Masternode 172.245.5.168:19999 - 147 now
2015-03-24 17:43:07 dsee - Got NEW Masternode entry 172.245.5.188:19999
2015-03-24 17:43:07 dsee - Accepted Masternode entry -1 -1
2015-03-24 17:43:07 CMasternodeMan: Adding new Masternode 172.245.5.188:19999 - 148 now
2015-03-24 17:43:11 CDarksendPool::Check() - entries count 0
ubuntu@node-71:~/testnet$ date
Tue Mar 24 13:52:47 EDT 2015
ubuntu@node-71:~/testnet$ kill -9 18985
ubuntu@node-71:~/testnet$ ./darkcoind -datadir=.
Dash server startingDone. same issue. Care to try with my uber-tdrk-rich wallet.dat? :wink:
I would LOVE for this issue to be solved once and for all!
[email protected]
are you sure you are on latest version? that was a known issue and should be fixed now...
[email protected]
are you sure you are on latest version? that was a known issue and should be fixed now...
Sent!
And yes. Feels like a regression.
Code:
ssh 080 'cd testnet; ./darkcoind -datadir=. getinfo'
{
"version" : 110211,
"protocolversion" : 70075,
"walletversion" : 61000,
"balance" : 1417.40004000,
"darksend_balance" : 0.00000000,
"blocks" : 25273,
"timeoffset" : 0,
"connections" : 9,
"proxy" : "",
"difficulty" : 0.01531988,
"testnet" : true,
"keypoololdest" : 1425796679,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}hmmm...
PS. 50+ Mb wallet
EDIT: Well.. it's a reeealy slow wallet. My "small" 10 Mb wallet reindex with no problems... will take a look deeper but that
is quite an edge case if you ask me :wink:
Last edited by a moderator:
hmmm...
PS. 50+ Mb wallet
I *did* say "LOTS", hehe.
But seriously, my mainnet wallet has grown to 66 megs within a couple months through normal (albeit heavy) use.
It's a few hundred receiving addresses plus a bunch of mixing.