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

[fruor]

Individual miners on a public node would see reduced variance in their own shares, since pool hash rate is taken out of the equation. They could do this by hand now with ADDR/1 (or say /.000001 for scrypt), but I think handling it automatically makes more sense (and keeps vardiff alive for miners that are maybe bigger than justifies using ADDR/1).

if I run my own p2pool node how do I change to ADDR/0.001?

is there a switch in run_p2pool to achieve this?
when i do run_p2pool -a <addr>/0.0001
it gives me a parse error

[phillipsjk]

Hi! I have the following problem. Sometimes, if the restart p2pool (quark-algoritm), when the power pool > ~ 150 MH / s, process starts to load the processor to 100% and all shares the dead. All logentries "DEAD ON ARRIVAL". Why this happens and how to solve this problem?

If it takes your node more than 30 seconds to verify a block, you will get 100% stales. Even without 6 different hashing algorithms, I have seen up to 12 seconds of CPU lag on my machine processing P2Pool.

Part of the problem may be that python is an interpreted, not compiled language. A Just-In-Time compiler like PyPy may help. (I think I will test that on my own machine)

Edit: I think actual block processing is handed off to Bitcoind. P2Pool still has its own chain though.
Edit: pypy Does not work:

Code:

Traceback (most recent call last):
  File "app_main.py", line 72, in run_toplevel
  File "./p2pool/run_p2pool.py", line 3, in <module>
    from p2pool import main
  File "/usr/home/P2Pool/p2pool/p2pool/main.py", line 17, in <module>
    from twisted.internet import defer, reactor, protocol, tcp
ImportError: No module named twisted

Update:

Got it working.

[roy7]

if I run my own p2pool node how do I change to ADDR/0.001?

is there a switch in run_p2pool to achieve this?
when i do run_p2pool -a <addr>/0.0001
it gives me a parse error

Is it the username your miner uses to connect to a node. Instead of username = payment address, use ADDR+DIFF to control the pseudo share difficulty (for graphing or support really old asics) or use ADDR/DIFF to control your share target. You can also use both. For instance I mine Uno (a sha256 coin) with ADDR/64000+64 on my Antminer S1 (180GH).

[paniczklos]

Hi guys, do you have any idea what might be causing this hashrate drops on my p2pool ?

http://freebtc.eu:8336/static/



I've upgaradedthe CPU and RAM since the firstdrop, but they occured again ;/ RAM and CPU are at 10% at most

Code:

2014-02-27 10:06:10.109157 > Unhandled Error
2014-02-27 10:06:10.109247 > Traceback (most recent call last):
2014-02-27 10:06:10.109336 >   File "/root/p2pool-blackcoin/p2pool/util/variable.py", line 75, in set
2014-02-27 10:06:10.109428 >     self.transitioned.happened(oldvalue, value)
2014-02-27 10:06:10.109563 >   File "/root/p2pool-blackcoin/p2pool/util/variable.py", line 42, in happened
2014-02-27 10:06:10.109641 >     func(*event)
2014-02-27 10:06:10.109717 >   File "/root/p2pool-blackcoin/p2pool/work.py", line 118, in _
2014-02-27 10:06:10.109792 >     self.new_work_event.happened()
2014-02-27 10:06:10.109869 >   File "/root/p2pool-blackcoin/p2pool/util/variable.py", line 42, in happened
2014-02-27 10:06:10.109944 >     func(*event)
2014-02-27 10:06:10.110019 > --- <exception caught here> ---
2014-02-27 10:06:10.110094 >   File "/root/p2pool-blackcoin/p2pool/bitcoin/stratum.py", line 38, in _send_work
2014-02-27 10:06:10.110171 >     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2014-02-27 10:06:10.110262 >   File "/root/p2pool-blackcoin/p2pool/work.py", line 176, in preprocess_request
2014-02-27 10:06:10.110348 >     raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2014-02-27 10:06:10.110424 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind
2014-02-27 10:06:10.110715 > Unhandled Error

Code:

