Hello!
The program works through a proxy?
I have access to the Internet only through the proxy.
Hi, You may try to use these parameters for an HTTP proxy: -Dhttp.proxyHost= proxyHost -Dhttp.proxyPort= proxyPortOr these for a SOCKS proxy: -DsocksProxyHost= proxyHost -DsocksProxyPort= proxyPortFor exemple: java -Dhttp.proxyHost=192.168.1.1 -Dhttp.proxyPort=1080 -jar stratum-proxy.jar ... |
|
|
|
|
The appendWorkerNames option is not compatible with Nicehash.
Nicehash accepts only one worker by stratum connection. If you use the appendWorkerNames, each time a worker connects to the proxy, the proxy issue an authorization request on the already established stratum connection to the pool (since the proxy merges all the worker connections to a single pool connection). When Nicehash receives the second authorization request, it closes the stratum connection.
=> set "appendWorkerNames":false
|
|
|
|
|
Hi,
Could you fill a bug on github with the log file (DEBUG level) when the problem happens ? I will have a look when I have some time.
Thanks.
|
|
|
|
|
I personally really appreciate your efforts. I think it takes a lots of time to setup and maintain all these servers.
Keep up the good work Chrys.
Thanks.
|
|
|
|
did anybody tried to buy hashing power from nicehash?
proxy get's rejected by nicehash because of extranounce2 size
my pool has size=4 => proxy will give 3 to nicehash which complaints that is too low..
i check the source code and found in getWorkerExtranonce2Size():
return extranonce2Size != null ? extranonce2Size - extranonce1TailSize : 0;
because extranonce1TailSize is 1 (DEFAULT VALUES).
if i will set the extranonce1TailSize=0, i will only get maximum one worker.
What should I do to have multiple workers (<256) and worker.extranounce2size=4 ?
Thanks,
It is not possible. It is a limitation of the stratum protocol. When the proxy "consumes" n bytes of extranonce2, it allows you to proxify 2^n workers. So, if you want to consume 0 byte of extranonce2 to be compatible with Nicehash, you can proxify only 2^0=1 worker. |
|
|
|
is there an easy way ( a formula maybe ) of defining which pool should get which weight for a specific time on the pool? ...
ie ... 7 pools that need to mine for different periods of time ... is there an easy way of calculating what the weight of each individual pool should be? ...
#crysx
The best way is to set the weight of each pool to the time you want it mines and set the roundDuration to the total time (weight) of all pools. For example, you have 3 pools and your needs are: Pool1 mines for 32 minutes Pool2 mines for 45 minutes Pool3 mines for 15 minutes Set the weight of pool1 to 32, the weight of pool2 to 45, the weight of pool3 to 15 and the roundDuration to 32 + 45 +15 = 92 minutes. Notice: If you add a new pool through the GUI, the above calculation is no more valid since a pool mining duration is relative to its weight, to the other pool weights and to the roundDuration. But at the moment, you cannot change dynamically the roundDuration (you need to change the configuration file and so to restart the proxy). hi all ... donation by mining ... dbm ... im very happy to announce that the donation links are now active for community use ... please have a look and read - and help with the mining donations to these awesome devs ... the op will be updated as soon as i collate the rest of the info required ... the thread post is here - https://bitcointalk.org/index.php?topic=1089744.msg12480969#msg12480969 ... join in and help hash for the devs ... btw - pfool ... i have a few more servers being setup soon - so if you could please send me a pm of your details ( btc donation address - website - dev details - etc ) - i would really like to add you to the list of devs ... #crysx Thank you for your job  |
|
|
|
i have an issue with the weightedRoundRobin 'situation' ...
if anyone can help that would be great ...
it seems that the settings for duration is not being adhered to ... i set it at 52 ( which im assuming is 52minutes ) and the each of the pool weight at 1 ( which im assuming is even 52minutes per pool ) ...
this is obviously wrong as the pools rotate at intervals much less than 52minuts ... i couldnt tell you how long between rotation - but its definitely NOT 52minutes ...
can someone please shed some light on how this is to be accomplished please? .. pfool? ...
btw - it is the latest version 0.8.0 - running in centos 7 x64 ...
#crysx
The "weightedRoundRobinRoundDuration" define the duration of a round robin cycle. During the cycle, each pool will become active in turn. The time a pool is active is defined by the Round time, the pool weight and the total weight of all pools : miningTimeOfPool = (poolWeight * roundDuration) / totalPoolWeight So, in your case, if all pools have a weight of 1 and for example you have 4 pools configured, each pool will mines 52/4 = 13 minutes before switching to the following. tanx for the info pfool ... i was wondering how to piece it all together ... is this documented anywhere? ... this explains why they are such small intervals ... if the weight was raised for any one or another ( like in the sample conf file - where pool one has a weight of 9 and pool two has a weight of one ) where they have different weights for the pool - how is it calculated then? ... edit - never mind ... i worked it out from the calculation ... i must have been asleep while i was responding to you ( which seems to be quite often lately ) ... from the formula - i would need to increase the roundDuration to 208 for the pools to mine at 52minutes each with a weight of 1 ... or as you would have it ... roundDuration = ( miningTimeOfPool * totalPoolWeight ) / poolWeight who said learning maths at school was useless? ...  ... what i didnt realize also was that the calculation is for EACH pool ... so the weight of each pool affects the time mined ... tanx again mate ... #crysx You've got it! |
|
|
|
i have an issue with the weightedRoundRobin 'situation' ...
if anyone can help that would be great ...
it seems that the settings for duration is not being adhered to ... i set it at 52 ( which im assuming is 52minutes ) and the each of the pool weight at 1 ( which im assuming is even 52minutes per pool ) ...
this is obviously wrong as the pools rotate at intervals much less than 52minuts ... i couldnt tell you how long between rotation - but its definitely NOT 52minutes ...
can someone please shed some light on how this is to be accomplished please? .. pfool? ...
btw - it is the latest version 0.8.0 - running in centos 7 x64 ...
#crysx
The "weightedRoundRobinRoundDuration" define the duration of a round robin cycle. During the cycle, each pool will become active in turn. The time a pool is active is defined by the Round time, the pool weight and the total weight of all pools : miningTimeOfPool = (poolWeight * roundDuration) / totalPoolWeight So, in your case, if all pools have a weight of 1 and for example you have 4 pools configured, each pool will mines 52/4 = 13 minutes before switching to the following. |
|
|
|
Any way to lock the web page by user name and password. Thanks in advance
in the latest version - you have the option in the configuration files ... username and password will access only to the ones you allocate and everything else is readonly as far i can tell - for others to view ... #crysx Indeed, in the last version you can: 1) Lock all the web page 2) Lock only the admin features (users without the credentials have a read-only access) 3) Lock nothing Here are the corresponding configurations: 1) apiUser and apiPassword set to not-empty values. apiReadOnlyAccessEnabled=false 2) apiUser and apiPassword set to not-empty values. apiReadOnlyAccessEnabled=true 3) apiUser and apiPassword not set or set to empty values. apiReadOnlyAccessEnabled=do not care For options 1) and 2), you should leave the apiEnableSsl option commented or set to true Call me a little slow can you please provide a sample config with the user and pass. Sorry my coding stinks. Thanks Just modify your configuration file like this: "apiUser": "username",
"apiPassword": "password",
"apiReadOnlyAccessEnabled": false,
"apiEnableSsl": true |
|
|
|
Any way to lock the web page by user name and password. Thanks in advance
in the latest version - you have the option in the configuration files ... username and password will access only to the ones you allocate and everything else is readonly as far i can tell - for others to view ... #crysx Indeed, in the last version you can: 1) Lock all the web page 2) Lock only the admin features (users without the credentials have a read-only access) 3) Lock nothing Here are the corresponding configurations: 1) apiUser and apiPassword set to not-empty values. apiReadOnlyAccessEnabled=false 2) apiUser and apiPassword set to not-empty values. apiReadOnlyAccessEnabled=true 3) apiUser and apiPassword not set or set to empty values. apiReadOnlyAccessEnabled=do not care For options 1) and 2), you should leave the apiEnableSsl option commented or set to true |
|
|
|
New version released (0.8.0): https://github.com/Stratehm/stratum-proxy/releasesChanges since 0.7.1-SNAPSHOT: -Fix the uptime when a pool is down. -Enable Kick Connection, Kick IP and Ban IP in the GUI. -Add worker version in the connection page and forward show_message from pool to clients -Try to fix a Getwork issue. Workers are not immediatly notified with job reset. -Add the apiReadOnlyAccessEnabled. If an apiUser is set and this option is present, the read-only API methods are publicly accessible. The displayed GUI will be read-only and login will be required to access to admin features (modify/create/delete pools, ban users...) -Starting pool is now done asynchronously to not delay the proxy startup if a pool is down. -Restore the GUI compatibility with Internet Explorer -Generate SSL certificate with SHA256 instead of sha-1 for GUI (remove stratum-proxy-keystore.jks from the database directory to generate a new certificate) -Add the share validation on Stratum Worker connections if the validateGetworkShares option is enabled. -Add the number of accepted/rejected shares in the user/list API method and in the users page. Changes since 0.7.0: -Allow the value 1 for the workerNumberLimit option. |
|
|
|
Version 0.7.0 released: https://github.com/Stratehm/stratum-proxy/releasesChanges since 0.6.0: -Fix issue #29: UI not available on some systems. -Fix issue #30: Enable Kick/Ban buttons on the User page. -Add ipVersion option to force the use of a particular IP version. (auto, v4 or v6) -Add the suggestedPoolDifficulty option to suggest a difficulty to the pool. -Add pool uptime and number of disconnections in the pool page. -Add a summary method to the API (#35) -Add I18n on dates. -Implementation of the connections page. -Fix the --version and --help option on command line. NOTE: I have no more enough time to "participate" to this thread. Now, I will mainly focus on Github requests. I let this Thread open so you can help people that need it. Thanks! Error:
Jar file was not found
1: org.glassfish.grizzly.http.server.CLStaticHttpHandler.getJarFile(CLStaticHttpHandler.java:339)
2: org.glassfish.grizzly.http.server.CLStaticHttpHandler.handle(CLStaticHttpHandler.java:278)
3: strat.mining.stratum.proxy.Launcher$2.handle(Launcher.java:294)
4: org.glassfish.grizzly.http.server.StaticHttpHandlerBase.service(StaticHttpHandlerBase.java:188)
5: org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:217)
6: org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:565)
7: org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:545)
8: java.lang.Thread.run(Unknown Source)
Please see the log for more detail.
where are the log files?
You should try the new version, a fix for this issue is included |
|
|
|
Did you have any problems with MRR (MiningRigRentals) when testing ?
MRR connects on Port 3333 usually but then redirects me to another Port, lets say 50002, often this redirect does not work so the Pool gets marked as DOWN and tries to reconnect every 5 seconds which still does not work.. A few restarts of the Pool then finally succeed.
If I connect my rigs directly to MRR - no problem.
Could you please send me your log file when you try to use MRR ? MRR surely uses the reconnect stratum notification (which should be supported by the proxy), but unfortunately I was not able to test it for real. It may be a bug in the management of this kind of notification. |
|
|
|
New release: 0.6.0 It can be downloaded here: https://github.com/Stratehm/stratum-proxy/releasesChanges: -Bug fix : All share where rejected with message Invalid Extrnaonce 2 size when the pool sent a new extranonce2Size through a notification. (Only Nicehash was impacted) -Bug fix : Pool was not declared as DOWN when a bad extranonce2Size was sent. -Add the real share difficulty logging on the Getwork connections with "logRealShareDifficulty" -Add the Getwork shares validation for the Scrypt with "validateGetworkShares" and "isScrypt": true -Bug #23 fixed : Accept non numeric ids in JSON-RPC requests to support last versions of BFGminer. -Bug #24 fixed : Username is mandatory only if "appendWorkerNames" is disabled and password is mandatory only if "useWorkerPassword" is disabled. -Update Bootstrap to 3.3.1, bootstrap-select to 1.6.3 and highsotock to 2.0.4 -GUI technical refactoring. -Add i18n (Only English and French at the moment) -Add the proxy version in the footer -Add the difficulty counters on users page. -Add workerNumberLimit parameters to set the maximum number of workers connected on the proxy (256 or 65536 workers) -Update the API documentation in README /!\ There are some changes in the configuration file. You may have to modify your old configuration files. pfool can you pls compile latest version ? i think it's 0.60 ?
thx
I saw your post during the packaging process |
|
|
|
------->Pool A
| (Active)
|
|
Single Betarig ------------> proxy stratum---------> Pool B
(Big renter) | (Active)
|
|
--------> Pool C
(Active)
possible? what would be the config?
yes - but not 'split' hashing for each pool ... just failover as far as i can see ... so it will jump from one pool to another to another and then back again once the initial pools come back online ... its how i run mine farm when i want to rent my hashes out ... please correct me if im wrong here ... #crysx I think you can set-up some kind of load balance mining 5 minutes on each pool round robin style. But i never tried... ok so how wud be the config and what user and pass should be put into the beta renter? for the load balance - you need to approach the owner / dev of the proxy ... pm him ... as for the failover - well - thats actually very easy as there is a sample of the conf in the package ... #crysx ok then lets wait for the author for a response The proxy cannot split the hashrate of a single worker. The real load-balancing is not possible to implement in a proxy (at least, I do not know how). Round-robin is the best candidate for those who are looking for something which seems like load-balancing through the proxy. |
|
|
|
Tried to recompile the latest version from github and got the following error in the "log" pane from the web interface (click to enlarge):
Fixed |
|
|
|
so example
-Xmx64M for 64mb?
Yes
so example
are 64mb enough to run it?
It depends of the number of workers connected on the proxy. I have had the proxy run with only 16mb with 4 workers. But you should experiment several values. It also depends if you run the proxy on a 32 bits or 64 bits JVM (64 bits will need more memory). If the memory is too low, you will surely see some MemoryError in the logs or see a high CPU usage of the proxy. i'm running it with 4 workers yes, and it give me plenty of error sometimes, refuse connection/closed connection, after that it stuck there and i must restart the whole vps You have to restart the VPS when the proxy craches ?  I rarelly saw a simple process craching a whole system since Windows 98... (and never on Linux) |
|
|
|
so example
-Xmx64M for 64mb?
Yes
so example
are 64mb enough to run it?
It depends of the number of workers connected on the proxy. I have had the proxy run with only 16mb with 4 workers. But you should experiment several values. It also depends if you run the proxy on a 32 bits or 64 bits JVM (64 bits will need more memory). If the memory is too low, you will surely see some MemoryError in the logs or see a high CPU usage of the proxy. |
|
|
|
how would you set this up for sha256, and scrypt, on one instace isscrypt false?, and on the next iscrypt true, and of course different ports
To run several instances of the proxy on a same host, you have indeed to change (or disable) the 3 ports for stratum, getwork and API, but you also have to set a different databaseDirectory for each instance through the "databaseDirectory" directory parameter. |
|
|
|
|
I will need your complete log file to help you.
How much RAM the proxy take on your computer ? You can try to lower the RAM consumption by adding the -XmxYYYM before the -jar option on the command line where YYY is the max memory size in MB for the java heap space (the java process will still consume a bit more than this specified size).
You can try with a 64MB size.
|
|
|
|
|
Show Posts
