- bug fixes.
Can you confirm if it has any stability improvements on Linux regarding statistics socket? 4.4 had issues, 4.5 didn't have as I thought but there was a report of them here. Today I also found the issue of loosing socket by 4.5 on Linux. What about 4.6, were any changes done for it?
Since you twice ignored this question, I assume the answer is "No changes, Linux 4.6 telemetry still is unstable".
Due to reject issues with 4.6 and some pools I set back to 4.5. After running two rigs for ~45 hours both at the same time and same uptime had lost telemetry sockets, still running fine for mining. I am sending you links to both full logs in PM.
Last seen: 2016-06-25 06:40:45
Error: no response
Last seen: 2016-06-25 06:42:01
Any chances to have stable telemetry on Linux? Or should I finally write an own process monitor and restart miner when telemetry is lost?
I still cannot reproduce this issue. PM me, I can send you a debug version with more detailed log, it seems it's the only way to fix this problem.
Now I repeated the case. Again, both rigs started at the same time stopped responding at the same time. That is common, the uptime - it is around 45 hours. I think some timer overflows with that period.