Prohashing Mining Pool Forums

Later today, Chris will be releasing a new version of the mining server.

This new version changes the way that connections from miners are handled. As before, every worker should be given a unique name, and names should never be reused even after decommissioning. The difference is that whereas before we have always warned not to use duplicate "n=" worker names, beginning with this release duplicate worker names will be prohibited. Workers with duplicate names will be refused authentication so that only the first worker with that name is able to submit shares.

The reason for the change is that it is currently possible for a worker to accidentally obtain multiple connections with the same worker. Misconfigured software, or entering the same backup pool as the primary pool, can lead to this issue. Workers then waste bandwidth when they receive multiple copies of work, have rejected shares, and use up CPU power of the mining server. The double-connected workers also increase estimated hashrate.

Chris will issue the change within the next 24 hours. Before then, please check to ensure that every miner has a unique "n=" password argument so that none of your workers are disconnected.

Steve Sokolowski wrote: Chris will issue the change within the next 24 hours. Before then, please check to ensure that every miner has a unique "n=" password argument so that none of your workers are disconnected.

What you mean?


the server kick me away with any passwort argument


Now iam going connecting and now "pool dead"


[2016-12-06 14:25:08] Pool 0 stratum+tcp://prohashing.com:3333/#xnsub
#skipcbcheck not responding!
[2016-12-06 14:25:10] pool 0 JSON stratum auth failed: (null)
[2016-12-06 14:25:42] pool 0 JSON stratum auth failed: (null)

And now that...

2000-01-01 22:42:45] Please check the details from the list below of
[2000-01-01 22:42:45] Most likely you have input the wrong URL, forgo
workers
[2000-01-01 22:42:45] Pool: 0 URL: stratum+tcp://prohashing.com:3333
word: m=solo c=gamecredit n=chrisstevepleasefaster
[2000-01-01 22:42:45] Press any key to exit, or BFGMiner will try aga
No servers could be used! Exiting



Now iam conected

And now again disconnected....

Please make it like before ! Before all works fine and now not

fugju wrote:

Steve Sokolowski wrote: Chris will issue the change within the next 24 hours. Before then, please check to ensure that every miner has a unique "n=" password argument so that none of your workers are disconnected.

What you mean?


the server kick me away with any passwort argument


Now iam going connecting and now "pool dead"


[2016-12-06 14:25:08] Pool 0 stratum+tcp://prohashing.com:3333/#xnsub
#skipcbcheck not responding!
[2016-12-06 14:25:10] pool 0 JSON stratum auth failed: (null)
[2016-12-06 14:25:42] pool 0 JSON stratum auth failed: (null)

And now that...

2000-01-01 22:42:45] Please check the details from the list below of
[2000-01-01 22:42:45] Most likely you have input the wrong URL, forgo
workers
[2000-01-01 22:42:45] Pool: 0 URL: stratum+tcp://prohashing.com:3333
word: m=solo c=gamecredit n=chrisstevepleasefaster
[2000-01-01 22:42:45] Press any key to exit, or BFGMiner will try aga
No servers could be used! Exiting



Now iam conected

And now again disconnected....

Please make it like before ! Before all works fine and now not

The release hasn't been issued yet, so it couldn't have caused this problem.

I'll have Chris investigate the issue and he will get back to you to see if this is a global problem, or if there is something in your configuration that you could change.

Now it works since 10min.

Chris issued this release last night, but he found that the implementation was incorrect.

Apparently, these A4s create a new connection and stop sending shares to the old connection. Our implementation was that when a duplicate miner connects, the new connection should be refused. It turns out that the correct implementation is to disconnect the old miner when a new connection is made, because the old miner never submits shares anymore.

We already reverted to the previous version and are making the changes now.