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

Just explain how do you expect "a good programmer" to differentiate server outage from smart-ass adding "127.0.0.1 www.devfeeserver.com" to his hosts file. That's close to impossible from software level.

Realistically, how do you expect this to happen. Even IF ZM had fail-over logic baked in, a lot of pools are down currently, not just flypool. Chances are fail-over server would be down as well. And if you remove this kind of logic from miner all together (shutting down when cannot connect to devfee serv), then any smart-ass can just host-disable devfee shares. GG

Stop this gibberish nonsense already.

I think what he means is that when telemetry fails to start due to whatever reason, miner won't start either. I noticed that as well, for me though it wasn't a problem.

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

CPU load is between 30-40 usually so I guess it's fine.

Concerning the card that yields less Sols, I think it's cuz it's the first one, and it has something to do with Xorg running on it. At least on W10 it behaved the same when I had my monitor connected to it, instead of Intel gpu. Quite a few people complained about the same issue always being with the first card.

Also I noticed that after some time I start getting
msg buffer full
Why is that, is it hurting me somehow?

Also after sorting out overclocking stuff I'm getting this annoying bug that 1 card doesn't get loaded properly (had it with ewfb's under w10 too occasionally).

   GPU0 61°C  Sol/s: 421.3  Sol/W: 3.98  Avg: 417.0  I/s: 227.2  Sh/s: 0.031  +
   GPU1 66°C  Sol/s: 446.8  Sol/W: 3.52  Avg: 439.3  I/s: 235.0  Sh/s: 0.015
   GPU2 64°C  Sol/s: 438.2  Sol/W: 3.52  Avg: 438.6  I/s: 234.8  Sh/s: 0.046
   GPU3 62°C  Sol/s: 305.1  Sol/W: 2.83  Avg: 310.7  I/s: 165.6  Sh/s: 0.015  +
   GPU4 62°C  Sol/s: 314.8  Sol/W: 2.85  Avg: 311.4  I/s: 165.8  Sh/s: 0.038  +
   GPU5 64°C  Sol/s: 492.7  Sol/W: 4.55  Avg: 488.9  I/s: 260.5  Sh/s: 0.038
   ========== Sol/s: 2418.9 Sol/W: 3.54  Avg: 2405.9 I/s: 1289.0 Sh/s: 0.185

Where GPU0 and GPU5 are both identical EVGA 1080 FTW

nvidia-smi also shows gpu utilization of 87% on that card. Anything I can do?

Fri Oct  6 13:32:21 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.90                 Driver Version: 384.90                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070    On   | 00000000:01:00.0  On |                  N/A |
| 30%   63C    P2   122W / 125W |    569MiB /  8113MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070    On   | 00000000:02:00.0  On |                  N/A |
| 24%   62C    P2   123W / 125W |    528MiB /  8114MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  On   | 00000000:04:00.0  On |                  N/A |
| 27%   59C    P2   110W / 120W |    506MiB /  6072MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  On   | 00000000:05:00.0  On |                  N/A |
| 28%   60C    P2   110W / 120W |    506MiB /  6072MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   4  GeForce GTX 1080    On   | 00000000:06:00.0  On |                  N/A |
| 18%   58C    P2    89W / 108W |    555MiB /  8114MiB |     84%      Default |
+-------------------------------+----------------------+----------------------+
|   5  GeForce GTX 1080    On   | 00000000:07:00.0  On |                  N/A |
| 23%   60C    P2   107W / 108W |    555MiB /  8114MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0       992      G   /usr/lib/xorg/Xorg                            33MiB |
|    0      1752      G   compiz                                        13MiB |
|    0      2307      C   /home/leo/mining_soft/zm/zm                  509MiB |
|    1       992      G   /usr/lib/xorg/Xorg                             7MiB |
|    1      2307      C   /home/leo/mining_soft/zm/zm                  509MiB |
|    2       992      G   /usr/lib/xorg/Xorg                             7MiB |
|    2      2307      C   /home/leo/mining_soft/zm/zm                  487MiB |
|    3       992      G   /usr/lib/xorg/Xorg                             7MiB |
|    3      2307      C   /home/leo/mining_soft/zm/zm                  487MiB |
|    4       992      G   /usr/lib/xorg/Xorg                             7MiB |
|    4      2307      C   /home/leo/mining_soft/zm/zm                  535MiB |
|    5       992      G   /usr/lib/xorg/Xorg                             7MiB |
|    5      2307      C   /home/leo/mining_soft/zm/zm                  535MiB |
+-----------------------------------------------------------------------------+

So far I've been using this settings:

nvidia-smi -pm 1
nvidia-smi -i 0 -pl 125
nvidia-smi -i 1 -pl 125
nvidia-smi -i 4 -pl 108
nvidia-smi -i 5 -pl 108
nvidia-smi -i 2 -pl 120
nvidia-smi -i 3 -pl 120

and

sudo nvidia-settings -a "[gpu:0]/GPUGraphicsClockOffset[3]=100" -a "[gpu:0]/GPUMemoryTransferRateOffset[3]=0"
sudo nvidia-settings -a "[gpu:1]/GPUGraphicsClockOffset[3]=100" -a "[gpu:1]/GPUMemoryTransferRateOffset[3]=0"
sudo nvidia-settings -a "[gpu:2]/GPUGraphicsClockOffset[3]=100" -a "[gpu:2]/GPUMemoryTransferRateOffset[3]=0"
sudo nvidia-settings -a "[gpu:3]/GPUGraphicsClockOffset[3]=100" -a "[gpu:3]/GPUMemoryTransferRateOffset[3]=0"
sudo nvidia-settings -a "[gpu:4]/GPUGraphicsClockOffset[3]=100" -a "[gpu:4]/GPUMemoryTransferRateOffset[3]=0"
sudo nvidia-settings -a "[gpu:5]/GPUGraphicsClockOffset[3]=100" -a "[gpu:5]/GPUMemoryTransferRateOffset[3]=0"

For me your miner is way more stable than ewfb's. While ewfb's simply hangs in 24-48hrs period on Windows and even sooner under Ubuntu, yours working stable. If only I could figure out how to overclock under Linux on a headless rig...

EDIT: However, It disconnected today twice. Once it just said server disconnected (i'm using nanopool) and failed to restore the connection, despite internet was working flawelessly on all other devices in a household. Restart of the miner itself immediately fixed the issue. And the second time it started throwing some connection errors, and again everything else worked like a charm. Restart fixed it as well.

Mate, you have out transactions in ur account. How do you do them if you don't any ETC on poloniex listed?

Same thing is happening to me right now. Sent 1.003 ETC, poloniex shows my balance as zero. Then sent another 0.1 ETC just to be sure I'm above min deposit value, and despite gastracker.io shows my balance just fine being 1.1011 ether, poloniex still shows zero. It now has been 4 days 6 hours as my ticket being processed...

https://gastracker.io/addr/0x4231ca8b8de5df4cdbc68174359f186d522d3964

Both transactions are way above 20000 confirmations right now.

These one were test ones, I'm just happy I haven't sent more, thought I still want my 20 bucks back =P.