New stratum/getwork proxy with Web-based GUI and pools management

[Pfool]

It is not a configuration problem. You are certainly using the latest BFGminer version which has broken its JSON-RPC protocol implementation (string IDs are not allowed in JSON-RPC). A workaround has been implemented in the proxy on the git repository. (and not yet released).

You should try to build the proxy package from the git repository to have the latest fixes. If you do not know how to do, I will soon build a pre-release of the next version.

[jk9694]

So I compiled the source and here is what im getting now

2014-12-24 10:19:20,254 INFO     [/192.168.1.13:60323-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection /192.168.1.13:60323 subscribed. 1 connections active on pool Paycoin.
2014-12-24 10:19:20,267 WARN     [/192.168.1.13:60323-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown request type on connection /192.168.1.13:60323. methodName: mining.get_transactions, id: txlist29c, params: [29c]

[Pfool]

Hum...It is a request that I do not know...

I have asked a question about it in the Stratum protocol thread.

[cloudhashing_patrick]

It is not a configuration problem. You are certainly using the latest BFGminer version which has broken its JSON-RPC protocol implementation (string IDs are not allowed in JSON-RPC).

id - The request id. This can be of any type. It is used to match the response with the request that it is replying to.
http://json-rpc.org/wiki/specification

(To be fair that is probably quite the nuisance to implement correctly...)

[Pfool]

Hum...my bad. I have indeed misread the specs. So, here is an erratum:

It is not a configuration problem. You are certainly using the latest BFGminer version which uses a string for JSON-RPC requests ids and my broken JSON-RPC protocol implementation does not handle correctly this id. The fix is available on the git repo.

Thank you cloudhashing_patrick

[tekke]

Hi to all. I have downloaded the proxy. Kudos to the author, thanks for it

I'm having a problem. I create a simple .conf file using the minimal sample. everithing boot up ok ( I guess) , I access to the web but I can't see any info on any of the tabs but on Logs. Also I can't get it to work , my remote worker tries to connect but I end up having this error on the log

Code:

2015-01-03 15:03:58,603 INFO     [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /186.14.28.73:52305.
2015-01-03 15:03:58,641 ERROR    [/186.14.28.73:52305-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection /186.14.28.73:52305. Failed to parse line {"id": 0, "method": "mining.subscribe", "params": ["cgminer/3.7.0"]}.

my cgminer conf is also very simple:

Code:

{
		"url" : "stratum+tcp://proxyip:3333",
		"user" : "1",
		"pass" : "x"
	},

This is my .conf for the proxy

Code:

{
  "pools" : [ {
    "host" : "stratum+tcp://us1.coinking.io",
    "user" : "u1.3"
  }
  } ]
}

Thanks for the help

[altcointalk14]

Hello,

I have about 60 asic running thru the stratum proxy server then to a btc pool.  It seems the stratum server goes down for 30-40 seconds each time a block is found.

Is this normal?

If not, what can I do to reduce this downtime.?  Thank You!

[Pfool]

Hello,

I have about 60 asic running thru the stratum proxy server then to a btc pool.  It seems the stratum server goes down for 30-40 seconds each time a block is found.

Is this normal?

If not, what can I do to reduce this downtime.?  Thank You!

Really odd. I cannot tell you what happen. How do you see that the proxy disconnects from the pool after a block is found ? Through the logs or through the GUI ?

[altcointalk14]

I am watching the cgminer terminal window in linux.  Now it wont do it, I am trying to catch a screenshot.  Watching multiple workers/windows they would all do it at the same time

[altcointalk14]

Here is a screen shot, it is about 30-40 seconds every time it happens.

[Pfool]

Could you send me the log file of the proxy ? (By default, in the temp directory of your OS and named stratum-proxy.log)

Thanks

[Anon39]

Hi guys, i installed the stratum but i have this error:

Code:

xxx on pool 1. Booo !!!!. Error: JsonRpcError [ code=23, message=low difficulty share of 0.000027396682152006082, traceback=null]

i can't understand why 

[Pfool]

Hi guys, i installed the stratum but i have this error:

Code:

xxx on pool 1. Booo !!!!. Error: JsonRpcError [ code=23, message=low difficulty share of 0.000027396682152006082, traceback=null]

i can't understand why 

Hi,
Which algorithm ? Wich mining software and hardware ?

[Anon39]

Hi guys, i installed the stratum but i have this error:

Code:

xxx on pool 1. Booo !!!!. Error: JsonRpcError [ code=23, message=low difficulty share of 0.000027396682152006082, traceback=null]

i can't understand why 

Hi,
Which algorithm ? Wich mining software and hardware ?

algo: scrypt

i have this problem with:

- amd radeon HD 7870 with cgminer 3.7.2
- rented gridseedx3

100% rejected with the above error

it seems to work with an unknown rented rig of 2.6 MH/s

PS: my radeon works perfectly if i point it directly to any pool

[Pfool]

Cgminer 3.7.2 has an extranonce2 size management bug. This bug prevents cgminer to work behind a proxy. You should try to upgrade to sgminer instead: https://www.nicehash.com/index.jsp?p=software#sgminer

For rented rigs, it depends if the renter's rigs run with this buggy version of cgminer or with a newer one.

[girino]

Hi,

i've been using this proxy for quite sometime and it is great. I just need to know a little more about this:

-Up to 256 workers at the same time (stratum and getwork)

1- is this the number of workers, or the number of connections? Can I have a single worker with 300 connections, for example?
2- is this a restriction of the architecture or can this be changed? (I don't mind having to compile the code to increase it, just need to know where to change it).

I have being looking into to the code and have not seen this restriction coded anywhere, that's why i asked question 2.

Thanks in advance,
Girino.

[Pfool]

Hi,

i've been using this proxy for quite sometime and it is great. I just need to know a little more about this:

-Up to 256 workers at the same time (stratum and getwork)

1- is this the number of workers, or the number of connections? Can I have a single worker with 300 connections, for example?
2- is this a restriction of the architecture or can this be changed? (I don't mind having to compile the code to increase it, just need to know where to change it).

I have being looking into to the code and have not seen this restriction coded anywhere, that's why i asked question 2.

Thanks in advance,
Girino.

This is a limit on the number of connections.

You can try to increase this limit to 65536 connections by modifying a constant in the source code. It should work but I never tested it. The drawback is that you may have problems with Nicehash. It should be rare but it may happen depending on the pool of the job you will work on (But you have no control on that). The symptom will be a disconnection of the pool with the message "The extranonce2Size for the pool nameOfThePool is too low. Size: X, mininum needed Y.". But on the next reconnection of the pool (if you are lucky), the problem will vanish since Nicehash will affect you on a different job.

Change the value of the constant DEFAULT_EXTRANONCE1_TAIL_SIZE in the Constants.java file from 1 to 2.

In all cases, I am interested by the result of your experiment.
Good luck.

[Anon39]

Cgminer 3.7.2 has an extranonce2 size management bug. This bug prevents cgminer to work behind a proxy. You should try to upgrade to sgminer instead: https://www.nicehash.com/index.jsp?p=software#sgminer

For rented rigs, it depends if the renter's rigs run with this buggy version of cgminer or with a newer one.

thank you very much!  
i will try to mine with sgminer

[girino]

Hi,

i've been using this proxy for quite sometime and it is great. I just need to know a little more about this:

-Up to 256 workers at the same time (stratum and getwork)

1- is this the number of workers, or the number of connections? Can I have a single worker with 300 connections, for example?
2- is this a restriction of the architecture or can this be changed? (I don't mind having to compile the code to increase it, just need to know where to change it).

I have being looking into to the code and have not seen this restriction coded anywhere, that's why i asked question 2.

Thanks in advance,
Girino.

This is a limit on the number of connections.

You can try to increase this limit to 65536 connections by modifying a constant in the source code. It should work but I never tested it. The drawback is that you may have problems with Nicehash. It should be rare but it may happen depending on the pool of the job you will work on (But you have no control on that). The symptom will be a disconnection of the pool with the message "The extranonce2Size for the pool nameOfThePool is too low. Size: X, mininum needed Y.". But on the next reconnection of the pool (if you are lucky), the problem will vanish since Nicehash will affect you on a different job.

Change the value of the constant DEFAULT_EXTRANONCE1_TAIL_SIZE in the Constants.java file from 1 to 2.

In all cases, I am interested by the result of your experiment.
Good luck.

Thanks for the answer. I am trying it right. Just out of curiosity, what happens when the number of connections exceeds 256?

I had this weird problem last Saturday in which the pool simply stopped working. the web interface was ok, but it did not accept connections nor connected to the pool. Seemed like the thread expecting connections had stopped. But there was no exception or any error in the logs.

The only thing I could think of is that just before it stopped i had an increase in connections (i do not control the connections, they come as a "2% time share" paid by those who use my optimized X11 miner, so more people using it, more connections). So i 'ill try this change and see if it will work, but it may take a long time before such a surge in connections happens again (usually whenever x11 mining profitability increases).

[Pfool]

The pool connection problem you describe sould not be caused by the connection limit. If you can retrieve the logs when this problem comes back, please send me the file.


When the limit number of connections is reached, the connection is rejected with the following error in the logs:

Too many connections on pool xxxx for the connection xxxxxx. Sending error and close the connection.


On the client side, the following error should be displayed in the mining software:

Too many connection on the pool.