Author

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

sr. member
Activity: 308
Merit: 250
Decentralize your hashing - p2pool - Norgz Pool
sorry I'm a windows person so don't have those Linux problems Tongue jokes

I have another problem, my own miners don't seem to show the payout on my pool. I have someone else on there now and their payout graph is showing just fine.
http://www.norgzpool.net.au/graphs.html?Hour

see my ant on 1CmHNDfj43tsQgSpSum5tDQ6kT4MwcUP6V doesn't show any payout and my payout to default address doesn't seem to change when I mine it with a username so it defaults to default payout. I changed it to a wallet address and still nothing.
full member
Activity: 932
Merit: 100
arcs-chain.com
Tried purging those and re installing them

Same result...

Twisted version 13.0.0-1 is installed

cd to folder where you have p2pool

cd /p2pool

./configure

make -j12

should do it

Replace ubuntu with Gentoo Smiley
full member
Activity: 161
Merit: 100
digging in the bits... now ant powered!
Tried purging those and re installing them

Same result...

Twisted version 13.0.0-1 is installed
sr. member
Activity: 308
Merit: 250
Decentralize your hashing - p2pool - Norgz Pool
Bleg!!!


I updated my linux system... Bad mistake.

Now I am getting these errors trying to start my p2pools!

Traceback (most recent call last):
  File "/opt/p2pool/run_p2pool.py", line 3, in
    from p2pool import main
  File "/opt/p2pool/p2pool/main.py", line 17, in
    from twisted.internet import defer, reactor, protocol, tcp
ImportError: No module named twisted.internet


Help please!!

have you tried:
•sudo apt-get install python-zope.interface python-twisted python-twisted-web

to install the packages? maybe the upgrade installed newer packages than is supported in which case you'll need to downgrade them.
full member
Activity: 161
Merit: 100
digging in the bits... now ant powered!
Bleg!!!


I updated my linux system... Bad mistake.

Now I am getting these errors trying to start my p2pools!

Traceback (most recent call last):
  File "/opt/p2pool/run_p2pool.py", line 3, in
    from p2pool import main
  File "/opt/p2pool/p2pool/main.py", line 17, in
    from twisted.internet import defer, reactor, protocol, tcp
ImportError: No module named twisted.internet


Help please!!
hero member
Activity: 798
Merit: 1000
legendary
Activity: 1258
Merit: 1027
Enjoying it as well IYF Smiley

bkminer, I have not seen what you want to do implemented, but if your node is all your miners I don't think it will be hard to implement.

hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
Lovin this block blitz........nice  Cool
full member
Activity: 216
Merit: 100
Don't let the nam-shub in your operating system.
Has anyone modified the alternate simple front end to allow for miners that don't use an address for their username?  If there is no BTC address each update adds 1 more line per miner to the list instead of updating it.... I'm running my own node and all my miners donate to the node.

If no one has I'll fork the repo and add it if anyone else is interested.

legendary
Activity: 1258
Merit: 1027
pooledtx are the ones that sit around in memory.  currentblocktx are the ones that are in the block your p2pool is mining. 

your latency graph looked to me like you are getting slammed w/ a whole bunch of unconfirmed transactions at once.  probably a lot of zero fee or zero fee priority transactions.  i haven't checked in a while, but the base behavior used to be to accept free transactions when a block was <10KB in size.  priority transactions up to 30KB. 

I used to use limitfreerelay=0.  Didn't want to have anything using up resources for nothing.  If you allow free transactions, your client will eventually have all of those stored & most will probably take a long time to get into a block.  Your graph looks to me like the same thing that happened w/ 75% or so of the nodes with the horsestaplebattery transactions.  I always had mine set to a min of .0005.

Anyway, something like blockmaxsize=250000 would speed it up also.
Thanks zvs, you rock! Made some changes based on your advice and my research, I'll post an updated graph in a few hours and see how we are looking.
zvs
legendary
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
Thanks zvs, that's not it, I tried setting mintxfee and minrelaytxfee and the spikes still occur...

mintxfee and minrelaytxfee wouldn't cover the transactions I was talking about, it would be limitfreerelay.

anyway, the easy way to check is next time it's going really slow just do a bitcoind mininginfo and see how many tx are queued

Thanks zvs, appreciate the help.

limitfreerelay looks interesting default = 15kb per minute so I assume reducing it to 10 or 5 should help?

Code:
bitcoind getmininginfo 
{
    "blocks" : 302249,
    "currentblocksize" : 556205,
    "currentblocktx" : 654,
    "difficulty" : 8853416309.12779999,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 68130160771479424,
    "pooledtx" : 2711,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}

I have not been closely watching this up until now so will start to track. Am I looking at currentblocktx or pooledtx (or both)? How can I determine if that is what is effecting the latency?

Again, really appreciate it, thanks.
pooledtx are the ones that sit around in memory.  currentblocktx are the ones that are in the block your p2pool is mining. 

your latency graph looked to me like you are getting slammed w/ a whole bunch of unconfirmed transactions at once.  probably a lot of zero fee or zero fee priority transactions.  i haven't checked in a while, but the base behavior used to be to accept free transactions when a block was <10KB in size.  priority transactions up to 30KB. 

I used to use limitfreerelay=0.  Didn't want to have anything using up resources for nothing.  If you allow free transactions, your client will eventually have all of those stored & most will probably take a long time to get into a block.  Your graph looks to me like the same thing that happened w/ 75% or so of the nodes with the horsestaplebattery transactions.  I always had mine set to a min of .0005.

Anyway, something like blockmaxsize=250000 would speed it up also.
legendary
Activity: 1258
Merit: 1027
Personally, I'd rather see the timestamp instead of the pretty date format.  Seeing "Found 2 days ago" for 6 shares doesn't tell me the distribution of those shares.

Thanks jonny, I like the "time ago" date format for the node stats, and main miner stats page; for me it gives a "quick glance" easy reference. Although you make a good point about tracking your share variance. Right now it will show only the 20 most recent shares, after I get the blocks added I'll make a per-miner share explorer so a miner can go through all their shares ever submitted to the node...
legendary
Activity: 1258
Merit: 1027
Thanks zvs, that's not it, I tried setting mintxfee and minrelaytxfee and the spikes still occur...

mintxfee and minrelaytxfee wouldn't cover the transactions I was talking about, it would be limitfreerelay.

anyway, the easy way to check is next time it's going really slow just do a bitcoind mininginfo and see how many tx are queued

Thanks zvs, appreciate the help.

limitfreerelay looks interesting default = 15kb per minute so I assume reducing it to 10 or 5 should help?

Code:
bitcoind getmininginfo 
{
    "blocks" : 302249,
    "currentblocksize" : 556205,
    "currentblocktx" : 654,
    "difficulty" : 8853416309.12779999,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 68130160771479424,
    "pooledtx" : 2711,
    "testnet" : false,
    "generate" : false,
    "hashespersec" : 0
}

I have not been closely watching this up until now so will start to track. Am I looking at currentblocktx or pooledtx (or both)? How can I determine if that is what is effecting the latency?

Again, really appreciate it, thanks.
zvs
legendary
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
Thanks zvs, that's not it, I tried setting mintxfee and minrelaytxfee and the spikes still occur...

mintxfee and minrelaytxfee wouldn't cover the transactions I was talking about, it would be limitfreerelay.

anyway, the easy way to check is next time it's going really slow just do a bitcoind mininginfo and see how many tx are queued
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Hey windpath,

I like what you've done so far, and storing historical share information is a pretty cool idea - a miner can look back and see variance over time.  Personally, I'd rather see the timestamp instead of the pretty date format.  Seeing "Found 2 days ago" for 6 shares doesn't tell me the distribution of those shares.

Also, I'd love to have the luck of one of the miners on your node... same hashing power as me, but his expected payouts are double mine.  I looked at his history for the past week and it's not like the payouts started that high, they started low and have just kept on rising, whereas every other miner has some kind of up and down curves - which is more in line with what I'd expect to see.

Can't wait for my SP-10 to arrive and point that at p2pool Smiley
sr. member
Activity: 308
Merit: 250
Decentralize your hashing - p2pool - Norgz Pool
ok so I have deployed out a copy of p2pool.info and it looks like it is still updating but it's a backup at least.

http://p2poolinfo.azurewebsites.net/

if you appreciate this work I am doing you can always donate to my addy in my profile.
legendary
Activity: 1258
Merit: 1027
Is http://p2pool.info/ down? I had been wondering why it was showing 5 days since last block until I tried refreshing the page (I don't reload my browser very often). I'm definitely seeing recent payouts in my wallet so I'm guessing the site is having some major issues.

These are found blocks from May 4th till now (note 1 orphan):

legendary
Activity: 1258
Merit: 1027
@oldbushie It's down for me to...we have a few days worth of blocks listed currently, soon to be last 20 @ http://mining.coincadence.com/index.php

@norgan Yes, one of the many next steps it to isolate the front end from the node as much as possible, once complete including data from multiple participating nodes should not be an issue...

http://mining.coincadence.com:9332/web/log is nice, but it does not have all the data I plan on storing (i.e. found blocks, found shares, etc...) I may end up pulling into the DB from other p2pool resources eventually, but for now the JS on the front end uses web/log as efficiently as I could imagine.... Also the /p2pool/data/bitcoin logs have some juicy data in them, however it may take a while to sort it all out with no/little docs on how p2pool stores them....
sr. member
Activity: 308
Merit: 250
Decentralize your hashing - p2pool - Norgz Pool

I'm happy to share everything I'm doing....


So that's where I'm at, more to come....


looks interesting. I've written mine to be independent of the node so you can take all the web files off the node server. In my mind this means the node is much more secure as no web traffic is on that box. (ultimately I want to disable the web-static directory and/or even the web server entirely).

It also means that if any one node is down you can tell and the main front end stays up.

Have you thought about pulling it from the /web/log json feed instead?
member
Activity: 94
Merit: 10
Is http://p2pool.info/ down? I had been wondering why it was showing 5 days since last block until I tried refreshing the page (I don't reload my browser very often). I'm definitely seeing recent payouts in my wallet so I'm guessing the site is having some major issues.
Jump to: