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

[mdude77]

Another example where things aren't working optimally:

I unpacked the latest git into a new folder, and fired it up.  A number of times as it was "processing xxx shares from [...]" it would take so long that when it finished, a bunch of errors would be thrown because things timed out.  I don't know Python very well at all, but it doesn't seem like p2pool is multithreaded.  I know multithreading isn't a trivial task.  Am I missing something, or is p2pool multithreaded and I'm just not seeing it?

M

[1713270331]

1713270331

[1713270331]

1713270331

[daemondazz]

Is there any way of getting the per-miner stats from p2pool as JSON or even just a raw number? I want to set up Nagios to alert me if any of my miners stop working.

Something like:
http://cryptominer.org:9332/miner/<username>

Returning (hash rate and dead/stale):
516.12312 12.1451

Currently getting familiar with the code, so I can add this if not already in place.

[Amph]

it seems that the latency is better now, i get 0.06ms, before was 0.290 or something

when he say" lost 8 share due to connection lost" it's equal to= i lost 8 transiction?

[mdude77]

Is there any way of getting the per-miner stats from p2pool as JSON or even just a raw number? I want to set up Nagios to alert me if any of my miners stop working.

Something like:
http://cryptominer.org:9332/miner/<username>

Returning (hash rate and dead/stale):
516.12312 12.1451

Currently getting familiar with the code, so I can add this if not already in place.

I think http://localhost:9554/local_stats is as close as you can get. 

M

[Richy_T]

I think http://localhost:9554/local_stats is as close as you can get. 

M

Wow, I didn't know that existed. That makes something I'm trying to do a lot easier.

[bitpop]

I get ---ERROR---

[Searinox]

For the first time in a month of mining on p2pool, the page is saying "Payout if a block were found now: 0 BTC". This is in spite of the hashrate being shown normal and DOAs/orphans next to nonexistent. And about an hour ago it was showing a non-zero payment. I restarted the entire btc, p2pool, bfgminer ensemble but it's still showing 0. Why does this happen?

[daemondazz]

Wow, I didn't know that existed. That makes something I'm trying to do a lot easier.

Yep, useful. What time period are those stats over? In particular I mean the miner_hash_rates and miner_dead_hash_rates. I need them over a reasonably short period for alarming to be able to react if a miner goes away.

[daemondazz]

For the first time in a month of mining on p2pool, the page is saying "Payout if a block were found now: 0 BTC". This is in spite of the hashrate being shown normal and DOAs/orphans next to nonexistent. And about an hour ago it was showing a non-zero payment. I restarted the entire btc, p2pool, bfgminer ensemble but it's still showing 0. Why does this happen?

Do you have any peer connections?

[centove]

Wow, I didn't know that existed. That makes something I'm trying to do a lot easier.

Yep, useful. What time period are those stats over? In particular I mean the miner_hash_rates and miner_dead_hash_rates. I need them over a reasonably short period for alarming to be able to react if a miner goes away.

Code:

