Author

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

hero member
Activity: 737
Merit: 500
I have been having the same problem in the past month. Restarting everything sometimes fixes it.  This is what it shows now:

Code:
Node uptime: 0.788 days Peers: 6 out, 8 in
Local rate: 1.38GH/s (3.1% DOA) Expected time to share: 31.2 hours
Shares: 0 total (0 orphaned, 0 dead) Efficiency: ???

It's not a "problem" in the sense that something is not working right.   Your hashrate is just low enough that you're finding shares very often.  There will be dry spells where you won't have found any shares and then every once in a while (on average every 31 hours), you'll find a share and get payments in the next couple blocks, etc.  Note, the 31 hour estimate is an *average*.  It is not uncommon to find shares more frequently than that or more infrequently.  In reality, you may commonly see the time between shares range from 8 hours to 5 days.
member
Activity: 90
Merit: 10
Hey guys - looking for a bit of advice here. Just done a complete reinstall Xubuntu after my SSD conked out. While doing so, I decided to move my wallet data to a separate SSD in an effort to reduce strain/latency/wear on the main system SSD. When I start my *coind's (merged mining) everything syncs up fine, but when I start the p2pool program it fails to load any shares, starts going straight to work & spits out py errors about still downloading shares. All my config files are exactly the same as before so I'm wondering if I need a different setting for p2pool because the data files are on a separate drive? I start my *coind's with the added command:

-datadir=/path/to/data  -  everything works there, is there something I need to add to the p2pool startup command as well?

This is the first time I've had my wallet data on a separate drive, and the first time I've had any problems with my configuration not working. All dependencies/packages are installed/checked/double checked. Any ideas/advice would be greatly appreciated  Wink

EDIT: I'm sure it's a basic, simple mistake I've made - I just can't see it....... Roll Eyes

EDIT1:  Or, am I the only person using a separate drive for their wallet data on p2pool.......and this is a bug?

I had a similar problem a long time ago in windows.  I just made a junction/symlink so when you browse to that folder on the C. Drive you're actually going to the other drive.  No idea if it's a bug or if I was doing something wrong I just wanted it back up as quick as possible and I was confident that'd work.  You can do the same thing in Linux I'm sure but I can't remember the command.
hero member
Activity: 1246
Merit: 501

EDIT1:  Or, am I the only person using a separate drive for their wallet data on p2pool.......and this is a bug?

No, you're not, though I was doing it on Windows.  It worked fine, the p2pool.exe shouldn't care where the data files are, it's just communicating with the *coind RPC interface(s).
hero member
Activity: 546
Merit: 500
I have been having the same problem in the past month. Restarting everything sometimes fixes it.  This is what it shows now:

Code:
Node uptime: 0.788 days Peers: 6 out, 8 in
Local rate: 1.38GH/s (3.1% DOA) Expected time to share: 31.2 hours
Shares: 0 total (0 orphaned, 0 dead) Efficiency: ???
sr. member
Activity: 337
Merit: 250
I have a huge problem! Shocked I didn't recieve payments from last 2 found blocks!!! My miner is working constantly but the last payment is from 29.08.2013 after that nothing.... This is my BTC address 1HhnzLoam81FRcrjBJkGYVHoWduDwsqs6C

What's your hashrate?  Have you found any shares recently?

In cgminer accepted shares are normal, and it works good, in p2pool.exe I have 0 shares and 0.0000 payout... Ihave just restarted PC and started all over again, but, with the same result....

cgminer shares are not real p2pool shares.  They are psuedo shares to help you see that your miner is working.  All that matters for getting paid is finding real, p2pool shares (which are much higher difficulty).  You have found 0.  That means you don't get any payout in any blocks found.  You didn't answer the question about your hashrate, but if you look at the p2pool console output, it will also tell you the average amount of time to fine 1 share at your current hashrate.  My guess is that your hashrate is pretty low and that average time is very long. 

My hashrate varies from 700-1600 MHs, according to p2pool. And average time to find share is from 7-20 hours. Anyway now it is all OK since I am getting paid. Thanks!
hero member
Activity: 737
Merit: 500
I have a huge problem! Shocked I didn't recieve payments from last 2 found blocks!!! My miner is working constantly but the last payment is from 29.08.2013 after that nothing.... This is my BTC address 1HhnzLoam81FRcrjBJkGYVHoWduDwsqs6C

What's your hashrate?  Have you found any shares recently?

In cgminer accepted shares are normal, and it works good, in p2pool.exe I have 0 shares and 0.0000 payout... Ihave just restarted PC and started all over again, but, with the same result....

