Do you want patches? I'm testing putting 50 miners through this proxy and was running into stability issues. I have mysql on a separate machine and am used to that being a bottleneck, so I looked into making it use persistent connections. I am not familiar with the PDO extension, but found the instantiator in common.inc.php on line 31; I added array(PDO::ATTR_PERSISTENT => true) to the new call and this took care of my problems.
I now have 32 connections from the proxy web server staying open (which is what I want).
Sounds like a good idea. I'll test this on my setup and commit if there are no issues.I now have 32 connections from the proxy web server staying open (which is what I want).
There should be a way to copy worker/pool configs
so instead of setting up 10x pools on 10x workers you can set it up once then copy it to the rest, then go in and change the logins as necessary. Or a way to use a variable in the config so you build X workers with the suffix X changed on each one
I might add one or more of these ideas in the future. Right now I'm trying to keep the number of features low and work on the ones that are having trouble.so instead of setting up 10x pools on 10x workers you can set it up once then copy it to the rest, then go in and change the logins as necessary. Or a way to use a variable in the config so you build X workers with the suffix X changed on each one
Problem 3 was solved by adding 'http://' to the pool's url. Won't work without.
Yup. 
I'll add something like this to the readme, and maybe add some validation too so that it will bail unless it sees a scheme in the URL.Really wish there was a way to monitor anything on solo mining besides getwork w/ the proxy
I've no clue what you're asking for here.What sort of values can i set for 'average_interval'? and what effects will it have?
When reporting on the number of shares submitted and the miner speed, this is the window of time it will look back to gather data. If you set it longer, the query will take longer and will generally even out more; if you set it shorter, the query will run faster but will result in wild fluctuations of the worker speed (for example) as the worker has lucky and unlucky periods.It is purely used for reports; it will have no effect on mining.
Also, please add rejected per hour and efficiency.
Another user has a nearly-ready patch that adds a lot of this information.connections to the proxy started timing out, so restarting apache fixed it, but i didn't trust it enough to keep going
This was on a VM w/ 1GB of ram
What kind of hardware are you guys running on?
I'm running with 768MB, most of which is in use by a Minecraft server...This was on a VM w/ 1GB of ram
What kind of hardware are you guys running on?
Try increasing the number of worker children in your Apache configuration. With more miners, you need more workers to keep up with the demand. If Apache hits its limit then it will simply stop responding to requests.
I'm getting the response
How can I troubleshoot this?
If you can, run a sniffer on the web server and see if it even tries to connect. If it does, see if you can diagnose the problem from the content of the HTTP conversation.Code:
{"error":"No enabled pools responded to the work request.","result":null,"id":1}
with Multipool. I just verified -- Multipool is up. In fact, when I make the exact same work request which I made to the proxy (with updated credentials) to multipool.hpc.tw, I get a response in under a second.How can I troubleshoot this?
If it does not try to connect:
- Verify that you have pools assigned to the worker you are using.
- Verify that the php allow_url_fopen configuration flag is set to On.
Unfortunately, I get extreme stale rates (>10%) when using the proxy on my local mining-rig. But I'm behind a firewall - could it be that the Mining Proxy needs to be listening on port 80 from the "outside" to be able to receive LP-queries?
No, the proxy needs no ports open except for the miners themselves. It may be worth running a packet sniffer and seeing if the LP requests are actually making it through. If you are not running on Apache, some config tweaks may be necessary to get LP to work at all.