2014-02-27 10:06:10.429822 > Traceback (most recent call last):
2014-02-27 10:06:10.429901 >   File "/root/p2pool-blackcoin/p2pool/util/variable.py", line 75, in set
2014-02-27 10:06:10.429978 >     self.transitioned.happened(oldvalue, value)
2014-02-27 10:06:10.430054 >   File "/root/p2pool-blackcoin/p2pool/util/variable.py", line 42, in happened
2014-02-27 10:06:10.430130 >     func(*event)
2014-02-27 10:06:10.430206 >   File "/root/p2pool-blackcoin/p2pool/work.py", line 118, in _
2014-02-27 10:06:10.430282 >     self.new_work_event.happened()
2014-02-27 10:06:10.430359 >   File "/root/p2pool-blackcoin/p2pool/util/variable.py", line 42, in happened
2014-02-27 10:06:10.430434 >     func(*event)
2014-02-27 10:06:10.430559 > --- <exception caught here> ---
2014-02-27 10:06:10.430641 >   File "/root/p2pool-blackcoin/p2pool/bitcoin/stratum.py", line 38, in _send_work
2014-02-27 10:06:10.430718 >     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2014-02-27 10:06:10.430796 >   File "/root/p2pool-blackcoin/p2pool/work.py", line 176, in preprocess_request
2014-02-27 10:06:10.430885 >     raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2014-02-27 10:06:10.430963 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind
2014-02-27 10:06:10.519798 > Error getting work from bitcoind:
2014-02-27 10:06:10.519982 > Traceback (most recent call last):
2014-02-27 10:06:10.520197 > Failure: twisted.internet.error.ConnectBindError: Couldn't bind: 24: Too many open files.
2014-02-27 10:06:10.558710 > Unhandled Error
2014-02-27 10:06:10.558896 > Traceback (most recent call last):
2014-02-27 10:06:10.558985 >   File "/root/p2pool-blackcoin/p2pool/main.py", line 578, in run
2014-02-27 10:06:10.559066 >     reactor.run()
2014-02-27 10:06:10.559146 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1192, in run
2014-02-27 10:06:10.559203 >     self.mainLoop()
2014-02-27 10:06:10.559295 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1201, in mainLoop
2014-02-27 10:06:10.559373 >     self.runUntilCurrent()
2014-02-27 10:06:10.559455 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 824, in runUntilCurrent
2014-02-27 10:06:10.559532 >     call.func(*call.args, **call.kw)
2014-02-27 10:06:10.559608 > --- <exception caught here> ---

[phillipsjk]

Hi guys, do you have any idea what might be causing this hashrate drops on my p2pool ?

http://freebtc.eu:8336/static/

I was going to guess no internet until you posted the error log.

"0197 > Failure: twisted.internet.error.ConnectBindError: Couldn't bind: 24: Too many open files."
 suggest you should look into raising the number of file descriptors. Have not run into that problem myself yet.

[paniczklos]

thanks I hope it will help.

root@panda:/etc/security# cat /proc/sys/fs/file-max
1000000
root@panda:/etc/security# ulimit -Sn
524288
root@panda:/etc/security# ulimit -Hn
524288

Many users had left my node so it helped anyway ;/

[CartmanSPC]

Part of the problem may be that python is an interpreted, not compiled language.

I have seen compiled versions of p2pool (at least for windows in the OP). Anyone have instructions on how to do so? I'm not so much interested in increasing the performance as making it easier for others to use without having to load dependencies.

[smooth]

I got an error where it said something about trying to broadcast a share without having all the transactions (?). Then the share was counted against orphans, I think. The message scrolled off before I could save it. There's no log file for p2pool right? At least I couldn't find it.

[roy7]

I got an error where it said something about trying to broadcast a share without having all the transactions (?). Then the share was counted against orphans, I think. The message scrolled off before I could save it. There's no log file for p2pool right? At least I couldn't find it.

It's in data/coinname/log

[smooth]

It's in data/coinname/log

Thank you.


2014-02-28 09:21:58.696997 > Error while processing Event callbacks:
2014-02-28 09:21:58.697274 > Traceback (most recent call last):
2014-02-28 09:21:58.697372 >   File "/home/p2pool/p2pool/p2pool/p2p.py", line 282, in handle_shares
2014-02-28 09:21:58.697467 >     self.node.handle_shares(result, self)
2014-02-28 09:21:58.697555 >   File "/home/p2pool/p2pool/p2pool/node.py", line 48, in handle_shares
2014-02-28 09:21:58.697869 >     self.node.set_best_share()
2014-02-28 09:21:58.697977 >   File "/home/p2pool/p2pool/p2pool/node.py", line 297, in set_best_share
2014-02-28 09:21:58.698067 >     self.best_share_var.set(best)
2014-02-28 09:21:58.698153 >   File "/home/p2pool/p2pool/p2pool/util/variable.py", line 74, in set
2014-02-28 09:21:58.698240 >     self.changed.happened(value)
2014-02-28 09:21:58.698327 > --- <exception caught here> ---
2014-02-28 09:21:58.698436 >   File "/home/p2pool/p2pool/p2pool/util/variable.py", line 42, in happened
2014-02-28 09:21:58.698523 >     func(*event)
2014-02-28 09:21:58.698608 >   File "/home/p2pool/p2pool/p2pool/node.py", line 96, in broadcast_share
2014-02-28 09:21:58.698694 >     peer.sendShares([share for share in shares if share.peer_addr != peer.addr], self.node.tracker, self.node.known_txs_var.value, include_txs_with\
=[share_hash])
2014-02-28 09:21:58.698782 >   File "/home/p2pool/p2pool/p2pool/p2p.py", line 290, in sendShares
2014-02-28 09:21:58.698867 >     assert tx_hash in known_txs, 'tried to broadcast share without knowing all its new transactions'
2014-02-28 09:21:58.698954 > exceptions.AssertionError: tried to broadcast share without knowing all its new transactions

[roy7]

I've put in a pull request to fix the problem with vardiff sending out 0 diff work that causes some GPU miners to spew endless HWs.

https://github.com/forrestv/p2pool/pull/185/files

[smoothrunnings]

Has anyone ever seen their P2Pool show "no shares yet" under the Active Miners on This Node?

I am seeing this on my Bitcoin P2Pool, also I am seeing the entire pool hashrate has dropped steeply to 99TH/s.

[paniczklos]

What could be worng if the local hashrate is higher than total p2pool hashrate ? ;/

[smoothrunnings]

What could be worng if the local hashrate is higher than total p2pool hashrate ? ;/

I don't think my 186GH/s is higher than the now 107TH/s.

[paniczklos]

What could be worng if the local hashrate is higher than total p2pool hashrate ? ;/

I don't think my 186GH/s is higher than the now 107TH/s.

Heh,

but look here:

http://freebtc.eu:9188/static/

[smoothrunnings]

What could be worng if the local hashrate is higher than total p2pool hashrate ? ;/

I don't think my 186GH/s is higher than the now 107TH/s.

Heh,

but look here:

http://freebtc.eu:9188/static/

That's not Bitcoin.

[roy7]

What could be worng if the local hashrate is higher than total p2pool hashrate ? ;/

It's possible the local and global hash rate figures on web interface are being averaged over different lengths of time.

[smoothrunnings]

Have a look at my node; http://p2pool.smoothrunnings.ca:9332/

My local hardware is which the top one is not showing any shares, it was even doing that before it took it down for a while today; I had another issue both with my bicoind (bitcoin-qt) and my own wallet; that issue is I transferred just over 1/2 a bitcoin out and it got stuck. So after a week it according to my personal wallet started to get peers (3 of 6 now), yet on my node it still shows 0 confirmations. Anyhow even after putting my node back up and its been a few hours the miner on the bottom which is running from a different location is getting shares.

The difference here is that the two inside miners have been updated to cgminer 4.0.1 while the outside miner uses 3.9.0 I wonder if the 4.0.1 cgminer is causing the "no shares yet" issue, if it's an issue?

What do you think?

Thanks,
 

[Tegija]

Have a look at my node; http://p2pool.smoothrunnings.ca:9332/

My local hardware is which the top one is not showing any shares, it was even doing that before it took it down for a while today; I had another issue both with my bicoind (bitcoin-qt) and my own wallet; that issue is I transferred just over 1/2 a bitcoin out and it got stuck. So after a week it according to my personal wallet started to get peers (3 of 6 now), yet on my node it still shows 0 confirmations. Anyhow even after putting my node back up and its been a few hours the miner on the bottom which is running from a different location is getting shares.

The difference here is that the two inside miners have been updated to cgminer 4.0.1 while the outside miner uses 3.9.0 I wonder if the 4.0.1 cgminer is causing the "no shares yet" issue, if it's an issue?

What do you think?

Thanks,
 

now your node shows 2 shares. considering your uptime it is ok.  both shares are probably made by your miner 1JiWFoe6QaE7N6mv2HBkjr4izuDX3cqDQQ. little patience and i think all will be ok.
it can be that both miners made one share and because you have 50%fee one of the shares is going to your node wallet. as you can see your node is "earning" more than your miners.
as far i cold notice there is no differences which version cgminer you have, results are practically equal. my miner with 4.0.1 work fine and i don´t see any difference to miners with 3.9.0.

[smoothrunnings]

Have a look at my node; http://p2pool.smoothrunnings.ca:9332/

My local hardware is which the top one is not showing any shares, it was even doing that before it took it down for a while today; I had another issue both with my bicoind (bitcoin-qt) and my own wallet; that issue is I transferred just over 1/2 a bitcoin out and it got stuck. So after a week it according to my personal wallet started to get peers (3 of 6 now), yet on my node it still shows 0 confirmations. Anyhow even after putting my node back up and its been a few hours the miner on the bottom which is running from a different location is getting shares.

The difference here is that the two inside miners have been updated to cgminer 4.0.1 while the outside miner uses 3.9.0 I wonder if the 4.0.1 cgminer is causing the "no shares yet" issue, if it's an issue?

What do you think?

Thanks,
 

now your node shows 2 shares. considering your uptime it is ok.  both shares are probably made by your miner 1JiWFoe6QaE7N6mv2HBkjr4izuDX3cqDQQ. little patience and i think all will be ok.
it can be that both miners made one share and because you have 50%fee one of the shares is going to your node wallet. as you can see your node is "earning" more than your miners.
as far i cold notice there is no differences which version cgminer you have, results are practically equal. my miner with 4.0.1 work fine and i don´t see any difference to miners with 3.9.0.

okay I will wait a bit longer to see what happen, but it used to never to this, both miners always showed  predicted payouts. On a different note the p2pool-note-status static page has been updated, it now shows the "payout if block were found now".