Mandatory : All users must update to v0.11.1.x

camosoul said:
Usually updates are a race, even when unimportant. But now we get one of the most important ones, and it's mandatory, and we still can't break 50% 48 hours after the mark?

This is why some people shouldn't run masternodes. They don't really care. They barely know how. They're not even paying attention... Some updates need to punt old versions, maybe getting no more payments will get their attention?
Click to expand...

I'm trying to start my masternodes and some of them are crashing, then I reindex and they crash at some point. Then I delete the blockchain and redownload and they crash at some point. Half of my nodes are up after 1 or 2 tries but the rest of them not yet. Dunno if others have similar problems.

Maybe it's because my VPS's are under powered because my local wallets crashed only once and have been working since.
 
Only had 1 crash in the last 24hrs since I updated to 11.0.7, but they all took several attempts deleting peers.dat/reindexing/etc. to update and get running properly.

All are consistent blockheight-wise with explorer.darkcoin.io, but chainz is lagging behind by about 40 blocks or forked off.
 
Since the massage: "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues." does not really provide much useful info to the normal user would not it be easier to simply change the text of the warning to "Please restart the client with --reindex" ?
 
Installed win-32bit v.11007 with -reindex, my wallet hasn't crashed like the previous version. But what does this mean in getinfo:

{
"version" : 110007,
"protocolversion" : 70052,
"walletversion" : 61000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 205262,
"timeoffset" : 3,
"connections" : 17,
"proxy" : "",
"difficulty" : 4137.66630283,
"testnet" : false,
"keypoololdest" : 1421520105,
"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."
}
Click to expand...

I guess block 205262 is the current correct block?

EDIT: 205263 now.
 
moli said:
Installed win-32bit v.11007 with -reindex, my wallet hasn't crashed like the previous version. But what does this mean in getinfo:



I guess block 205262 is the current correct block?

EDIT: 205263 now.
Click to expand...

My nodes are on 205263 now.
 
<gitcow> [ darkcoin | master | Evan Duffield | 3 minutes ago ] 539a868 Added LiteMode

Anyone knows what that is? Hope it's not about LTC :D
 
jpr said:
<gitcow> [ darkcoin | master | Evan Duffield | 3 minutes ago ] 539a868 Added LiteMode

Anyone knows what that is? Hope it's not about LTC :D
Click to expand...
Ya I was wondering if we're going back to Litecoin codebase after all these hassles :/ Hope not!!!!
 
elbereth said:
Not sure if it is normal, but blocktemplate in v11 has changed the values for coinbasevalue.

v10: coinbasevalue was total generated coins for the block
v11: is now only the miner's part

This caused the wrong percentage paid blocks on 204703 204704 204706 and 204707.
Click to expand...


I've created new issue on Github regarding this.
 
moli said:
Ya I was wondering if we're going back to Litecoin codebase after all these hassles :/ Hope not!!!!
Click to expand...
No

"
LiteMode disables Darksend/Masternodes/InstantX for clients
who want speed and don't need access to these features. UI
for Darksend is also hidden while in this mod"
 
Just got that again

Code: 
error: {"code":-2,"message":"Safe mode: Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."}
 
I had this info in my debug:
CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 205072 (00000000000ed82c8f1423b779e0bc2074df80ec1407f894bb3923efe9048a17)
lasting to height 205282 (00000000000fb14c20847ac5e634ae65f2db84c57e0cad474b31f04e190effaa).
Chain state database corruption likely.

edit: forgot to post this. qt crashed first time after these infos. I had it opened all day with no mixing
 
Last edited by a moderator:
Lukas_Jackson said:
I had this info in my debug:
CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 205072 (00000000000ed82c8f1423b779e0bc2074df80ec1407f894bb3923efe9048a17)
lasting to height 205282 (00000000000fb14c20847ac5e634ae65f2db84c57e0cad474b31f04e190effaa).
Chain state database corruption likely.
Click to expand...
That sounds very bad!
 
UdjinM6 said:
Looks like ourlink have p2pool running on 11.00.07
https://darkcointalk.org/threads/an...mining-us-miner-stats-graphs.2735/#post-36954
ourlink can you help please?
Click to expand...

IYFTech - In dstorm's p2pool git you need to make some modifications;

p2pool/bitcoin/p2p.py (~ line 21)
Code: 
     def connectionMade(self):
         self.send_version(
-            version=70043,
+            version=70052,
             services=1,
             time=int(time.time()),
             addr_to=dict(

p2pool/networks.py (~ line 27)
Code: 
         ANNOUNCE_CHANNEL='#p2pool-drk',
-        VERSION_CHECK=lambda v: v >= 101514,
+        VERSION_CHECK=lambda v: v >= 110006,

This should get you back up and running..
 
You must log in or register to reply here.
Back
Top