v0.11.0 - Darkcoin Core Release

jpr

Active Member
May 11, 2014
493
393
133
Are you guys monitoring your nodes using drk.mn? Or checking status using SSH?
I mean, how do you know your nodes stopped went offline?
 

coingun

Active Member
Masternode Owner/Operator
Jul 8, 2014
489
402
133
masternode.io
Yep. local wallet is .11 Mac. Updating that was the 1st thing I did. Deleted peers.dat on all locals and MNs. Even tried doing a full restart on two of the nodes, no change in behavior.
Nodes are now dropping off the masternode list, which makes sense it's been just over an hour. So they are definitely not active
I'm having the exact same experience with the Mac v11.0.11 client. Masternodes send start successfully show up in the list but then they are dropping out. The complete disregard for mac users of the wallets is how do I put it... annoying?
 

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
I'm having the exact same experience with the Mac v11.0.11 client. Masternodes send start successfully show up in the list but then they are dropping out. The complete disregard for mac users of the wallets is how do I put it... annoying?
It's not just mac users having this problem.
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
so i waited 2 hours until masternode disappeared from the list. Then started daemon and activation from scratch and now I successful get the "
2015-01-21 21:33:18 CActiveMasternode::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
" message
I've tested v0.11.0.11 with a remote masternode and everything seems to function correctly, nothing was changed that would cause any problems.

However if you run "masternode start" on a remotely activated masternode, it's state will be reset and it'll stop pinging (this existed on all v11 versions). This will be fixed in v0.11.0.12, for the time being if you see "EnableHotColdMasterNode" in the log it should be fine.
 

coingun

Active Member
Masternode Owner/Operator
Jul 8, 2014
489
402
133
masternode.io
This will be fixed in v0.11.0.12, for the time being if you see "EnableHotColdMasterNode" in the log it should be fine.
And if you are unable to achieve this? Do you have any suggestions. We have multiple people reporting they aren't ever able to get this expected behavior from windows or mac local mn wallets.
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
I've found that doing start-many won't propagate my MN's unless I issue the start-many command within around 30 seconds of starting the remote daemons.

It appears to be if the remote daemons are updated and fully synced, it seems to disregard the local start-many command. It seems to only accept it while syncing up and retrieving the MN list.
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
And if you are unable to achieve this? Do you have any suggestions. We have multiple people reporting they aren't ever able to get this expected behavior from windows or mac local mn wallets.
I've just made a masternode from scratch on windows and successfully started a remote machine on linux, which in turn started pinging.

1.) Start the remote masternode
2.) Open your local wallet, with the 1000DRK, then type "masternode outputs". You should see the output you're trying to start.
3.) Start the masternode with "masternode start" or "masternode start-alias mn1 'password'"
4.) Look through the remote masternode debug for "EnableHotColdMasterNode", if it says that it's successful. DONT TYPE "masternode start" on the remote side due to the v11 issue (will be fixed in v0.11.0.12)
5.) Next you should see something like
2015-01-22 00:20:49 CActiveMasternode::ManageStatus() - Begin
2015-01-22 00:20:49 CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing vin = CTxIn(COutPoint(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, 0), scriptSig=)

I'll let my node run for a few hours to make sure it's not dying for some reason. However, everything seems to work.

Let me know if those instructions help or not, I'm curious to figure out what's going on.
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
eduffield One of my MN's has this in the debug file. Should I reindex the daemon?
debug said:
2015-01-22 00:47:53 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 207095 (00000000000fbacc124b1477066f633181bdbf053fbb78a8cb28588d412b206d)
lasting to height 207105 (00000000000243e9009e6c0de9c9313b1552bab3c7756dcd5243a3517544cd11).
Chain state database corruption likely.
2015-01-22 00:47:53 ProcessBlock: ACCEPTED
EDIT: and the daemon has this in getinfo

"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
}

EDIT EDIT: One daemon has block count at 207105 another at 207098. Fork?
 

coingun

Active Member
Masternode Owner/Operator
Jul 8, 2014
489
402
133
masternode.io
Network is acting very funny for me. I've been waiting almost 1.5 hours for the last 6 blocks. Seems as if the network might be forking or something along those lines between old and new clients? I can't think of any reason why we'd be waiting almost 2 hours for 6 blocks? Anyone else noticing this weird long block. Anyone running any sort of block chain health type check? Hopefully it's just another anomaly but almost feels like an attack of some sort. Went to check the changelog for this release to see what else was fixed but that change log is well... a bit out of date.

https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/CHANGELOG.md
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
eduffield, I'm also getting the warning and having another Darksend tx being stuck:

20:18:34

{
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 61000,
"balance" : 66.77211480,
"darksend_balance" : 0.00000000,
"blocks" : 207100,
"timeoffset" : 7,
"connections" : 20,
"proxy" : "",
"difficulty" : 1598.86151011,
"testnet" : false,
"keypoololdest" : 1421857166,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
}
EDIT: It's being stuck at block 207098 which is the highest block on explorer.darkcoin.fr. What's the current block right now?
Will restart with -reindex.
 
