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

eduffield

eduffield

Core Developer
We have seen an issue on the network, which comes from a disagreement between v10 and v11 clients. It appears to be an issue the network has always had, but never caused an issue until we upgraded the core client. This caused the v11 client to get stuck this morning, when a block was created and accepted by v10 and not by v11. V11 was correct to reject the block, as it has improved masternode payment detection capabilities.

Due to this, we need all users to update from v10 to v11, this includes end-users, masternodes and miners. Anyone left on the v10 will fork from the network and orphan blocks until they upgrade.

If you have an error "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues." just restart the client with --reindex

Edit by vertoe: All users must update to v0.11.1.x now!
 
Last edited by a moderator:
And this will clear up the ERROR I'm getting?

{
"version" : 110006,
"protocolversion" : 70052,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204572,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 4083.62714253,
"testnet" : false,
"keypoololdest" : 1411407802,
"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."
}
 
MangledBlue said:
And this will clear up the ERROR I'm getting?

{
"version" : 110006,
"protocolversion" : 70052,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204572,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 4083.62714253,
"testnet" : false,
"keypoololdest" : 1411407802,
"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...

Try --reindex
 
And they need to reindex...

Because I updated a couple of hours ago from v10 to v11 and v11 accepted the fork without the reindex.
 
I just finished the reindex with 0.11.0.7:

/opt/darkcoind/0.11/darkcoind-0.11.0.7 getinfo
{
"version" : 110007,
"protocolversion" : 70052,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204709,
"timeoffset" : -180,
"connections" : 11,
"proxy" : "",
"difficulty" : 2792.20437713,
"testnet" : false,
"keypoololdest" : 1394017965,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}

Still on the bad fork?
204709 00000000001776e3f483bd15db28a51e5201f869a61b290207bf1ea5fbd4af8e
 
elbereth said:
I just finished the reindex with 0.11.0.7:

/opt/darkcoind/0.11/darkcoind-0.11.0.7 getinfo
{
"version" : 110007,
"protocolversion" : 70052,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204709,
"timeoffset" : -180,
"connections" : 11,
"proxy" : "",
"difficulty" : 2792.20437713,
"testnet" : false,
"keypoololdest" : 1394017965,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}

Still on the bad fork?
204709 00000000001776e3f483bd15db28a51e5201f869a61b290207bf1ea5fbd4af8e
Click to expand...
\


SAME

ugh - off ta work
 
All nodes updated without a problem. I started with the local client (First time upgrading to Darkcoin core from 0.10.xx) and only did a "masternode password start" on local wallets. Everything is synced up correctly.
 
oblox said:
If you reindexed and are still stuck close to the current block, like you are:

./darkcoind stop

Remove peers.dat

./darkcoind -resync
Click to expand...


at work now - have to look at it tonight :) thx
 
My blockchain explorer stopped working:
Code: 
RPC service lacks full txindex
catch_up_rpc: abort
Opened /home/drk/.darkcoin/Server/blocks/blk00003.dat
incomplete block of length 1991840519 chain 15

The server is fully synced (block 204737 right now).

I know vertoe or flare have an updated version of Abe, but I cannot find a link, even with the fantastic :rolleyes: forum search...

Or do you use the original Bitcoin Abe as well?

I also wouldn't like to drop the complete table and build it again...
 
Last edited by a moderator:
crowning said:
My blockchain explorer stopped working:
Code: 
RPC service lacks full txindex
catch_up_rpc: abort
Opened /home/drk/.darkcoin/Server/blocks/blk00003.dat
incomplete block of length 1991840519 chain 15

The server is fully synced (block 204737 right now).

I know vertoe or flare have an updated version of Abe, but I cannot find a link, even with the fantastic :rolleyes: forum search...

Or do you use the original Bitcoin Abe as well?

I also wouldn't like to drop the complete table and build it again...
Click to expand...

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.
 
I can't get v11 to work with p2pool - so I can't upgrade......Ever since I upgraded to the latest version I've been unable to get p2pool to connect on port 9999:

2015-01-16 16:38:13.821624 p2pool (version 81fc6c5-dirty)
2015-01-16 16:38:13.821724
2015-01-16 16:38:13.821780 Testing bitcoind RPC connection to 'REMOVED' with username 'IYFTechDRK'...
2015-01-16 16:38:13.850612 ...success!
2015-01-16 16:38:13.850710 Current block hash: 5f2afca31990cbc9c8be1722088daafeac266253c55a1e7f06a47
2015-01-16 16:38:13.850753 Current block height: 204176
2015-01-16 16:38:13.850777
2015-01-16 16:38:13.850815 Testing bitcoind P2P connection to '127.0.0.1:9999'...
2015-01-16 16:38:18.851266 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used...

If I revert to v10 I have no problem..........it just won't connect on 9999
 
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.
 
You must log in or register to reply here.
Back
Top