[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 98.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Running Core v0.12 I got loads or these errors:

Code:

2016-02-19 17:55:11.831105 > Error while processing Event callbacks:
2016-02-19 17:55:11.831211 > Traceback (most recent call last):
2016-02-19 17:55:11.831237 >   File "/home/rig/p2pool/p2pool/util/variable.py", line 74, in set
2016-02-19 17:55:11.831263 >     self.changed.happened(value)
2016-02-19 17:55:11.831287 >   File "/home/rig/p2pool/p2pool/util/variable.py", line 42, in happened
2016-02-19 17:55:11.831311 >     func(*event)
2016-02-19 17:55:11.831335 >   File "/home/rig/p2pool/p2pool/node.py", line 243, in _
2016-02-19 17:55:11.831360 >     self.mining_txs_var.set(new_mining_txs)
2016-02-19 17:55:11.831383 >   File "/home/rig/p2pool/p2pool/util/variable.py", line 75, in set
2016-02-19 17:55:11.831410 >     self.transitioned.happened(oldvalue, value)
2016-02-19 17:55:11.831434 > ---  ---
2016-02-19 17:55:11.831457 >   File "/home/rig/p2pool/p2pool/util/variable.py", line 42, in happened
2016-02-19 17:55:11.831481 >     func(*event)
2016-02-19 17:55:11.831505 >   File "/home/rig/p2pool/p2pool/p2p.py", line 211, in update_remote_view_of_my_mining_txs
2016-02-19 17:55:11.831541 >     assert self.remote_remembered_txs_size <= self.max_remembered_txs_size
2016-02-19 17:55:11.831565 > exceptions.AssertionError: 
2016-02-19 17:55:11.833002 > Error while processing Event callbacks:
2016-02-19 17:55:11.833105 > Traceback (most recent call last):
2016-02-19 17:55:11.833132 >   File "/home/rig/p2pool/p2pool/util/variable.py", line 74, in set
2016-02-19 17:55:11.833157 >     self.changed.happened(value)
2016-02-19 17:55:11.833182 >   File "/home/rig/p2pool/p2pool/util/variable.py", line 42, in happened
2016-02-19 17:55:11.833206 >     func(*event)
2016-02-19 17:55:11.833230 >   File "/home/rig/p2pool/p2pool/node.py", line 243, in _
2016-02-19 17:55:11.833257 >     self.mining_txs_var.set(new_mining_txs)
2016-02-19 17:55:11.833280 >   File "/home/rig/p2pool/p2pool/util/variable.py", line 75, in set
2016-02-19 17:55:11.833304 >     self.transitioned.happened(oldvalue, value)
2016-02-19 17:55:11.833327 > ---  ---
2016-02-19 17:55:11.833351 >   File "/home/rig/p2pool/p2pool/util/variable.py", line 42, in happened
2016-02-19 17:55:11.833374 >     func(*event)
2016-02-19 17:55:11.833398 >   File "/home/rig/p2pool/p2pool/p2p.py", line 211, in update_remote_view_of_my_mining_txs
2016-02-19 17:55:11.833421 >     assert self.remote_remembered_txs_size <= self.max_remembered_txs_size
2016-02-19 17:55:11.833445 > exceptions.AssertionError:

...& my DOA/Orphan rate was quite high - anyone else experience this?

Since going back to the previous master branch the errors have gone & my DOA/Orphan rate is fine again.

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: luthermarcus on February 19, 2016, 12:14:13 PM

Does anyone know if the parameter -maxuploadtarget would affect p2pool negatively?
From what i read it it used to limit uploads to new bitcoin nodes who are downloading the blockchain.
I'm trying to use this as an alternative and/or in combination with -maxconnections parameter.

It should have no effect, it's a Bitcoin setting and unrelated to P2Pool P2P traffic.

FWIW I set -maxconnections to 15 for Bitcoin and 25 for P2Pool

luthermarcus

full member

Activity: 213

Merit: 100

Does anyone know if the parameter -maxuploadtarget would affect p2pool negatively?
From what i read it it used to limit uploads to new bitcoin nodes who are downloading the blockchain.
I'm trying to use this as an alternative and/or in combination with -maxconnections parameter.

luthermarcus

full member

Activity: 213

Merit: 100

Quote from: windpath on February 19, 2016, 09:23:14 AM

Quote from: luthermarcus on February 19, 2016, 01:11:41 AM

I'm still relatively new to Linux how would i go about installing bitcoin core rc5.
I probably could figure it out but i dont want to mess anything up in the process. Thanks in advance.

0.12.0 has been tagged for release, no need to use the release candidate, I imagine the binaries will be out today if you do want to wait, if not you can build yourself with the directions below.

https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md

Thanks windpath for that link and security update too. I just finished building it then i saw your post. It was a good experience for me normally i would stick to windows but bitcoin has me working on lunix. Greatly appreciated.

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: luthermarcus on February 19, 2016, 01:11:41 AM

I'm still relatively new to Linux how would i go about installing bitcoin core rc5.
I probably could figure it out but i dont want to mess anything up in the process. Thanks in advance.

0.12.0 has been tagged for release, no need to use the release candidate, I imagine the binaries will be out today if you do want to wait, if not you can build yourself with the directions below.

https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md

Meuh6879

legendary

Activity: 1512

Merit: 1012

wait a little more ... https://bitcointalksearch.org/topic/m.13932025

luthermarcus

full member

Activity: 213

Merit: 100

I'm still relatively new to Linux how would i go about installing bitcoin core rc5.
I probably could figure it out but i dont want to mess anything up in the process. Thanks in advance.

wariner

legendary

Activity: 1257

Merit: 1004

pool.sexy

Quote from: p3yot33at3r on February 17, 2016, 02:23:05 PM

Quote from: windpath on February 17, 2016, 12:38:34 PM

So, if you have not heard yet there is another serious vulnerability for anyone running Unix based machines.

A severe vulnerability in the Gnu C Library's DNS client has been discovered and it affects just about EVERY bitcoin implementation.

Info here: http://linux.slashdot.org/story/16/02/16/1724222/red-hat-google-disclose-severe-glibc-dns-vulnerability-patched-but-widespread

Patches are available, but you must update.

For Debian/Ubuntu:

Code:

sudo apt-get update && sudo apt-get upgrade && sudo reboot

The reboot is important.

Thanks for the heads up windpath - done.

+1 Thank you
Wink

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: windpath on February 17, 2016, 12:38:34 PM

So, if you have not heard yet there is another serious vulnerability for anyone running Unix based machines.

A severe vulnerability in the Gnu C Library's DNS client has been discovered and it affects just about EVERY bitcoin implementation.

Info here: http://linux.slashdot.org/story/16/02/16/1724222/red-hat-google-disclose-severe-glibc-dns-vulnerability-patched-but-widespread

Patches are available, but you must update.

For Debian/Ubuntu:

Code:

sudo apt-get update && sudo apt-get upgrade && sudo reboot

The reboot is important.

Thanks for the heads up windpath - done.

windpath

legendary

Activity: 1258

Merit: 1027

So, if you have not heard yet there is another serious vulnerability for anyone running Unix based machines.

A severe vulnerability in the Gnu C Library's DNS client has been discovered and it affects just about EVERY bitcoin implementation.

Info here: http://linux.slashdot.org/story/16/02/16/1724222/red-hat-google-disclose-severe-glibc-dns-vulnerability-patched-but-widespread

Patches are available, but you must update.

For Debian/Ubuntu:

Code:

sudo apt-get update && sudo apt-get upgrade && sudo reboot

The reboot is important.

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: Meuh6879 on February 17, 2016, 07:41:30 AM

Classic and XT are based on 0.11.2 + somes 0.12.0 features.
0.12.0 RC5 is really a good build for all.

Both Core and Classic version 12 are release candidates and not recommended for mining.

That being said, on my testing node the speed improvements are impressive.

Meuh6879

legendary

Activity: 1512

Merit: 1012

Classic and XT are based on 0.11.2 + somes 0.12.0 features.
0.12.0 RC5 is really a good build for all.

wariner

legendary

Activity: 1257

Merit: 1004

pool.sexy

Quote from: windpath on February 16, 2016, 10:37:57 AM

Quote from: wariner on February 16, 2016, 05:28:05 AM

you confirm me that for bitcoin classic it's enough use bitcoin classic instead of bitcoin core?

or need change something on this line?

p2pool/p2pool/work.py

Code:

372 version=min(self.current_work.value['version'], 4),

You need to change the version in the line you quoted (372 in work.py) to:

Code:

version=min(self.current_work.value['version'], 0x30000000),

or

Code:

version=min(self.current_work.value['version'], 805306368),

Both work.

Thank you

But i'm come back to bitcoin core, to me it seems more efficient at this time compared to classic...you have noticed the same thing?

Meuh6879

legendary

Activity: 1512

Merit: 1012

looking good ... (refreshed local blockchain + refreshed shares of P2Pool)

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Ah, sorry. I misunderstood your question...... Tongue

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: wariner on February 16, 2016, 05:28:05 AM

you confirm me that for bitcoin classic it's enough use bitcoin classic instead of bitcoin core?

or need change something on this line?

p2pool/p2pool/work.py

Code:

372 version=min(self.current_work.value['version'], 4),

You need to change the version in the line you quoted (372 in work.py) to:

Code:

version=min(self.current_work.value['version'], 0x30000000),

or

Code:

version=min(self.current_work.value['version'], 805306368),

Both work.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

As far as I'm aware it's a straight swap - no changes needed. I tried the classic client for a few hours, but the latency was higher & a bit erratic, so I reverted back to core again.

wariner

legendary

Activity: 1257

Merit: 1004

pool.sexy

you confirm me that for bitcoin classic it's enough use bitcoin classic instead of bitcoin core?

or need change something on this line?

p2pool/p2pool/work.py

Code:

372 version=min(self.current_work.value['version'], 4),

Meuh6879

legendary

Activity: 1512

Merit: 1012

0.12.0 RC5 is ready : https://bitcoin.org/bin/bitcoin-core-0.12.0/test/

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Quote from: p3yot33at3r on February 14, 2016, 05:43:28 AM

Nice to wake up to a long overdue BLOCK!

Hopefully there will be a few more before the halving, when I'll be switching off my miners Sad

Interesting factoid: The last p2pool block was the first one found by a Bitcoinclassic node.......

It's because I came back of course. Anyway it's looking like it settled down to 94% or so with a .3s latency that seems to be constant.

Nice!

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 98. (Read 2591920 times)