|
Aseras
|
 |
May 03, 2012, 05:24:28 PM
Last edit: May 03, 2012, 05:37:40 PM by Aseras |
|
switched from cgminer 2.3.6 to 2.4. p2pool is primary with another as failover
was running 2.3.6 and .10.3 and was getting a share every 10-20 minutes
I've only gotten 1 share in 4 hours with >4GH somethings not happy.
I'm going to switch back and see whats happening.
012-05-03 13:25:05.584000 P2Pool: 17398 shares in chain (17402 verified/17402 total) Peers: 10 (0 incoming)
012-05-03 13:25:05.584000 Local: 4101MH/s in last 10.0 minutes Local dead on arrival: ~1.6% (0-3%) Expected time to share: 11.1 minutes
012-05-03 13:25:05.584000 Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-66%) Efficiency: ~110.8% (37-111%) Current payout: 0.0732 BTC
012-05-03 13:25:05.584000 Pool: 310GH/s Stale rate: 9.8% Expected time to block: 5.8 hours
Edit, switched to .10.3 with the current 2.4 cgminer and got 4 shares already. Either I had the worst luck and then the best luck or something's hokey for me.
|
|
|
|
|
|
tiker
|
|
May 03, 2012, 05:43:53 PM |
|
forestv: 0.11.1 - accessing page /peer_addresses returns: Request did not return a string Request: <GET /peer_addresses HTTP/1.1> Resource: <p2pool.web.WebInterface instance at 0xbfdb1ac> Value: u' .. ip addresses.... |
|
|
|
|
|
Aseras
|
|
May 03, 2012, 08:12:55 PM |
|
forestv: 0.11.1 - accessing page /peer_addresses returns: Request did not return a string Request: <GET /peer_addresses HTTP/1.1> Resource: <p2pool.web.WebInterface instance at 0xbfdb1ac> Value: u' .. ip addresses.... this works fine for me I'm still not getting any shares ( on .11.1 )  |
|
|
|
|
|
|
|
Aseras
|
|
May 03, 2012, 09:49:30 PM |
|
Nope get the error on your pool.
Did you delete the data folder and replace the web-static folder when you upgraded?
|
|
|
|
|
|
ChanceCoats123
|
|
May 03, 2012, 10:05:39 PM |
|
I'm about to get my update going in a second. Will report back.
|
|
|
|
|
|
echris1
|
|
May 03, 2012, 11:51:01 PM |
|
Looks like your page is working tiker, at least for me. I also upgraded a few hours ago, but everything seems to be working just fine. |
|
|
|
|
|
tiker
|
|
May 04, 2012, 03:31:46 AM |
|
Ya, I did another 'git pull' and got more updates. Restarted and it's working again.
|
|
|
|
|
|
Shadow383
|
|
May 04, 2012, 12:59:41 PM |
|
Updated my node last night - I seem to be getting notably lower DoA rates now which is interesting - has anything changed which you'd expect to affect this?
|
|
|
|
|
|
Prattler
|
|
May 04, 2012, 01:09:01 PM |
|
This switchover is different from previous ones - Instead of a scheduled time, all nodes will automatically switch 22 hours after 95% of the P2Pool hash rate has upgraded. Therefore, please upgrade as soon as possible so you're not part of the last 5%!
Superb idea, but I'm afraid that you might be aiming too high. 95% could never happen. I'd say 75% would be better. |
|
|
|
|
|
Dhomochevsky
|
|
May 04, 2012, 01:49:05 PM |
|
Complete noob to p2pool here. I have a strange problem, but first, a little background: I decided to slowly move all my hashing power to p2pool but for starters I wanted to experiment with it for a while, get the ropes. Followed the instructions HERE to the letter. I started mining using poclbm via guiminer on a single card, the miner shows ~340 MH and the p2pool server shows anywhere from 260 MH to 460 MH, with a median of about 330 MH per second, so that's about right. The DoA percentage is also fine, about 4% in general. The expected time to share shown is 2-2.5 hrs and my current efficiency is 108%. My problem is this: p2pool.info and my p2pool running process both show that p2pool has 300-something GH per second. Therefore my 300-something MH per second should yield about 5 BTcents per block solved by the pool. Since I started mining p2pool several blocks were solved and each of them gave me only 2.7 BTcents, about 60% of what 330 MH should've yielded. This last block is being worked on for more than ten hours now. Initially the payout showed the usual 2.7 cents, then 4.4 and now it dropped to 3.7 . I should mention that over these several blocks I accumulated 7 shares so far. I'm pretty sure that I'm missing something, but before I move my entire hashing power to p2pool I need to understand why a block yields less than it should and if it actually matters, given the way the shares work in p2pool. [edit] While I was writing this it seems one or two more blocks were solved and that's why the payout was changing, but still. |
|
|
|
|
|
Aseras
|
|
May 04, 2012, 02:08:16 PM |
|
p2pool is PPLNS. Your shares build value slowly and loose value slowly. It's to encourage long term mining. You won't see your maximum payout until a couple block go by, and even then your reward will be split among several later blocks as well. There's a good explanation with pictures here, http://pool-x.eu/aboutpplns |
|
|
|
|
DeathAndTaxes
Donator
Legendary
 Offline
Activity: 1218
Merit: 1079
Gerald Davis
|
|
May 04, 2012, 02:14:45 PM |
|
I'm pretty sure that I'm missing something, but before I move my entire hashing power to p2pool I need to understand why a block yields less than it should and if it actually matters, given the way the shares work in p2pool. PPLNS pays out your % of shares in the sharechain (not per block). If payouts were per block pool hoppers would rape p2pool to death. The sharechain is ~ 24 hours long. So your payouts in each block will be the % of shares you contributed for the last 24 hours (not that block). As new shares join the sharechain the oldest shares drop off. So the payout breakdown at any particular point in time is dependent on the prior 24 hours worth of shares. This is how any PPLNS (not just p2pool) pool works. If your hashing power is stable after ~ 24 hours your % of payout should be roughly equal (subject to variance) to your % of pool's hashing power. If you got 5% of hashing power you get ~5% of the reward each block. |
|
|
|
|
Qoheleth
Legendary
Offline
Activity: 960
Merit: 1028
Spurn wild goose chases. Seek that which endures.
|
|
May 04, 2012, 05:59:49 PM |
|
Does P2Pool have Socks4 support today? If not, is it a planned feature for the near future?
|
If there is something that will make Bitcoin succeed, it is growth of utility - greater quantity and variety of goods and services offered for BTC. If there is something that will make Bitcoin fail, it is the prevalence of users convinced that BTC is a magic box that will turn them into millionaires, and of the con-artists who have followed them here to devour them.
|
|
|
|
|
Qoheleth
Legendary
Offline
Activity: 960
Merit: 1028
Spurn wild goose chases. Seek that which endures.
|
|
May 04, 2012, 07:14:20 PM |
|
Also: is there any way to switch to a new destination address without restarting p2pool?
|
If there is something that will make Bitcoin succeed, it is growth of utility - greater quantity and variety of goods and services offered for BTC. If there is something that will make Bitcoin fail, it is the prevalence of users convinced that BTC is a magic box that will turn them into millionaires, and of the con-artists who have followed them here to devour them.
|
|
|
|
Krak
|
|
May 04, 2012, 07:37:45 PM |
|
Also: is there any way to switch to a new destination address without restarting p2pool?
Only thing you could do is put the new address as the username on your miner. |
BTC: 1KrakenLFEFg33A4f6xpwgv3UUoxrLPuGn
|
|
|
Gabi
Legendary
Offline
Activity: 1148
Merit: 1008
If you want to walk on water, get out of the boat
|
|
May 04, 2012, 08:21:54 PM |
|
Updated!
|
|
|
|
|
Red Emerald
|
|
May 04, 2012, 10:53:52 PM |
|
Also: is there any way to switch to a new destination address without restarting p2pool?
Only thing you could do is put the new address as the username on your miner. That works. If you want to ensure virtually no downtime, you can start a second instance of p2pool with the new parameters. It will complain about not being able to bind ports, but this is okay. Once it loads the share chain, quit the first instance and the new instance will bind to the ports as soon as it can. |
|
|
|
rav3n_pl
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
 |
May 04, 2012, 11:26:45 PM |
|
Maybe consider lower diff a bit and less longpool messages? I haven't share over last 24hrs...
I have only ~170MH/s and most of my worker get works are break by longpool reset.
In description it is about 10s between longpolls but in most cases i get longpool restart every 5s...
Also after upgrading to 11.1 i`m getting ALOT of dead on arrival (about 30% vs under 5% on 10.3), same worker and config.
|
|
|
|
|
