I have a little tool that checks via my local wallet every so often and plays an mp3 when there's a problem.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?
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?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
It's not just mac users having this 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 have a little tool that checks via my local wallet every so often and plays an mp3 when there's a problem.
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.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
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.This will be fixed in v0.11.0.12, for the time being if you see "EnableHotColdMasterNode" in the log it should be fine.
I've just made a masternode from scratch on windows and successfully started a remote machine on linux, which in turn started pinging.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.
EDIT: and the daemon has this in getinfodebug 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: It's being stuck at block 207098 which is the highest block on explorer.darkcoin.fr. What's the current block right now?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."
}
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.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" : ""
}
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.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.
Ooooh... Be sure and update us lurkers here when you learn what the proper fork is... I am rebuilding blocks and reindexing now!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.
Hey you can join our "fork party" on Freenode if you like, just /join #darkcoinOoooh... Be sure and update us lurkers here when you learn what the proper fork is... I am rebuilding blocks and reindexing now!
Please tell me you're at least on Core and not Onyx... if you're on Onyx, you're not helping.Network forked again - my pool was on wrong chain for few hours and I switched back to previous daemon version
only Onyx keeps correct chain at this moment - all my new daemons forkedPlease 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.only Onyx keeps correct chain at this moment - all my new daemons forked
at least onyx daemon has higher diff and more blocks on it so i suppose this is a orrect chain :|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.
Not sure you can really say that. 67GH is on the chain I'm on, all core clients, last block 207236at 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
and this is my chain as wellNot sure you can really say that. 67GH is on the chain I'm on, all core clients, last block 207236