v0.11.0 - Darkcoin Core Release
- Thread starter eduffield
- Start date
I have a little tool that checks via my local wallet every so often and plays an mp3 when there's a problem.
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?
You can't just dangle stuff like this in front of us and not provide details!!!!!
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.
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.
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.
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:
seep() - 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?
"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?
EDIT: and the daemon has this in getinfodebug said:
"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?
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
https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/CHANGELOG.md
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.
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.
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?
"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:
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.
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.
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" : ""
}
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" : ""
}
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.

{
"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:
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.
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!
Hey you can join our "fork party" on Freenode if you like, just /join #darkcoin
Please tell me you're at least on Core and not Onyx... if you're on Onyx, you're not helping.
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
Not sure you can really say that. 67GH is on the chain I'm on, all core clients, last block 207236