Quote from: Zirillian on May 07, 2018, 01:55:16 AM

Quote from: HashAuger on May 06, 2018, 11:52:14 PM

Quote from: Zirillian on May 06, 2018, 04:40:33 PM

2) Just downloaded 1.8.6 this morning. Some time after benchmarking the new ccminer-phi and nanashi algos, I got a message saying that both algorithms cannot communicate with ahashpool while trying to mine lyra2v2, and would stop mining with those miners. Looking at the benchmarks now, it seems those miners benched higher than tpruvot and thus won out. Not sure what the issue here is, but say it's a fix on your end...does HA go back and try using those miners again at some other time to see if the issue is fixed, or do I need to manually rebenchmark at some point?

Here's a follow-up on this issue after some testing. The error messages were not as clear as they could have been and made it seem that the problem was with the miner and not the pool. It was probably just a coincidence that the error occurred with these two new miners based on that they both tend to benchmark pretty high with Lyra2v2. I have been mining on AHashPool with both miners and haven't had an issue yet. Basically this situation happens in response to a stratum connection failed. Unfortunately, the current settings might be a little too aggressive at responding to this type of error. I'm going to adjust the error messages and increase the tolerance a bit to better handle brief interruptions in connectivity. As I noted before, the software will automatically resume using an algorithm or pool suspended due to a communication error an hour after the most recent error occurred.

Yeah it definitely looked like a pool error and not a miner error...probably just coincidence but thought I'd mention since I had never seen before and coincidentally had very recently turned on the two new miners.

I totally understand; the timing was very suspect. I'm glad you asked about it because it gave me some extra motivation to clarify those error messages and put a little more tolerance into handling these types of connectivity errors. The changes will be in the next release, which will most likely be in a few days as 1.8.7.