Quote from: jstefanop on January 15, 2019, 10:32:53 PM

Quote from: crypto_curious on January 14, 2019, 10:39:30 PM

Quote from: stef942 on January 14, 2019, 09:57:54 PM

try to run only MMR, no failover

Spot on, mate. It worked Shocked

https://imgur.com/a/W2MKbxC

At least for now. Dashboard show status as "unknown", but Apollo continues to mine there. Thanks!

Yea the issue is how bfgminer handles failovers. Currently it assumes that everything its mining is the same coin (this is based from bfgminers original bitcoin origins, it was never designed to handle multiple coins of the same algorithm).

This gets pronounced when your on a multipoool, then have failover/donation configured to Litecoin. This ASIC is different from the Moonlanders and uses a midstate, so the midstate of one coin is injected into another and stuff gets confused.

Sadly bfgminer is starting to show its age, ill see if there is a short term fix, but for now if your on mutipool/rental pool make sure thats the only pool configured.

I had the exact same issue, MRR as first pool, Litecoinpool as 2nd.

Rig was rented, problems with renters pool, Apollo swapped over to 2nd pool, but never swapped back. Ended up removing 2nd pool, and just having MRR (now need to keep eye on email notifications)