v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.
A great way to check your logs is to do this. Start Darkcoin Daemon on testnet and then do:
Code: 
cd ~/.darkcoin/testnet3
tail -f debug.log | grep "CheckBlock()"
This will keep a terminal window open that will immediately list any instances of the above string.

Edit:
Also could I have money? n1SVYuRxfX4f3kMr6d8bDgYZgh3nWzgFBz
 
don't spend it all at one place!

Also, anyone know why I can't get my darkcoind to finish downloading blocks? I tried reindex severaltimes, deleted chain and block, added addnode= and took 'em all away except the 25.25.xx.xx one, and I can't get them to load the whole block chain

should I just not use 10.9 ?
 
Propulsion said:
A great way to check your logs is to do this. Start Darkcoin Daemon on testnet and then do:
Code: 
cd ~/.darkcoin/testnet3
tail -f debug.log | grep "CheckBlock()"
This will keep a terminal window open that will immediately list any instances of the above string.

Edit:
Also could I have money? n1SVYuRxfX4f3kMr6d8bDgYZgh3nWzgFBz
Click to expand...

3000 DRK sent. Thanks for the code.
 
I just checked my debug log, and found 2 CheckBlock() proof of work failed, is that something Evan would want?
 
Propulsion said:
A great way to check your logs is to do this. Start Darkcoin Daemon on testnet and then do:
Code: 
cd ~/.darkcoin/testnet3
tail -f debug.log | grep "CheckBlock()"
This will keep a terminal window open that will immediately list any instances of the above string.
Click to expand...
That's not gonna work because the stdout of tail -f never ends and grep will never be executed. All this does is occupy your terminal!

Ignore this, I tried it and it obviously works. I'm pretty sure that it didn't when I last tried this. That was on a Debian system, though.
 
Last edited by a moderator:
Wouldn't have thought that there's a difference.. It works via 2 SSH sessions or using screen. But won't work using the local terminal of my Debian VM.
I'm pretty sure there's an easy explanation for this though. I have to admit that my knowledge of pipes is rather shallow :/

Anyway, there were about 15 CheckBlock errors logged during ~6h.
 
Code: 
       "subver" : "/Satoshi:0.10.8.11/",
        "subver" : "/Satoshi:0.10.8.11/",
        "subver" : "/Satoshi:0.10.8.11/",
        "subver" : "/Satoshi:0.10.8.11/",
        "subver" : "/Satoshi:0.9.4.11/",
        "subver" : "/Satoshi:0.9.4.11/",
        "subver" : "/Satoshi:0.9.4.11/",
        "subver" : "/Satoshi:0.9.4.11/",
        "subver" : "/Satoshi:0.9.4.11/",
        "subver" : "/Satoshi:0.9.4.11/",
        "subver" : "/Satoshi:0.9.5/",
        "subver" : "/Satoshi:0.9.5/",
        "subver" : "/Satoshi:0.9.5/",
        "subver" : "/Satoshi:0.9.5/",
        "subver" : "/Satoshi:0.9.5/",

not yet updated...

I should make a stat page(actually doing now)
 
daaarkcoins said:
Wouldn't have thought that there's a difference.. It works via 2 SSH sessions or using screen. But won't work using the local terminal of my Debian VM.
I'm pretty sure there's an easy explanation for this though. I have to admit that my knowledge of pipes is rather shallow :/
....
Click to expand...

If you're using -printtoconsole, a patch was made recently to bitcoin that fixes this problem:
https://github.com/bitcoin/bitcoin/commit/283e405c063acfca304acbff505badcbbcb814c9

edit(testnet):
sometimes when my P2Pool node sends submitblocks to the daemon i get the error:
ERROR: AcceptBlock() : incorrect proof of work

Anyone else notice that? P2pool global stale rate is also creeping up, but I have only 3 peers connected.
 
Last edited by a moderator:
hmmm, mpos pool forked.
I will make another nomp pool with rc binary.
 
Last edited by a moderator:
Still just 2 of us with MN on testnet? Am I on the proper chain?

Code: 
ubuntu@ip-10-252-204-115:~$ darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 1760.50030000,
    "blocks" : 12556,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 1.15982939,
    "testnet" : true,
    "keypoololdest" : 1401626368,
    "keypoolsize" : 99,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
ubuntu@ip-10-252-204-115:~$ darkcoind masternode list
{
    "54.76.47.232:19999" : 1,
    "54.203.217.224:19999" : 1
}
ubuntu@ip-10-252-204-115:~$ darkcoind masternode votes
{
    "12555" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12556" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG",
    "12557" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12558" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12559" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12560" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12561" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12562" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG",
    "12563" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG",
    "12564" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG"
}
ubuntu@ip-10-252-204-115:~$
 
If you are having trouble syncing the testnet chain then you need to add nodes.
To do this in qt go to the debug window and type in "addnode [ip address] add"
To do this in console do "./darkcoind addnode [ip address] add"
Here's some nodes:
23.23.186.131
54.183.73.24
54.198.19.83
54.76.47.232
54.203.217.224
Example Included.
Code: 
./darkcoind addnode 54.203.217.224 add
 
jimbit said:
Still just 2 of us with MN on testnet? Am I on the proper chain?

Code: 
ubuntu@ip-10-252-204-115:~$ darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 1760.50030000,
    "blocks" : 12556,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 1.15982939,
    "testnet" : true,
    "keypoololdest" : 1401626368,
    "keypoolsize" : 99,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
ubuntu@ip-10-252-204-115:~$ darkcoind masternode list
{
    "54.76.47.232:19999" : 1,
    "54.203.217.224:19999" : 1
}
ubuntu@ip-10-252-204-115:~$ darkcoind masternode votes
{
    "12555" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12556" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG",
    "12557" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12558" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12559" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12560" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12561" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
    "12562" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG",
    "12563" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG",
    "12564" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG"
}
ubuntu@ip-10-252-204-115:~$
Click to expand...
compare your height to http://23.23.186.131:1234/chain/DarkCoin
 
jimbit said:
looks like it is me soloing: mmdysz5PhmC36uF6fzp9GVuFMK9SPnEzTk

On a windows box with the current darksend qt client.

edit: would you rather have me mining on the pool? or stay solo?
Click to expand...

I rename your address to jimbit_qt_solo :)
I think qt solo is more helpful.
 
well, one of my masternodes is off the chain again after I got both of them working, should I fix this, or should I send in my debug?
 
I was having trouble syncing the testnet chain on onde masternode. I tried everithing proposed in this thread with no success.
So I used the stable version to synchronize, no problems there, and then updated the binary to rc3.
Still synchronized :smile:

Can anyone send 1k to msBm7XEsX4x5DSkLcC44tayXS3hYyN8wBR so I can start the masternode? Thks

PS- 1k received! thank you
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top