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

[Pfool]

Hi,

Could you send me the log file of the proxy please? I cannot see the begining of the error.

[jorneyflair]

Hi,

Could you send me the log file of the proxy please? I cannot see the begining of the error.

how to get the log file ? where?

[Pfool]

Hi,

Could you send me the log file of the proxy please? I cannot see the begining of the error.

how to get the log file ? where?

On Windows, it is located by default in the temp folder of the user: use %temp% in the address bar of the file explorer. The file is called stratum-proxy.log

[jorneyflair]

https://mega.co.nz/#!BUZHUKKJ!wIn6SdIrlwXVdn0VOAvG2u23ZvSH-LYbMU3z0k2FRJg

stratum-proxy.log uploaded , please helpme if possible.

[Pfool]

Could you enable the DEBUG logLevel and disable the second pool in your configuration file ?

In the configuration file:
Change the value of:
 "logLevel" : "DEBUG",
 "disableLogAppend": true,

And in the second pool configuration (Westhash), add/change the line:
"isEnabled": false

I have read the log file and it seems that a worker has successfully submited shares. Have you several workers? If so, could you do the tests only with the workers which does not work ?

Thanks

[jorneyflair]

Could you enable the DEBUG logLevel and disable the second pool in your configuration file ?

In the configuration file:
Change the value of:
 "logLevel" : "DEBUG",
 "disableLogAppend": true,

And in the second pool configuration (Westhash), add/change the line:
"isEnabled": false

I have read the log file and it seems that a worker has successfully submited shares. Have you several workers? If so, could you do the tests only with the workers which does not work ?

Thanks

i dont think the problem is  worker ,im using asicminer 850G tube , they say this shit cant mine anything except Ghash?

[proctologic]

I just found out about this great stratum-proxy and its perfect but i missing Balance. Is it anything that can be implented?

Cheers

[Pfool]

Hi,

Could you explain which balance you are talking about ?

[proctologic]

BALANCE:
This strategy monitors the amount of difficulty 1 shares solved for each pool
and uses it to try to end up doing the same amount of work for all pools.

[Pfool]

 
I like the way you explained it.

Maybe the already existing Weighted round robin strategy can be used with a weight of 1 for each pool. This strategy will mine in turn on each pool for the same amount of time. You will statistically have the same number of difficulty 1 shares on each pool. To lessen the variance effect, you can use a long round duration

Let me know if this could do the trick.

[proctologic]

It didnt work so implenting balance would be perfect.


https://www.dropbox.com/s/8h7e1gof722u4f2/startum-proxy.PNG

[proctologic]

I like the way you explained it.

Maybe the already existing Weighted round robin strategy can be used with a weight of 1 for each pool. This strategy will mine in turn on each pool for the same amount of time. You will statistically have the same number of difficulty 1 shares on each pool. To lessen the variance effect, you can use a long round duration

Let me know if this could do the trick.

Maybe this will work better?

LOAD BALANCE:
This strategy sends work to all the pools on a quota basis. By default, all
pools are allocated equal quotas unless specified with --quota. This
apportioning of work is based on work handed out, not shares returned so is
independent of difficulty targets or rejected shares. While a pool is disabled
or dead, its quota is dropped until it is re-enabled. Quotas are forward
looking, so if the quota is changed on the fly, it only affects future work.
If all pools are set to zero quota or all pools with quota are dead, it will
fall back to a failover mode. See quota below for more information.

The failover-only flag has special meaning in combination with load-balance
mode and it will distribute quota back to priority pool 0 from any pools that
are unable to provide work for any reason so as to maintain quota ratios
between the rest of the pools.

[Pfool]

I think we can really have a similar behavior with the WeightedRoundRobin strategy.

Could you try to lower the roundDuration of this strategy, for example with a 1 minute value (in the configuration file):
"weightedRoundRobinRoundDuration": 1,

If it works better (it should), you can try to adjust this parameter to have the best result (the pool difficulties and the number of pool can greatly modify results).

Does your miner support the set_extranonce extension ? (the Nicehash stratum extension) If so, it is fine. If not, do not set the parameter with a small value, since the miners have to be disconnected in order to switch pool (thus, it may kill your hashrate).

I hope this will work since it will be hard to implement a real loadBalance strategy (it is far easier to implement in a mining software than in a proxy) and I have not enough time to implement this strategy.

[proctologic]

Well the problem is that pool starts with diff 20 and Nicehash  is diff 30 minimum so every switch takes about 15 min to reconnect.

Same when i connect with my miners 30-40Mhs  and tries Round Robin it drops and takes forever to gain correct diff.

When i use load-balance in cgminer it remanins connected to all pools and never drops.

[Pfool]

every switch takes about 15 min to reconnect.

I do not really understand your problem. What is it taking 15 minutes to reconnect ? The proxy to a pool or your miner to the proxy ?

Load-balance in cgimner works fine since it can do a real load-balancing since it knows the real miner hashrate and it can switch pool at will. The proxy will not be able to do so with the stratum protocol. This protocol lacks of a way to switch pool without breaking the miner connection, except with the stratum extension implemented by Nicehash (the set_extranonce notification).

If your miner is compatible with this extension, the WeightedRoundRobin with a low round time (this is important) should have almost the same effect as the cgminer load-balancing. If your miner is not compatible, unfortunately, I will not be able to do something.

[andy75]

What about set the hash speed for each account in proxy manually?

[proctologic]

What are this lines and how can i optimize them?

  "poolHashrateSamplingPeriod" : 600,
  "userHashrateSamplingPeriod" : 600,
  "connectionHashrateSamplingPeriod" : 600,
  "hashrateDatabaseSamplingPeriod": 60,
  "hashrateDatabaseHistoryDepth": 7,

[Ambros]

Hi ! I have tried to point some rented miners (miningrigsrental.com) to the proxy. I wanna use this awesome software to switch them all together and to monitor locally. When i point rented miners to the proxy i see the connections under user table, but i have no hash rate . Someone has a solution or can explain me what i'm doing wrong ?
Thank everyone for help

[Develop]

Can someone please post a working config file for nicehash sha-256 config please, I would like to point several S3 Antminers to my box thats running this program and then point the box at nicehash.. Any help would be much appreciated.

[Goldenboyz]

Hello, is there a way to optimize the ram usage?
I made it run on rasp pi(using the precompiled .zip) and i noticed that it starts with 10.1% of ram usage and then it slowly grow up to 18.8%(84148Kb) up to now( after near 10 hours ).
The proxy is set to only show error log.
It would be nice if it can be optimized for devices like rasp pi(not so ram equipped).

Another thing is "weightedRoundRobinRoundDuration", i set it to "5" but it's not really mining 5 minutes then switch to other pool, but it switch much early, like 1 minute or so. Or could be i'm wrong with what that "5" means lol.
My config is:

Code:

"poolConnectionRetryDelay" : 5,
  "poolReconnectStabilityPeriod" : 5,
  "poolNoNotifyTimeout" : 240,
  "rejectReconnectOnDifferentHost" : false,
  "poolHashrateSamplingPeriod" : 600,
  "userHashrateSamplingPeriod" : 600,
  "connectionHashrateSamplingPeriod" : 600,
  "isScrypt" : true,
  "databaseDirectory": "",
  "hashrateDatabaseSamplingPeriod": 60,
  "hashrateDatabaseHistoryDepth": 7,
  "noMidstate": false,
  "apiLogLevel": "INFO",
  "validateSha26GetworkShares": true,
  "poolSwitchingStrategy": "weightedRoundRobin",
  "weightedRoundRobinRoundDuration": 5,

and every pool has "weight" : 1 . The pool is the same, just with 4 different accounts and it's a scrypt pool( doge ).
It's not that problem, mining seems to works good anyway, just to talk if the round of "X minutes" is really as expected.
Thanks for the proxy!