• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

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

mattmct

mattmct

Active member
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:
Thanks for the info.
I have the same "gentx doesn't match hash_link" errors. Any help is highly appreciated.
 
Something must have happend some hours ago. Because all the errors are gone now. :smile:
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 ?
 
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.
 
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?
 
mattmct said:
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.
Click to expand...

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?
 
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.
 
dstorm said:
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.
Click to expand...

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 said:
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/
Click to expand...
dstorm should we better be hardforking the p2pool network next time too?
 
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 said:
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!
Click to expand...
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!
 
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:
ourlink said:
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!
Click to expand...

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?
 
fabioganga said:
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?
Click to expand...
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.
 
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.
 
You must log in or register to reply here.
Back
Top