|
dstm (OP)
|
 |
November 13, 2017, 08:18:45 AM |
|
The server closes the connection periodically - even if I'm using a single connection to it.
You might see it more often on zm since it uses multiple connections, however you should also see similar behavior on other mining software.
luckpool.org
ZEN mining SAME PROBLEM.
Even on single 1060 card. Something wrong with mining ZEN.
Could you check please?
I did a short test (about 30min) luckpool had a stable connection during this test. Look at balkeep's reply: https://bitcointalk.org/index.php?topic=2021765.msg24366043#msg24366043 He's mining ZEN for about 20h - there is not a single disconnect for him. |
|
|
|
|
|
|
|
|
|
|
|
In order to achieve higher forum ranks, you need both activity points and merit points.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
Coin++
|
|
November 13, 2017, 08:33:15 AM |
|
Hi all,
Can you please remember me what are the two last numbers in each line of the miner display when mining with the last version 0.5.4 ?
Thank you.
|
|
|
|
|
dstm (OP)
|
|
November 13, 2017, 08:54:40 AM |
|
Hi all,
Can you please remember me what are the two last numbers in each line of the miner display when mining with the last version 0.5.4 ?
Thank you.
The README file contains a description for it: Sh : <shares per minute> <accepted shares ratio> <network latency in ms> |
|
|
|
|
|
Coin++
|
|
November 13, 2017, 09:11:01 AM |
|
Hi all,
Can you please remember me what are the two last numbers in each line of the miner display when mining with the last version 0.5.4 ?
Thank you.
The README file contains a description for it: Sh : <shares per minute> <accepted shares ratio> <network latency in ms> Thank you for the reply and explanation. .. and sorry to not thinking about the readme file : I only look at the OP. Have a nice day :-). |
|
|
|
|
crocozino
|
|
November 13, 2017, 11:03:54 AM |
|
Does anyone else have a problem where miner just shuts down, no error no nothing, just closes ?
yes, can confirm that! worst part of it, it is not showing any error! and only by dropping temps in Afterburner I can see that there is a problem would be so much better, if miner exits - then in but file will be executed goto loop command and all will be good again! |
|
|
|
|
|
|
|
dstm (OP)
|
|
November 13, 2017, 12:29:49 PM |
|
Hi all,
Can you please remember me what are the two last numbers in each line of the miner display when mining with the last version 0.5.4 ?
Thank you.
The README file contains a description for it: Sh : <shares per minute> <accepted shares ratio> <network latency in ms> Thank you for the reply and explanation. .. and sorry to not thinking about the readme file : I only look at the OP. Have a nice day :-). Thx for reporting, I've updated the OP. |
|
|
|
|
|
dstm (OP)
|
|
November 13, 2017, 12:30:28 PM |
|
Please provide API to working with Awesome miner , Thank you very much
ZM reports stats via json-rpc. It's described in json-rpc.txt. |
|
|
|
|
|
dstm (OP)
|
|
November 13, 2017, 12:31:51 PM |
|
Does anyone else have a problem where miner just shuts down, no error no nothing, just closes ?
yes, can confirm that! worst part of it, it is not showing any error! and only by dropping temps in Afterburner I can see that there is a problem would be so much better, if miner exits - then in but file will be executed goto loop command and all will be good again! I guess you're on windows. This is how batch files work on windows if you launch them by double clicking. The window closes on termination of last command. You might add 'pause' as the last command in your batch file. This way you should be able to see the error message. |
|
|
|
|
Trololino
Newbie
 Offline
Activity: 17
Merit: 0
|
|
November 13, 2017, 02:08:21 PM |
|
Does anyone else have a problem where miner just shuts down, no error no nothing, just closes ?
There were problems with the ZCash network recently, while the EWBF's CUDA Zcash miner lost connect with the pool, but it continued to work, reporting a connection error, and dstm's miner was unexpectedly closed. After the pool started working again, EWBF continued to work, and dstm no, because closed before. It's need to make dstm's miner didn't finish work, when the connection is lost. Thx, this was reported multiple times - I'm working on it. If its any help, it happened on my 4 x 1080 rig (regulars non ti), works perfectly on my 1070 and 1060 rigs. |
|
|
|
|
|
lolchina
|
|
November 14, 2017, 02:07:27 AM |
|
zm --dev --server ssl://zec.suprnova.cc --port 2242 --user yourusername.yourworkername --pass x --time thx man  |
|
|
|
|
gurupool
Newbie
Offline
Activity: 49
Merit: 0
|
|
November 14, 2017, 02:21:37 AM |
|
DSTM is tested on our Bitcoin Gold Mining Pool: https://gpool.guru. Have fun! |
|
|
|
|
Veladrin
Newbie
Offline
Activity: 5
Merit: 0
|
|
November 14, 2017, 03:02:16 AM |
|
@dstm - Didn't see this reported, apologies if it was. I think I found a small reporting bug with the server and logging info. It's a super edge case but I don't know the implications as it seems to retain application start values. The use case was that the miner started before the power setting init ran, and after the power settings changed (see https://imgur.com/a/OziUT), zm seems to misreport power stats (see https://imgur.com/a/rE2KF). This could be corrected after restarting zm (see https://imgur.com/a/GN9uV) This system is running on ubuntu desktop 16.04.3, nvidia-smi v384.98, miner version 0.5.4. I can run through the logs too but they show the same info. I realize I should've included the server timestamps for reference, but they're within minutes of each other in the above order. |
|
|
|
|
|
dstm (OP)
|
|
November 14, 2017, 03:17:02 AM |
|
@dstm - Didn't see this reported, apologies if it was. I think I found a small reporting bug with the server and logging info. It's a super edge case but I don't know the implications as it seems to retain application start values. The use case was that the miner started before the power setting init ran, and after the power settings changed (see  ), zm seems to misreport power stats (see  ). This could be corrected after restarting zm (see  ) This system is running on ubuntu desktop 16.04.3, nvidia-smi v384.98, miner version 0.5.4. I can run through the logs too but they show the same info. I realize I should've included the server timestamps for reference, but they're within minutes of each other in the above order. ZM reports averages for power consumption and efficiency - since that's the most accurate way. So it reports correctly the average power consumption of your system. It will converge after some time. |
|
|
|
|
Veladrin
Newbie
Offline
Activity: 5
Merit: 0
|
|
November 14, 2017, 03:43:27 AM |
|
@dstm - Didn't see this reported, apologies if it was. I think I found a small reporting bug with the server and logging info. It's a super edge case but I don't know the implications as it seems to retain application start values. The use case was that the miner started before the power setting init ran, and after the power settings changed (see https://imgur.com/a/OziUT), zm seems to misreport power stats (see https://imgur.com/a/rE2KF). This could be corrected after restarting zm (see https://imgur.com/a/GN9uV) This system is running on ubuntu desktop 16.04.3, nvidia-smi v384.98, miner version 0.5.4. I can run through the logs too but they show the same info. I realize I should've included the server timestamps for reference, but they're within minutes of each other in the above order. ZM reports averages for power consumption and efficiency - since that's the most accurate way. So it reports correctly the average power consumption of your system. It will converge after some time. Ah, I thought it was sampled live stats rather than averages, that wasn't clear to me. I actually analyzed logs a few days ago and noted the lack of variance for zm, that puts it into perspective ! edit: I also should've paid more attention to the first post's description on logs ^^ |
|
|
|
|
|
crazydane
|
|
November 14, 2017, 12:53:16 PM |
|
@dstm - Any plans to fix the issue with DSTM not being able to report WATT (and therefore SOL/W) for 1050Ti GPUs? See below:  Thanks! |
|
|
|
|
Ivars1970
Newbie
Offline
Activity: 1
Merit: 0
|
|
November 14, 2017, 02:36:28 PM
Last edit: November 14, 2017, 03:25:22 PM by Ivars1970 |
|
I think it's not a dstm's, it's a NVIDIA driver, after 385.69 I have same problem in ewfb 0.34b.
|
|
|
|
|
|
crazydane
|
|
November 14, 2017, 03:21:38 PM |
|
Ah ok, thanks.
|
|
|
|
|
harut
Newbie
Offline
Activity: 6
Merit: 0
|
|
November 14, 2017, 05:01:30 PM |
|
Hi
How can I get json stats?
I only get http.
|
|
|
|
|
|
dstm (OP)
|
|
November 14, 2017, 05:31:12 PM |
|
@dstm - Any plans to fix the issue with DSTM not being able to report WATT (and therefore SOL/W) for 1050Ti GPUs?
Thanks!
Does nvidia-smi report power usage properly? Btw. that a nice usage of frames to have multiple rigs on one page. I was also thinking to provide a html template for something similar. |
|
|
|
|
|
