[GUIDE]Updating Darkcoind / P2Pool After Reverting RC3 Masternode Payments Fork June 21st

mattmct

Member
Mar 13, 2014
259
92
88
After the failed fork on the 20th, we all have to update to v0.9.10.2.

I couldn't find any instructions on what to do with my p2pool, and was going around in circles looking for info. Hopefully this will help someone out. There are many p2pools which haven't updated.

Quick and dirty guide .

p2p pool.
1) Kill the python p2pool process
2) delete the p2pool data folder [ rm -rf data]

darkcoind
3) stop and update darkcoind to v0.9.10.2 (Excellent guide here) BUT change download link to wget http://www.darkcoin.io/downloads/darkcoind ...and be sure to start up darkcoind with reindex (step 4)
4) start darkcoind with reindex [ darkcoind -reindex]

I've been told on IRC etc that the latest version of the p2pool software will work fine, no need to use old comit version or change code. So as long as you were ready for the fork on the 20th, it should work, just be sure to delete your data folder as instructed in step 1.

My pool, http://x11p2p.com:7903/static/ looks to be working correctly. Although I like others, are getting errors, any help out be appreciated!

Code:
  if not self.attempt_verify(share):
2014-06-21 15:24:28.378488 > --- <exception caught here> ---
2014-06-21 15:24:28.378550 >   File "/home/x/p2pool-drk/p2pool/data.py", line 450, in attempt_verify
2014-06-21 15:24:28.378620 >     share.check(self)
2014-06-21 15:24:28.378682 >   File "/home/x/p2pool-drk/p2pool/data.py", line 335, in check
2014-06-21 15:24:28.378757 >     raise ValueError('''gentx doesn't match hash_link''')
2014-06-21 15:24:28.378827 > exceptions.ValueError: gentx doesn't match hash_link
2014-06-21 15:24:28.380754 > Share check failed: 000000002615046ee30ad5bb90aaf444a049631ca8a85cd070baddfb3c079a79 -> 000000004a69b81e28a81f8e69bccd156d3cd85a7158e3674513462468d776e2
2014-06-21 15:24:28.380840 > Traceback (most recent call last):
2014-06-21 15:24:28.380909 >   File "/home/x/p2pool-drk/p2pool/util/deferral.py", line 284, in _worker
2014-06-21 15:24:28.380979 >     self.func(*self.args, **self.kwargs)
2014-06-21 15:24:28.381049 >   File "/home/x/p2pool-drk/p2pool/node.py", line 361, in clean_tracker
2014-06-21 15:24:28.381113 >     self.set_best_share()
2014-06-21 15:24:28.381176 >   File "/home/x/p2pool-drk/p2pool/node.py", line 299, in set_best_share
2014-06-21 15:24:28.381235 >     best, desired, decorated_heads, bad_peer_addresses = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
 
Last edited by a moderator:
  • Like
Reactions: fydel

fydel

New Member
May 20, 2014
29
10
3
Thanks for the info.
I have the same "gentx doesn't match hash_link" errors. Any help is highly appreciated.
 
  • Like
Reactions: mattmct

fydel

New Member
May 20, 2014
29
10
3
Something must have happend some hours ago. Because all the errors are gone now. :)
Dead and orphaned rate is back to normal.

But I still would like to know what caused this. Pools/Miners who were still on 9.10.1 / 10.10.1 ?
 

mattmct

Member
Mar 13, 2014
259
92
88
Something still isn't right, my p2pool, and others, is saying that they've not found a block for 14 hours (89558), but the p2pool node scanner reports the last p2pool block found was 5 (89762) and 11 hours ago.
Although I WAS paid 5 hours ago, so it looks like it is paying out, but not reporting, either way, something isn't right with the p2pools right now.

One thing that concerns me is, if we're all using the same latest version, but some haven't updated darkcoind.... they're all still sharing the same information around the p2pool network no? Maybe this is what was / is causing the previous errors.
 
  • Like
Reactions: ourlink

ourlink

Well-known Member
Foundation Member
Jun 9, 2014
237
65
188
Heartland, USA
www.p2poolmining.us
It's been 15 hours since my P2Pool Node found the last DRK block. Does anyone know what is going on?

I have upgraded by software to the latest release candidate according to the instructions put out in this post;
https://darkcointalk.org/threads/reverting-rc3-masternode-payments-fork.1458/
I'm monitoring my pool and I see that I am getting shares and my efficiency looks good. However, I am not receiving any notifications about new FOUND blocks.
Does anyone know why?
 

ourlink

Well-known Member
Foundation Member
Jun 9, 2014
237
65
188
Heartland, USA
www.p2poolmining.us
Something still isn't right, my p2pool, and others, is saying that they've not found a block for 14 hours (89558), but the p2pool node scanner reports the last p2pool block found was 5 (89762) and 11 hours ago.
Although I WAS paid 5 hours ago, so it looks like it is paying out, but not reporting, either way, something isn't right with the p2pools right now.

One thing that concerns me is, if we're all using the same latest version, but some haven't updated darkcoind.... they're all still sharing the same information around the p2pool network no? Maybe this is what was / is causing the previous errors.
I am seeing the same issue on my P2Pool node. I updated to the latest release Candidate this morning because the last found block was reported as 15 hours ago. However, even after the update it is not updating for any found blocks.

I getting new shares but the reporting for FOUND blocks seems to have stopped working... Any ideas? Anyone?
 

fydel

New Member
May 20, 2014
29
10
3
Sadly you are not alone.
But dstorm is informed and looking into it.
 

dstorm

New Member
May 9, 2014
15
19
3
Some p2pools are on a sharechain fork with 440MH/s. They found the 3 blocks earlier today. The correct chain has just really bad luck.

If you have block 89323 in the "recent blocks" list you need to delete the "data" directory and restart the pool.
 
  • Like
Reactions: vertoe

mattmct

Member
Mar 13, 2014
259
92
88
Some p2pools are on a sharechain fork with 440MH/s. They found the 3 blocks earlier today. The correct chain has just really bad luck.

If you have block 89323 in the "recent blocks" list you need to delete the "data" directory and restart the pool.
Cheers for the reply dstorm. My p2pool is on the correct darkcoind fork (not the 440MH/s one) but are you saying it's possible that the pools / sharechain could be sharing with the p2pools on the wrong fork?....

Unfortunately block 89323 is too long ago to show on my pool.

I'm still not convined this is the problem / solution, every single p2pool I can find (on the correct 2.44GH/s fork) , shows block 89558 as the last, 14 hours ago. But the p2pnode explorer shows 89762 as the most recent. http://chainz.cryptoid.info/drk/block.dws?89762.htm
 

dstorm

New Member
May 9, 2014
15
19
3

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
My guess is that some pools didn't update the wallet and that created a p2pool sharechain fork. Even if they updated the wallet later, the pool will still be on the wrong chain unless they delete the "data" directory.

The "gentx doesn't match hash_link" errors was because of shares submitted from pools on the wrong chain.

I have found some pools:
http://64.231.8.35:7903/static/
http://p2pool.e-pool.net:7903/static/
http://173.20.138.223:7903/static/
dstorm should we better be hardforking the p2pool network next time too?
 

fabioganga

New Member
Jun 18, 2014
17
2
3
Thanks for the suggestions!

How long is the -reindex process supposed to last for? Mine has been running for a good hours and is still running.

Thanks!
 

ourlink

Well-known Member
Foundation Member
Jun 9, 2014
237
65
188
Heartland, USA
www.p2poolmining.us
Thanks for the suggestions!

How long is the -reindex process supposed to last for? Mine has been running for a good hours and is still running.

Thanks!
Fabioganga,

The reindex will only take ~5 minutes. If it's taking longer than that then it's probably more related to the deletion of the peers.dat file in the ~/.dark directory. After you delete that file add the following to your darkcoin.conf file;

addnode=23.23.186.131
addnode=50.16.206.102
addnode=50.19.116.123
addnode=98.165.130.67
addnode=54.242.50.205
addnode=50.17.98.53
addnode=54.225.43.37

That will ensure everything comes back up on the proper fork.

It worked for me!
 

DrkMiner

Member
Jun 7, 2014
204
63
88
My p2pool is on the correct fork 9.10.02.
Last block found 20 hours ago 89558.
Something must be wrong!

Checking the debug file of my PC wallet i see many on:
0.10.8.11
0.9.4.11
Why is the system still accepts from these nodes? They should be rejected!
 
Last edited by a moderator:

fabioganga

New Member
Jun 18, 2014
17
2
3
Fabioganga,

The reindex will only take ~5 minutes. If it's taking longer than that then it's probably more related to the deletion of the peers.dat file in the ~/.dark directory. After you delete that file add the following to your darkcoin.conf file;

addnode=23.23.186.131
addnode=50.16.206.102
addnode=50.19.116.123
addnode=98.165.130.67
addnode=54.242.50.205
addnode=50.17.98.53
addnode=54.225.43.37

That will ensure everything comes back up on the proper fork.

It worked for me!
Thanks ourlink, I figured out that something was wrong, so I deleted the entire blockchain, everything BUT wallet.dat and darkcoin.conf.
Then, I added to my .conf file TWO masternodes from this list (the closest to me and active) and downloaded the blockchain again:
https://elbzo.net/masternodes.html
Would this achieve the same result or do I have to specify the ones you mention?
 
  • Like
Reactions: benzmuircroft

ourlink

Well-known Member
Foundation Member
Jun 9, 2014
237
65
188
Heartland, USA
www.p2poolmining.us
Thanks ourlink, I figured out that something was wrong, so I deleted the entire blockchain, everything BUT wallet.dat and darkcoin.conf.
Then, I added to my .conf file TWO masternodes from this list (the closest to me and active) and downloaded the blockchain again:
https://elbzo.net/masternodes.html
Would this achieve the same result or do I have to specify the ones you mention?
It depends if the nodes you added are on the right Fork... If they aren't then you back to square one.
The list of nodes I posted are all on the proper fork. You can check if you are on the right one by looking at your recent blocks for you pool. If the last block found was 89558 then you should be fine.
 

