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

illodin

Member
Apr 26, 2014
122
71
78
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?
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.
 

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
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.
 

hard_forker

Member
Jun 20, 2014
41
14
48
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" ?
 
  • Like
Reactions: strix

Propulsion

The buck stops here.
Feb 26, 2014
1,008
468
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
Is it possible to kick all pre version 11 daemons off the network?
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
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."
}
I guess block 205262 is the current correct block?

EDIT: 205263 now.
 

jpr

Active Member
May 11, 2014
493
393
133
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.
My nodes are on 205263 now.
 
  • Like
Reactions: moli

jpr

Active Member
May 11, 2014
493
393
133
<gitcow> [ darkcoin | master | Evan Duffield | 3 minutes ago ] 539a868 Added LiteMode

Anyone knows what that is? Hope it's not about LTC :D
 
  • Like
Reactions: GilAlexander

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
<gitcow> [ darkcoin | master | Evan Duffield | 3 minutes ago ] 539a868 Added LiteMode

Anyone knows what that is? Hope it's not about LTC :D
Ya I was wondering if we're going back to Litecoin codebase after all these hassles :/ Hope not!!!!
 

Coinotron

New Member
May 15, 2014
21
21
3
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.

I've created new issue on Github regarding this.
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
Ya I was wondering if we're going back to Litecoin codebase after all these hassles :/ Hope not!!!!
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"
 
  • Like
Reactions: splawik21 and moli

jpr

Active Member
May 11, 2014
493
393
133
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."}
 

Lukas_Jackson

Member
Nov 9, 2014
160
70
88
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:

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,341
575
283
Finland
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.
That sounds very bad!
 

scratchy

Member
Jun 24, 2014
218
92
88
Seems P2Pool source doesnt work for the new version,anyone else got trouble like this?
 

ourlink

Well-known Member
Foundation Member
Jun 9, 2014
237
65
188
Heartland, USA
www.p2poolmining.us
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..
 

crowning

Well-known Member
May 29, 2014
1,414
1,997
183
Alpha Centauri Bc
You can use upstream https://github.com/bitcoin-abe/bitcoin-abe

As for the update: I don't know of any update procedure, redid the whole DB.
Right now my abe doesn't work with v0.11.1.19:

with blkfile: OverflowError: Python int too large to convert to C long

with RPC: RPC failed: No JSON object could be decoded ... File "Abe/DataStore.py", line 2521, in catch_up raise Exception("RPC load failed")

I re-build the complete blockchain with blkfile until the error stops it.
I switched to RPC and it still won't work. And, yes, the darkcoin.conf file is readable for all.

Any idea?
 

flare

Grizzled Member
May 18, 2014
2,286
2,404
1,183
Germany
Right now my abe doesn't work with v0.11.1.19:

with blkfile: OverflowError: Python int too large to convert to C long

with RPC: RPC failed: No JSON object could be decoded ... File "Abe/DataStore.py", line 2521, in catch_up raise Exception("RPC load failed")

I re-build the complete blockchain with blkfile until the error stops it.
I switched to RPC and it still won't work. And, yes, the darkcoin.conf file is readable for all.

Any idea?
No, i did not touch explorer.darkcoin.io yet - will try later.
 

Raico

Well-known Member
Foundation Member
Dash Support Group
May 28, 2014
138
142
193
Updated all my MN to 11.1.19. Most of them works fine. But only one. It's very strange.

In loading splash screen, there is a rescanning showed, it's very slow compared with other wallets. And when it get to 88%, it's crashed and through out an error:snapshot49.png

But this wallet works with "darkcoind"....


OS: Ubuntu 12.04 LTS 64
Darkcoin version: V11.1.19 linux

working screen shot with darkcoind:snapshot50.png


And i've tried this wallet with many historical backup version. All of them failed with QT.





EDIT:
use -reindex -zapwallettxes as parameters. It works!!

Thanks guys that mention it.
 
Last edited by a moderator:

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183
Updated all my MN to 11.1.19. Most of them works fine. But only one. It's very strange.

In loading splash screen, there is a rescanning showed, it's very slow compared with other wallets. And when it get to 88%, it's crashed and through out an error:View attachment 991

But this wallet works with "darkcoind"....


OS: Ubuntu 12.04 LTS 64
Darkcoin version: V11.1.19 linux

working screen shot with darkcoind:View attachment 992


And i've tried this wallet with many historical backup version. All of them failed with QT.





EDIT:
use -reindex -zapwallettxes as parameters. It works!!

Thanks guys that mention it.
You also might need -upgradewalet. pre 61000 crashes with DB error on reindex sometimes.
 
  • Like
Reactions: Raico