def get_local_stats():
...
   lookbehind = min(node.tracker.get_height(node.best_share_var.value), 3600//node.net.SHARE_PERIOD)
...

SHARE_PERIOD=10, # seconds for BTC...

So... I would guess that it's a 10 sec resolution?

[Searinox]

For the first time in a month of mining on p2pool, the page is saying "Payout if a block were found now: 0 BTC". This is in spite of the hashrate being shown normal and DOAs/orphans next to nonexistent. And about an hour ago it was showing a non-zero payment. I restarted the entire btc, p2pool, bfgminer ensemble but it's still showing 0. Why does this happen?

Do you have any peer connections?

...I have them right now. And my payout's back to normal. I'm not sure about before. If it happens again, I'll check.

[forrestv]

For the first time in a month of mining on p2pool, the page is saying "Payout if a block were found now: 0 BTC". This is in spite of the hashrate being shown normal and DOAs/orphans next to nonexistent. And about an hour ago it was showing a non-zero payment. I restarted the entire btc, p2pool, bfgminer ensemble but it's still showing 0. Why does this happen?

Do you have any peer connections?

...I have them right now. And my payout's back to normal. I'm not sure about before. If it happens again, I'll check.

Do you have a pretty low hash rate? If you don't get a share every 24 hours, your payout will drop to zero at times.

Wow, I didn't know that existed. That makes something I'm trying to do a lot easier.

Yep, useful. What time period are those stats over? In particular I mean the miner_hash_rates and miner_dead_hash_rates. I need them over a reasonably short period for alarming to be able to react if a miner goes away.

Code:

def get_local_stats():
...
   lookbehind = min(node.tracker.get_height(node.best_share_var.value), 3600//node.net.SHARE_PERIOD)
...

SHARE_PERIOD=10, # seconds for BTC...

So... I would guess that it's a 10 sec resolution?

No, one hour (3600 seconds).

[daemondazz]

Code:

def get_local_stats():
...
   lookbehind = min(node.tracker.get_height(node.best_share_var.value), 3600//node.net.SHARE_PERIOD)
...

SHARE_PERIOD=10, # seconds for BTC...

So... I would guess that it's a 10 sec resolution?

No, one hour (3600 seconds).

Yeah, that'll be pulling out the last 360 samples - at 10 seconds each for an hour in total.

Perfect! Thanks!

[centove]

For the first time in a month of mining on p2pool, the page is saying "Payout if a block were found now: 0 BTC". This is in spite of the hashrate being shown normal and DOAs/orphans next to nonexistent. And about an hour ago it was showing a non-zero payment. I restarted the entire btc, p2pool, bfgminer ensemble but it's still showing 0. Why does this happen?

Do you have any peer connections?

...I have them right now. And my payout's back to normal. I'm not sure about before. If it happens again, I'll check.

Do you have a pretty low hash rate? If you don't get a share every 24 hours, your payout will drop to zero at times.

Wow, I didn't know that existed. That makes something I'm trying to do a lot easier.

Yep, useful. What time period are those stats over? In particular I mean the miner_hash_rates and miner_dead_hash_rates. I need them over a reasonably short period for alarming to be able to react if a miner goes away.

Code:

def get_local_stats():
...
   lookbehind = min(node.tracker.get_height(node.best_share_var.value), 3600//node.net.SHARE_PERIOD)
...

SHARE_PERIOD=10, # seconds for BTC...

So... I would guess that it's a 10 sec resolution?

No, one hour (3600 seconds).

Oops... Well yeah I never claimed to be good with math

[Tittiez]

I'm trying to set up P2Pool for an altcoin, but it is hanging at:

Code:

Testing bitcoind P2P connection to '127.0.0.1:19323'

What would cause this? I can see the node on the daemon.

Code:

{
        "addr" : "127.0.0.1:51311",
        "services" : "00000000",
        "lastsend" : 0,
        "lastrecv" : 1367878607,
        "conntime" : 1367878607,
        "version" : 0,
        "subver" : "",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : -1,
        "banscore" : 0
    }

[forrestv]

I'm trying to set up P2Pool for an altcoin, but it is hanging at:

Code:

Testing bitcoind P2P connection to '127.0.0.1:19323'

What would cause this? I can see the node on the daemon.

Code:

{
        "addr" : "127.0.0.1:51311",
        "services" : "00000000",
        "lastsend" : 0,
        "lastrecv" : 1367878607,
        "conntime" : 1367878607,
        "version" : 0,
        "subver" : "",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : -1,
        "banscore" : 0
    }

Setting the magic numbers in p2pool/bitcoin/networks.py incorrectly.

[mdude77]

I get ---ERROR---

I use port 9554, yours may be different.

M

[daemondazz]

Code:

def get_local_stats():
...
   lookbehind = min(node.tracker.get_height(node.best_share_var.value), 3600//node.net.SHARE_PERIOD)
...

SHARE_PERIOD=10, # seconds for BTC...

So... I would guess that it's a 10 sec resolution?

No, one hour (3600 seconds).

Yeah, that'll be pulling out the last 360 samples - at 10 seconds each for an hour in total.

Perfect! Thanks!

Just to follow up on this, I've posted my nagios plugin on github: https://github.com/daemondazz/nagios-plugins

[baloo_kiev]

I'd like to point out some basic difficulty-related considerations here, which I believe were not mentioned in this thread. Please correct me if I am wrong!

Here's how I suggest to determine desired share difficulty. Variance of miner's income depends both on his own share generation variance and the p2pool's block generation variance. Even if you have high hashrate and generate shares every minute or so, you still get payouts only from blocks found by p2pool. One familiar with statistics/probability theory may see that payout variance ((rms deviation) / (estimated value)) after mining for T hours is proportional to

Code:

variance ~ sqrt(((miner's estimated time to share) + (p2pool's estimated time to block)) / T)

At the time of this post, p2pool is running at ~800 GH/s with Bitcoin difficulty ~10M and share difficulty ~1500. At this rate, expected time to block is ~16 hours.
At default share difficulty, estimated time to share for a miner with 1 GH/s is ~1.8 hours, which gives him overall variance coefficient ~sqrt( 16 + 1.8 ). If the miner manually sets his share difficulty to 5000, it will become ~sqrt(16 + 6), which is only ~11% higher.
Similarly, for a miner with 10 GH/s time to share is 0.18 hours, so variance at default difficulty is ~sqrt(16 + 0.18). So he can set his difficulty to 35,000, which gives variance of ~sqrt(16 + 4.2), which is again only 12% higher than default.
Only when a miner's time to share is comparable to (say, 3-5 times smaller than) the p2pool's time to block, increase of share difficulty will have considerable impact on his variance.

Tl;dr: I suggest that reasonable share difficulty for a miner is such, that estimated time to share is a couple of times lower than the p2pool's time to block. Setting it lower will harm small miners (increase their variance) without any serious decrease of the miner's own variance. Setting it higher will increase the miner's own variance.

[Richy_T]

I've been mining pretty well I thought but I didn't get a payout on the last block.

https://blockchain.info/block/000000000000006fdeafb19ca3c74baa5f31f1f36f98b79fb914229d1dc7fe9e

Also, the "Blocks found in last day" is showing a very old block

time   number   hash/explorer link   share
Thu May 02 2013 12:20:58 GMT-0500 (Central Daylight Time)   234219   000000000000003ca0bd661df02a9bba63fe0324b11c6c648a45d8b6b47adafb   →

Anyone know what's going on here?