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

Pfool

full member

Activity: 217

Merit: 100

Quote from: altcointalk14 on January 03, 2015, 04:56:03 PM

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

sr. member

Activity: 751

Merit: 253

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!

tekke

legendary

Activity: 854

Merit: 1000

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

Pfool

full member

Activity: 217

Merit: 100

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

cloudhashing_patrick

newbie

Activity: 5

Merit: 0

Quote from: Pfool on December 24, 2014, 04:29:52 AM

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).

Quote

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

full member

Activity: 217

Merit: 100

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

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

jk9694

full member

Activity: 274

Merit: 122

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

full member

Activity: 217

Merit: 100

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

full member

Activity: 274

Merit: 122

OK so I am tired of beating my head on the desk,

2014-12-23 21:45:06,882 ERROR [/107.170.50.27:25404-Thread]:strat.mining.stratum.proxy.network.StratumConnection - JSON-RPC Parsing error with line: {"id":"auth","method":"mining.authorize","params":["x","x"]}

Can anyone shed some light on this.

Conf...

{
  "isScrypt" : true,
  "hashrateDatabaseSamplingPeriod": 10,
  "stratumListenPort" : 3333,
  "stratumListenAddress" : "192.168.1.10",
  "disableStratum": false,
  "getworkListenPort" : 3332,
  "getworkListenAddress" : "192.168.1.10",
  "disableGetwork": true,
  "apiListenPort" : 8888,
  "apiListenAddress" : "0.0.0.0",
  "databaseDirectory": "database2",
  "noMidstate": false,
  "pools" :
  [
  {
   "name" : "------------",
   "host" : "---------------------------------",
   "user" : "---------------------------------",
   "password" : "x",
   "enableExtranonceSubscribe" : false
  }
  ]
}

I get this error whenever I try to connect with stratum+tcp://192.168.1.10:3333 user:x pass:x

noMidstate is probably not needed, just trying other options blindly...

Pfool

full member

Activity: 217

Merit: 100

Quote from: smracer on December 19, 2014, 12:47:43 PM

I have been fucking around with Slush's stratum-mining-proxy for 2 days. It would run for 15min - 1 hour and then disconnect with Duplicate shares errors.

I installed this server in 15 min and it has been stable thus far with 247 workers.

It it stays up for a few hours I am sending you a tip.

Thanks!

I hope it will be fine. Please, let me know the result of your testing.

Thanks

Pfool

full member

Activity: 217

Merit: 100

Quote from: cloudhashing_patrick on December 18, 2014, 12:53:56 PM

First of all, excellent work, this works very well (which is something I cannot say for the majority of mining related software).

A few suggestions:

The documentation could be more complete, especially around the available configuration options.

Validation for stratum submissions would be pretty useful (there are certain clients which attempt to submit work on re-connect even if extranoonce1 changes).

Consider making multiple connections to the upstream pool to support > 256 clients. (Possibly this could simply be equally weighted round robin).

Ability to specify the source address for the upstream pool's tcp connection, lots of pools have various rate limiting restrictions which can be effectively side stepped this way.

Indeed, the documentation is out of date, I will try to find time to update it.

The stratum validation and outgoing connection local address binding are already in the todo list. Multiple connections to pools is a bit harder to implement, so I cannot promise you it will be done one day.

smracer

donator

Activity: 1057

Merit: 1021

I have been fucking around with Slush's stratum-mining-proxy for 2 days. It would run for 15min - 1 hour and then disconnect with Duplicate shares errors.

I installed this server in 15 min and it has been stable thus far with 247 workers.

It it stays up for a few hours I am sending you a tip.

Thanks!

cloudhashing_patrick

newbie

Activity: 5

Merit: 0

First of all, excellent work, this works very well (which is something I cannot say for the majority of mining related software).

A few suggestions:

The documentation could be more complete, especially around the available configuration options.

Validation for stratum submissions would be pretty useful (there are certain clients which attempt to submit work on re-connect even if extranoonce1 changes).

Consider making multiple connections to the upstream pool to support > 256 clients. (Possibly this could simply be equally weighted round robin).

Ability to specify the source address for the upstream pool's tcp connection, lots of pools have various rate limiting restrictions which can be effectively side stepped this way.

Pfool

full member

Activity: 217

Merit: 100

Quote

I have "validateSha26GetworkShares": true , I thought this would prevent any rejected shares?

The "validateSha26GetworkShares" option only validate shares that are submitted by Getwork workers. It has no impact on stratum.

Quote

Code:

Worker  Speed accepted  Speed rejected     Diff       Time (minutes)  Multi-algo parameters  Extranonce subscription
VWG       38.4829       274.8779 (87.72%)   128.0000  381		                     Y
Home    5981.3433         0.0000 (0.00%)   4096.0000  299		                     Y
SP30B   4104.8434         0.0000 (0.00%)   4096.0000   27		                     N
Not all workers are using extranonce.subscribe. Check out how to optimise your mining speed with extranonce.subscribe.

Quote

These numbers are through the proxy or with miners directly connected to Nicehash/Westhash ?

Quote

Is it possible to connect to a stratum proxy server in a remote location? Would the traffic be high? Would the added delay be unacceptable?

The reason I ask is that my mining rig is split across three locations, and it would be handy to not have to set up and maintain three stratum proxy servers.

Quote

No problem to connect workers on the proxy remotly. Just be sure that the port 3333 of the proxy is reachable from Internet. However, take care of the network latency between your worker and the proxy and between the proxy and the pool. A high latency will increase the reject rate of your workers.

Zelek Uther

hero member

Activity: 700

Merit: 504

Run a Bitcoin node.

I have the following workers on WestHash:

Code:

Worker  Speed accepted  Speed rejected     Diff       Time (minutes)  Multi-algo parameters  Extranonce subscription
VWG       38.4829       274.8779 (87.72%)   128.0000  381		                     Y
Home    5981.3433         0.0000 (0.00%)   4096.0000  299		                     Y
SP30B   4104.8434         0.0000 (0.00%)   4096.0000   27		                     N
Not all workers are using extranonce.subscribe. Check out how to optimise your mining speed with extranonce.subscribe.

The "VWG" and "Home" workers are stratum servers. "Home" should be 6.6TH/s and "VWG" should be 3.1TH/s.
SB30B is a directly connected SP30, I plan to put it and SP30A on a stratum proxy to avoid the disconnects. SP30A is offline right now, no idea why.

Why is VWG so low? It was previously showing us as 3000, now it is very low with a high percentage of speed rejected.
I have "validateSha26GetworkShares": true , I thought this would prevent any rejected shares?

I'm pointing 18TH/s at WestHash, but only being recognised for 10TH/s.

Zelek Uther

hero member

Activity: 700

Merit: 504

Run a Bitcoin node.

Is it possible to connect to a stratum proxy server in a remote location? Would the traffic be high? Would the added delay be unacceptable?

The reason I ask is that my mining rig is split across three locations, and it would be handy to not have to set up and maintain three stratum proxy servers.

Zelek Uther

hero member

Activity: 700

Merit: 504

Run a Bitcoin node.

How to install Pfool's stratum proxy on a Raspberry Pi running Raspbian

Noob note: the lines below with a colon at the end are headings to describe each section. You only need to type the commands underneath them.

Get latest updates:
sudo apt-get update
sudo apt-get dist-upgrade

Get Java:
sudo apt-get install openjdk-7-jre

Pfool's stratum proxy install:
wget https://github.com/Stratehm/stratum-proxy/releases/download/0.5.1/stratum-proxy-0.5.1.zip
unzip stratum-proxy-0.5.1.zip

EDIT: simplify the instructions.

Zelek Uther

hero member

Activity: 700

Merit: 504

Run a Bitcoin node.

Quote from: Pfool on December 17, 2014, 04:36:41 AM

For the grizzly error, it seems that the Getwork TCP port is already in user by another program (The Getwork error prevents the WebClient to start). If you do not use Getwork, you can disable it with the "disableGetwork": true option.

I have seen your post on the Nicehash thread and the nicehash response. I was not aware of this bug with the appendWorkerName and I do not understand why it does not work. I will try to contact Nicehash to get some details on this bug.

For your raspberry problem, the proxy only works with java >= 1.7 (the installed one is 1.6). You can try to install it with: sudo apt-get install openjdk-7-jre

Thanks for the tips Pfool, I'll try the disableGetwork parameter.

It would be awesome if appendWorkerName could work with Nice/WestHash!

I solved the Java issue a different way (which I'll post up just for reference). Next time I install it I'll try the command you suggest as it is easier than the method I used. (EDIT: done, and altered the instructions to use the simpler Java install command you suggested).

Pfool

full member

Activity: 217

Merit: 100

For the grizzly error, it seems that the Getwork TCP port is already in user by another program (The Getwork error prevents the WebClient to start). If you do not use Getwork, you can disable it with the "disableGetwork": true option.

I have seen your post on the Nicehash thread and the nicehash response. I was not aware of this bug with the appendWorkerName and I do not understand why it does not work. I will try to contact Nicehash to get some details on this bug.

For your raspberry problem, the proxy only works with java >= 1.7 (the installed one is 1.6). You can try to install it with: sudo apt-get install openjdk-7-jre

Zelek Uther

hero member

Activity: 700

Merit: 504

Run a Bitcoin node.

Quote from: Pfool on December 17, 2014, 03:28:08 AM

Quote from: Zelek Uther on December 17, 2014, 03:10:58 AM

Does the appendWorkerNames feature work with NiceHash / WestHash?

I keep getting "worker not authorized" errors, and it seems that only one worker makes it through to the pool.

I do not remember if Nicehash is able to track each of your worker individually (with a worker name like that BTC_ADDRESS.WORKER_NAME). But I think that only one worker can be authorized by TCP connection on Nicehash. If so, the appendWorkerNames will not work (and should indeed send this kind of error).

For your others errors:
-Do you now have access to the WebClient ?
-Do you connect your workers to the proxy through stratum or getwork ?

NiceHash/WestHash does allow individual worker names by appending .workername to the BTC address.

The WebClient still isn't working, still getting a grizzly error.

All workers are connecting through stratum.

A new issue I have is that I'm trying to do another install of the stratum proxy on a Raspberry Pi (for use at one of my mining locations).
I'm using Raspbian "Wheezy".

Code:

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ uname -a
Linux raspberrypi5 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ cat /proc/version
Linux version 3.12.22+ (dc4@dc4-arm-01) (gcc version 4.7.2 20120731 (prerelease) (crosstool-NG linaro-1.13.1+bzr2458 - Linaro GCC 2012.08) ) #691 PREEMPT Wed Jun 18 18:29:58 BST 2014

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ cat /etc/issue
Raspbian GNU/Linux 7 \n \l

This is the error:

Code:

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ java -version
java version "1.6.0_32"
OpenJDK Runtime Environment (IcedTea6 1.13.4) (6b32-1.13.4-1~deb7u1+rpi1)
OpenJDK Zero VM (build 23.25-b01, mixed mode)

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ java -jar /home/pi/stratum-proxy-0.5.1/stratum-proxy.jar -f /home/pi/stratum-proxy-0.5.1/stratum-proxy.conf
Exception in thread "main" java.lang.UnsupportedClassVersionError: strat/mining/stratum/proxy/Launcher : Unsupported major.minor version 51.0
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:643)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
	at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
Could not find the main class: strat.mining.stratum.proxy.Launcher. Program will exit.

This is the Java version that was installed by the command:
sudo apt-get install default-jre

Topic: New stratum/getwork proxy with Web-based GUI and pools management - page 17. (Read 120906 times)