• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

V12 Testing Thread

We need patience though, the dev team have bigger fish to fry right now just to get the system to work. Class will have to wait!
 
TanteStefana said:
Ok, so do I have this right? We now need all these program "pieces" in the bin file (save qt if you're using daemon) in the same folder as dashd or dash-qt for the wallet to function? I just moved dash-cli into my folder and it didn't work, so I put dashd in there, and it worked briefly, so now I've put everything into the folder and am hoping it'll work now??

It's a big difference if the above assumption is correct. Please, will someone explain which programs go where during installation? Thanks!

Very weird, when I unpacked to my desktop, the date modified is a screwy. Says 1-9-2014? or April something....? depending on which file :p
Click to expand...

dashd = daemon i.e. the main program (and you can run it in background)
dash-cli = console i.e. the pogram to control daemon (to ask it smth) through rpc when it's already running (and that also means you can have it anywhere, there is no need to copy it to some specific folder)
dash-qt = GUI wallet (GUI + main program)

That date is "static" and used to get deterministic (reproducible) builds every bit of which match no matter who build it if he doesn't modified the source. That way you can build binaries yourself and prove that binaries from official site were build from actual code in repo for example.

TanteStefana said:
I dunno, my dash is crashing on my server. I can't get the masternode to run.

Explain it to me, and I'll do it, Tao LOL
Click to expand...

Yep, there is a buffer overflow issue, should be fixed in next binaries https://github.com/dashpay/dash/pull/360

EDIT: Oh, you already found it on bitcoin site, I should reload page before posting :smile:
 
Ok, gonna come back in a bit when you're all ready, I'll try to write something up on how to use the "new" set up so it's not confusing to others.

UdjinM6, you say we can put the dash-cli program anywhere, but we have to access it via command line from within the folder it resides in, no? Please let me know if that is correct. Thanks!

Also, what are the test versions for? Do we use those instead while testing? Or??? Don't understand their presence. Thanks again! :)
 
testnet p2pool down with error => p2pool.util.jsonrpc.NarrowError: -1 CreateNewBlock() : TestBlockValidity failed
Code: 
2015-06-17 23:42:16.850957  Local: 520kH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-2%) Expected time to share: 1.0 minutes
2015-06-17 23:42:16.851005  Shares: 534 (13 orphan, 41 dead) Stale rate: ~10.1% (7-13%) Efficiency: ~92.9% (89-96%) Current payout: 0.0000 tDASH
2015-06-17 23:42:16.851055  Pool: 1209kH/s Stale rate: 3.2% Expected time to block: 1.2 minutes
2015-06-17 23:42:18.243599 GOT SHARE! yCfdjrP9AySxu8A2m3aFzHwNeAtpSvTSPo 0791721a prev 125b47f5 age 47.47s
2015-06-17 23:42:18.249776 New work for worker yCfdjrP9AySxu8A2m3aFzHwNeAtpSvTSPo! Difficulty: 0.000244 Share difficulty: 0.007324 Total block value: 23.214286 tDASH including 1 transactions
2015-06-17 23:42:19.852901 P2Pool: 970 shares in chain (974 verified/974 total) Peers: 2 (1 incoming)
2015-06-17 23:42:19.852974  Local: 526kH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-2%) Expected time to share: 59.8 seconds
2015-06-17 23:42:19.853009  Shares: 535 (13 orphan, 41 dead) Stale rate: ~10.1% (7-13%) Efficiency: ~92.9% (89-96%) Current payout: 0.0000 tDASH
2015-06-17 23:42:19.853036  Pool: 1201kH/s Stale rate: 3.2% Expected time to block: 1.2 minutes
2015-06-17 23:42:25.856969 P2Pool: 970 shares in chain (974 verified/974 total) Peers: 2 (1 incoming)
2015-06-17 23:42:25.857140  Local: 529kH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-2%) Expected time to share: 59.4 seconds
2015-06-17 23:42:25.857194  Shares: 535 (13 orphan, 41 dead) Stale rate: ~10.1% (7-13%) Efficiency: ~92.9% (89-96%) Current payout: 0.0000 tDASH
2015-06-17 23:42:25.857264  Pool: 1201kH/s Stale rate: 3.2% Expected time to block: 1.2 minutes
2015-06-17 23:42:28.858870 P2Pool: 970 shares in chain (974 verified/974 total) Peers: 2 (1 incoming)
2015-06-17 23:42:28.858956  Local: 533kH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-2%) Expected time to share: 59.0 seconds
2015-06-17 23:42:28.859001  Shares: 535 (13 orphan, 41 dead) Stale rate: ~10.1% (7-13%) Efficiency: ~92.9% (89-96%) Current payout: 0.0000 tDASH
2015-06-17 23:42:28.859039  Pool: 1201kH/s Stale rate: 3.2% Expected time to block: 1.2 minutes
2015-06-17 23:42:31.311990 > Error getting work from dashd:
2015-06-17 23:42:31.312052 > Traceback (most recent call last):
2015-06-17 23:42:31.312087 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 577, in _runCallbacks
2015-06-17 23:42:31.312110 >     current.result = callback(current.result, *args, **kw)
2015-06-17 23:42:31.312131 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1155, in gotResult
2015-06-17 23:42:31.312150 >     _inlineCallbacks(r, g, deferred)
2015-06-17 23:42:31.312169 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1097, in _inlineCallbacks
2015-06-17 23:42:31.312223 >     result = result.throwExceptionIntoGenerator(g)
2015-06-17 23:42:31.312248 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
2015-06-17 23:42:31.312296 >     return g.throw(self.type, self.value, self.tb)
2015-06-17 23:42:31.312330 > --- <exception caught here> ---
2015-06-17 23:42:31.312362 >   File "/home/test/p2pool-dash/p2pool/util/deferral.py", line 41, in f
2015-06-17 23:42:31.312387 >     result = yield func(*args, **kwargs)
2015-06-17 23:42:31.312407 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1097, in _inlineCallbacks
2015-06-17 23:42:31.312426 >     result = result.throwExceptionIntoGenerator(g)
2015-06-17 23:42:31.312445 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
2015-06-17 23:42:31.312465 >     return g.throw(self.type, self.value, self.tb)
2015-06-17 23:42:31.312483 >   File "/home/test/p2pool-dash/p2pool/dash/helper.py", line 30, in getwork
2015-06-17 23:42:31.312502 >     work = yield go()
2015-06-17 23:42:31.312521 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1097, in _inlineCallbacks
2015-06-17 23:42:31.312540 >     result = result.throwExceptionIntoGenerator(g)
2015-06-17 23:42:31.312558 >   File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
2015-06-17 23:42:31.312578 >     return g.throw(self.type, self.value, self.tb)
2015-06-17 23:42:31.312598 >   File "/home/test/p2pool-dash/p2pool/util/jsonrpc.py", line 143, in _http_do
2015-06-17 23:42:31.312627 >     raise Error_for_code(resp['error']['code'])(resp['error']['message'], resp['error'].get('data', None))
2015-06-17 23:42:31.312648 > p2pool.util.jsonrpc.NarrowError: -1 CreateNewBlock() : TestBlockValidity failed
 
TanteStefana said:
Ok, gonna come back in a bit when you're all ready, I'll try to write something up on how to use the "new" set up so it's not confusing to others.

UdjinM6, you say we can put the dash-cli program anywhere, but we have to access it via command line from within the folder it resides in, no? Please let me know if that is correct. Thanks!

Also, what are the test versions for? Do we use those instead while testing? Or??? Don't understand their presence. Thanks again! :)
Click to expand...

I'm not sure I get the question right... you should call it /what/ever/path/is/to/dash-cli some_command OR put it in /usr/bin/ and just use dash-cli some_command from anywhere

EDIT: that ^^^^ is for Linux of course
 
 
Last edited by a moderator:
test dashninja is on 12.0.1
Please note Dashninja is still unable to parse 0.12.0.x data... I had no time yet to work on it.

"overall" : "Successfully started 4 masternodes, failed to start 0, total 4",
 
Got two windows wallets up and started DS mixing.

Edit: Now I'm reindexing my wallets because these wallets were from the last version and they had a different block height than what was on flare's and elbereth's explorers..
 
Last edited by a moderator:
TanteStefana said:
Ok, gonna come back in a bit when you're all ready, I'll try to write something up on how to use the "new" set up so it's not confusing to others.

UdjinM6, you say we can put the dash-cli program anywhere, but we have to access it via command line from within the folder it resides in, no? Please let me know if that is correct. Thanks!

Also, what are the test versions for? Do we use those instead while testing? Or??? Don't understand their presence. Thanks again! :)
Click to expand...
It isn't really taht confusing. You basically only use dashd to start the daemon. All your other interaction is just now done with dash-cli.

So before it was dashd getinfo now it's dash-cli getinfo all of the "interaction" with the daemon is simply done with a different program. This makes it more robust so that teh daemon runs individually from the rest of the code querying it.
 
OK, I'm up and running with v12, but I haven't been on Testnet in a really long time so I am encountering a "No block source available" message. Do I have to add a specific node to the dash.conf?
 
TaoOfSatoshi said:
OK, I'm up and running with v12, but I haven't been on Testnet in a really long time so I am encountering a "No block source available" message. Do I have to add a specific node to the dash.conf?
Click to expand...

If you go to Tools -> Debug Console, then type:

setgenerate true

this will start you CPU mining, likely the blockchain needs a little nudge ;-)

Submitted a Pull Request to fix the Available + Pending labels on the overview page, everything else looking and working great so far!
 
snogcel said:
If you go to Tools -> Debug Console, then type:

setgenerate true

this will start you CPU mining, likely the blockchain needs a little nudge ;-)

Submitted a Pull Request to fix the Available + Pending labels on the overview page, everything else looking and working great so far!
Click to expand...


ALL CORES
setgenerate true -1

1 CORE
setgenerate true 1



don't burn up your lappy
 
THANK YOU !!!!

For starting/changing: Coin Selection in LIST MODE :)
It's the little things that make me happy
...and all the new tool tabs :-D
 
snogcel said:
If you go to Tools -> Debug Console, then type:

setgenerate true

this will start you CPU mining, likely the blockchain needs a little nudge ;-)

Submitted a Pull Request to fix the Available + Pending labels on the overview page, everything else looking and working great so far!
Click to expand...
Thanks, tried it, but my wallet still staring at me wondering when I'm going to give it a block source...:mad: I'm going to bed now. Cheers.
 
coingun said:
It isn't really taht confusing. You basically only use dashd to start the daemon. All your other interaction is just now done with dash-cli.

So before it was dashd getinfo now it's dash-cli getinfo all of the "interaction" with the daemon is simply done with a different program. This makes it more robust so that teh daemon runs individually from the rest of the code querying it.
Click to expand...
It's very simple, I understand, however, it is incomprehensible if nobody explains it to a lay person like myself and most of the other users / masternode owners out there ;) We kind of need it all explained with no ambiguity ;) LOL :)
 
Hi guys, i have joined Testnet its my 1st time to help test

Ubuntu x64 dash-qt started and syncing as we speak

Glad to help, just say if you need anything
 
You must log in or register to reply here.
Back
Top