[ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 133.

dstm

full member

Activity: 350

Merit: 126

Quote from: patinencomun on October 25, 2017, 12:40:46 AM

Hi dstm's developer,

I found a "bug", if telemetry fails at boot, for example when a power lose / power restore situation occurs, the miner won't start. System reboots on power fails, and miner start on boot, but for the router is not started yet...

Could you fix this?
Thank you.

I'm not sure I understand it correctly - could you pls explain this a bit more.

dstm

full member

Activity: 350

Merit: 126

Quote from: NameTaken on October 25, 2017, 12:04:24 AM

Quote from: dstm on October 24, 2017, 09:13:15 AM

Quote from: Elange on October 24, 2017, 08:42:13 AM

Hi.

Tried out your miner. It is, in fact, about 10% faster than EWBF. However, it has a nasty bug that forced me to go back to EWBF.

I mine ZEC on nanopool, recently they've had some service disruptions. So, if pool drops connection, EWBF simply tries to reconnect and succeeds finally, while dstm's ZM miner goes into "0 connection closed by server - reconnecting..." infinite loop, scrolling text very fast and never actually resumes mining.

Using Linux version under Ubuntu 16.04 LTS.

Thanks!

Thx for reporting, this is a know bug, NameTaken had similar issues.
It will be fixed in the next release - this path is unlikely to hit, zm 0.5.2 should reconnect properly in almost all cases.

Woke up today to find all my rigs had stopped working due to this.

Sry for this, I'll release 0.5.3 earlier than planed due to this - however it won't contain all the requested adjustments. I'm expecting to release it tomorrow.

jpl

member

Activity: 154

Merit: 11

Quote from: DevonMiner on October 19, 2017, 01:23:22 PM

Quote

how can you run 14 GTX cards with Windows 10 ?

I'm not, I'm running 14 rigs x5 cards each.

Holy fuckin shit.. really? wow. lol.. sorry.

patinencomun

jr. member

Activity: 76

Merit: 1

Hi dstm's developer,

I found a "bug", if telemetry fails at boot, for example when a power lose / power restore situation occurs, the miner won't start. System reboots on power fails, and miner start on boot, but for the router is not started yet...

Could you fix this?
Thank you.

NameTaken

hero member

Activity: 630

Merit: 502

Quote from: dstm on October 24, 2017, 09:13:15 AM

Quote from: Elange on October 24, 2017, 08:42:13 AM

Hi.

Tried out your miner. It is, in fact, about 10% faster than EWBF. However, it has a nasty bug that forced me to go back to EWBF.

I mine ZEC on nanopool, recently they've had some service disruptions. So, if pool drops connection, EWBF simply tries to reconnect and succeeds finally, while dstm's ZM miner goes into "0 connection closed by server - reconnecting..." infinite loop, scrolling text very fast and never actually resumes mining.

Using Linux version under Ubuntu 16.04 LTS.

Thanks!

Thx for reporting, this is a know bug, NameTaken had similar issues.
It will be fixed in the next release - this path is unlikely to hit, zm 0.5.2 should reconnect properly in almost all cases.

Woke up today to find all my rigs had stopped working due to this.

PL84

newbie

Activity: 27

Merit: 0

@dstm

I sent message you about implementing your miner to EthOS. Have a look and reply if you are interested about it.

dstm

full member

Activity: 350

Merit: 126

Quote from: sp_ on October 24, 2017, 02:25:36 PM

if you implement a accepted share count, and a rejected share count like other miners, it's easier to see wich of the workers that's just been restarted. Easier to troubleshoot

It's there, it's accessible via json-rpc or webui.
How do you monitor your workers? For large worker counts people usually use json-rpc.
Json-rpc will contain uptime and connection-time in the next release which is useful in this kind of situations.
If it's useful I'll output a/r shares also on terminal.

Quote

When a worker is restarted I loose hashrate.

Not sure if I understand this correctly. Do the GPUs perform slower after a restart?

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

if you implement a accepted share count, and a rejected share count like other miners, it's easier to see wich of the workers that's just been restarted. Easier to troubleshoot
When a worker is restarted I loose hashrate.

dstm

full member

Activity: 350

Merit: 126

Quote from: sp_ on October 24, 2017, 01:30:27 PM

Did a test with 60 workers. Unstable at first, but then I added a simple failover script and it seems to work..

What's failing?

dstm

full member

Activity: 350

Merit: 126

Quote from: chancefx on October 24, 2017, 10:46:16 AM

is there any --log command? don't find on first page

There is currently no logfile support. I'll ad it in one of the next releases.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: UrsaUrsa on October 24, 2017, 01:55:36 PM

I assume your workers are running Linux?

No

The test is conducted with the Version 0.5.2 exe file

UrsaUrsa

member

Activity: 104

Merit: 11

Quote from: sp_ on October 24, 2017, 01:30:27 PM

Did a test with 60 workers. Unstable at first, but then I added a simple failover script and it seems to work..

I assume your workers are running Linux?

balkeep

newbie

Activity: 9

Merit: 0

Quote from: laineux on October 24, 2017, 09:29:22 AM

Quote from: Elange on October 24, 2017, 08:42:13 AM

Hi.

Tried out your miner. It is, in fact, about 10% faster than EWBF. However, it has a nasty bug that forced me to go back to EWBF.

I mine ZEC on nanopool, recently they've had some service disruptions. So, if pool drops connection, EWBF simply tries to reconnect and succeeds finally, while dstm's ZM miner goes into "0 connection closed by server - reconnecting..." infinite loop, scrolling text very fast and never actually resumes mining.

Using Linux version under Ubuntu 16.04 LTS.

Thanks!

Hi,

I got the same problem with suprnova pool. I am using 0.5.2 on windows.
Infinite loop.

I just looked if I can had a list of pools but it seems impossible...

Yep, having the same problem with suprnova and ZEN on win10 ltsb x64 and 0.5.2 version. Have to restart manually, but when I do it reconnects instantly.

zm --server zen.suprnova.cc --port 3618 --user balkeep.Stacey --pass XXXX --telemetry=192.168.1.10:42000

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Did a test with 60 workers. Unstable at first, but then I added a simple failover script and it seems to work..

promomei

sr. member

Activity: 399

Merit: 254

make video set it up on youtube XD
will be nice Grin

Ill try it later with my 1060 farm-let you know guys

B00gieman

newbie

Activity: 65

Merit: 0

Hello.
Tested on 8x Gigabyte NVIDIA 1700 rig on W64.
Connected to Flypool.

460/470 sol's
1100w PowerDraw

Keep testing and waiting for BTG Wink

UrsaUrsa

member

Activity: 104

Merit: 11

Quote from: dstm on October 24, 2017, 09:39:52 AM

Quote from: laineux on October 24, 2017, 09:29:22 AM

Quote from: Elange on October 24, 2017, 08:42:13 AM

Hi.

Tried out your miner. It is, in fact, about 10% faster than EWBF. However, it has a nasty bug that forced me to go back to EWBF.

I mine ZEC on nanopool, recently they've had some service disruptions. So, if pool drops connection, EWBF simply tries to reconnect and succeeds finally, while dstm's ZM miner goes into "0 connection closed by server - reconnecting..." infinite loop, scrolling text very fast and never actually resumes mining.

Using Linux version under Ubuntu 16.04 LTS.

Thanks!

Hi,

I got the same problem with suprnova pool. I am using 0.5.2 on windows.
Infinite loop.

I just looked if I can had a list of pools but it seems impossible...

Could you pls post the suprnava server and port you're using, I'll test the current dev branch against it.

The one time my miner had disconnected it was the same and zm did not reconnect.

SpecialX

newbie

Activity: 3

Merit: 0

http://upimg.org/image.php?di=AO3R

chancefx

member

Activity: 153

Merit: 10

In Decentralization We Trust

Quote from: SpecialX on October 24, 2017, 11:14:22 AM

--telemetry=0.0.0.0:42000

It can not work

you need to edit 0.0.0.0 to you local rig address

crazydane

full member

Activity: 558

Merit: 194

Right, use the actual IP of the miner.

Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 133. (Read 224961 times)