Kristof here?

[Steve Sokolowski]

Kristof,

If you're here, could you try your messed up KNC miner against the pool for a minute or two, and see what its hashrate is? It's possible that some issues with Cryptsy were responsible for the losses we were having earlier, and I want to see if perhaps the pool's code itself isn't responsible at all.

[cryptorific]

As of 2:17 It's on the pool but bfgminer is giving me:

Code: Select all

[2014-10-29 18:18:29] Stratum connection to pool 0 interrupted
 [2014-10-29 18:18:29] Pool 0 http://prohashing.com:3333 not responding!
 [2014-10-29 18:18:30] Stratum connection to pool 0 interrupted
 [2014-10-29 18:18:30] Pool 0 http://prohashing.com:3333 not responding!
 [2014-10-29 18:18:31] Stratum connection to pool 0 interrupted
 [2014-10-29 18:18:31] Pool 0 http://prohashing.com:3333 not responding!

[Steve Sokolowski]

Thanks for the tip. I wonder if there is something on the server that is disconnecting miners, like bandwidth saturation or another process.

I'll look into the issue and get back to you.

[Chris Sokolowski]

I've experienced this issue with our miners, so I don't think we need Kristof to troubleshoot this issue right now since we can replicate it on our own.

If you look at the status of the miner connected through the Raspberry Pi, it occasionally generates those pool not responding errors, although they are intermixed with the accepted shares. If you look at the miner connected to the Windows server running CGminer 3.1.1, it never has the pool not responding error unless the pool is actually offline. I am not sure if the issue is also occurring on the Windows server and CGminer does not display it or if the software on the Raspberry Pi is at fault and we need to work around it. What's unusual is that even with the disconnects, both miners generate the same hashrate.

[cryptorific]

Simply applying "stratum+tcp://" will get it to connect however it doesn't last for long and then goes into the above loop of output. I don't think it matters either way.

[Steve Sokolowski]

Could you try again, but this time, use d=65536 as your password?

I wonder if these huge hashrate miners are submitting so many shares that, when a new block occurs on the networks, the shares are all rejected and the system bans the miner thinking that it is an attack.

I'm going to increase the ban threshold at the same time, and let's see what happens.

[cryptorific]

It does connect and start mining with d=65536 but the flushing issue is apparent (9 seconds for a full flush!):

Code: Select all

 [2014-10-30 04:31:55] KNC 0[1-0] Flushing stale works (New work)
 [2014-10-30 04:31:55] KNC 0[1-1] Flushing stale works (New work)
 [2014-10-30 04:31:56] KNC 0[1-2] Flushing stale works (New work)
 [2014-10-30 04:31:56] KNC 0[1-3] Flushing stale works (New work)
 [2014-10-30 04:31:57] KNC 1akk[2:0:270]: Got nonce for unknown work in slot 8
 [2014-10-30 04:31:57] KNC 1[2-0] Flushing stale works (New work)
 [2014-10-30 04:31:57] KNC 1[2-1] Flushing stale works (New work)
 [2014-10-30 04:31:58] KNC 1[2-2] Flushing stale works (New work)
 [2014-10-30 04:31:59] KNC 1[2-3] Flushing stale works (New work)
 [2014-10-30 04:31:59] KNC 2akl[4:0:271]: Got nonce for unknown work in slot 8
 [2014-10-30 04:31:59] KNC 2[4-0] Flushing stale works (New work)
 [2014-10-30 04:32:00] KNC 2[4-1] Flushing stale works (New work)
 [2014-10-30 04:32:00] KNC 2[4-2] Flushing stale works (New work)
 [2014-10-30 04:32:01] KNC 2czd[4:3:292]: Got nonce for unknown work in slot 8
 [2014-10-30 04:32:01] KNC 2[4-3] Flushing stale works (New work)
 [2014-10-30 04:32:02] KNC 3[5-0] Flushing stale works (New work)
 [2014-10-30 04:32:02] KNC 3[5-1] Flushing stale works (New work)
 [2014-10-30 04:32:03] KNC 3[5-2] Flushing stale works (New work)
 [2014-10-30 04:32:04] KNC 3[5-3] Flushing stale works (New work)
 [2014-10-30 04:32:05] Accepted 00007d22 KNC 0bkx pool 0 Diff 2/1
 [2014-10-30 04:32:05] KNC 0ccg[1:2:268]: Got nonce for unknown work in slot 10
 [2014-10-30 04:32:08] KNC 2alf[4:0:291]: Got nonce for unknown work in slot 10
 [2014-10-30 04:32:09] KNC 2cnz[4:3:2]: Got nonce for unknown work in slot 10
 [2014-10-30 04:32:09] Accepted 00001a35 KNC 2crk pool 0 Diff 9/1

As well as messages like:

Code: Select all

[2014-10-30 04:35:23] Rejected 000063df KNC 2bzh pool 0 Diff 2/1 (Share is above target of 655)

and

Code: Select all

[2014-10-30 04:36:17] Pool 0 is issuing work for an old block: 7a21ed677165dd57518918253f50401388fa9b6de897d6b67acda4c4fcae9b44

Overall the rejects are above 60% and bfg reports a hashrate of 130MH vs 260MH on an ltc pool. Might I suggest you try to get in touch with KNC since they seem somewhat willing to work with mining pools to get their miners working. If you can get titans working well you'll see a huge bump in hashrate i'm sure.