cgminer shares are not real p2pool shares.  They are psuedo shares to help you see that your miner is working.  All that matters for getting paid is finding real, p2pool shares (which are much higher difficulty).  You have found 0.  That means you don't get any payout in any blocks found.  You didn't answer the question about your hashrate, but if you look at the p2pool console output, it will also tell you the average amount of time to fine 1 share at your current hashrate.  My guess is that your hashrate is pretty low and that average time is very long. 
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
Hey guys - looking for a bit of advice here. Just done a complete reinstall Xubuntu 12.04 after my SSD conked out. While doing so, I decided to move my wallet data to a separate SSD in an effort to reduce strain/latency/wear on the main system SSD. When I start my *coind's (merged mining) everything syncs up fine, but when I start the p2pool program it fails to load any shares, starts going straight to work & spits out py errors about still downloading shares. All my config files are exactly the same as before so I'm wondering if I need a different setting for p2pool because the data files are on a separate drive? I start my *coind's with the added command:

-datadir=/path/to/data  -  everything works there, is there something I need to add to the p2pool startup command as well?

This is the first time I've had my wallet data on a separate drive, and the first time I've had any problems with my configuration not working. All dependencies/packages are installed/checked/double checked. Any ideas/advice would be greatly appreciated  Wink

EDIT: I'm sure it's a basic, simple mistake I've made - I just can't see it....... Roll Eyes

EDIT1:  Or, am I the only person using a separate drive for their wallet data on p2pool.......and this is a bug?

OK, nothing doing here - I'll ask around instead.......
sr. member
Activity: 337
Merit: 250
I have a huge problem! Shocked I didn't recieve payments from last 2 found blocks!!! My miner is working constantly but the last payment is from 29.08.2013 after that nothing.... This is my BTC address 1HhnzLoam81FRcrjBJkGYVHoWduDwsqs6C

What's your hashrate?  Have you found any shares recently?

In cgminer accepted shares are normal, and it works good, in p2pool.exe I have 0 shares and 0.0000 payout... Ihave just restarted PC and started all over again, but, with the same result....
hero member
Activity: 737
Merit: 500
I have a huge problem! Shocked I didn't recieve payments from last 2 found blocks!!! My miner is working constantly but the last payment is from 29.08.2013 after that nothing.... This is my BTC address 1HhnzLoam81FRcrjBJkGYVHoWduDwsqs6C

What's your hashrate?  Have you found any shares recently?
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
Hey guys - looking for a bit of advice here. Just done a complete reinstall Xubuntu 12.04 after my SSD conked out. While doing so, I decided to move my wallet data to a separate SSD in an effort to reduce strain/latency/wear on the main system SSD. When I start my *coind's (merged mining) everything syncs up fine, but when I start the p2pool program it fails to load any shares, starts going straight to work & spits out py errors about still downloading shares. All my config files are exactly the same as before so I'm wondering if I need a different setting for p2pool because the data files are on a separate drive? I start my *coind's with the added command:

-datadir=/path/to/data  -  everything works there, is there something I need to add to the p2pool startup command as well?

This is the first time I've had my wallet data on a separate drive, and the first time I've had any problems with my configuration not working. All dependencies/packages are installed/checked/double checked. Any ideas/advice would be greatly appreciated  Wink

EDIT: I'm sure it's a basic, simple mistake I've made - I just can't see it....... Roll Eyes

EDIT1:  Or, am I the only person using a separate drive for their wallet data on p2pool.......and this is a bug?
sr. member
Activity: 337
Merit: 250
I have a huge problem! Shocked I didn't recieve payments from last 2 found blocks!!! My miner is working constantly but the last payment is from 29.08.2013 after that nothing.... This is my BTC address 1HhnzLoam81FRcrjBJkGYVHoWduDwsqs6C
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
Have received this error twice now. This is on a DGC p2pool with 30 Mh/s. When the error occurs it stops all mining until the pool is restarted.

Based off of p2pool 13.3. 6 nodes with one having 98% of the hashrate. Any help would be appreciated.

Where's the source for DGC-P2Pool? This seems like it should be impossible with vanilla P2Pool.
You can also use my fork for altcoins: https://github.com/Rav3nPL/p2pool-rav
legendary
Activity: 1270
Merit: 1000
Where's the source for DGC-P2Pool? This seems like it should be impossible with vanilla P2Pool.

https://github.com/CartmanSPC/p2pool

Files modified:
p2pool/networks.py
p2pool/bitcoin/networks.py
hero member
Activity: 516
Merit: 643
Have received this error twice now. This is on a DGC p2pool with 30 Mh/s. When the error occurs it stops all mining until the pool is restarted.

Based off of p2pool 13.3. 6 nodes with one having 98% of the hashrate. Any help would be appreciated.

Where's the source for DGC-P2Pool? This seems like it should be impossible with vanilla P2Pool.
legendary
Activity: 1270
Merit: 1000
Quote
Quote
Based off of p2pool 13.3. 6 nodes with one having 98% of the hashrate. Any help would be appreciated.
I wouldn't have a clue how to fix it, but it'd probably be helpful to (someone) to know if you're the node that's contributing the 98%

Yes. The node contributing 98% is the one that got the error.
zvs
legendary
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
Quote
If you want to be taken seriously present your case clearly "a block that'll most likely be orphaned" is not the same than an orphaned p2pool share. It's a misleading statement at best FUD at worst, don't be surprised to see "bullshit" in response.

I usually don't read your posts in details anymore as I can't understand much of it without disproportionate efforts, but what reads like a risk of orphaned blocks with no basis is enough to catch my attention...

Everything is "FUD", misleading, or needs more data...  go ahead, present yourself as the resident p2pool 'guru', solicit more donations

my pool is public and I make shit all from it, but it is fun to tinker with.  like the change regarding punishing shares, it's 35/35 since then.  ofc that's too small a sample to make a conclusive opinion, but it's promising

i don't read your posts either, unless they're directed towards me.  obvious, right?  otherwise I wouldn't be spewing all the FUD as I'd already know all the answers

Quote
Based off of p2pool 13.3. 6 nodes with one having 98% of the hashrate. Any help would be appreciated.
I wouldn't have a clue how to fix it, but it'd probably be helpful to (someone) to know if you're the node that's contributing the 98%
legendary
Activity: 1270
Merit: 1000
Have received this error twice now. This is on a DGC p2pool with 30 Mh/s. When the error occurs it stops all mining until the pool is restarted.



Based off of p2pool 13.3. 6 nodes with one having 98% of the hashrate. Any help would be appreciated.
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
It is useless to compare P2pool to any other pool after 24h mining...
See p2pool.info - if luck >100% you are earning more than 0% PPS, if <100% you earning less.
full member
Activity: 201
Merit: 100
You will get paid more for the higher difficulty shares.  It will reduce your bandwidth usage if you are putting out a lot of hash power.
Could just be anecdotal rather than consequential, but since adjusting my miners' difficulty the number of orphaned shares has dropped significantly:
to 23/August: Shares: 54 total (10 orphaned, 1 dead)
as at 28/August: Shares: 85 total (11 orphaned, 2 dead)

So only 1 orphan, 1 dead in 5 days compared to 10 orphan and 1 dead in previous 8

I've set (local) difficulty to nearest power of 2 up from actual ghs/2 (after doing some testing with a few pps pools and comparing 24h earnings at various difficulties - 30 Gh/s @ 32 actually earned more (2.1%) than 30Gh/s @ 16, but 30Gh/s @ 64 earned 17% less.
hero member
Activity: 896
Merit: 1000

except sometimes those stales that solve blocks... are, well, a stale right after a block was found.  re the shenanigans that go on when switching from one block to another

not sure if p2pool would proceed along it's own chain or not?  either way, it's a block that'll most likely be orphaned.  that's when the slow getblocktemplate matters


Bullshit.

After heaps of messages on this subject on this very thread (last was mine a few messages ago) you still don't understand that p2pool doesn't rely on getblocktemplate result being available to build the coinbase miners are working on.
p2pool is connected to the bitcoin P2P network and detects blocks before a getblocktemplate result is available for the new block and present a valid coinbase to miners ASAP. So there's absolutely no reason a "stale p2pool share" block would have more chance of being orphaned than any other block.

I think you're the one that doesn't understand, lol.

Maybe you should look at the specifics presented.

Listen, there's a reason why so many shares  get 'punished'.  

ed:  since I've disabled the 'punish' feature you'll be able to see all the orphans.  most of the time it's just one, the person unfortunate enough to have the share right before the new block, but just wait for a block where you have 2 or 3 orphans coming off of it,  some will have a received time after the new block, but still be working on old block.

If you want to be taken seriously present your case clearly "a block that'll most likely be orphaned" is not the same than an orphaned p2pool share. It's a misleading statement at best FUD at worst, don't be surprised to see "bullshit" in response.

I usually don't read your posts in details anymore as I can't understand much of it without disproportionate efforts, but what reads like a risk of orphaned blocks with no basis is enough to catch my attention...
Jump to: