After several reconnections the api crashes and don't work anymore. Can you add a trigger like a key stroke to reload the api server?
Could you pls describe this in more detail? How do you access the telemetry data? What is actually not working. If there is a bug the proper way is to fix it, not providing a restart key.
I run zm on Windows 10 1709 (great work by the way) with telemtry on port 2709 and i constantly monitor it via web browser (i also made a little C# app to query over json-rpc).
Currently i have issues with my broadband connection dropping several times a day and my ISP have me scheduled for a visit after several support calls. That being said, zm works fine, up time reaches over days but conn time resets every time my modem restarts the connection with my ISP, still telemetry works fine when connection is restored, but after about 2 days of this dropped connections the telemtry just stops working via web browser or my c# app. I ran this tests on the rig itself, even telnet cant open a connection. I "know" i has to be the connection issue but when the telemtry dies i have to log in to the rig and restart zm. Definitely not a deal breaker but maybe i just have to live with it while my ISP fix my line.
Thx for the description, I'll try to reproduce this, it sounds like a bug in zm.
I already wrote in this topic about the problem. So can confirm it. I have 2 rigs. Both of them has the problem with the telemetry server (dstm v0.5.6 and v.0.5.7 tested). It becomes unavailable after 5-10 successful connections. If I start miner and do not try to connect to the server even couple days, and after that I do 5-10 successful connections, it becomes unavailable. If I try to connect (5-10 times) just after 5 minutes after the miner started, it becomes unavailable too until I'll restart it. I hope you'll understand what I mean, despite my bad eng.
Post
Topic
BoardMining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs
v3.0.0 doesn't work for me. It appears to successfully connect to luckpool.org, receive a difficulty value from the server, and then says "Miner died, restarting"; repeat, ad nauseum. This is a Win7 x64 SP1 machine with (2) GTX 1060 3GB cards. DSTM 0.5.6 and 0.5.7 work fine (indeed, 0.5.7 is running now) on the same pool with the same credentials.
At this point I am done screwing around with this train wreck, as I am philosophically opposed to paying for the "privilege" of being a beta tester.
What is your MoBo and CPU? I have the same problem. Two identical rigs on the old 775 socket. But first rig with quad-core CPU core2quad Q8400 (bminer works excellent, about week uptime without errors). The second rig with the same mobo, same GPU's and dual-core CPU core2duo E6750 says "Miner died, restarting" too. On the same time DSTM 0.5.6 and 0.5.7 work fine on this E6750 rig.
Telemetry server becomes unavailable after couple hours. Any solution? Miner ver. 0.5.7. OS: Win 7 x64.
Post
Topic
BoardMining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs
by
TONY_GUN
on 18/12/2017, 20:14:58 UTC
First at all - thanks for excellent miner! I have best results with it. But I have some problem. I have 2 rigs on the old 775 socket with identical ASUS P5K Premium MoBos. First rig has 4 gtx 1060 and core2quad q8400 cpu. Bminer works like a charm on this rig. (2,5 - 3 % cpu load and about 1300 sol/s). But the second rig with 2 gtx 1060 and core2duo E6750 cpu fails to run bminer. At the same time DSTM's miner works good with this E6750 cpu. I've made a commandline screenshot of the error. http://images2.imagebam.com/e3/96/06/9368a5692349993.png
