Bitcoin Forum
December 05, 2016, 10:35:51 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 [145] 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2029988 times)
doobeedoo
Newbie
*
Offline Offline

Activity: 24


View Profile
July 01, 2012, 08:23:17 PM
 #2881

I obeserved today a phenomenon

Suddenly my stales rate went drasticaly up allso the whole machine was lagging badly, im not sure about what did cause that, i could not find any activities in my logs so that wasnt caused by any apache related activity, just p2pool and the chains was running. I suspect that this has something to do with peers; this could be intentionaly or cause of a bug. i realized that stales and orphaned shares on the p2pool operating chain are probably caused trough this.

got the same problem.
my DOA increased to 40-50 %.
using bitcoind 6.3.


investigated that my ztex-boards caused the problem. for some reason java took 100% of all 4 cores.
did a reboot and every thing is fine now.

Did this per chance happen at midnight 12 AM on the 1st of July? There was a leap second adjustment that has caused all kinds of problems. The solution is to reboot the computer that is having issues. This max CPU usage is something I have heard developers in other non Bitcoin related IRC channels mention.

thanks!
yes, it happened at 12AM and it was caused by the leap-second. I read that bitlc.net had some trouble with their java-apps too.

BTC:  123aoTXpQEtdQvN3WMMgmhzsueadVFpLgP
NMC: N47xa4CCDcRvhHCLPVrdiUQw4wN6rJ2dQq
1480934151
Hero Member
*
Offline Offline

Posts: 1480934151

View Profile Personal Message (Offline)

Ignore
1480934151
Reply with quote  #2

1480934151
Report to moderator
1480934151
Hero Member
*
Offline Offline

Posts: 1480934151

View Profile Personal Message (Offline)

Ignore
1480934151
Reply with quote  #2

1480934151
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480934151
Hero Member
*
Offline Offline

Posts: 1480934151

View Profile Personal Message (Offline)

Ignore
1480934151
Reply with quote  #2

1480934151
Report to moderator
1480934151
Hero Member
*
Offline Offline

Posts: 1480934151

View Profile Personal Message (Offline)

Ignore
1480934151
Reply with quote  #2

1480934151
Report to moderator
1480934151
Hero Member
*
Offline Offline

Posts: 1480934151

View Profile Personal Message (Offline)

Ignore
1480934151
Reply with quote  #2

1480934151
Report to moderator
Prattler
Full Member
***
Offline Offline

Activity: 192


View Profile
July 02, 2012, 05:32:13 AM
 #2882

So I realize it hasn't been very long, but have the new share changes helped the orphan rate?

Yes! So far v3 changes have helped to save 1 block from being orphaned.

http://blockchain.info/block-index/241146

Still quite a lot of orphans past few days, hopefully it's just bad luck - they were all close calls.
Icoin
Hero Member
*****
Offline Offline

Activity: 585



View Profile WWW
July 02, 2012, 07:22:48 PM
 #2883

chapeau for the new version 3.1-15 my node works flawless since the update to bitcoind 0.6.3 thanks for the awesome work !!

rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
July 02, 2012, 08:38:26 PM
 #2884

Outdated clients/nodes/miners:

1PoNvnRhbvFE4xebEXjcVWfA3f2CGQkrCw
1DpJ9tfVotdAXc2FKfUDRJhHLP72hzBtQ4
17n2PjMRMZWsz6fiF9KpQZpLwRDzum7TzV
1HM8ysRnYZzmXD5i4W7FEiDP3brCZGsYC5
1Hxhyew5cJthaxX1iGi6gKjguaGYHpPoLj
16i6LtbydUput1BPDABmHtiFpuKAk9mtVT

Check your P2pool software and update it!

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
July 02, 2012, 10:38:47 PM
 #2885

Outdated clients/nodes/miners:

...

Check your P2pool software and update it!

Sadly, people running outdated clients are almost certainly not reading this thread.  Pretty much the only way to get their attention is to force an upgrade (i.e. fork them so that they stop getting paid regularly).

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
sharky112065
Sr. Member
****
Offline Offline

Activity: 383



View Profile
July 03, 2012, 12:19:30 AM
 #2886

Outdated clients/nodes/miners:

1PoNvnRhbvFE4xebEXjcVWfA3f2CGQkrCw
1DpJ9tfVotdAXc2FKfUDRJhHLP72hzBtQ4
17n2PjMRMZWsz6fiF9KpQZpLwRDzum7TzV
1HM8ysRnYZzmXD5i4W7FEiDP3brCZGsYC5
1Hxhyew5cJthaxX1iGi6gKjguaGYHpPoLj
16i6LtbydUput1BPDABmHtiFpuKAk9mtVT

Check your P2pool software and update it!

Sadly, you are wrong. My address is in that list and I upgraded my node three days ago and have double checked via the stats page.

Donations welcome: 12KaKtrK52iQjPdtsJq7fJ7smC32tXWbWr
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
July 05, 2012, 01:09:05 AM
 #2887

https://en.bitcoin.it/wiki/P2Pool#Miners
Added simple tips that help few ppl reduce local DOA when using cgminer (best miner imo).

We have 2 kind of stales/doa there.

1. Miner getting work from p2pool
2. Miner finds a share diff>1 solution and send it to pool
3. Pool register share to calculate hash speed of miner
4. Pool checking that SD of share is higher that current SD of p2pool
5. If 4 is true Pool sending share to to other nodes.

Tuning miner options can reduce DOA that appears between 2 and 3. We can see it as red line in local graph.
It will NOT reduce doa/stales in between 4 and 5. Forrestv is struggling to improve logic of pool in that point. BUT like in "real" bitcoin share chain there is no way to reduce number of orphans to 0... ;]

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1946


Poor impulse control.


View Profile WWW
July 05, 2012, 01:17:51 AM
 #2888

Couple of questions, rav3n_pl:

How dynamic is the difficulty? How often does it change?

If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?

Thanks for the work you do explaining p2Pool - it's really very helpful for those of us that want to understand it better but don't actually mine there.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
July 05, 2012, 01:31:01 AM
 #2889

How dynamic is the difficulty? How often does it change?
If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?

I don't know if it changes every share or every few shares, but I'm not sure how the frequency of difficulty changes, alone is causing extra DOA/orphaned shares.  If, when you started looking for a share the difficulty was 800 and you find a share that is valid for difficulty <= 800, the only way that that wouldn't be valid is if someone else found a share in between when you started looking and when you found a share (which is the only time the difficulty changes).  But if that happens, then your share is DOA anyway because your share doesn't build off the most recent share (which arrived at your node and changed the difficulty). 

Maybe I am missing something, though?

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1946


Poor impulse control.


View Profile WWW
July 05, 2012, 02:11:12 AM
 #2890

How dynamic is the difficulty? How often does it change?
If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?
If, when you started looking for a share the difficulty was 800 and you find a share that is valid for difficulty <= 800, the only way that that wouldn't be valid is if someone else found a share in between when you started looking and when you found a share (which is the only time the difficulty changes). 

If you start looking for a solution at difficulty, but by the time you submit it the difficulty is 900 and your solution is too large for the retarget, it will get rejected - is that DOA or orphaned? Not sure.

Either way, if difficulty changes too often then when it increase you'd expect to have an increase in submitted shares that do not solve the current difficulty. Or is the LP mechanism fast enough to prevent this?

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
July 05, 2012, 02:47:58 AM
 #2891

How dynamic is the difficulty? How often does it change?
If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?
If, when you started looking for a share the difficulty was 800 and you find a share that is valid for difficulty <= 800, the only way that that wouldn't be valid is if someone else found a share in between when you started looking and when you found a share (which is the only time the difficulty changes). 

If you start looking for a solution at difficulty, but by the time you submit it the difficulty is 900 and your solution is too large for the retarget, it will get rejected - is that DOA or orphaned? Not sure.

Either way, if difficulty changes too often then when it increase you'd expect to have an increase in submitted shares that do not solve the current difficulty. Or is the LP mechanism fast enough to prevent this?

If you submit a pseudo share (i.e. a diff 1 share) and it doesn't meet the requirements of the current share difficulty, it is just not a share.  It's not orphaned or DOA just because it doesn't meet the difficulty.  This is common as most shares that the miner submits meet the diff 1 requirements but not the diff 800 requirements.

Now, if a pseudo share comes in that builds off of share X, but share X+1 has arrived at the node in the mean time, then that is a DOA pseudo share, regardless of if it meets the difficulty requirements.  If it happens to meet the difficulty requirements it will be counted in the "dead shares" statistics.

Since share difficulty only changes in response to new shares being added to the share chain, the only way difficulty could change while your pseudo share was "in flight" would be if a new share had been added to the sharechain.  In that case, your pseudo share is DOA no matter what because it isn't building off the head of the sharechain.  Again, difficulty change or not, it's DOA, so I don't think the difficulty change rate matters.

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1946


Poor impulse control.


View Profile WWW
July 05, 2012, 03:47:19 AM
 #2892

If you submit a pseudo share (i.e. a diff 1 share) and it doesn't meet the requirements of the current share difficulty, it is just not a share.  It's not orphaned or DOA just because it doesn't meet the difficulty.  This is common as most shares that the miner submits meet the diff 1 requirements but not the diff 800 requirements.

I follow - I was assuming the miner would be mining at the appropriate difficulty and only sending shares that met it. But if you're sending D1 shares which then may be rejected if they don't meet diff 800, then this isn't an issue. Thanks for the explanation, twmz.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
July 05, 2012, 04:32:17 AM
 #2893

If you submit a pseudo share (i.e. a diff 1 share) and it doesn't meet the requirements of the current share difficulty, it is just not a share.  It's not orphaned or DOA just because it doesn't meet the difficulty.  This is common as most shares that the miner submits meet the diff 1 requirements but not the diff 800 requirements.

I follow - I was assuming the miner would be mining at the appropriate difficulty and only sending shares that met it. But if you're sending D1 shares which then may be rejected if they don't meet diff 800, then this isn't an issue. Thanks for the explanation, twmz.

Yes, p2pool "lies" to the miner and tells it to look for diff 1 shares.  This was done for multiple reasons.  It helps verify the miner is working more quickly because shares are found 800 times faster.  It allows p2pool to estimate hashrate of local miners more accurately.  Also, some miners choke on shares that are higher than diff 1 and so this is also done to be as compatible with existing miners as possible.

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
Diapolo
Hero Member
*****
Offline Offline

Activity: 769



View Profile WWW
July 05, 2012, 05:46:36 AM
 #2894

https://en.bitcoin.it/wiki/P2Pool#Miners
Added simple tips that help few ppl reduce local DOA when using cgminer (best miner imo).

We have 2 kind of stales/doa there.

1. Miner getting work from p2pool
2. Miner finds a share diff>1 solution and send it to pool
3. Pool register share to calculate hash speed of miner
4. Pool checking that SD of share is higher that current SD of p2pool
5. If 4 is true Pool sending share to to other nodes.

Tuning miner options can reduce DOA that appears between 2 and 3. We can see it as red line in local graph.
It will NOT reduce doa/stales in between 4 and 5. Forrestv is struggling to improve logic of pool in that point. BUT like in "real" bitcoin share chain there is no way to reduce number of orphans to 0... ;]

You did not even mention the diakgcn kernel in CGMINER (use -v 2 -w 256 with it for optimal performance) :-P, at least it should be mentioned as an option and perhaps it can be valuable for some users out there Smiley.

Dia

Liked my former work for Bitcoin Core? Drop me a donation via:
1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x
bitcoin:1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x?label=Diapolo
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
July 05, 2012, 06:43:28 AM
 #2895

Couple of questions, rav3n_pl:

How dynamic is the difficulty? How often does it change?

If it changes often and this causes orphaned shares, what would the downside of changing it less frequently be?

Thanks for the work you do explaining p2Pool - it's really very helpful for those of us that want to understand it better but don't actually mine there.
Share diff is changing about every 10 sec. Every LP in P2pool means that some node found a valid p2pool chain share and diff is adjusted to meet another share in about 10sec.
DOA share appears when it is delivered to pool after LP message (it is from "previous" LP) and it can not be joined into chain.
Orphaned share is like in bitcoin chain - 2 shares almost at once and win that one what follows quicker by another valid share.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
Proofer
Sr. Member
****
Offline Offline

Activity: 251


View Profile
July 05, 2012, 02:53:06 PM
 #2896

Ubuntu 11.04, p2pool Version: 3.1-17-gb3a4925: If I try to run p2pool without my bitcoind username and password at the end of the command line, I get:

Code:
Traceback (most recent call last):
  File "/home/user/src/p2pool/run_p2pool.py", line 5, in <module>
    main.run()
  File "/home/user/src/p2pool/p2pool/main.py", line 676, in run
    cp.readfp(StringIO.StringIO('[x]\r\n' + f.read()))
  File "/usr/lib/python2.7/ConfigParser.py", line 316, in readfp
    self._read(fp, filename)
  File "/usr/lib/python2.7/ConfigParser.py", line 538, in _read
    raise e
ConfigParser.ParsingError: File contains parsing errors: <???>
        [line  5]: ' # Network-related settings:\n'
        [line  7]: ' # Run on the test network instead of the real bitcoin network.\n'
        [line  8]: ' #testnet=1\n'

 # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
 
 ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##

[the rest of my bitcoin.conf file is listed here]

rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
July 05, 2012, 04:39:15 PM
 #2897

Try move lines
Code:
rpcuser=xxxx
rpcpass=yyy
to the top of bitccoin.conf file

Looks like you have some syntax error on it that kill p2pool parser.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
Proofer
Sr. Member
****
Offline Offline

Activity: 251


View Profile
July 05, 2012, 05:08:06 PM
 #2898

Try move lines
Code:
rpcuser=xxxx
rpcpass=yyy
to the top of bitccoin.conf file

Looks like you have some syntax error on it that kill p2pool parser.
Thanks; before I moved the lines, I noticed the error:  all the lines starting with the first one that p2pool complained about have a leading space.  That didn't cause a problem with bitcoind.  This bitcoin.conf was originated on an OS X system by the OS X bitcoin app months ago.  I've replaced it with one not having leading spaces and that solves the problem.
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 05, 2012, 08:53:36 PM
 #2899

I'm playing with p2pool again.

I'm seeing this a lot in the output for all 3 of my miners.  When I say a lot, I can sit and watch the visual output and it happens enough for me to see it regularly within a few minute period.

2012-07-05 16:49:49.262000 > Worker miner1 @ 192.168.0.110 submitted share more than once!

All the miners have different names.  The one with the most power seems to get the message the most, sometimes 2x back to back.  Two miners are on cgminer 2.4.4; one has 4 GPUs behind it, one has 1 GPU behind it.  The third miner is on phoenix 2.0.0, with 4 GPUs behind it.

I'm using the latest p2pool for windows, 3.1.

I posted this in cgminer before I got confirmation this is coming from my phoenix miner as well.

Any thoughts?

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
July 07, 2012, 11:04:38 AM
 #2900

How's this possible? 

2012-07-07 07:02:28.254000 New work for worker! Difficulty: 0.999985 Share difficulty: 639.252514 Total block value: 63.655207 BTC including 219 transactions

I've never seen blocks above 51 btc, including transactions.  If p2pool doing something to make up for the 20 hours we've been without a block?

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
Pages: « 1 ... 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 [145] 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!