Pages:
Author

Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 72. (Read 58981 times)

newbie
Activity: 157
Merit: 0
Hope it helpful for you and add --exit option (close miniZ when it crash)
Thanks
Hi topteam,
thanks for the logs, they were helpful. It should be fixed in the next version.
miniZ already exits when a crash happens. Could you clarify what you mean?
miniZ not exit when crash (just freeze) during ~2 minutes, after that my watchdog reboot the system
full member
Activity: 211
Merit: 100
Nice miner.

GTX 1060 3G - GMINER 1.10 - 1800 Core / 4100 Memory - 27~29 sol/s
GTX 1060 3G - MINIZ v1.0h - 1800 Core / 4100 Memory -  30~31 sol/s

GTX 1070 - GMINER 1.10 - 1700 Core / 4200 Memory - 47 sol/s
GTX 1070 - MINIZ v1.0h - 1700 Core / 4200 Memory - 50~51 sol/s
member
Activity: 679
Merit: 17
miner is still unstable for me at OC settings lower than those stable in gminer. i run my cards at 50-55% PL. im getting crashes every few hrs, sometimes less. OC settings are not high at all. sometimes runs for many hrs and sometimes few minutes
Hi fistsofgod,
we corrected a few bugs and it is now more stable. This should be fixed in the next version.

Hope it helpful for you and add --exit option (close miniZ when it crash)
Thanks
Hi topteam,
thanks for the logs, they were helpful. It should be fixed in the next version.
miniZ already exits when a crash happens. Could you clarify what you mean?

why big ping?
Hi rusian4040,
when the miner starts you see a higher latency time because of communication handshake, and because the average time window was too big. This will be corrected in the next version.


Thank you all for your feedback!
We are working to release a new version soon. 
member
Activity: 194
Merit: 10
newbie
Activity: 157
Merit: 0
this cuda error log doesnt mean anything to me. would be great to know which gpu caused error
also no error logged if file already exists
Hi fistsofgod,
It looks like that the GPU became unstable. Try to tweak the OC settings, they might need adjustment.
We'll include the GPU in the error in the next version.
miniZ appends error to existing file. Could you check again?
Thank you!


crash after day of working
Code:
139944018290312:error:1409F07F:SSL routines:ssl3_write_pending:bad write retry:s3_pkt.c:1097:
what means this percents (98.0%) (2.0%)?
Hi topteam,
that error doesn't happen often and it is difficult to reproduce, but we think we got it already and should be fixed in the next version.
As fistsofgod said those percent values refer to the mining times (you vs fee). https://miniz.ch/usage/
Thanks!
After 20 hours Sad crash
Code:
[ 0d19h36m13s] S:14005/4 713(720) [fee.server]- 80ms (98.0%) (2.0%)
0>GTX 1070       [54°C/55%] 26.91 I/s 53.4(54.1) Sol/s 135.6W clk=1809MHz mclk=4452MHz Sol/W=0.40
1>GTX 1070       [46°C/55%] 27.34 I/s 53.9(54.9) Sol/s 135.4W clk=1847MHz mclk=4452MHz Sol/W=0.41
2>GTX 1070       [48°C/55%] 27.76 I/s 54.5(55.7) Sol/s 136.5W clk=1873MHz mclk=4452MHz Sol/W=0.41
3>GTX 1070       [45°C/55%] 27.44 I/s 54.5(55.2) Sol/s 134.2W clk=1898MHz mclk=4452MHz Sol/W=0.41
4>GTX 1070       [48°C/55%] 27.74 I/s 55.5(55.5) Sol/s 135.9W clk=1885MHz mclk=4452MHz Sol/W=0.41
kernel: [70890.120225] show_signal_msg: 18 callbacks suppressed
kernel: [70890.120228] miniZ[2545]: segfault at 1e8 ip 00005591ac481238 sp 00007fa63f7fd880 error 4 in miniZ[5591ac381000+8e6000]
5>GTX 1070 Ti    [41°C/55%] 31.98 I/s 63.5(64.3) Sol/s 136.3W clk=1847MHz mclk=4452MHz Sol/W=0.47
6>GTX 1070 Ti    [43°C/55%] 31.90 I/s 64.0(64.3) Sol/s 136.5W clk=1835MHz mclk=4452MHz Sol/W=0.47
7>GTX 1070 Ti    [49°C/55%] 31.48 I/s 63.0(63.1) Sol/s 135.8W clk=1784MHz mclk=4452MHz Sol/W=0.46
8>GTX 1070 Ti    [46°C/55%] 31.63 I/s 63.6(63.5) Sol/s 134.7W clk=1784MHz mclk=4452MHz Sol/W=0.47
9>GTX 1070 Ti    [47°C/55%] 31.82 I/s 64.0(63.9) Sol/s 135.4W clk=1822MHz mclk=4452MHz Sol/W=0.47
10>GTX 1070 Ti    [49°C/55%] 31.03 I/s 60.8(62.1) Sol/s 135.7W clk=1746MHz mclk=4452MHz Sol/W=0.46
11>GTX 1070 Ti    [45°C/55%] 31.39 I/s 62.3(63.1) Sol/s 134.5W clk=1797MHz mclk=4452MHz Sol/W=0.47
[ 0d19h36m23s] S:14006/4 713(720) [europe.equihash-hub.miningpoolhub.com]- 264ms (98.0%) (2.0%)
0>GTX 1070       [54°C/55%] 26.92 I/s 53.6(54.1) Sol/s 135.6W clk=1822MHz mclk=4452MHz Sol/W=0.40
1>GTX 1070       [46°C/55%] 27.37 I/s 53.8(54.9) Sol/s 135.4W clk=1847MHz mclk=4452MHz Sol/W=0.41
2>GTX 1070       [48°C/55%] 27.77 I/s 54.6(55.7) Sol/s 136.8W clk=1898MHz mclk=4452MHz Sol/W=0.41
3>GTX 1070       [44°C/55%] 27.48 I/s 54.2(55.2) Sol/s 134.0W clk=1847MHz mclk=4452MHz Sol/W=0.41
4>GTX 1070       [48°C/55%] 27.75 I/s 55.5(55.5) Sol/s 135.9W clk=1873MHz mclk=4452MHz Sol/W=0.41
5>GTX 1070 Ti    [41°C/55%] 32.00 I/s 63.8(64.3) Sol/s 136.3W clk=1847MHz mclk=4452MHz Sol/W=0.47
6>GTX 1070 Ti    [43°C/55%] 31.92 I/s 64.0(64.3) Sol/s 136.5W clk=1835MHz mclk=4452MHz Sol/W=0.47
7>GTX 1070 Ti    [49°C/55%]*31.49 I/s 62.9(63.1) Sol/s 135.8W clk=1784MHz mclk=4452MHz Sol/W=0.46
8>GTX 1070 Ti    [46°C/55%] 31.63 I/s 63.5(63.5) Sol/s 134.7W clk=1784MHz mclk=4452MHz Sol/W=0.47
9>GTX 1070 Ti    [47°C/55%] 31.83 I/s 64.2(63.9) Sol/s 135.4W clk=1822MHz mclk=4452MHz Sol/W=0.47
10>GTX 1070 Ti    [49°C/55%] 31.03 I/s 60.7(62.1) Sol/s 135.7W clk=1746MHz mclk=4452MHz Sol/W=0.46
11>GTX 1070 Ti    [45°C/55%] 31.40 I/s 62.3(63.1) Sol/s 134.5W clk=1797MHz mclk=4452MHz Sol/W=0.47
systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks...
nvidia-persistenced: Received signal 15
Hope it helpful for you and add --exit option (close miniZ when it crash)
Thanks

and after one day
Code:
[ 1d 2h 6m39s] S:19083/5 720(719) [europe.equihash-hub.miningpoolhub.com]- 311ms (98.0%) (2.0%)
0>GTX 1070       [54°C/55%] 27.11 I/s 54.6(54.2) Sol/s 135.6W clk=1784MHz mclk=4452MHz Sol/W=0.40
1>GTX 1070       [48°C/55%] 27.48 I/s 54.7(54.8) Sol/s 133.7W clk=1847MHz mclk=4452MHz Sol/W=0.41
2>GTX 1070       [50°C/55%] 27.86 I/s 55.3(55.4) Sol/s 135.6W clk=1873MHz mclk=4452MHz Sol/W=0.41
3>GTX 1070       [46°C/55%] 27.61 I/s 55.0(55.0) Sol/s 135.3W clk=1885MHz mclk=4452MHz Sol/W=0.41
kernel: [94323.259974] show_signal_msg: 18 callbacks suppressed
kernel: [94323.259977] miniZ[2527]: segfault at 1e8 ip 000055765dd38238 sp 00007f4b11ffe880 error 4 in miniZ[55765dc38000+8e6000]
4>GTX 1070       [49°C/55%] 27.83 I/s 55.7(55.6) Sol/s 135.5W clk=1873MHz mclk=4452MHz Sol/W=0.41
5>GTX 1070 Ti    [43°C/55%] 32.16 I/s 64.0(64.2) Sol/s 135.8W clk=1873MHz mclk=4452MHz Sol/W=0.47
6>GTX 1070 Ti    [45°C/55%] 32.15 I/s 64.4(64.1) Sol/s 135.7W clk=1809MHz mclk=4452MHz Sol/W=0.47
7>GTX 1070 Ti    [51°C/55%] 31.56 I/s 63.8(63.2) Sol/s 135.2W clk=1771MHz mclk=4452MHz Sol/W=0.47
8>GTX 1070 Ti    [47°C/55%] 31.74 I/s 64.6(63.4) Sol/s 135.5W clk=1797MHz mclk=4452MHz Sol/W=0.47
9>GTX 1070 Ti    [49°C/55%] 31.96 I/s 63.9(63.8) Sol/s 135.1W clk=1822MHz mclk=4452MHz Sol/W=0.47
10>GTX 1070 Ti    [51°C/55%] 31.12 I/s 62.1(62.3) Sol/s 136.2W clk=1771MHz mclk=4452MHz Sol/W=0.46
11>GTX 1070 Ti    [46°C/55%] 31.53 I/s 62.4(62.9) Sol/s 136.9W clk=1809MHz mclk=4452MHz Sol/W=0.46
[ 1d 2h 6m49s] S:19090/5 720(719) [europe.equihash-hub.miningpoolhub.com]- 311ms (98.0%) (2.0%)
0>GTX 1070       [54°C/55%] 27.12 I/s 54.3(54.2) Sol/s 135.6W clk=1847MHz mclk=4452MHz Sol/W=0.40
1>GTX 1070       [48°C/55%] 27.49 I/s 54.5(54.8) Sol/s 133.7W clk=1847MHz mclk=4452MHz Sol/W=0.41
2>GTX 1070       [50°C/55%] 27.85 I/s 55.4(55.4) Sol/s 135.7W clk=1911MHz mclk=4452MHz Sol/W=0.41
3>GTX 1070       [46°C/55%] 27.61 I/s 54.8(55.0) Sol/s 135.5W clk=1873MHz mclk=4452MHz Sol/W=0.41
4>GTX 1070       [49°C/55%] 27.83 I/s 55.4(55.6) Sol/s 135.7W clk=1860MHz mclk=4452MHz Sol/W=0.41
5>GTX 1070 Ti    [43°C/55%] 32.16 I/s 64.0(64.2) Sol/s 135.1W clk=1885MHz mclk=4452MHz Sol/W=0.48
6>GTX 1070 Ti    [45°C/55%] 32.15 I/s 64.6(64.2) Sol/s 135.7W clk=1835MHz mclk=4452MHz Sol/W=0.47
7>GTX 1070 Ti    [51°C/55%] 31.57 I/s 63.6(63.2) Sol/s 135.3W clk=1784MHz mclk=4452MHz Sol/W=0.47
8>GTX 1070 Ti    [47°C/55%] 31.75 I/s 64.5(63.4) Sol/s 135.5W clk=1784MHz mclk=4452MHz Sol/W=0.47
9>GTX 1070 Ti    [49°C/55%] 31.96 I/s 63.9(63.8) Sol/s 135.2W clk=1835MHz mclk=4452MHz Sol/W=0.47
10>GTX 1070 Ti    [51°C/55%] 31.12 I/s 62.2(62.3) Sol/s 136.1W clk=1746MHz mclk=4452MHz Sol/W=0.46
11>GTX 1070 Ti    [46°C/55%] 31.52 I/s 62.3(62.9) Sol/s 136.9W clk=1784MHz mclk=4452MHz Sol/W=0.46
[ 1d 2h 6m59s] S:19091/5 713(719) [fee.server]- 52ms (98.0%) (2.0%)
0>GTX 1070       [54°C/55%] 26.90 I/s 53.8(54.2) Sol/s 135.4W clk=1822MHz mclk=4452MHz Sol/W=0.40
1>GTX 1070       [48°C/55%] 27.49 I/s 54.2(54.8) Sol/s 133.6W clk=1847MHz mclk=4452MHz Sol/W=0.41
2>GTX 1070       [50°C/55%] 27.85 I/s 55.6(55.4) Sol/s 135.8W clk=1873MHz mclk=4452MHz Sol/W=0.41
3>GTX 1070       [46°C/55%] 27.62 I/s 54.9(55.0) Sol/s 135.4W clk=1860MHz mclk=4452MHz Sol/W=0.41
4>GTX 1070       [49°C/55%] 27.82 I/s 55.7(55.6) Sol/s 135.6W clk=1885MHz mclk=4452MHz Sol/W=0.41
5>GTX 1070 Ti    [43°C/55%] 31.95 I/s 63.8(64.2) Sol/s 135.1W clk=1809MHz mclk=4452MHz Sol/W=0.48
6>GTX 1070 Ti    [45°C/55%] 31.92 I/s 64.1(64.1) Sol/s 135.6W clk=1809MHz mclk=4452MHz Sol/W=0.47
7>GTX 1070 Ti    [51°C/55%] 31.35 I/s 62.8(63.2) Sol/s 135.5W clk=1784MHz mclk=4452MHz Sol/W=0.47
8>GTX 1070 Ti    [47°C/55%] 31.76 I/s 64.7(63.4) Sol/s 135.4W clk=1784MHz mclk=4452MHz Sol/W=0.47
9>GTX 1070 Ti    [48°C/55%] 31.94 I/s 63.8(63.8) Sol/s 133.2W clk=1822MHz mclk=4452MHz Sol/W=0.48
10>GTX 1070 Ti    [50°C/55%] 30.90 I/s 61.9(62.2) Sol/s 134.0W clk=1733MHz mclk=4452MHz Sol/W=0.46
11>GTX 1070 Ti    [46°C/55%] 31.51 I/s 62.4(62.9) Sol/s 134.9W clk=1771MHz mclk=4452MHz Sol/W=0.47
systemd[1]: Stopping ACPI event daemon...
newbie
Activity: 164
Merit: 0
miner is still unstable for me at OC settings lower than those stable in gminer. i run my cards at 50-55% PL. im getting crashes every few hrs, sometimes less. OC settings are not high at all. sometimes runs for many hrs and sometimes few minutes
member
Activity: 679
Merit: 17
this cuda error log doesnt mean anything to me. would be great to know which gpu caused error
also no error logged if file already exists
Hi fistsofgod,
It looks like that the GPU became unstable. Try to tweak the OC settings, they might need adjustment.
We'll include the GPU in the error in the next version.
miniZ appends error to existing file. Could you check again?
Thank you!


crash after day of working
Code:
139944018290312:error:1409F07F:SSL routines:ssl3_write_pending:bad write retry:s3_pkt.c:1097:
what means this percents (98.0%) (2.0%)?
Hi topteam,
that error doesn't happen often and it is difficult to reproduce, but we think we got it already and should be fixed in the next version.
As fistsofgod said those percent values refer to the mining times (you vs fee). https://miniz.ch/usage/
Thanks!



newbie
Activity: 164
Merit: 0

what means this percents (98.0%) (2.0%)?
2.0% is dev fee % of mining time
newbie
Activity: 157
Merit: 0
crash after day of working
Code:
kernel: [98716.258383] show_signal_msg: 18 callbacks suppressed
kernel: [98716.258387] miniZ[2533]: segfault at 7f47940008b0 ip 00007f47940008b0 sp 00007f47407f67d8 error 15
[ 1d 3h20m04s] S:19579/4 722(720) [europe.equihash-hub.miningpoolhub.com]- 331ms (98.0%) (2.0%)
0>GTX 1070       [54°C/55%] 27.12 I/s 53.0(54.1) Sol/s 136.6W clk=1847MHz mclk=4452MHz Sol/W=0.40
1>GTX 1070       [46°C/55%] 27.58 I/s 55.3(55.0) Sol/s 134.8W clk=1847MHz mclk=4452MHz Sol/W=0.41
2>GTX 1070       [48°C/55%] 27.87 I/s 56.0(55.7) Sol/s 136.5W clk=1923MHz mclk=4452MHz Sol/W=0.41
3>GTX 1070       [44°C/55%] 27.69 I/s 54.8(55.3) Sol/s 134.7W clk=1873MHz mclk=4452MHz Sol/W=0.41
4>GTX 1070       [48°C/55%] 27.81 I/s 55.1(55.5) Sol/s 134.9W clk=1860MHz mclk=4452MHz Sol/W=0.41
5>GTX 1070 Ti    [41°C/55%] 32.21 I/s 64.9(64.4) Sol/s 136.0W clk=1847MHz mclk=4452MHz Sol/W=0.47
6>GTX 1070 Ti    [43°C/55%] 32.20 I/s 65.2(64.4) Sol/s 136.8W clk=1809MHz mclk=4452MHz Sol/W=0.47
7>GTX 1070 Ti    [49°C/55%] 31.59 I/s 64.2(63.1) Sol/s 135.9W clk=1822MHz mclk=4452MHz Sol/W=0.46
8>GTX 1070 Ti    [46°C/55%] 31.77 I/s 63.8(63.4) Sol/s 134.7W clk=1809MHz mclk=4452MHz Sol/W=0.47
9>GTX 1070 Ti    [48°C/55%] 32.00 I/s 63.0(63.8) Sol/s 135.3W clk=1835MHz mclk=4452MHz Sol/W=0.47
10>GTX 1070 Ti    [50°C/55%] 31.15 I/s 63.8(62.4) Sol/s 136.8W clk=1759MHz mclk=4452MHz Sol/W=0.46
11>GTX 1070 Ti    [45°C/55%] 31.54 I/s 63.1(62.9) Sol/s 136.0W clk=1784MHz mclk=4452MHz Sol/W=0.46
[ 1d 3h20m14s] S:19582/4 723(720) [fee.server]- 51ms (98.0%) (2.0%)
0>GTX 1070       [54°C/55%]*27.12 I/s 53.0(54.1) Sol/s 136.5W clk=1784MHz mclk=4452MHz Sol/W=0.40
1>GTX 1070       [46°C/55%]*27.58 I/s 55.3(55.0) Sol/s 134.7W clk=1873MHz mclk=4452MHz Sol/W=0.41
2>GTX 1070       [48°C/55%] 27.86 I/s 55.8(55.7) Sol/s 136.4W clk=1873MHz mclk=4452MHz Sol/W=0.41
3>GTX 1070       [44°C/55%] 27.70 I/s 54.9(55.3) Sol/s 134.7W clk=1885MHz mclk=4452MHz Sol/W=0.41
4>GTX 1070       [48°C/55%] 27.81 I/s 55.3(55.5) Sol/s 134.9W clk=1860MHz mclk=4452MHz Sol/W=0.41
5>GTX 1070 Ti    [41°C/55%] 32.21 I/s 65.1(64.4) Sol/s 136.3W clk=1847MHz mclk=4452MHz Sol/W=0.47
6>GTX 1070 Ti    [43°C/55%] 32.20 I/s 65.1(64.4) Sol/s 136.8W clk=1847MHz mclk=4452MHz Sol/W=0.47
7>GTX 1070 Ti    [49°C/55%] 31.58 I/s 64.2(63.1) Sol/s 135.8W clk=1784MHz mclk=4452MHz Sol/W=0.46
8>GTX 1070 Ti    [46°C/55%] 31.77 I/s 63.5(63.4) Sol/s 134.8W clk=1784MHz mclk=4452MHz Sol/W=0.47
9>GTX 1070 Ti    [48°C/55%] 32.00 I/s 63.0(63.8) Sol/s 135.2W clk=1797MHz mclk=4452MHz Sol/W=0.47
10>GTX 1070 Ti    [49°C/55%] 31.15 I/s 63.8(62.4) Sol/s 136.7W clk=1746MHz mclk=4452MHz Sol/W=0.46
11>GTX 1070 Ti    [45°C/55%]*31.55 I/s 62.8(62.9) Sol/s 136.0W clk=1809MHz mclk=4452MHz Sol/W=0.46
139944018290312:error:1409F07F:SSL routines:ssl3_write_pending:bad write retry:s3_pkt.c:1097:
what means this percents (98.0%) (2.0%)?
newbie
Activity: 164
Merit: 0
Code:
2018-12-03 00:55:29: CUDA error 'the launch timed out and was terminated' in func 'eq~~p:hWsmnJv11i>x,::solve' line 878

2018-12-03 00:55:29: CUDA error 'the launch timed out and was terminated' in func 'eq~~p:hWsmnJv11i>x,::solve' line 948

2018-12-03 00:55:29: CUDA error 'the launch timed out and was terminated' in func 'eq~~p:hWsmnJv11i>x,::solve' line 878

2018-12-03 00:55:29: CUDA error 'the launch timed out and was terminated' in func 'eq~~p:hWsmnJv11i>x,::solve' line 878

this cuda error log doesnt mean anything to me. would be great to know which gpu caused error
also no error logged if file already exists
newbie
Activity: 157
Merit: 0
Hi topteam,

Sorry for the misunderstanding, now it is clear that you do not want to use miniZ log file, you just want to redirect all the output
directly to your syslog.
  
The --nocolor option removes the color from the logfile (generated with --logfile option that you are not using).

To achieve what you need, try:

Code:
stdbuf -o0 ./miniZ --url [email protected]:20595 --pers BgoldPoW --par=144,5 --telemetry 0 --gpu-line --extra --templimit 70C --tempunits C --latency 2>&1 |  sed -E s/'\x1B\[[0-9;]+[m|K]'//g

Cheers!
Thanks, now work!!!
But i hope you fix it in next version (remove symbols from buffer not good idea)
Code:
Algo:#011#011EQ[144,5]
Pool#0:#011#011user[user.rig1] server[europe.equihash-hub.miningpoolhub.com] port[20595] ssl[no] pers[BgoldPoW]
member
Activity: 679
Merit: 17
Hi topteam,

Sorry for the misunderstanding, now it is clear that you do not want to use miniZ log file, you just want to redirect all the output
directly to your syslog.
 
The --nocolor option removes the color from the logfile (generated with --logfile option that you are not using).

To achieve what you need, try:

Code:
stdbuf -o0 ./miniZ --url [email protected]:20595 --pers BgoldPoW --par=144,5 --telemetry 0 --gpu-line --extra --templimit 70C --tempunits C --latency 2>&1 |  sed -E s/'\x1B\[[0-9;]+[m|K]'//g

Cheers!
newbie
Activity: 157
Merit: 0
I write log directly to syslog, can you check your syslog?
And have line in sh before miner
Code:
export SYSLOG=1
Hi topteam, both our OS and the miner ignore the export SYSLOG=1.
Are you including the --nocolor option?
We cannot reproduce your problem. Could you send us your miniZ cmd line?
Thanks!!
option --nocolor not work on ubuntu 16
can you check it?
Code:
./miniZ --url [email protected]:20595 --pers BgoldPoW --par=144,5 --telemetry 0 --gpu-line --extra --nocolor --templimit 70C --tempunits C --latency
member
Activity: 679
Merit: 17
I write log directly to syslog, can you check your syslog?
And have line in sh before miner
Code:
export SYSLOG=1
Hi topteam, both our OS and the miner ignore the export SYSLOG=1.
Are you including the --nocolor option?
We cannot reproduce your problem. Could you send us your miniZ cmd line?
Thanks!!


im using coinblockers, today miner stop again without error. I must add log option
Hi reciu,
we do not see any problem so far. But we are still checking this in various pools, also coinblockers.
Please keep us up to date with your findings.
Thanks!


I'm getting this on 0.5-82. That's because Hive folder for custom miners has changed in 0.6 for which you did the package. On 0.6 it is fine.
Quote
/hive/custom/miniZ/h-run.sh: line 7: /hive/miners/custom/miniZ/h-manifest.conf: No such file or directory
No CUSTOM_CONFIG_FILENAME is set
custom miniZ exited, waiting to cooldown a bit
Hi abudfv2008,
Thanks for reporting this. We added compatibility with Hive OS 0.5. Can you try again and let us know how it went?

Cheers everyone!
full member
Activity: 728
Merit: 106
Hi everyone,

You can now run miniZ  with Hive OS.

Support @ https://miniz.ch/2018/11/29/hive-os-support/

Happy mining!
I'm getting this on 0.5-82. That's because Hive folder for custom miners has changed in 0.6 for which you did the package. On 0.6 it is fine.
Quote
/hive/custom/miniZ/h-run.sh: line 7: /hive/miners/custom/miniZ/h-manifest.conf: No such file or directory
No CUSTOM_CONFIG_FILENAME is set

custom miniZ exited, waiting to cooldown a bit
newbie
Activity: 22
Merit: 0
im using coinblockers, today miner stop again without error. I must add log option
newbie
Activity: 157
Merit: 0
Good job!!!
But not all color symbol remove from log with --nocolor option

and show ping latency too high (911 ms)

Fix it in next version

Hi topteam, we cannot see any color symbols in our log. Can you double check the log file? The miner appends the log to an existing file, is it possible that you looked at a previous version log part of the file? If not, can you check whether you wrote --nocolor in the command line?
Regarding ping latency, we wil reduce ping time window used to compute average in the next version.



Thank you all for your feedback.

Cheers

I write log directly to syslog, can you check your syslog?
And have line in sh before miner
Code:
export SYSLOG=1
member
Activity: 679
Merit: 17
Hi everyone,

You can now run miniZ  with Hive OS.

Support @ https://miniz.ch/2018/12/13/hive-os-support/

Happy mining!
member
Activity: 679
Merit: 17
195 core
700 memory
62% power limit

edit: 195 crash , back to 185 core

miner recomended :3 the fastest at this moment

Try to add watchdog like in gminer Smiley
update
miner avg speed shows 198 sols but pool only 185-189
gminer shows 192-195 but on pool 195-205

Hi reciu,

the program should not crash, with watchdog the program restarts with same OC settings so it is likely that it will crash again.
It is better to modify the OC settings. Watchdog can make it harder to understand other crash causes. But we may look into it in the future.
For the time being, if you really want to restart automatically, you can run the program within a while loop.

Regarding the reported speed in the pool vs miner, can you tell us which pool you are using?
This should not happen and in all our tests we never saw anything like that happening, usually the pool reports a little more than the miner.

Be sure that miniZ runs stable for at least 3h without any restarts, or modifications to setting values.

We are currently carefully rechecking this matter.

Thank you for your feedback.

Cheers
member
Activity: 679
Merit: 17
Hello!
when you add your wonderful manners to the platform of hive OS

Hello!
It works fine but shows average ping rather than actual.
When I start mining, I see a large ping and after a while it becomes relevant.
And hive os support is also interesting
Thanks for your job

Hi A11an, dgeo,
thank you. We made a package for support with Hive OS. Check @ https://miniz.ch/2018/12/13/hive-os-support/
Regarding ping latency, we wil reduce ping time window used to compute average the average in the next version.


Good job!!!
But not all color symbol remove from log with --nocolor option

and show ping latency too high (911 ms)

Fix it in next version

Hi topteam, we cannot see any color symbols in our log. Can you double check the log file? The miner appends the log to an existing file, is it possible that you looked at a previous version log part of the file? If not, can you check whether you wrote --nocolor in the command line?
Regarding ping latency, we wil reduce ping time window used to compute average in the next version.



Thank you all for your feedback.

Cheers
Pages:
Jump to: