Pause the progress if T-Rex Miner has error?

[igotek]

I use HiveOS for mining ALPH.

The miner sometimes gives error because of high overclock. The miner restarts mining progress. I dont want its restart. I want to see the error which gpu has.
How could it possible ? is there any code to write in extra config ?

I see the error code if i only watch the mining progress…
But there are so many rigs. ı cannot watch the progress. I only need the information which gpu has the problem.

Windows has an opiton to do it. The mining progress is being stopped at any error if I write “pause” to the next line of the bat file. For example:

t-rex.exe -a etchash -o stratum+ssl://etc-de.flexpool.io:5555 -u 0xbc1f6b39719f5d587de3ea90c67cd162c585b0cb -p x -w Z04
pause

But HiveOS stop the mining progress and restarts t-rex miner. I dont want to log of the miner progress as I use Flash disk. Stop mining and send notification at any error of the mining progress. So i can check the miner log and fix the problem.

20220916 14:40:20 [ OK ] 40/40 - 14.44 GH/s, 55ms … GPU #0
20220916 14:40:33 [ OK ] 41/41 - 14.44 GH/s, 47ms … GPU #2
20220916 14:40:41 TREX: Can’t find nonce with device [ID=4, GPU #4], cuda exception: CUDA_ERROR_LAUNCH_TIMEOUT, try to reduce overclock to stabilize GPU state
20220916 14:40:41 WARN: Miner is going to shutdown…
20220916 14:40:42 Main loop finished. Cleaning up resources…
20220916 14:40:42 ApiServer: stopped listening on 127.0.0.1:4059
20220916 14:40:44 T-Rex finished.

t-rex exited (exitcode=0), waiting to cooldown a bit

Trying to release TIME_WAIT sockets:
tcp 0 0 127.0.0.1:33498 127.0.0.1:4059 TIME_WAIT
tcp 0 0 127.0.0.1:33478 127.0.0.1:4059 TIME_WAIT
tcp 0 0 127.0.0.1:33494 127.0.0.1:4059 TIME_WAIT
tcp 0 0 127.0.0.1:33482 127.0.0.1:4059 TIME_WAIT
tcp 0 0 127.0.0.1:33490 127.0.0.1:4059 TIME_WAIT
tcp 0 0 127.0.0.1:33486 127.0.0.1:4059 TIME_WAIT

20220916 14:40:48 T-Rex NVIDIA GPU miner v0.26.5 - [Linux]
20220916 14:40:48 r.b70faa49dd35
20220916 14:40:48
20220916 14:40:48
20220916 14:40:48 NVIDIA Driver v510.60.02
20220916 14:40:48
20220916 14:40:48 + GPU #0: [00:03.0|2204] GeForce RTX 3090, 24268 MB
20220916 14:40:48 + GPU #1: [00:04.0|2204] GeForce RTX 3090, 24268 MB
20220916 14:40:48 + GPU #2: [00:05.0|2204] GeForce RTX 3090, 24268 MB
20220916 14:40:48 + GPU #3: [00:06.0|2204] GeForce RTX 3090, 24268 MB
20220916 14:40:48 + GPU #4: [00:08.0|2204] GeForce RTX 3090, 24268 MB
20220916 14:40:48 + GPU #5: [00:09.0|2204] GeForce RTX 3090, 24268 MB

[keaton_hiveon]

@igotek

20220916 14:40:41 TREX: Can’t find nonce with device [ID=4, GPU #4], cuda exception: CUDA_ERROR_LAUNCH_TIMEOUT, try to reduce overclock to stabilize GPU state

It tells you which gpu and what to do

[igotek]

Yes I know. But I see it if i only watch the mining progress screen.

T-REX MINER in ethash:
The rig reboots itself and send a red color notification if any error on any gpu.
HiveOS sends the notifications.

T-REX MINER in blake3-alph and in kawpow:
T-rex miner progresss restarts if any error on any gpu and there is no any notification.
is it possible to send a red color notification in blake3-alph and in kawpow of t-rex miner ?

[keaton_hiveon]

You can likely disable the built in trex watchdog. Check their GitHub for the flag. But you shouldn’t need to look at your logs more than once to see which card is causing the crash and adjusting the oc on that card to keep it from crashing.