I believe I have identified the issue with sha256 miners on this pool.

My sha256 miners have been repeatedly crashing on this pool, obviously I don't want that but I like zpool so I'm hoping I can help fix this if need be   I've been dev'ing since the 80s so if I can lend a hand in that way, please let me know.

Forgive me for stinking at formatting, if there's something I can do to make what's coming more readable, again please let me know.
                                 "comments shortened"
This happens very consistently on both my Antminers and Spondoolies.

They're all running cgminer4.8.0 so the log output is nearly identical for all of them.

This would account for what some of the posts in this thread are saying about the slowly reducing hashrate reported by the zpool website that results in 0 hash.

What is the problem?

Well I would have to look at the zpool logs to identify the problem as this is expected behavior from cgminer but since that is unlikely I'll take a stab, it's likely:

When the algo switches coins, one or more of the coins is not sending proper (or empty, or headlerless) packets or NULLs to the miners, which the sha256 miners and cgminer read as empty/garbage, leading to the miner eventually dying. The pool software is not switching to a new coin at that point because it is not receiving the expected output from the miners either, leading it to attempt to resend the same packet over and over as the msg the miner is sending is telling the pool that it didn't receive the packet (hence the timeout), leading to an infinite loop or at least a failing one.


My suggestion:

Do a (relatively) quick look at the logs for the sha256 coins and see which ones have not created any blocks on this pool and remove them, or, trim the sha256 coins down to the only ones with a regular hashrate on the site. It's likely one of the non-producing coins that is causing the issue.

If there's anything I can do to help, please let me know- I love using zpool