mattmct

Member
Mar 13, 2014
259
92
88
Surely a new version of the p2pool is needed, which only connects to other p2pools which are running the latest software, with the latest darkcoind on the correct fork.

It's crazy that we can be running the latest darkcoind on the correct fork, redindexed etc, but still getting the wrong chain because we're connecting to messed up nodes with the wrong fork.
 
  • Like
Reactions: fydel

mattmct

Member
Mar 13, 2014
259
92
88
Looks like my pool, and most others are now showing the latest p2pool block found (as shown by the node scanner) 90075.

The idea of adding nodes which we know are on the correct fork sounds like a good idea. But not a solution as it could connect to some "bad" p2pool / nodes also..
 

dstorm

New Member
May 9, 2014
15
19
3
Surely a new version of the p2pool is needed, which only connects to other p2pools which are running the latest software, with the latest darkcoind on the correct fork.

It's crazy that we can be running the latest darkcoind on the correct fork, redindexed etc, but still getting the wrong chain because we're connecting to messed up nodes with the wrong fork.
It is the p2pool sharechain that is forked, not blockchain. The other pools can't affect your blockchain. Everything will be fine as long as most pools are on the correct sharechain. We will just get some errors in the logfile and the global hashrate will be lower.
 

fabioganga

New Member
Jun 18, 2014
17
2
3
You need to update the wallet and p2pool code. Delete the "data" directory and restart the pool to get the correct chain.
I have update the wallet and it would seem that I am on the correct chain, what change to the code do I have do to in thecode of my P2Pool please?

Thanks!
 

dstorm

New Member
May 9, 2014
15
19
3
I have update the wallet and it would seem that I am on the correct chain, what change to the code do I have do to in thecode of my P2Pool please?

Thanks!
If you have block 92131 in the "recent blocks" list you don't need to do anything.
 

fydel

New Member
May 20, 2014
29
10
3
I am having gentx errors again since the sporck. Do others have similar problems? Or a solution maybe?
I am running latest darkcoind (91105) and latest p2pool (fac408d-dirty). /data was deleted and a --reindex was done.
Any held is appreciated as these errors seems to have a negative impact on p2pool efficiency.
 

penambang

New Member
Jun 9, 2014
6
2
3
Indonesia
I am having gentx errors again since the sporck. Do others have similar problems? Or a solution maybe?
I am running latest darkcoind (91105) and latest p2pool (fac408d-dirty). /data was deleted and a --reindex was done.
Any held is appreciated as these errors seems to have a negative impact on p2pool efficiency.
I have same issue on my pool :(
Using latest darkcoind and p2pool (fac408d-dirty) too.
Code:
2014-07-03 18:09:37.667014 Requesting parent share bfee4f13 from 23.239.28.247:42400
2014-07-03 18:09:37.889686 > Share check failed: 0000000066f7d0dab55a481c0cdcd9e16c46341701674c70c11e5a127f461073 -> 00000005b0bd4546bc6bf954250f776234be65ca4722507cde8791b8d3b2cbf6
2014-07-03 18:09:37.889763 > Traceback (most recent call last):
2014-07-03 18:09:37.889795 >  File "/home/penambang/p2p-drk-new/p2pool/p2p.py", line 282, in handle_shares
2014-07-03 18:09:37.889821 >  self.node.handle_shares(result, self)
2014-07-03 18:09:37.889846 >  File "/home/penambang/p2p-drk-new/p2pool/node.py", line 48, in handle_shares
2014-07-03 18:09:37.889870 >  self.node.set_best_share()
2014-07-03 18:09:37.889894 >  File "/home/penambang/p2p-drk-new/p2pool/node.py", line 299, in set_best_share
2014-07-03 18:09:37.889919 >  best, desired, decorated_heads, bad_peer_addresses = self.tracker.think(self.get_height_rel_highest, self.bitcoind_work.value['previous_block'], self.bitcoind_work.value['bits'], self.known_txs_var.value)
2014-07-03 18:09:37.889959 >  File "/home/penambang/p2p-drk-new/p2pool/data.py", line 506, in think
2014-07-03 18:09:37.889984 >  if not self.attempt_verify(share):
2014-07-03 18:09:37.890008 > --- <exception caught here> ---
2014-07-03 18:09:37.890031 >  File "/home/penambang/p2p-drk-new/p2pool/data.py", line 450, in attempt_verify
2014-07-03 18:09:37.890056 >  share.check(self)
2014-07-03 18:09:37.890080 >  File "/home/penambang/p2p-drk-new/p2pool/data.py", line 335, in check
2014-07-03 18:09:37.890104 >  raise ValueError('''gentx doesn't match hash_link''')
 
Last edited by a moderator:
  • Like
Reactions: fydel

fydel

New Member
May 20, 2014
29
10
3
All other p2pools running without gentx errors?
Did we miss something obvious?