Last edited by a moderator:

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
My V10 nodes were stuck this afternoon prior to me updating to V11.
 

Crahl

New Member
Nov 23, 2014
11
11
3
This is showing up in my logs.

2015-01-22 01:39:44 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 207095 (00000000000fbacc124b1477066f633181bdbf053fbb78a8cb28588d412b206d)
lasting to height 207122 (00000000000eb367eccdca2a0800f3c955304cd7dd54dd30ebdffcbefe9dd59a).
Chain state database corruption likely.
 
  • Like
Reactions: thelonecrouton

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
Had a blast of panic.mp3 about 20 minutes ago, reindexing all my MNs and my local wallet now, all but one had the 'some folk are experiencing issues' warning.
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
467
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
Network on first chain:

"blocks" : 207106,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 888.44160881,
This network has 59GH/s

Network on Second Chain:

"blocks" : 207133,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 3073.60266676,
This network has 67GH/s

Which is the correct chain?
 
Last edited by a moderator:

Crahl

New Member
Nov 23, 2014
11
11
3
So i reindexed one of my masternodes and it jumped to the larger chain.

MN on block 207111
2015-01-22 02:17:16 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 207095 (00000000000fbacc124b1477066f633181bdbf053fbb78a8cb28588d412b206d)
lasting to height 207139 (00000000001823509dfca36c142efd50412b116d4b2935e8c6cb9e37caee7ca9).
Chain state database corruption likely.


MN on block 207139
2015-01-22 02:17:08 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 207095 (00000000000fbacc124b1477066f633181bdbf053fbb78a8cb28588d412b206d)
lasting to height 207111 (000000000011dd9884fd95562600ed81363a59897daa72c44525ceb45b0e8ea4).
Chain state database corruption likely.
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
I think my wallet is on the correct fork:


22:06:37
getinfo
22:06:37

{
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 61000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 207152,
"timeoffset" : 8,
"connections" : 10,
"proxy" : "",
"difficulty" : 2158.43949547,
"testnet" : false,
"keypoololdest" : 1421891341,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
OK.. Now I'm getting that warning again... eduffield ?

{
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 61000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 207166,
"timeoffset" : 8,
"connections" : 8,
"proxy" : "",
"difficulty" : 2141.90869126,
"testnet" : false,
"keypoololdest" : 1421891341,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
}

EDIT: I think this is just a warning, doesn't mean it says I'm on the right or wrong fork. I read that the bitcoin code base tends to be verbose about fork warnings.
 
Last edited by a moderator:

ourlink

Well-known Member
Foundation Member
Jun 9, 2014
237
65
188
Heartland, USA
www.p2poolmining.us
I think my wallet is on the correct fork:


22:06:37
getinfo
22:06:37

{
"version" : 110011,
"protocolversion" : 70054,
"walletversion" : 61000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 207152,
"timeoffset" : 8,
"connections" : 10,
"proxy" : "",
"difficulty" : 2158.43949547,
"testnet" : false,
"keypoololdest" : 1421891341,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
Looking at http://explorer.darkcoin.io/chain/Darkcoin it would appear to me that you are off on the wrong fork. Currently, the latest block is 207098.
 

ourlink

Well-known Member
Foundation Member
Jun 9, 2014
237
65
188
Heartland, USA
www.p2poolmining.us
No, that block has been stuck for about 4 hours. We're discussing this in IRC, I think i'm on the right fork but I can't be positive 100%. Still waiting to hear from our devs.
Ooooh... Be sure and update us lurkers here when you learn what the proper fork is... I am rebuilding blocks and reindexing now!
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Ooooh... Be sure and update us lurkers here when you learn what the proper fork is... I am rebuilding blocks and reindexing now!
Hey you can join our "fork party" on Freenode if you like, just /join #darkcoin :)
 
  • Like
Reactions: ourlink

feeleep

New Member
Oct 18, 2014
29
33
13
Network forked again - my pool was on wrong chain for few hours and I switched back to previous daemon version
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
Network forked again - my pool was on wrong chain for few hours and I switched back to previous daemon version
Please tell me you're at least on Core and not Onyx... if you're on Onyx, you're not helping.
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
only Onyx keeps correct chain at this moment - all my new daemons forked
You don't know that... the fact of the matter is V11 should be causing V10's to fork off as they are old clients that should have updated to Core. The problem looks, well... bad right now.
 

feeleep

New Member
Oct 18, 2014
29
33
13
You don't know that... the fact of the matter is V11 should be causing V10's to fork off as they are old clients that should have updated to Core. The problem looks, well... bad right now.
at least onyx daemon has higher diff and more blocks on it so i suppose this is a orrect chain :|

anyway - after Core reindex it is on chain now, but I am a bit afraid to switch to it until Evan will release the fix or something
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
at least onyx daemon has higher diff and more blocks on it so i suppose this is a orrect chain :|

anyway - after Core reindex it is on chain now, but I am a bit afraid to switch to it until Evan will release the fix or something
Not sure you can really say that. 67GH is on the chain I'm on, all core clients, last block 207236