- General
-
Bugs
0
Fixed
ZCash Connection closed by server
Hey all!
So, after running for a tiny bit the Cuda Miner in your instructions page, I began getting messages of "connection closed by server r:0", getting stuck in a loop. If I attempt to restart the miner, it'll stay locked in that loop.
Here's the command I'm using in order to start the miner:
./zm --server zec.poolmining.org --port 3036 --user <zcash_address>.<worker_name> --temp-target 65 --logfile
any suggestion on why that might be happining?
Customer support service by UserEcho
I would need either your current IP or your wallet address to investigate. If you'd like to keep it confidential mail to info@poolmining.org.
This is what whatsmyip.com reports: 84.90.214.80
And the address: t1cQvdwU5Rn2TG89sXo2LfC2XiahGjG2jiL
Could you try again? It might happen again but this time I will be able to figure out why.
Restarted and it's currently running ok. If it happens again (not hopefully in a while), I'll notify here.
And it happened again
Edit: In fact it's stuck between loops of "Connection closed by server" and "Connection closed by peer".
Here's a piece of the log:
2017-11-14 23:09:59|> GPU0 61C Sol/s: 146.6 Sol/W: 1.36 Avg: 117.7 I/s: 78.2 Sh: 4.53 1.00 104 +++
2017-11-14 23:10:19| GPU0 61C Sol/s: 144.7 Sol/W: 1.36 Avg: 117.7 I/s: 78.2 Sh: 4.53 1.00 104 ++
2017-11-14 23:10:39|> GPU0 61C Sol/s: 146.8 Sol/W: 1.36 Avg: 117.8 I/s: 78.2 Sh: 4.54 1.00 100 ++
2017-11-14 23:10:48|# connection closed by server r:0
2017-11-14 23:10:48|# reconnecting
2017-11-14 23:10:59|# GPU0 connected to: zec.poolmining.org:3036
2017-11-14 23:10:59|recv: Connection reset by peer
2017-11-14 23:11:01|# GPU0 connected to: zec.poolmining.org:3036
2017-11-14 23:11:01|# connection closed by server r:0
2017-11-14 23:11:03|# GPU0 connected to: zec.poolmining.org:3036
2017-11-14 23:11:03|# connection closed by server r:0
2017-11-14 23:11:05|# GPU0 connected to: zec.poolmining.org:3036
2017-11-14 23:11:05|# connection closed by server r:0
2017-11-14 23:11:07|# GPU0 connected to: zec.poolmining.org:3036
2017-11-14 23:11:07|# connection closed by server r:0
2017-11-14 23:11:10|# GPU0 connected to: zec.poolmining.org:3036
2017-11-14 23:11:10|recv: Connection reset by peer
2017-11-14 23:11:12|# GPU0 connected to: zec.poolmining.org:3036
2017-11-14 23:11:12|# connection closed by server r:0
2017-11-14 23:11:14|# GPU0 connected to: zec.poolmining.org:3036
2017-11-14 23:11:14|recv: Connection reset by peer
2017-11-14 23:11:16|# GPU0 connected to: zec.poolmining.org:3036
2017-11-14 23:11:16|# connection closed by server r:0
Well, I just returned and everything is running fine now! Guess you did something, thank you!
I've identified a security measure in the pool code that was acting too aggressively on perceived malformed data sent by clients. This feature is now disabled until we find a fix without side-effects. Sorry for that.
A bug in the pool-code responsible for this issue has been fixed and this should not happen again.