Open aleqx opened 7 years ago
... now if I execute it again I get:
# node proxy.js
zecProxy is listening on port 8000
zecProxy connected to eu1-zcash.flypool.org:3333
undefined:1
^
SyntaxError: Unexpected token
at Object.parse (native)
at DestroyableTransform.strict (/root/zecProxy/node_modules/ldjson-stream/index.js:14:26)
at DestroyableTransform.transform [as _transform] (/root/zecProxy/node_modules/split2/index.js:27:21)
at DestroyableTransform.Transform._read (/root/zecProxy/node_modules/readable-stream/lib/_stream_transform.js:184:10)
at DestroyableTransform.Transform._write (/root/zecProxy/node_modules/readable-stream/lib/_stream_transform.js:172:12)
at doWrite (/root/zecProxy/node_modules/readable-stream/lib/_stream_writable.js:237:10)
at writeOrBuffer (/root/zecProxy/node_modules/readable-stream/lib/_stream_writable.js:227:5)
at DestroyableTransform.Writable.write (/root/zecProxy/node_modules/readable-stream/lib/_stream_writable.js:194:11)
at Socket.ondata (_stream_readable.js:528:20)
at emitOne (events.js:82:20)
Did the pool ban me? Hmm
On nanopool with nodejs 4.2.6 I get this:
./miner --server localhost --port 8000 --user ${MY_ZCASH_ADDRESS}.proxy/${MY_EMAIL} --pass x --solver 0
# node proxy.js
zecProxy is listening on port 8000
zecProxy connected to zec-eu1.nanopool.org:6666
====================================
miner listener received data{"id":1,"method":"mining.subscribe","params":["EWBF 0.3.4b",null,"localhost","8000"]}
this data has been sent to the mining pool
====================================
====================================
pool socket has received data{"id":1,"result":[null,"605901000000000070b887d5a58e565f"],"error":null}
====================================
====================================
pool socket has received data{"id":null,"params":["000369d000000000000000000000000000000000000000000000000000000000"],"method":"mining.set_target"}
sending this to the miners{"id":null,"params":["000369d000000000000000000000000000000000000000000000000000000000"],"method":"mining.set_target"}
====================================
====================================
miner listener received data{"id":2,"method":"mining.authorize","params":["${MY_ZCASH_ADDRESS}.proxy/${MY_EMAIL}","x"]}
this data has been sent to the mining pool
====================================
====================================
pool socket has received data{"id":2,"result":true,"error":null}
/root/zecProxy/lib/pool_listener.js:32
miners.get(obj.id).write(JSON.stringify(obj) + '\n');
^
TypeError: Cannot read property 'write' of undefined
at DestroyableTransform.<anonymous> (/root/zecProxy/lib/pool_listener.js:32:22)
at emitOne (events.js:77:13)
at DestroyableTransform.emit (events.js:169:7)
at DestroyableTransform.<anonymous> (/root/zecProxy/node_modules/readable-stream/lib/_stream_readable.js:786:14)
at emitNone (events.js:67:13)
at DestroyableTransform.emit (events.js:166:7)
at emitReadable_ (/root/zecProxy/node_modules/readable-stream/lib/_stream_readable.js:448:10)
at emitReadable (/root/zecProxy/node_modules/readable-stream/lib/_stream_readable.js:444:5)
at readableAddChunk (/root/zecProxy/node_modules/readable-stream/lib/_stream_readable.js:187:9)
at DestroyableTransform.Readable.push (/root/zecProxy/node_modules/readable-stream/lib/_stream_readable.js:149:10)
Looking at the code, I have to ask: have you actually used this successfully with multiple miners behind the proxy? The reason I'm asking is that your code sends the same job to all miners for all broadcast jobs from the pool (the mining.notify
method) ... isn't that going to create duplicate work for the miners?
Hi guys, We have same issue (first post) with eu1-zcash.flypool.org Any hint ?
I have the same issue as the first post with EWBF. nhqminer works fine.
Any ideas?
I just installed this according to instructions on a Ubuntu 16.04.2 with all updates to date. I tried flypool, nanopool, suprnova using the EWBF miner ... all fail. Connecting directly to the pools works just fine.
my config.json is
Launched the proxy ... seems to work so far:
Then I launched the ewbf miner ... it fails:
The proxy output says:
Executing the miner directly works just fine: