no you COULD solve a namecoin block
plus with namecoin, your solution must solve an ENTIRE block, there are no shares
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 705. (Read 2591919 times)
woot, two blocks in less than a week with just 3.2GH
Also, I have a quick question, if you solve the bitcoin block do you also solve a namecoin block at the same time? I'm pretty sure that is what merged mining means.
Also, I have a quick question, if you solve the bitcoin block do you also solve a namecoin block at the same time? I'm pretty sure that is what merged mining means.
I am running p2pool with great results on debian, however for best efficiency I am planning on running on a server I have on the internet that runs centos, the debian server I use for mining and it is best not to have the miners and the mining pool on the same server.
I get this strange error when running on centos 5.5
forrestv-p2pool-04283e9]# ./run_p2pool.py
Traceback (most recent call last):
File "/home/sergio/forrestv-p2pool-04283e9/p2pool/__init__.py", line 36, in _get_version
if len(dir_name) >= 7 and (len(dir_name) == 7 or dir_name[-8] not in chars) and all(c in chars for c in dir_name[-7:]):
NameError: global name 'all' is not defined
Traceback (most recent call last):
File "./run_p2pool.py", line 3, in ?
from p2pool import main
File "/home/sergio/forrestv-p2pool-04283e9/p2pool/main.py", line 27
from . import p2p, networks, web
^
SyntaxError: invalid syntax
Any ideas on how to fix that error, is there a patch available to run p2pool in centos 5.5 ?
On centos python is version 2.4 on debian it is 2.6.6
Python 2.4 is not compatible with p2pool. Sorry I get this strange error when running on centos 5.5
forrestv-p2pool-04283e9]# ./run_p2pool.py
Traceback (most recent call last):
File "/home/sergio/forrestv-p2pool-04283e9/p2pool/__init__.py", line 36, in _get_version
if len(dir_name) >= 7 and (len(dir_name) == 7 or dir_name[-8] not in chars) and all(c in chars for c in dir_name[-7:]):
NameError: global name 'all' is not defined
Traceback (most recent call last):
File "./run_p2pool.py", line 3, in ?
from p2pool import main
File "/home/sergio/forrestv-p2pool-04283e9/p2pool/main.py", line 27
from . import p2p, networks, web
^
SyntaxError: invalid syntax
Any ideas on how to fix that error, is there a patch available to run p2pool in centos 5.5 ?
On centos python is version 2.4 on debian it is 2.6.6
Getting 2.7 running on Centos is a PITA. I just had to mess around with it for work and we ended up using ubuntu 12.04 LTS.
I don't know why considering 2.7 is almost 2 years old. 2.6 is in EPEL though.
I am running p2pool with great results on debian, however for best efficiency I am planning on running on a server I have on the internet that runs centos, the debian server I use for mining and it is best not to have the miners and the mining pool on the same server.
I get this strange error when running on centos 5.5
forrestv-p2pool-04283e9]# ./run_p2pool.py
Traceback (most recent call last):
File "/home/sergio/forrestv-p2pool-04283e9/p2pool/__init__.py", line 36, in _get_version
if len(dir_name) >= 7 and (len(dir_name) == 7 or dir_name[-8] not in chars) and all(c in chars for c in dir_name[-7:]):
NameError: global name 'all' is not defined
Traceback (most recent call last):
File "./run_p2pool.py", line 3, in ?
from p2pool import main
File "/home/sergio/forrestv-p2pool-04283e9/p2pool/main.py", line 27
from . import p2p, networks, web
^
SyntaxError: invalid syntax
Any ideas on how to fix that error, is there a patch available to run p2pool in centos 5.5 ?
On centos python is version 2.4 on debian it is 2.6.6
I get this strange error when running on centos 5.5
forrestv-p2pool-04283e9]# ./run_p2pool.py
Traceback (most recent call last):
File "/home/sergio/forrestv-p2pool-04283e9/p2pool/__init__.py", line 36, in _get_version
if len(dir_name) >= 7 and (len(dir_name) == 7 or dir_name[-8] not in chars) and all(c in chars for c in dir_name[-7:]):
NameError: global name 'all' is not defined
Traceback (most recent call last):
File "./run_p2pool.py", line 3, in ?
from p2pool import main
File "/home/sergio/forrestv-p2pool-04283e9/p2pool/main.py", line 27
from . import p2p, networks, web
^
SyntaxError: invalid syntax
Any ideas on how to fix that error, is there a patch available to run p2pool in centos 5.5 ?
On centos python is version 2.4 on debian it is 2.6.6
Yeah, to be honest I don't think p2pool is terribly practical for less serious miners at this stage 
Hell, I'd gone back to mining PPS entirely before the recent update, which has cut my DOA rate down to a quarter of what it was previously.
Also, look at the luck! I've been using p2pool for a while and I've never seen the 1-day luck go above 100%.
Has the recent update fixed anything?
Hell, I'd gone back to mining PPS entirely before the recent update, which has cut my DOA rate down to a quarter of what it was previously.
Also, look at the luck! I've been using p2pool for a while and I've never seen the 1-day luck go above 100%.
Has the recent update fixed anything?
Or use my node below ;
)
) 
Just a comment: these monthly forced updates are not really practical for people who don't engulf their entire lives in Bitcoin. I was fortunate to have caught this update and the previous one because I just happened to check in here.
I will be away for the next 60 days. Hopefully my miners will still be working when I get back.
I will be away for the next 60 days. Hopefully my miners will still be working when I get back.
You can use P2Pmining.com and let me take care of the updates for you.
Just a comment: these monthly forced updates are not really practical for people who don't engulf their entire lives in Bitcoin. I was fortunate to have caught this update and the previous one because I just happened to check in here.
I will be away for the next 60 days. Hopefully my miners will still be working when I get back.
I will be away for the next 60 days. Hopefully my miners will still be working when I get back.
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.
...
Since you have a small rig, it might be worth mining at p2pmining.com. He runs a public, merged mining p2pool node with diff 1 shares designed for smaller miners.I have only ~170MH/s and most of my worker get works are break by longpool reset.
...
(at the moment with a difficulty of 1508589.6720603)
BTC per day: 0.11334309 BTC
Shares per Minute: 2.3749 (1 difficulty shares - not p2pool paying shares)
However ... average expected amount per block will depend on the hash rate of the pool!
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.
...
Since you have a small rig, it might be worth mining at p2pmining.com. He runs a public, merged mining p2pool node with diff 1 shares designed for smaller miners.I have only ~170MH/s and most of my worker get works are break by longpool reset.
...
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.
Since you have a small rig, it might be worth mining at p2pmining.com. He runs a public, merged mining p2pool node with diff 1 shares designed for smaller miners.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.
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.
Since you have a small rig, it might be worth mining at p2pmining.com. He runs a public, merged mining p2pool node with diff 1 shares designed for smaller miners.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.
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.
Since you have a small rig, it might be worth mining at p2pmining.com. He runs a public, merged mining p2pool node with diff 1 shares designed for smaller miners. 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.
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.
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.
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.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.
Updated!
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. 
Also: is there any way to switch to a new destination address without restarting p2pool?
Does P2Pool have Socks4 support today? If not, is it a planned feature for the near future?
Jump to: