undertrey / farmwatchbot Goto Github PK

View Code? Open in Web Editor NEW

91.0 23.0 28.0 749 KB

FarmWatchBot for Ewbf, Claymore, Dstm, CCminer, Bminer, Ethminer, Cast XMR, Phoenix, T-Rex, Gminer, NB miner

License: GNU General Public License v3.0

Batchfile 100.00%

autorun claymore dstm bminer ccminer farmwatchbot phoenixminer zec miner xmr

farmwatchbot's People

Contributors

Stargazers

Watchers

farmwatchbot's Issues

Crash of EWBF watchdog

EWBF bug report
If those messages are detected in log watchbot crashes
20.07.2018 08:19:21 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable" 02.08.2018 15:33:25 CUDA: Device: 1 Thread exited with message: "an illegal memory access was encountered"

Error written in watchbot log

[2018-08-02][15:36:27] CUDA-capable

It happens on every detected line that contains "

>> %~n0.log ECHO [%Date%][%Time:~-11,8%] reports:%reports% 3:%~3 Chat:%chatid% prints reports:0 3:02.08.2018 15:33:25 CUDA: Device: 1 Thread exited with message: "an Chat:0

When I added REM to lines 796 and 797 watchbot works fine
I've tried to edit those lines, to just write to log simple message, but it also didn't work

Also I see this version is still missing current server and queue number

PhoenixMiner - unable to get fan speed - Unknown Error (999) - not counted?

I believe this error is not counted.
unable to get fan speed - Unknown Error (999)

2018.07.23:11:10:41.062: eths Eth: New job #e25417d1 from europe.ethash-hub.miningpoolhub.com:20535; diff: 4300MH
2018.07.23:11:10:41.209: main Eth speed: 265.566 MH/s, shares: 4559/0/9, time: 21:05
2018.07.23:11:10:41.209: main GPUs: 1: 55.620 MH/s (960/9) 2: 55.138 MH/s (936) 3: 55.181 MH/s (949) 4: 33.195 MH/s (610) 5: 33.186 MH/s (581) 6: 33.246 MH/s (523)
2018.07.23:11:10:42.908: hwmc GPU4: unable to get fan speed - Unknown Error (999)
2018.07.23:11:10:43.033: main GPU1: 57C 61%, GPU2: 59C 66%, GPU3: 57C 61%, GPU4: 53C, GPU5: 54C 56%, GPU6: 50C 50%
2018.07.23:11:10:46.284: main Eth speed: 265.675 MH/s, shares: 4559/0/9, time: 21:05
2018.07.23:11:10:46.284: main GPUs: 1: 55.621 MH/s (960/9) 2: 55.015 MH/s (936) 3: 55.153 MH/s (949) 4: 33.295 MH/s (610) 5: 33.285 MH/s (581) 6: 33.305 MH/s (523)
2018.07.23:11:10:48.042: eths Eth: Received: {"id":null,"method":"mining.notify","params":["4ef0","0x8e01b76c5582b4dc7767c826796e3686f76800a582969ee015467943b568544d","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7",true]}
2018.07.23:11:10:48.042: eths Eth: New job #8e01b76c from europe.ethash-hub.miningpoolhub.com:20535; diff: 4300MH
2018.07.23:11:10:48.906: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xfc6afc8","0x147cd3249fdeace1c3c74eae574a2ef8b94672b90dc9a6eb740bd5f989c33bf6"]}

Official answer by PhoenixMiner

This is an NVML (the Nvidia hardware monitoring library) internal error. We have seen similar errors on our GTX1060s. Additional symptoms include high CPU usage (either by the miner or the MSI Afterburner). The same problems were also observed with Claymore's miner on the same rig. The short term-solution is to restart the rig (not just the miner) but the only long-term solution is to lower the memory overclock a little. We have found that even 20-30 MHz lower memory clocks completely solve the problem. Or you can continue mining and ignore the errors but the high CPU usage can be a real PITA when trying to control the rig via VNC or TeamViewer.

In my case, Afterburner completely freezes, can't do anything with it, but the mining continues. Remote desktop works.

And yes, I tried more aggressive overclocks, but I wasn't saved to an Afterburner profile, so a restart would solve this problem for me, and a stable Afterburner profile is selected by FarmWatchBot.

Wrong screenshot name

PhoenixMiner

The screenshot name is: miner_7.30_18.58.jpg
But the time was different as seen on this picture: 07.31. 01:43.

The other screenshots are named with correct date and time (5-10 minutes differences), only this one is not.

Phnxautorun.log

[2018. 07. 31.][ 1:43:18] Process PhoenixMiner.exe crashed...
[2018. 07. 31.][ 1:43:18] Miner restarting, please wait... Miner ran for *06:45:06*.
[2018. 07. 31.][ 1:44:03] log*.txt moved to Logs folder as miner_7.31_1.43.log
[2018. 07. 31.][ 1:44:06] Miner was started. Script v.2.0.1.
[2018. 07. 31.][ 1:44:21] Ensure PhoenixMiner.exe -pool -log 1 options added to the miners command line in this order.

miner_7.31_1.43.log end

2018.07.31:01:42:38.464: main Eth speed: 274.427 MH/s, shares: 1550/0/1, time: 6:43
2018.07.31:01:42:38.464: main GPUs: 1: 55.132 MH/s (308) 2: 54.792 MH/s (317) 3: 54.608 MH/s (319) 4: 54.962 MH/s (313/1) 5: 54.932 MH/s (293)
2018.07.31:01:42:41.714: eths Eth: Received: {"id":null,"method":"mining.notify","params":["b3","0x584a8a8833a7b04ec1cda7bc2ab7bc5f34766e6515201afdaff2deb3ccfd5f45","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7",true]}
2018.07.31:01:42:41.714: eths Eth: New job #584a8a88 from europe.ethash-hub.miningpoolhub.com:20535; diff: 4300MH
2018.07.31:01:42:42.083: GPU1 GPU1: Starting up... (0)
2018.07.31:01:42:42.083: GPU1 Eth: Generating light cache for epoch #202
2018.07.31:01:42:42.114: GPU4 GPU4: Starting up... (0)
2018.07.31:01:42:42.124: GPU5 GPU5: Starting up... (0)
2018.07.31:01:42:42.169: GPU2 GPU2: Starting up... (0)
2018.07.31:01:42:42.207: GPU3 GPU3: Starting up... (0)
2018.07.31:01:42:43.135: main  
2018.07.31:01:42:43.135: main *** 6:43 *** 7/31 01:42 **************************************
2018.07.31:01:42:43.135: main Eth: Mining ETH on europe.ethash-hub.miningpoolhub.com:20535 for 6:43
2018.07.31:01:42:43.135: main Eth: Accepted shares 1550 (0 stales), rejected shares 0 (0 stales)
2018.07.31:01:42:43.135: main Eth: Incorrect shares 1 (0.06%), est. stales percentage 0.00% 
2018.07.31:01:42:43.135: main Eth: Maximum difficulty of found share: 11.5 TH (!!!)
2018.07.31:01:42:43.135: main Eth: Average speed (5 min): 274.399 MH/s
2018.07.31:01:42:43.135: main Eth: Effective speed: 275.06 MH/s; at pool: 275.06 MH/s
2018.07.31:01:42:43.135: main  
2018.07.31:01:42:43.539: main Eth speed: 0.000 MH/s, shares: 1550/0/1, time: 6:43
2018.07.31:01:42:43.539: main GPUs: 1: 0.000 MH/s (308) 2: 0.000 MH/s (317) 3: 0.000 MH/s (319) 4: 0.000 MH/s (313/1) 5: 0.000 MH/s (293)

Are you sure it's crashed? It started to generating light cache for epoch.

SRBMiner support

Hello @Undertrey!
Very nice work indeed.. Many 10x for that.

Can I kindly ask you to provide support for SRBMiner as well?
Thanks in advance for your time..

Hashrate unit

Hi,

First, I find your bot very useful. Great work!

I have encountered an issue with the Hashrate calculation. Since I have very different GPUs, (1x 1080TI, 2 x 1080, 3 x 1070), their hashrates are also quite different. Now, ccminer reports everything below 10 MH/s as 9999 KH/s (why 10MH and not 1??? nobody knows...) and the 1070's are giving me something like 8000 KH/s, whereas the ti gets as high as 22 MH/s.

I think, you can see the problem, since with your script, the numbers are just added (KH + MH), giving me nonsensical values (funny in fact, since if the ti drops out, with only "22" MH, it will not be noticed at all :) ) and I cannot really make use of the awesome low hashrate detection function.

Is there a possibility to correct this? or is there a parameter for ccminer to fix the output unit maybe?

Can you add a function - check whether the network is unobstructed, otherwise kill miner?

Because if my mining machine has a network error, it will crash and cannot be restarted by using remote software. Therefore,choose to kill the miner according to the network changes(can use the ping command to finish this?). After killed, can constantly detect whether the network is unobstructed through the ping command. If it is unobstructed, restart the miner.

Miner working OK." Do not worry. - how to get full information in the miner?

Hello,

how to get full information in the miner?
I do not want to receive a "Miner working OK." Do not worry. " I want to see full statistics online.
this can be done?

Thanks!

[Feature request] Count incorrect shares, above x percentage do some action

PhoenixMiner:

Eth speed: 262.887 MH/s, shares: 4787/0/11, time: 22:08
GPUs: 1: 55.369 MH/s (1018/11) 2: 54.722 MH/s (988) 3: 52.902 MH/s (984) 4: 33.295 MH/s (627) 5: 33.296 MH/s (607) 6: 33.303 MH/s (563)

*** 22:08 *** 7/23 12:13 **************************************
Eth: Mining ETH on europe.ethash-hub.miningpoolhub.com:20535 for 22:08
Eth: Accepted shares 4787 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 11 (0.23%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 104.8 TH (!!!)
Eth: Average speed (5 min): 264.606 MH/s
Eth: Effective speed: 258.33 MH/s; at pool: 258.33 MH/s

Eth speed: 263.307 MH/s, shares: 4787/0/11, time: 22:08
GPUs: 1: 55.367 MH/s (1018/11) 2: 54.803 MH/s (988) 3: 53.242 MH/s (984) 4: 33.295 MH/s (627) 5: 33.297 MH/s (607) 6: 33.302 MH/s (563)

I have 11 incorrect shares, which is 0,25%. Above 1% I would do something: restart miner, restart machine, etc.

What do you think?

More example. This incorrect shares percentage is too much, need to restart computer:

*** 34:37 *** 7/25 08:29 **************************************
Eth: Mining ETH on europe.ethash-hub.miningpoolhub.com:20535 for 18:20
Eth: Accepted shares 7590 (1 stales), rejected shares 1 (0 stales)
Eth: Incorrect shares 156 (2.01%), est. stales percentage 0.01%
Eth: Maximum difficulty of found share: 11.3 TH (!!!)
Eth: Average speed (5 min): 273.437 MH/s
Eth: Effective speed: 261.84 MH/s; at pool: 261.81 MH/s

Now I'am using every 24 hour restarts.

Loaded too many GPUs? I have gpus=0 in the config.

Phnxautorun.log:

[2018. 08. 01.][ 4:31:35] Miner was started. Script v.2.0.3.
[2018. 08. 01.][ 4:31:50] Ensure PhoenixMiner.exe -pool -log 1 options added to the miners command line in this order.
[2018. 08. 01.][ 4:32:55] Loaded too many GPUs. This must be set to a number higher than 1 in your Config_ePhnx.ini file under gpus. Number of GPUs: 5/1.
[2018. 08. 01.][ 4:32:55] Computer restarting...
[2018. 08. 01.][ 4:35:46] Config_ePhnx.ini loaded.
[2018. 08. 01.][ 4:36:26] log*.txt moved to Logs folder as miner_8.1_4.35.log
[2018. 08. 01.][ 4:36:29] Miner was started. Script v.2.0.3.
[2018. 08. 01.][ 4:36:44] Ensure PhoenixMiner.exe -pool -log 1 options added to the miners command line in this order.

I have gpus=0 in Config_ePhnx.ini

Attached the miner_8.1_4.35.log (it's not long):
miner_8.1_4.35.log

I changed cputimeout to 10. This could be a problem?

Time and date format inconsistency

I really like your FarmWatchBot! Thank your for your work!

I just want to let you know, that the date and time format is different everywhere you use it.

Some examples:

What time format is this?

42,12?
Logs folder:

miner_7.19_10.31.log
miner_7.20_0.18.log
miner_7.20_0.8.log
miner_7.20_22.33.log

I dont understand, what time was this? miner_7.20_0.8.log

Current log filename:
log20180720_223357.txt
This is good, fully understandable. :)
Screenshot folder:
miner_7.20_0.18.jpg
Timestamps used in logs:
2018.07.19:10:32:09.370

I think the best format for the file names should look like this:
log_20180720_223357.txt
screenshot_20180720_223357.jpg
miner_20180720_223357.txt

Firewall

I have a firewall. When I run the eth_miner.exe after setup was done, It never connects. When I disable the firewall it connects, but the log is constantly spinning the cards with no work done. And for some strange reason it connects to ethermine.org only (it's the third option).

When i run clean bat file it connects to my pool instantly

Request: FarmWatchBot for z-enemy-1.09a miner

Hi, can you please update your script to support z-enemy-1.09a miner. (link to download below)
It has become a new hot miner X16S and X16R and LUX coins.
Unfortunately there is currently nothing on the market to watch these script and restart it when it crashes.
I have to do it fairly often on my rig. Please help!
You can download script here:
https://www.asylab.com/single-post/2018/05/10/Z-Enemy-miner-v109a-NVIDIA-for-Ravencoin-RVN-Pigeoncoin-PGN-Windows-Linux

I need help

I have this error on PhoenixMiner 5.0e

How does last share timeout check works? It killed the process 30 minutes later?

PhoenixMiner

What happened here?

Phnxautorun.log

[2018. 08. 01.][ 4:03:35] Long share timeout... 1/50.
[2018. 08. 01.][ 4:03:44] Miner restarting, please wait... Miner ran for *03:50:19*.
[2018. 08. 01.][ 4:30:52] Process PhoenixMiner.exe was successfully killed.
[2018. 08. 01.][ 4:31:32] log*.txt moved to Logs folder as miner_8.1_4.27.log

miner_8.1_4.27.log

I see ETH share found! during that time. For example:
2018.08.01:04:03:17.231: GPU1 Eth: GPU1: ETH share found!

I see my hashrate dropped that time, but that was because sometime miner restarted: New month reached
And this miner restart messed up my overclock settings. Only miner restart is not always working good for me. A reboot would be better. Any option for that? Instead restarting miner, restart PC in some cases.

I like your program but there is only one issue for claymore eth only mode

your script does not let me select claymore eth mode only, i have to use dpool pool also, how can i just use eth only mode using ClayETHautorun.bat help

phoenix miner hashrate report

Hi,

I have started using your script with phoenix miner. not sure if i am doing something wrong but when i enable telegram notifications it only says how long it is online and no hashrate information is sent to telegram.

PhoenixMiner CUDA errors

I have some more errors for PhoenixMiner (3.0c).

In this case, PC was rebooted because ".*CUDA-capable.*" is counted. But you could add more error texts.

2018.07.20:22:29:33.401: GPU4 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.20:22:29:33.430: GPU5 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.20:22:29:33.454: GPU6 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.20:22:29:33.662: GPU3 CUDART error in CudaProgram.cu:56 : all CUDA-capable devices are busy or unavailable (46)
2018.07.20:22:29:33.662: GPU1 CUDART error in CudaProgram.cu:56 : all CUDA-capable devices are busy or unavailable (46)
2018.07.20:22:29:33.673: GPU2 CUDART error in CudaProgram.cu:56 : all CUDA-capable devices are busy or unavailable (46)
2018.07.20:22:29:34.093: GPU4 GPU4 initMiner error: unspecified launch failure
2018.07.20:22:29:34.093: GPU2 GPU2 initMiner error: all CUDA-capable devices are busy or unavailable
2018.07.20:22:29:34.093: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable
2018.07.20:22:29:34.093: GPU6 GPU6 initMiner error: unspecified launch failure
2018.07.20:22:29:34.093: GPU3 GPU3 initMiner error: all CUDA-capable devices are busy or unavailable
2018.07.20:22:29:34.093: GPU5 GPU5 initMiner error: unspecified launch failure

In this case the built in watchdog is kicked in, and by default it does this:

restart with the same command line options

2018.07.22:14:03:56.127: GPU4 CUDA error in CudaProgram.cu:329 : an illegal instruction was encountered (715)
2018.07.22:14:03:56.127: GPU4 GPU4 search error: an illegal instruction was encountered
2018.07.22:14:03:56.141: GPU1 CUDA error in CudaProgram.cu:329 : an illegal instruction was encountered (715)
2018.07.22:14:03:56.141: GPU1 GPU1 search error: an illegal instruction was encountered
2018.07.22:14:03:56.188: GPU6 CUDA error in CudaProgram.cu:329 : an illegal instruction was encountered (715)
2018.07.22:14:03:56.188: GPU6 GPU6 search error: an illegal instruction was encountered
2018.07.22:14:03:56.204: GPU2 CUDA error in CudaProgram.cu:329 : an illegal instruction was encountered (715)
2018.07.22:14:03:56.204: GPU5 CUDA error in CudaProgram.cu:329 : an illegal instruction was encountered (715)
2018.07.22:14:03:56.204: GPU2 GPU2 search error: an illegal instruction was encountered
2018.07.22:14:03:56.204: GPU5 GPU5 search error: an illegal instruction was encountered
2018.07.22:14:03:56.235: GPU3 CUDA error in CudaProgram.cu:329 : an illegal instruction was encountered (715)
2018.07.22:14:03:56.235: GPU3 GPU3 search error: an illegal instruction was encountered
2018.07.22:14:03:56.652: main Eth speed: 261.474 MH/s, shares: 1631/0/0, time: 7:22
2018.07.22:14:03:56.652: main GPUs: 1: 54.612 MH/s (347) 2: 54.556 MH/s (356) 3: 53.975 MH/s (333) 4: 32.857 MH/s (227) 5: 32.856 MH/s (196) 6: 32.617 MH/s (172)
2018.07.22:14:03:56.921: wdog Thread(s) not responding. Restarting.

I would prefer a PC reboot instead by FarmWatchBot.

Can FarmWatchBot deal with auto miner restarts?

Can’t start the bot

I am not sure how to properly translate this error into English, but essentially I configured the .ini and after trying to start the bot this comes up:

Feature Request: Pause Mining between certain time of day

Utility now forces me to be on tier. It is most expensive to mine from 5-8pm, would like ability to tell system to pause all mining activity to save power between specified time. thank

undertrey / farmwatchbot Goto Github PK

farmwatchbot's People

Contributors

Stargazers

Watchers

Forkers

farmwatchbot's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs