Flexible mining proxy

[tito13kfm]

Rebooted after crash and now Worker Status table on main dashboard is completely blank.  Recent work submissions and recent failed submissions still show up just fine in the top 2 tables, but the bottom table is blank.

Any ideas?

Edit:  I was also having connection issues.  I exported my workers and pools settings.  Imported the original schema back, and imported those saved settings.  All is well now.

[1714802184]

1714802184

[1714802184]

1714802184

[1714802184]

1714802184

[cdhowie]

Rebooted after crash and now Worker Status table on main dashboard is completely blank.  Recent work submissions and recent failed submissions still show up just fine in the top 2 tables, but the bottom table is blank.

Any ideas?

Edit:  I was also having connection issues.  I exported my workers and pools settings.  Imported the original schema back, and imported those saved settings.  All is well now.

Sounds like the MySQL database got corrupted.  Which is weird, since table logs are supposed to keep that from happening.  :/

[teknohog]

Has anyone got this working with Lighttpd (under Gentoo)? I am trying to rule out wider system-level errors before digging deeper into this code. Basically, my clients (Phoenix) are connecting to the proxy, but they are not getting any work. My PHP setup should be OK as I use it for other web content, and the admin interface seems to work fine. I have set this up in a separate port so there are no subdirectory issues for clients.

[Freakin]

Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /home/REDACTED/public_html/admin/index.php on line 28

Hmm, not sure why i'm getting this.  This is on the admin page.  It complains about line 125 on the root

[cdhowie]

Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /home/REDACTED/public_html/admin/index.php on line 28

Hmm, not sure why i'm getting this.  This is on the admin page.  It complains about line 125 on the root

Which version of PHP?  It's possible that your version does not support function access modifiers.

[Freakin]

Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /home/REDACTED/public_html/admin/index.php on line 28

Hmm, not sure why i'm getting this.  This is on the admin page.  It complains about line 125 on the root

Which version of PHP?  It's possible that your version does not support function access modifiers.

4.4.8

5.x required?

[exahash]

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.

The whole line now looks like this:

return new PDO($BTC_PROXY['db_connection_string'], $BTC_PROXY['db_user'], $BTC_PROXY['db_password'], array(PDO::ATTR_PERSISTENT => true) );

I now have 32 connections from the proxy web server staying open (which is what I want).

Hopefully this helps someone.

[btcLeger]

4.4.8

5.x required?

5.3 at least.

[Freakin]

Cool got it working on a Centos 5.6 VM w/ 5.3.6

had a bit of difficulty getting PDO installed but it went ok.

looking forward to getting this working!

[Freakin]

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

[krom]

All working "quite" well with 1 miner and 1 pool.

Some things i've noticed:

• I have a lot of "Listener for "Proxy": 15/06/2011 00:23:30, Unexpected error:" lines on GUIMiner's console, using poclbm and the proxy.
• Long polls seem to get through sometimes, but not all the time - i get a lot more of these when connecting to the pool directly, but maybe this was random.
• Fall back to other pools does not work for me, nor will the miner work on any other pool than the first one i created, even if i disable that pool overall or remove it from the worker's list.
• A second worker i added is able to get work (only from the first pool i defined as well), but the returned shares never show up anywhere - not on the dashboard nor the pool's stats page. "Last accepted submission" is "Never" for that worker all the time as well.

I'll dig into the problem further, but have no time to do so yet.
Besides that: Good work and keep it up! When i'll have more than some fractions of BC, i'll donate to you.

Update:
Long poll seem to be okay.
Problem 3 was solved by adding 'http://' to the pool's url. Won't work without.

[Freakin]

Really wish there was a way to monitor anything on solo mining besides getwork w/ the proxy

[kripz]

Testing out now, looks fairly solid.

What sort of values can i set for 'average_interval'? and what effects will it have?

Also, please add rejected per hour and efficiency.

Edit: I get alot of miner idle using this...

[Freakin]

I had problems with this once i connected 4 machines to it (6 total miners).

Tried it soloing and on bitparking and while I slept and found that I wasn't getting what I was supposed to.

turned off both namecoin options and was hitting slush and deepbit and getting about 2/3 of the shares I should have

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?

[pwnyboy]

Really wish there was a way to monitor anything on solo mining besides getwork w/ the proxy

There is indeed, it's called pushpool.  But it's a real PITA to build.  Once you have it going, it'll log shares to a text file, which you can use to dig out the info you want/need.  You can also make it log shares to the database backend (SQLite, MySQL etc).

[Freakin]

Really wish there was a way to monitor anything on solo mining besides getwork w/ the proxy

There is indeed, it's called pushpool.  But it's a real PITA to build.  Once you have it going, it'll log shares to a text file, which you can use to dig out the info you want/need.  You can also make it log shares to the database backend (SQLite, MySQL etc).

yeah I think I'm going to set up a POC pool on a VM for personal use and play around.

After 3 days soloing namecoin with 2GH and not finding a single block I don't plan on doing that again anyways... Wouldn't be so bitter if I hadn't found 23 blocks in the week before (half at ~3k difficulty) for BitParking

[carlo]

Im testing your proxy now since a week. they main problem seems to be the apache.

i figured out that it does reject lesser shares if i run this settings for the apache:
KeepAlive=On
KeepAliveTimeout=60
MaxKeepAliveRequests=250
MaxClients=100

I run 8 GPU miners.

But its still not the same reject rate if i connect directly to a pool. Im happy if somebody has other ideas, cause the fail-over is so nice in days of ddos.

Problems during the last 2 days:

Code:

ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: Work not found in proxy database.
ERROR: Cannot connect to Bitcoin: Bitcoin returned error message: <?xml version="1.0" encoding

cheers

[kripz]

Is it safe to drop the submitted work data? I want to reset my stats so i can use it for benchmarking.

Also what is average_interval?

EDIT: Once a pool goes down, does it auto switch as a fail over and then switch back once it's back up?
EDIT: How do you test if the pool is down? Mine seems to be constantly cycling through the pools even though they seem to be ok.

[krom]

EDIT: Once a pool goes down, does it auto switch as a fail over and then switch back once it's back up?
EDIT: How do you test if the pool is down? Mine seems to be constantly cycling through the pools even though they seem to be ok.

If a pool does not respond within a given time, which is about 3 seconds, the proxy will continue with the next pool in the priority list.

[kripz]

So when does it switch back to the highest priority?