Love the program, I too wish to see a stratum version soon, as well.
One annoyance at the moment I would like to know how to solve, if possible, is getting the connection error to reset to normal after the miner disconnects. Right now it keeps saying:
"[Errno 10054] An existing connection was forcibly closed by the remote host"
After the miner is disconnected but I know it is running just fine after I reconnect. The current solution is to simply just close and reopen Rollproxy but I will lose my collected stats if I do so. So it's either lose my stats or not have a log in the mean time.
Thank you.
Topic: RollProxy - a bandwidth-saving mining proxy (Read 14395 times)
Is this proxy works with quark algorithm?
Its working but it auto crashes at random times (10 mins or 30 mins) by itself for me
I am running in a centos dedicated server with python 2.6
I am running in a centos dedicated server with python 2.6
Hello. i setup pushpool + bitcoind. is there appropriate mechanism to proxy to bigger mining pull to share profit with them? we are young and it will be difficult at first time to earn something.
it is possible to create something like that:
miners-> pushpool -> proxy -> another_pool?
will i be able to gather statistics from Rollproxy via SimpleBTC? now simplebtc connects to bitcoind via rpc and get all stat.
i looked at rollproxy and it seems it can help me.
Thanks in advance.
it is possible to create something like that:
miners-> pushpool -> proxy -> another_pool?
will i be able to gather statistics from Rollproxy via SimpleBTC? now simplebtc connects to bitcoind via rpc and get all stat.
i looked at rollproxy and it seems it can help me.
Thanks in advance.
I used rollproxy to force reuse of work units when solo-mining ppcoin for a few days. It worked very well, fixing my problem with running out of work when pointing miners directly to ppcoind. I found 2 blocks and those were the only shares submitted to rollproxy. Why would you want any other difficulty "shares" on a setup like that, or are you thinking of something different?
When you have multiple machines accessing the same pool server/proxy, it's nice to know that the miners are online and functioning properly. If they submit lower difficulty shares I will be able to tell this (even if they aren't difficulty 1.. 1 share every 5 or 10 minutes would be fine.)
You could turn this into a simple pool software that could mine on litecoind if you did the 2 following things:
#1) Allow the rollproxy to rewrite target difficulty
#2) Add the option to only submit shares that meet difficulty upstream.
Would you be willing to implement this for solo miners?
I used rollproxy to force reuse of work units when solo-mining ppcoin for a few days. It worked very well, fixing my problem with running out of work when pointing miners directly to ppcoind. I found 2 blocks and those were the only shares submitted to rollproxy. Why would you want any other difficulty "shares" on a setup like that, or are you thinking of something different?
You could turn this into a simple pool software that could mine on litecoind if you did the 2 following things:
#1) Allow the rollproxy to rewrite target difficulty
#2) Add the option to only submit shares that meet difficulty upstream.
Would you be willing to implement this for solo miners?
Hey. I need a small code addon. Is it possible?
Basically, I would like for the proxy to restart if there are >5% stale shares.
I think it's just a few lines of code. I'd do it myself, but I don't know Python.
Thanks a bunch!
Basically, I would like for the proxy to restart if there are >5% stale shares.
I think it's just a few lines of code. I'd do it myself, but I don't know Python.
Thanks a bunch!
any way to log mining data like shares submitted per worker etc ? like in a text file or something?
Done. There's now a --sharelog option that allows you to specify a file for logging submissions.
Sweet thanks !
any way to log mining data like shares submitted per worker etc ? like in a text file or something?
Done. There's now a --sharelog option that allows you to specify a file for logging submissions.
any way to log mining data like shares submitted per worker etc ? like in a text file or something?
I'm getting noticeably higher rejects when mining through rollproxy. Long poll is enabled on both cgminer and rollproxy, but my rejects are still 1-2% compared to the 0.5% max when directly connecting. There's no additional network delay since rollproxy is running on localhost. Has anyone else noticed higher reject rates? What might be the cause?
Looks like you've downloaded the github website but not the python code...
Try this:
Try this:
Code:
wget https://raw.github.com/pooler/rollproxy/master/rollproxy.py -O rollproxy.py
2to3 -w rollproxy.py
python3 rollproxy.py -v "your pools"
help me :
Quote
robin@ubuntu:~$ 2to3 -w rollproxy.py
RefactoringTool: Skipping implicit fixer: buffer
RefactoringTool: Skipping implicit fixer: idioms
RefactoringTool: Skipping implicit fixer: set_literal
RefactoringTool: Skipping implicit fixer: ws_comma
RefactoringTool: Can't parse rollproxy.py: ParseError: bad input: type=20, value=u'<', context=(u'', (1, 0))
RefactoringTool: No files need to be modified.
RefactoringTool: There was 1 error:
RefactoringTool: Can't parse rollproxy.py: ParseError: bad input: type=20, value=u'<', context=(u'', (1, 0))
robin@ubuntu:~$
RefactoringTool: Skipping implicit fixer: buffer
RefactoringTool: Skipping implicit fixer: idioms
RefactoringTool: Skipping implicit fixer: set_literal
RefactoringTool: Skipping implicit fixer: ws_comma
RefactoringTool: Can't parse rollproxy.py: ParseError: bad input: type=20, value=u'<', context=(u'', (1, 0))
RefactoringTool: No files need to be modified.
RefactoringTool: There was 1 error:
RefactoringTool: Can't parse rollproxy.py: ParseError: bad input: type=20, value=u'<', context=(u'', (1, 0))
robin@ubuntu:~$
Quote
robin@ubuntu:~$ python rollproxy.py -v "pool"
File "rollproxy.py", line 1
^
SyntaxError: invalid syntax
robin@ubuntu:~$
File "rollproxy.py", line 1
^
SyntaxError: invalid syntax
robin@ubuntu:~$
AFAIK that's not possible but RollProxy provides a webinterace where you can check your miners status...
Hi,
is it possible to connect with different workernames to a pool ? i lose controll which worker is down.
I could start a bunch of rollproxies on different ports, but that looks for me like a waste of recources.
Miner_1 =>> Rollproxy ==> worker1@abcpool
Miner_2 =>> same Rollproxy ==> worker2@abcpool
Thats what i mean.
Thanks
is it possible to connect with different workernames to a pool ? i lose controll which worker is down.
I could start a bunch of rollproxies on different ports, but that looks for me like a waste of recources.
Miner_1 =>> Rollproxy ==> worker1@abcpool
Miner_2 =>> same Rollproxy ==> worker2@abcpool
Thats what i mean.
Thanks
Sure, no problem. Just switched back to 0.5.2 and started logging to a file. If anything shows up I'll send it to you.
Ok, so after six days of using v0.5.2 (again) everything is fine. Whatever my problem was I'm unable to reproduce it...
Unfortunately that doesn't help. What is needed is a way for RollProxy to connect to the Internet through a SOCKS4/5 proxy, not a way for the miners to connect to RollProxy through an additional local proxy.
Use socat.
for mining through tor,
socat tcp-listen:18332,fork,reuseaddr socks4a:127.0.0.1:pool.com:8332,socksport=9050
Sure, no problem. Just switched back to 0.5.2 and started logging to a file. If anything shows up I'll send it to you.
Rolled back to v0.5.1. On pool errors v0.5.2 started rotating over all configured pools in a endless loop...
I just had a look at the 0.5.2 commit. All I did is adding a 1-second pause between retries; I don't think I've changed anything else in the failover mechanism.
So I'd say if the problem you describe exists in 0.5.2 it should also exist in 0.5.1.
Can you please send me some logs if the issue shows up again?
Jump to: