Author

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

full member
Activity: 350
Merit: 126
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://bitcointalksearch.org/topic/m.24366043                                                       

He's mining ZEN for about 20h - there is not a single disconnect for him.
full member
Activity: 350
Merit: 126
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.
newbie
Activity: 176
Merit: 0
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?
full member
Activity: 308
Merit: 110
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.
newbie
Activity: 16
Merit: 0
Quote
zm --dev --server  ssl://zec.suprnova.cc --port 2242 --user yourusername.yourworkername --pass x --time
full member
Activity: 294
Merit: 103
can someone pls show example of bat config for suprnova pool,have problem typing the right stuff for it
member
Activity: 153
Merit: 10
In Decentralization We Trust
Does anyone else have a problem where miner just shuts down, no error no nothing, just closes ?
type "pause" in the end of .bat file and you will see error messages or add --logfile
newbie
Activity: 2
Merit: 0
Hi,

Does anyone get a different checksum than what is specified in OP?

for the linux version 0.5.4 I get sha1 c235e56830aab5f57b4a9bdffbfbd60a08951b02
and in OP it says it's suppose to be sha1 02816754ab46191109bed9f89f17c073000b0950

UPDATE:
Nevermind, I checked the checksum of the tar file.
sr. member
Activity: 471
Merit: 250
Does anyone else have a problem where miner just shuts down, no error no nothing, just closes ?

Yes I get that from time to time on Windows 10 ... it's down to overclocking usually. I lower core and memory clocks by 5 and restart. If the problem doesn't repeat itself then I have a stable rig, otherwise I lower again until it is.

Sometimes I'll increase the TDP as well.

... it's all about tuning your rig for the best watt/hash performance.

newbie
Activity: 17
Merit: 0
Does anyone else have a problem where miner just shuts down, no error no nothing, just closes ?
full member
Activity: 350
Merit: 126
Hey DSTM. Do not worry about the bug of this week about the fees. We are 100% behind you.
Thx for supporting me - including all the people with their previous post. I'm not happy about the failure ofc but the current dev branch contains a solution to this already.

Quote
For us, this problem shows more a BIG centralizing trouble on Flypool. Amazing that all goes to 1 pool without worrying about the consequences.
Right, this a valid point. POW based cryptocurrencies are vulnerable to 51% attacks - decentralization is crucial to them and may affect their acceptance. Reward variance is larger for smaller pools ofc - however expected reward values are equal (if there are no other differences) - so this is not a disadvantage in general.

Quote
We suggest you apply your fees on ALL pools. Randomly.
This is the most optimal solution. However there are some constraints regarding the pool quality. Current dev branch has all the needed functionality for this - so it's easy to add new pools.
full member
Activity: 350
Merit: 126
is this miner capable of pointing each gpu to different pools?

ZM has no support for this currently - however zm is capable of this due to it's design. If there is demand for this I'll add it. I'm not sure if the additional (configuration) complexity is worth it. Something similar is achievable by using the '--dev' option + starting multiply zm processes.
newbie
Activity: 49
Merit: 0
Hey DSTM. Do not worry about the bug of this week about the fees. We are 100% behind you. For us, this problem shows more a BIG centralizing trouble on Flypool. Amazing that all goes to 1 pool without worrying about the consequences.

We suggest you apply your fees on ALL pools. Randomly.

Don't forget to try our new Zcash Pool: https://zpool.guru
Bitcointalk thread: https://bitcointalksearch.org/topic/zpoolguru-zcash-pool-v152-2262047

And we will publish a testnet pool next week. This can be usefull in some dev cases.
member
Activity: 99
Merit: 10
is this miner capable of pointing each gpu to different pools?
hero member
Activity: 710
Merit: 502
I dont understand how you can have 8 hours downtime ( from the miner point of view )
When this network failed happened i got notification from flypool and from my watchdog, i investigated, took me 10 minutes to switch back all my rigs on ewbf and to change the server from europe to asia.
In that day i made more coins then usual because a lot of miners didnt react to flypool europe server failure and the difficulty dropped.
The next day i switched back to dstm's miner.

If you mine and want uptime USE WATCHDOGS  SCRIPTS dont blame this on the mining software.


I do have watchdogs, but the process was not unloaded entirely, so the watchdog didn't see that.
I periodically check the miners, but this particular day i was in a plant dealing with a PLC from an automated extrusion machine that was acting up, and i didn't have the time to check, because i had the engineers discussing what could be the problem plus the management guys coming every 5 minutes to see if i was able to fix it so.... Grin like i said, unique scenario, normally i'll find out in a couple of hours tops.
Oh! on top of that my business parner (which he also check for my rigs, was on vacation)
perfect storm, you know....
Oh, did I mention this plant is in the middle of the country, with no LTE connection, only wifi from the plant, 1MB connection via radio which sucks, and also the wifi does not cover the entire plant so where i was working i had no data coverage at all, had to go to the office to get that 100 mts away.... so.... perfect storm +1  Grin
newbie
Activity: 39
Merit: 0
Problem while mining ZEN ON  https://zenmine.pro

eu.zenmine.pro:9009

Every 2 minutes conection closed by server r:0

Could you check please?

EWBS work on this server without problem, with dstm every ~2-4 minutes conection closed by server r:0

I'm able to reproduce this.
The server sends a TCP FIN packet i.e. closes the connection periodically.
Are you sure about your tests with other mining software?
I had the same problem using zm with pool.sexy but not every 2 min , i think more than 30
newbie
Activity: 9
Merit: 0
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.

Please FIX.

EWBF work fine.


uptime:     0 days  20:16:11
contime:     0 days  20:16:01
version:   zm 0.5.4
host:   Stacey
server:   zen.suprnova.cc:3618
user:   balkeep.Stacey
newbie
Activity: 176
Merit: 0
One from my rings on EWBF and he is work properly on this poll, without reconnect 2 hours in the time while dstm have a lot of reconnect.
I'm sure it was in the same time.

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.

Please FIX.

EWBF work fine.

The server sends a TCP FIN packet i.e. closes the connection periodically.
Could dstm miner ignore this packet ? continue mining ?

zm 0.5.4
full member
Activity: 350
Merit: 126
One from my rings on EWBF and he is work properly on this poll, without reconnect 2 hours in the time while dstm have a lot of reconnect.
I'm sure it was in the same time.

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.
newbie
Activity: 9
Merit: 0
I dont understand how you can have 8 hours downtime ( from the miner point of view )

Agree. At first I recieved a message from programmatic wathdog that connection is lost. Second - tryed to switch to another pool on dstm, had no luck. At third, I have a VNC Client on my phone, so when I saw that fypool in EU is down and dstm is unable to connect, I quickly switched EWBF to US server. It took me 10 mins to restore mining from my mobile phone, being in the ofiice at that time.
Jump to: