Quote from: dogedood on March 22, 2017, 05:30:23 PM

Quote from: kano on March 15, 2017, 09:20:08 PM

Quote from: agentcash on March 15, 2017, 08:00:09 PM

... Is there a way to prevent this switch from happening on a pool restart?

It's more a problem of knowing at what commit the ckpool programs are tested and working ...
As far as I know that is some time last year ...
The last tag is v0.9.4 2016-08-23 (for standard ckpool I run ded126d5 which is the same thing since there's no ckpool changes in between them and there's a deadlock some point after that and the workinfo changes after that can break ckdb shift processing and payouts)

The problem is that there's a collection of ckpool programs in there and they aren't all tested properly or at all (and at what version/commit):
Mining pool, standard proxy, passthru proxy, proxy node, remote node, redirector, bitmain's hidden ckpool api to manage ckpool programs directly.

This deadlock you mention, can you provide more info?

It's no longer relevant.
ckpool deadlocks talking to ckdb, he doesn't test his changes with ckdb ... i.e. Bitmain pays him to break ckdb ... often.
... and he doesn't even test the effects of his changes on all the other ckpool modules Tongue