Author

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

legendary
Activity: 1148
Merit: 1008
If you want to walk on water, get out of the boat
Quick, everyone go back on deepbit!
newbie
Activity: 23
Merit: 0
No block found for like 4h, something seriously stinks here.



 Roll Eyes


legendary
Activity: 1204
Merit: 1000
฿itcoin: Currency of Resistance!
I've been working on a self-contained network-provisioned bitcoind + namecoind + p2pool USB stick.  I had horrible problems with bitcoind getting stuck for minutes at a time.

I came up with a solution, but it isn't pretty.  I run bitcoind entirely out of RAM now.

I have precisely this setup working here...
BTW, I also have Devcoin and Litecoin working... My USB stick have 8G...
My machine have 1G of RAM...

Cheers!
Thiago
hero member
Activity: 516
Merit: 643

I don't think that that will work. It doesn't seem to support the "getmemorypool" RPC call.
hero member
Activity: 558
Merit: 500
kjj
legendary
Activity: 1302
Merit: 1026
I've been working on a self-contained network-provisioned bitcoind + namecoind + p2pool USB stick.  I had horrible problems with bitcoind getting stuck for minutes at a time.

I came up with a solution, but it isn't pretty.  I run bitcoind entirely out of RAM now.
hero member
Activity: 516
Merit: 643
Maybe look in P2Pool's log around those times?

Is any other log rather that one that I at the output on the screen?

There's a log file in data/bitcoin/log. Also, P2Pool doesn't use IPv6; The traffic displayed on that graph is tiny anyway.
hero member
Activity: 558
Merit: 500
Definitely possible - bitcoind sometimes gets stuck for a little while and doesn't answer RPC queries.

Can somebody give me bitcoin RPC gateway with no lags? I will pay Smiley
hero member
Activity: 558
Merit: 500
Maybe look in P2Pool's log around those times?

Is any other log rather that one that I at the output on the screen?
full member
Activity: 373
Merit: 100
Code:
Failure: twisted.internet.defer.TimeoutError: Getting http://127.0.0.1:8332/ took longer than 5 seconds.

Impossible - because they on the same server + I don't see any errors in log anyway.

Definitely possible - bitcoind sometimes gets stuck for a little while and doesn't answer RPC queries.
hero member
Activity: 558
Merit: 500
Code:
Failure: twisted.internet.defer.TimeoutError: Getting http://127.0.0.1:8332/ took longer than 5 seconds.

Impossible - because they on the same server + I don't see any errors in log anyway.

Does bitcoin or p2pool use IPV6? I see this strange pattern in monitoring



hero member
Activity: 737
Merit: 500
Another question... can somebody comment why it is such big variance in mining speed?


Is it because of intensity in miner is not on maximum?

Can somebody explain why it is better to set intensity 20% below maximum? ( like -I 8 is better than -I 10 in cgminer)

As I understand it, higher intensity just mean "hey, GPU, run for a longer period of time before asking for new work".  The idea is to minimize time wasted by constantly asking for more work.  But with p2pool, running for a long time without asking for new work means a higher probability that the GPU will spend time working on stale work.
hero member
Activity: 516
Merit: 643
I keep getting the following error. It's on Arch Linux. Dependencies should be installed and everything seems to work well. It loads shares and build up connections, but after a few seconds this is what I get. Version 5250df6.

neptop, that's kind of normal if you're downloading the sharechain on a slow computer. The "Watchdog" errors just mean that P2Pool didn't respond for a while, in this case because it was spending time processing shares. This shouldn't happen in normal operation.

Another question... can somebody comment why it is such big variance in mining speed?

Is it because of intensity in miner is not on maximum?

Can somebody explain why it is better to set intensity 20% below maximum? ( like -I 8 is better than -I 10 in cgminer)

Seeing some variance is normal. P2Pool estimates your speed from the number of pseudoshares your miner submits, which varies randomly.

Lower intensities make your miner work on smaller chunks of work at a time, so they can start on a new one faster when a long poll comes in. However, I don't think that that is your problem because of the bulges in the dead rate... Maybe look in P2Pool's log around those times?
hero member
Activity: 558
Merit: 500
Another question... can somebody comment why it is such big variance in mining speed?


Is it because of intensity in miner is not on maximum?

Can somebody explain why it is better to set intensity 20% below maximum? ( like -I 8 is better than -I 10 in cgminer)
sr. member
Activity: 314
Merit: 251
I keep getting the following error. It's on Arch Linux. Dependencies should be installed and everything seems to work well. It loads shares and build up connections, but after a few seconds this is what I get. Version 5250df6.

Code:
2012-02-12 16:16:08.016118 ... done processing 209 shares. New: 209 Have: 12263/~17280
2012-02-12 16:16:08.017009 > Watchdog timer went off at:
2012-02-12 16:16:08.017406 >   File "run_p2pool.py", line 5, in
2012-02-12 16:16:08.017821 >     main.run()
2012-02-12 16:16:08.018156 >   File "/home/neptop/p2pool/p2pool/main.py", line 1186, in run
2012-02-12 16:16:08.018555 >     reactor.run()
2012-02-12 16:16:08.018952 >   File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1169, in run
2012-02-12 16:16:08.019369 >     self.mainLoop()
2012-02-12 16:16:08.019697 >   File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 1181, in mainLoop
2012-02-12 16:16:08.020076 >     self.doIteration(t)
2012-02-12 16:16:08.020397 >   File "/usr/lib/python2.7/site-packages/twisted/internet/pollreactor.py", line 167, in doPoll
2012-02-12 16:16:08.020802 >     log.callWithLogger(selectable, _drdw, selectable, fd, event)
2012-02-12 16:16:08.021141 >   File "/usr/lib/python2.7/site-packages/twisted/python/log.py", line 84, in callWithLogger
2012-02-12 16:16:08.021505 >     return callWithContext({"system": lp}, func, *args, **kw)
2012-02-12 16:16:08.021837 >   File "/usr/lib/python2.7/site-packages/twisted/python/log.py", line 69, in callWithContext
2012-02-12 16:16:08.022236 >     return context.call({ILogContext: newCtx}, func, *args, **kw)
2012-02-12 16:16:08.022593 >   File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 118, in callWithContext
2012-02-12 16:16:08.022929 >     return self.currentContext().callWithContext(ctx, func, *args, **kw)
2012-02-12 16:16:08.023315 >   File "/usr/lib/python2.7/site-packages/twisted/python/context.py", line 81, in callWithContext
2012-02-12 16:16:08.023645 >     return func(*args,**kw)
2012-02-12 16:16:08.024056 >   File "/usr/lib/python2.7/site-packages/twisted/internet/posixbase.py", line 581, in _doReadOrWrite
2012-02-12 16:16:08.024390 >     why = selectable.doRead()
2012-02-12 16:16:08.024760 >   File "/usr/lib/python2.7/site-packages/twisted/internet/tcp.py", line 199, in doRead
2012-02-12 16:16:08.025098 >     rval = self.protocol.dataReceived(data)
2012-02-12 16:16:08.025468 >   File "/home/neptop/p2pool/p2pool/p2p.py", line 65, in new_dataReceived
2012-02-12 16:16:08.025849 >     old_dataReceived(data)
2012-02-12 16:16:08.026218 >   File "/home/neptop/p2pool/p2pool/util/datachunker.py", line 40, in _DataChunker
2012-02-12 16:16:08.026564 >     wants = receiver.send(buf.get(wants))
2012-02-12 16:16:08.026901 >   File "/home/neptop/p2pool/p2pool/bitcoin/p2p.py", line 64, in dataReceiver
2012-02-12 16:16:08.027286 >     self.packetReceived(command, payload2)
2012-02-12 16:16:08.027616 >   File "/home/neptop/p2pool/p2pool/p2p.py", line 78, in packetReceived
2012-02-12 16:16:08.028036 >     bitcoin_p2p.BaseProtocol.packetReceived(self, command, payload2)
2012-02-12 16:16:08.028457 >   File "/home/neptop/p2pool/p2pool/bitcoin/p2p.py", line 74, in packetReceived
2012-02-12 16:16:08.028955 >     handler(**payload2)
2012-02-12 16:16:08.029299 >   File "/home/neptop/p2pool/p2pool/p2p.py", line 210, in handle_shares
2012-02-12 16:16:08.029705 >     self.node.handle_shares(res, self)
2012-02-12 16:16:08.030035 >   File "/home/neptop/p2pool/p2pool/main.py", line 269, in handle_shares
2012-02-12 16:16:08.030412 >     set_real_work2()
2012-02-12 16:16:08.030737 >   File "/home/neptop/p2pool/p2pool/main.py", line 184, in set_real_work2
2012-02-12 16:16:08.031094 >     best, desired = tracker.think(get_height_rel_highest, pre_current_work.value['previous_block'], pre_current_work.value['bits'])
2012-02-12 16:16:08.031445 >   File "/home/neptop/p2pool/p2pool/data.py", line 289, in think
2012-02-12 16:16:08.031773 >     if self.attempt_verify(share):
2012-02-12 16:16:08.032181 >   File "/home/neptop/p2pool/p2pool/data.py", line 268, in attempt_verify
2012-02-12 16:16:08.032523 >     share.check(self)
2012-02-12 16:16:08.032897 >   File "/home/neptop/p2pool/p2pool/data.py", line 133, in check
2012-02-12 16:16:08.033224 >     share_info, gentx = generate_transaction(tracker, self.share_info['share_data'], self.header['bits'].target, self.share_info['timestamp'], self.net)
2012-02-12 16:16:08.033666 >   File "/home/neptop/p2pool/p2pool/data.py", line 209, in generate_transaction
2012-02-12 16:16:08.034008 >     other_weights, other_total_weight, other_donation_weight = tracker.get_cumulative_weights(previous_share_hash, min(height, chain_length), 65535*max(0, max_att - this_att))
2012-02-12 16:16:08.034416 >   File "/home/neptop/p2pool/p2pool/util/skiplist.py", line 55, in __call__
2012-02-12 16:16:08.034746 >     updates[x] = updates[x][0], self.combine_deltas(updates[x][1], delta) if updates[x][1] is not None else delta
2012-02-12 16:16:08.035138 >   File "/home/neptop/p2pool/p2pool/skiplists.py", line 13, in combine_deltas
2012-02-12 16:16:08.035469 >     return share_count1 + share_count2, math.add_dicts(weights1, weights2), total_weight1 + total_weight2, total_donation_weight1 + total_donation_weight2
2012-02-12 16:16:08.035902 >   File "/home/neptop/p2pool/p2pool/util/math.py", line 64, in add_dicts
2012-02-12 16:16:08.036240 >     res[k] = res.get(k, 0) + v
2012-02-12 16:16:08.036595 >   File "/home/neptop/p2pool/p2pool/main.py", line 887, in
2012-02-12 16:16:08.036934 >     sys.stderr.write, 'Watchdog timer went off at:\n' + ''.join(traceback.format_stack())
2012-02-12 16:16:08.111189 P2Pool: 12263 shares in chain (3622 verified/12263 total) Peers: 1 (0 incoming)
hero member
Activity: 737
Merit: 500
p2pool - latest from git

cgminer 2.2.3
-I 8 -g 1

PS. How can I separate workers on the graph? where to config it. Each of mine miners runs under different username

My setup is similar except I experimentally determined that I get the best hashrate (and the lowest stales with -I 6 -g 2).  I doubt that is making that big of a difference though.

For seperate workers, you need to configure your workers to use a special password (the VIP password).  You can find it either by looking at the p2pool log output as it starts up, or look at the contents of the file ./p2pool/data/bitcoin/vip_pass

Then there will be graphs per worker (worker name is whatever you are using for username).
donator
Activity: 798
Merit: 500
Guys, why "local dead on arrival" spikes so much ( 20% rate)?

I saw this when I was getting communication errors between p2pool and bitcoind.  Look for connection errors in your p2pool log.

EDIT: Here is the exact error
Code:
Failure: twisted.internet.defer.TimeoutError: Getting http://127.0.0.1:8332/ took longer than 5 seconds.
hero member
Activity: 558
Merit: 500
p2pool - latest from git ( edit : 5250df6)

cgminer 2.2.3
-I 8 -g 1

PS. How can I separate workers on the graph? where to config it. Each of mine miners runs under different username
hero member
Activity: 737
Merit: 500
Guys, why "local dead on arrival" spikes so much ( 20% rate)?

http://178.79.169.240:9332/graphs/localrate_day or

I have a feeling that it has something to do with blocks being found.

After I restart p2pool everything goes back to normal 1-2% rate, sometimes even without restart



Mine doesn't spike.  What miner are you using?



(sorry, it's a bit hard to see the red Dead line on top of the dark red device0 area, but it's there and essentially flat)
legendary
Activity: 1148
Merit: 1008
If you want to walk on water, get out of the boat
Almost 240ghash/s
Jump to: