Hi,
scripts are fantastic, but I have a small problem with ccminer bot.
When miner crash, WatchBot still detect hashrate and does not restart miner.
Here is log:
2018-03-13 12:28:08] GPU #2: unspecified launch failure
[2018-03-13 12:28:08] GPU #4: unspecified launch failure
[2018-03-13 12:28:08] GPU #3: unspecified launch failure
[2018-03-13 12:28:09] GPU #3: MSI GTX 1080 Ti, 5563.03 MH/s
[2018-03-13 12:28:09] GPU #3: unspecified launch failure
[2018-03-13 12:28:09] GPU #0: MSI GTX 1080 Ti, 2737.09 MH/s
[2018-03-13 12:28:09] GPU #0: unspecified launch failure
[2018-03-13 12:28:09] GPU #1: MSI GTX 1080 Ti, 2321.70 MH/s
[2018-03-13 12:28:09] GPU #1: unspecified launch failure
[2018-03-13 12:28:09] GPU #4: MSI GTX 1080 Ti, 4041.11 MH/s
[2018-03-13 12:28:09] GPU #4: unspecified launch failure
[2018-03-13 12:28:09] GPU #2: MSI GTX 1080 Ti, 2393.04 MH/s
[2018-03-13 12:28:09] GPU #2: unspecified launch failure
[2018-03-13 12:28:09] GPU #0: unspecified launch failure
[2018-03-13 12:28:09] GPU #1: unspecified launch failure
[2018-03-13 12:28:09] GPU #4: unspecified launch failure
Can you look at this situation?
Thank you.
Topic: [CMD] FarmWatchBot Ewbf, Claymore, Bminer, Dstm, CC, Eth, CastXMR, Phoenix - page 5. (Read 37024 times)
March 13, 2018, 12:46:57 PM
March 10, 2018, 12:57:14 PM
Does this work for Claymore CPU cryptonight?
March 09, 2018, 01:59:18 AM
Also, ccminer is giving me card hash rates in mh and kh, which is ruining the hash rate reboot monitor. Any chance to remediate that somehow?
March 08, 2018, 08:29:01 AM
Is there a way to view the ccminer window or the log or whatever while it's operating?
March 08, 2018, 08:27:42 AM
The addition of \update which automatically updates the script to the latest version is an extremely useful feature, especially when running multiple computers like me... This is a wonderful batch.
March 07, 2018, 09:22:46 AM
Today version 1.9.5 released!
Cпиcoк измeнeний - 1.9.5
Changelog - 1.9.5
Ewbf Equihash - Ewbfautorun.bat
Dstm Equihash - Dstmautorun.bat
Claymore Equihash - ClayZECautorun.bat
Claymore CryptoNote - ClayXMRautorun.bat
Claymore NeoScrypt - ClayNSautorun.bat
Claymore Dagger-Hashimoto - ClayETHautorun.bat
Ethminer Dagger-Hashimoto - Ethrautorun.bat
Ccminer tpruvot, alexis (palgin), KlausT - CCautorun.bat
Premium price 0.05ZEC or eq in other cryptocurrency.
Cпиcoк измeнeний - 1.9.5- Дoбaвлeнa пpoвepкa нa paзмep фaйлa лoгoв.
- Дoбaвлeн eщe oдин бoт для пoмoщи в oбpaбoткe зaпpocoв.
- Измeнeнo кoличecтвo лoгoв и cкpиншoтoв, кoтopыe coxpaняютcя в пaпкax c 50 дo 30.
- Пapaмeтp hashrate= в config.ini дoпoлнeн инфopмaциeй.
- Иcпpaвлeнa пpoблeмa кoppeктнoгo чтeния cкopocти Ethminer.
- Дoбaвлeнa eщe oднa oшибкa в oбpaбoтчик для Ccminer.
- GPU_FORCE_64BIT_PTR тeпepь paвнo 1 для Claymores Zec и Xmr.
- Кocмeтичecкиe иcпpaвлeния.
Changelog - 1.9.5- Added check for the size of the log file.
- Added another bot to help with query processing.
- Changed the number of logs and screenshots that are stored in folders from 50 to 30.
- The hashrate = parameter in config.ini is supplemented with information.
- Fixed the problem of correct reading of the Ethminer speed.
- Another error was added to the handler for Ccminer.
- GPU_FORCE_64BIT_PTR is now 1 for Claymores Zec and Xmr.
- Cosmetic fixes.
Ewbf Equihash - Ewbfautorun.bat
Dstm Equihash - Dstmautorun.bat
Claymore Equihash - ClayZECautorun.bat
Claymore CryptoNote - ClayXMRautorun.bat
Claymore NeoScrypt - ClayNSautorun.bat
Claymore Dagger-Hashimoto - ClayETHautorun.bat
Ethminer Dagger-Hashimoto - Ethrautorun.bat
Ccminer tpruvot, alexis (palgin), KlausT - CCautorun.bat
Premium price 0.05ZEC or eq in other cryptocurrency.
March 06, 2018, 05:26:51 PM
Telegram will not let me contact you, Every time i try it says I can only message mutual contacts. Anyway, what I did was set the miner to operate up to 80c but have NV-Instector limit to 70c, so that issue is just fine. As far as the ZEC payments. I am interested in the telegram bot. I may not be able to contact you, but I can receive so telegram notifications will be nice.
Write to me in private your Telegram nickname starting from @ and I will add you. It is not a problem.
Any chance of a Linux version? 
Sorry, only Windows. I will not support Linux, you can try other good products like "hiveos" etc...
Can i get more reviews from people who tried it ?
I'm using it. And not only does it do "as advertised" it has increased my average hash rate from 6.3 to 6.7 Kh/s. I'm running Claymore 12.6 with three 7990's, three R9-295X2's, three Radeon Pro Duo 12gb, and six RX-580's. My rigs were all relatively stable before I found this, but I was still having occasional issues with Claymore hanging. This resolved that. I also like the auto reboot every two days.
I give this five out of five stars!
Thank you very much for your trust and support!
March 06, 2018, 12:02:49 PM
GPU temp is the biggest issue for me right now. Anyone know how to contact the dev besides telegram? I just signed up but it wont let me message anyone. I sent the 0.05 ZEC to get the other features and stuff. But I cant use it with the temp limit. I want DTSM to do its job with the temp limit.
Every change I make to the bat file just causes it to crash. Tried to comment out the warningslist, tried to stop it from parsing for temp data. nothing
Every change I make to the bat file just causes it to crash. Tried to comment out the warningslist, tried to stop it from parsing for temp data. nothing
Hello. I'm always answer here, on other forums, in Telegram and on my Facebook page. Also i have email.
Remove --temp-limit 80 from config.ini. Or set it to 90C. What`s a problem?
About donations, when you sent 0.05 ZEC? Why you dont contact me in Telegram? I confused, why you donating for premium features if premium features - Telegram bot...
Telegram will not let me contact you, Every time i try it says I can only message mutual contacts. Anyway, what I did was set the miner to operate up to 80c but have NV-Instector limit to 70c, so that issue is just fine. As far as the ZEC payments. I am interested in the telegram bot. I may not be able to contact you, but I can receive so telegram notifications will be nice.
March 06, 2018, 12:01:39 PM
Any chance of a Linux version?
March 05, 2018, 10:06:47 PM
Can i get more reviews from people who tried it ?
I'm using it. And not only does it do "as advertised" it has increased my average hash rate from 6.3 to 6.7 Kh/s. I'm running Claymore 12.6 with three 7990's, three R9-295X2's, three Radeon Pro Duo 12gb, and six RX-580's. My rigs were all relatively stable before I found this, but I was still having occasional issues with Claymore hanging. This resolved that. I also like the auto reboot every two days.
I give this five out of five stars!
March 05, 2018, 04:38:25 PM
Logfile option missing.
Thank you a lot.
March 05, 2018, 04:09:33 PM
GPU temp is the biggest issue for me right now. Anyone know how to contact the dev besides telegram? I just signed up but it wont let me message anyone. I sent the 0.05 ZEC to get the other features and stuff. But I cant use it with the temp limit. I want DTSM to do its job with the temp limit.
Every change I make to the bat file just causes it to crash. Tried to comment out the warningslist, tried to stop it from parsing for temp data. nothing
Every change I make to the bat file just causes it to crash. Tried to comment out the warningslist, tried to stop it from parsing for temp data. nothing
Hello. I'm always answer here, on other forums, in Telegram and on my Facebook page. Also i have email.
Remove --temp-limit 80 from config.ini. Or set it to 90C. What`s a problem?
About donations, when you sent 0.05 ZEC? Why you dont contact me in Telegram? I confused, why you donating for premium features if premium features - Telegram bot...
Ok, checked it. It seems like script was restarting the rig due to insufficient hashrate. I've set average hashrate in config file as 2900, but in reality its more like ~2850, so miner was restarting due to hashrate errors. So I've set it to 2800 and that seem to solve the problem, thanks! But can you please add commentary in the config file explaining why we need to set average hashrate and how it affects script functionality, in the future versions? Because I had no idea why that parameter exists and how it affects mining.
Hello. Okay I will add more information. Thx.
As you can see, if hashrate is lower - miner will be restarted. Sometimes it helps when hashrate drops because of miner long run.
Hi,
I tried clayethautorun.bat script today at my 12GPU rig and there is small problem. Sricp run Clay miner, but than kill it right before Clay load all 12 gpu with.
Is there some time out before autorun check for running Claymore?
Thank you.
I tried clayethautorun.bat script today at my 12GPU rig and there is small problem. Sricp run Clay miner, but than kill it right before Clay load all 12 gpu with.
Is there some time out before autorun check for running Claymore?
Thank you.
Hello. Check ClayETHautorun.log.
March 05, 2018, 04:04:33 PM
Hi,
I tried clayethautorun.bat script today at my 12GPU rig and there is small problem. Script run Clay miner, but than kill it right before Clay load all 12 gpu.
Is there some time out before autorun check for running Claymore?
Thank you.
I tried clayethautorun.bat script today at my 12GPU rig and there is small problem. Script run Clay miner, but than kill it right before Clay load all 12 gpu.
Is there some time out before autorun check for running Claymore?
Thank you.
March 05, 2018, 04:26:06 AM
GPU temp is the biggest issue for me right now. Anyone know how to contact the dev besides telegram? I just signed up but it wont let me message anyone. I sent the 0.05 ZEC to get the other features and stuff. But I cant use it with the temp limit. I want DTSM to do its job with the temp limit.
Every change I make to the bat file just causes it to crash. Tried to comment out the warningslist, tried to stop it from parsing for temp data. nothing
Every change I make to the bat file just causes it to crash. Tried to comment out the warningslist, tried to stop it from parsing for temp data. nothing
March 04, 2018, 04:40:01 PM
Hello! I'm getting quite strange behavior of the latest (1.9.4) version of the script working with DSTM 0.6. Runtime error check fills up for 5/5 very quickly, in 5 minutes or less, causing rig to restart, and there is nothing wrong with miner itself - it mines as usual without problems. Can you please investigate?
Hello. Check Dstmautorun.log.
March 04, 2018, 08:46:16 AM
Today version 1.9.4 released!
Cпиcoк измeнeний 1.9.2 - 1.9.3 - 1.9.4
Changelog - 1.9.2 - 1.9.3 - 1.9.4
Ewbf Equihash - Ewbfautorun.bat
Dstm Equihash - Dstmautorun.bat
Claymore Equihash - ClayZECautorun.bat
Claymore CryptoNote - ClayXMRautorun.bat
Claymore NeoScrypt - ClayNSautorun.bat
Claymore Dagger-Hashimoto - ClayETHautorun.bat
Ethminer Dagger-Hashimoto - Ethrautorun.bat
Ccminer tpruvot, alexis (palgin), KlausT - CCautorun.bat
Premium price 0.05ZEC or eq in other cryptocurrency.
Cпиcoк измeнeний 1.9.2 - 1.9.3 - 1.9.4- Дoбaвлeнa пoддepжкa oтoбpaжeния бoльшeгo кoличecтвa видeoкapт в Claymore.
- Увeличeн тaймep oжидaния coздaния фaйлa лoгoв нa 5 ceкyнд.
- Умeньшeнo вpeмя oжидaния пepeд пepeзaгpyзкoй кoмпьютepa в cлyчae пoтepи coeдинeния нa 5 минyт.
- Дoбaвлeнa вoзмoжнocть пepeпиcывaть тo кoличecтвo cepвepoв, кoтopoe былo зaдaнo изнaчaльнo, a нe вceгдa 5.
- Дoбaвлeн peжим internetcheck=2 - oтключaeт пepeключeниe cepвepoв нo ocтaвляeт зa coбoй пpoвepкy интepнeтa.
- Измeнeния нa cтopoнe cepвepa бoтa. Зaпycк нoвoй вepcии cepвepa кoмaнд.
- Teпepь Бимaйнep кoppeктнo видит и pacпoзнaeт oшибки.
- Улyчшeнo pacпoзнaвaниe имeн Pигoв.
- Уcкopeнa oбpaбoткa Teлeгpaм кoмaнд.
- Cкpипт тeпepь пpинимaeт кoмaнды пooчepeднo (oднy зa дpyгoй), a нe тoлькo пocлeднюю.
- Дoбaвлeнa oшибкa в oбpaбoтчик для Dstm и Ewbf мaйнepoв.
- Иcпpaвлeнa кoмaндa pool для Bminer.
- Дoбaвлeнa вoзмoжнocть oтключить пoлнocтью вce yвeдoмлeния в Teлeгpaм.
- Cepвep и мaйнep нe бyдeт пepeключaтcя ecли oн yжe paбoтaeт нa этoй oпции.
- Дoбaвлeнa пpoвepкa цeлocтнocти фaйлa пocлe oбнoвлeния, a тaкжe пpoвepкa нa иcпoльзoвaниe пocлeднeй вepcии cкpиптa.
- Пoддepжкa Claymore Neoscrypt и Ethminer.
- Пoддepжкa oтoбpaжeния инфopмaции для Ccminer lux.
- Oптимизaция oтoбpaжeния инфopмaции для Ccminer.
- Дoпoлнeны и иcпpaвлeны oбpaбoтчики oшибoк Ccminer, Bminer.
- Дoбaвлeны бoты для бoлee быcтpoй oбpaбoтки oнлaйн cepвepa.
- Дoбaвлeнa пpoвepкa нa oтпpaвкy пycтыx cooбщeний.
- Heмнoгo yдaлocь ycкopить чтeниe лoгoв для Claymore.
- Улyчшeния aпдeйтepa.
- Meлкиe и кocмeтичecкиe иcпpaвлeния.
Changelog - 1.9.2 - 1.9.3 - 1.9.4- Added support for displaying more video cards in the claymore.
- Increased the wait logging timer for 5 seconds.
- Reduced the wait time before rebooting the computer in the event of a connection loss for 5 minutes.
- Added the ability to overwrite the number of servers that were initially assigned, and not always 5.
- Added the mode internetcheck = 2 - disables the switching of servers but reserves the Internet check.
- Changes on the server side of the bot. Run a new version of the command server.
- Now Bminer correctly sees and recognizes errors.
- Improved recognition of Rig names.
- The processing of Telegram commands is accelerated.
- The script now takes commands one at a time (one after another), not just the last one.
- An error has been added to the handler for the Dstm and Ewbf miners.
- Fixed the pool command for Bminer.
- Added the ability to completely turn off all notifications in Telegram.
- The server and the miner will not switch if it already works on this option.
- Added file integrity check after update, as well as checking for the latest version of the script.
- Added support for Claymore Neoscrypt and Ethminer.
- Support for displaying information for Ccminer lux is provided.
- Optimization of information display for Ccminer.
- The error handlers Ccminer, Bminer are added and corrected.
- Added bots for faster processing of the online server.
- Added check for sending empty messages.
- A little has been done to speed up reading the logs for Claymore.
- Improvements of the updater.
- Minor and cosmetic corrections.
Ewbf Equihash - Ewbfautorun.bat
Dstm Equihash - Dstmautorun.bat
Claymore Equihash - ClayZECautorun.bat
Claymore CryptoNote - ClayXMRautorun.bat
Claymore NeoScrypt - ClayNSautorun.bat
Claymore Dagger-Hashimoto - ClayETHautorun.bat
Ethminer Dagger-Hashimoto - Ethrautorun.bat
Ccminer tpruvot, alexis (palgin), KlausT - CCautorun.bat
Premium price 0.05ZEC or eq in other cryptocurrency.
March 02, 2018, 09:35:33 PM
Thanks for the great program. It's extremely useful!
March 02, 2018, 03:54:17 PM
- The ability to update the script via the Telegram command is added.
Everything works great! One minor comment - in the Telegram bot, when you click "/" there is no "update" in the auto-complete options. Also, "update" is not in the "/help" result. I tried the "/update" and it worked just fine, it's just not in the list (using the premium 1.9.2). Thanks!
Fixed.
Today version 1.9.1 released!
Ewbf Equihash
Dstm Equihash
Claymore Equihash
Claymore CryptoNote
Claymore Dagger-Hashimoto
Ccminer tpruvot, alexis (palgin), KlausT
Ewbf Equihash
Dstm Equihash
Claymore Equihash
Claymore CryptoNote
Claymore Dagger-Hashimoto
Ccminer tpruvot, alexis (palgin), KlausT
Awesome little script Acrefawn!
You should make one for hsrminer!
Hi,
I use the PhoenixMiner.exe ver 2.6,
Link - https://bitcointalksearch.org/topic/phoenixminer-62c-fastest-ethereumethash-miner-with-lowest-devfee-winlinux-2647654
And HSRMINER
Link - https://bitcointalksearch.org/topic/hsrminer-nvidia-mining-software-for-various-algos-by-palginalexkap-2565979
which of the scripts versions will fit, if any? if not, I would LOVE if you'll support those in the very near future
Thanks again for the great work!
I use the PhoenixMiner.exe ver 2.6,
Link - https://bitcointalksearch.org/topic/phoenixminer-62c-fastest-ethereumethash-miner-with-lowest-devfee-winlinux-2647654
And HSRMINER
Link - https://bitcointalksearch.org/topic/hsrminer-nvidia-mining-software-for-various-algos-by-palginalexkap-2565979
which of the scripts versions will fit, if any? if not, I would LOVE if you'll support those in the very near future
Thanks again for the great work!
Thank you. Will think about it. On this weekends update i will share some other miners.
Hello!
Im got error use dstm 0.6 win10
zm.log is missing. Probably zm.exe hangs...
Im got error
use dstm 0.6 win10zm.log is missing. Probably zm.exe hangs...
Hello i hope you fixed this error, if not - contact me in Telegram t.me/acrefawn
How can we remove thE GPU | Power usage and Efficiency, its wasting of time.. ! I don't know why its keeping showing.
Dont understand what you are talking about. Sorry.
Can we get an option to disable the scheduled miner restart messages? I have multiple rigs with audio alerts on the telegram bot chat in case of problems so it is annoying to be spammed with "scheduled miner restart" and "miner started" messages only to find out there is nothing that requires my attention when I check the app.
Done. Will be added in 1.9.4 version.
Hi, do you planning to add phoenix miner support?
Yes.
Hi,
I have a bug with the Claymore zcash 12.6 version of autorun:
When Claymore generates the error "GPU 0 mining has stopped because -tstop temerature reached" autorun closes. Claymore continues running but autorun does not.
I have a bug with the Claymore zcash 12.6 version of autorun:
When Claymore generates the error "GPU 0 mining has stopped because -tstop temerature reached" autorun closes. Claymore continues running but autorun does not.
Thank you for report I will test it now and fix.
Hi,
Nice work on bat
Im testing the functionality, but i have two doubts.
If i want to add an backup pool i add this on Config_xClay:
# =================================================== [Miner]
# Set the main server mining command here to auto-create Clay_miner.bat file if it is missing or wrong. [keep default order]
commandserver1=NsGpuCNMiner.exe -xpool stratum+tcp://eu.xxxxmine.graft.network:4444 -xwal xxxx -xpsw x -allpools 1 -tstop 80 -logfile miner.log -wd 0
# When the main server fails, ClayXMRautorun.bat will switch to the additional server below immediately. [in order]
commandserver2=NsGpuCNMiner.exe -xpool stratum+tcp://pool.graftpool.online:4444 -xwal xxxx -xpsw x -allpools 1 -tstop 80 -logfile miner.log -wd 0
# Configure miner command here. Old Clay_miner.bat will be removed and a new one will be created with this value. [keep default order] internetcheck=1 required.
# The default number of servers is 5, however, you can add or remove as many as you need. e.g. you can have servers 1 2 3 or you can have 1 2 3 4 5 6 7 8 9. There is no upper limit - e.g. you can have 1000 if you want. The minimum is 1.
# =================================================== [Overclock program]
But when for example i put purposely an error in my first server1, the program doesn t shift to commandserver2!
Its ok my syntax? or have to change the ClayXMRautorun instead of Config_xClay..
Another thing is If i tried to change :
# Set how many GPU devices are enabled.
gpus=1
and have 8 gpus, doens t gives me any error too..
and why it comes with default valor of 0, and worked good with 0 value? Even if i have more gpus installed..
Regards
Nice work on bat
Im testing the functionality, but i have two doubts.
If i want to add an backup pool i add this on Config_xClay:
# =================================================== [Miner]
# Set the main server mining command here to auto-create Clay_miner.bat file if it is missing or wrong. [keep default order]
commandserver1=NsGpuCNMiner.exe -xpool stratum+tcp://eu.xxxxmine.graft.network:4444 -xwal xxxx -xpsw x -allpools 1 -tstop 80 -logfile miner.log -wd 0
# When the main server fails, ClayXMRautorun.bat will switch to the additional server below immediately. [in order]
commandserver2=NsGpuCNMiner.exe -xpool stratum+tcp://pool.graftpool.online:4444 -xwal xxxx -xpsw x -allpools 1 -tstop 80 -logfile miner.log -wd 0
# Configure miner command here. Old Clay_miner.bat will be removed and a new one will be created with this value. [keep default order] internetcheck=1 required.
# The default number of servers is 5, however, you can add or remove as many as you need. e.g. you can have servers 1 2 3 or you can have 1 2 3 4 5 6 7 8 9. There is no upper limit - e.g. you can have 1000 if you want. The minimum is 1.
# =================================================== [Overclock program]
But when for example i put purposely an error in my first server1, the program doesn t shift to commandserver2!
Its ok my syntax? or have to change the ClayXMRautorun instead of Config_xClay..
Another thing is If i tried to change :
# Set how many GPU devices are enabled.
gpus=1
and have 8 gpus, doens t gives me any error too..
and why it comes with default valor of 0, and worked good with 0 value?
Even if i have more gpus installed..Regards
Thank you!
1) For test server failover put an mistake in server name or server port in commandserver1, then wait for 2 minutes, then server will be switched. Program can recognize if it is server problem or internet. So just cable disconnecting will not help to test. And program wait for 2 minutes because of miner self reconnect period.
2) Because if you use gpus=0 it will count them automatically, and if you use gpus=NUMBER program knows EXACT value. About "doesnt gives me any error" you probably disabled allowrestart function.
Hi Acrefawn,
Thanks for your excellent work here.
I am finding that I am experiencing a couple of issues with this using DSTM's miner 0.5.6 with Autorun ver 1.8.1.
Issue 1:
When the server changes difficulty on several GPU's at once, there is sometimes a significant, temporary hashrate drop which autorun incorrectly identifies as a real problem and restarts the miner.
Issue 2:
I regularly receive the "Loaded too many GPUs" report on only one of my rigs.
This is a 7 card rig but for some reason Autorun is detecting 14/7 cards despite the problem not actually existing in the miner.
I suspect that this is related to an erroneous log output from the miner as follows; note that the miner has reported two iterations of each card before outputting the "average" line (the last line of the extract below)
2017-12-07 9:39:51 AM| ========== Sol/s: 2898.4 Sol/W: 3.89 Avg: 2874.0 I/s: 1565.8 Sh: 39.13 1.00 357
2017-12-07 9:39:51 AM|# GPU4 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:53 AM|# GPU5 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:55 AM|# GPU6 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:58 AM| GPU0 63C Sol/s: 291.4 Sol/W: 3.94 Avg: 432.1 I/s: 158.8 Sh: 4.97 1.00 349
2017-12-07 9:39:59 AM| GPU1 67C Sol/s: 279.9 Sol/W: 3.80 Avg: 419.6 I/s: 149.5 Sh: 5.31 1.00 352 ++
2017-12-07 9:40:01 AM| GPU2 54C Sol/s: 295.4 Sol/W: 3.99 Avg: 424.5 I/s: 154.2 Sh: 3.82 1.00 344
2017-12-07 9:40:03 AM| GPU3 66C Sol/s: 284.6 Sol/W: 3.74 Avg: 421.5 I/s: 152.0 Sh: 6.15 1.00 375 +
2017-12-07 9:40:05 AM| GPU4 70C Sol/s: 298.7 Sol/W: 3.83 Avg: 435.5 I/s: 159.8 Sh: 6.31 1.00 416
2017-12-07 9:40:05 AM|> GPU0 62C Sol/s: 229.0 Sol/W: 2.06 Avg: 229.0 I/s: 121.5 Sh: 5.99 1.00 343 ++
2017-12-07 9:40:06 AM|> GPU1 67C Sol/s: 225.1 Sol/W: 2.02 Avg: 225.1 I/s: 120.1 Sh: 2.96 1.00 344 +
2017-12-07 9:40:08 AM|> GPU2 54C Sol/s: 219.8 Sol/W: 2.06 Avg: 219.8 I/s: 119.7 Sh: 5.99 1.00 352 ++
2017-12-07 9:40:09 AM| GPU5 71C Sol/s: 276.1 Sol/W: 3.73 Avg: 437.3 I/s: 148.8 Sh: 7.44 1.00 344 +
2017-12-07 9:40:10 AM|> GPU3 66C Sol/s: 222.7 Sol/W: 1.95 Avg: 222.7 I/s: 119.4 Sh: 5.81 1.00 351 ++
2017-12-07 9:40:11 AM| GPU6 49C Sol/s: 162.0 Sol/W: 3.69 Avg: 248.7 I/s: 84.8 Sh: 3.79 0.96 360 +
2017-12-07 9:40:11 AM| ========== Sol/s: 1888.2 Sol/W: 3.82 Avg: 2819.2 I/s: 1008.0 Sh: 37.79 1.00 362
As a side note;
Inputting the real "average" hashrate into the config.bat file tends to cause autorun to detect too many instances of low hashrate because any reported hashrate below the average appears to be considered an error.
I'd suggest this parameter would be better if named "minimum acceptable hashrate" or similar
or
Add a configurable tolerance to the acceptable range of hashrates. ie, within (say) 10% of the average is -not- considered to be a hashrate error.
Further, (just an idea) rather than the user nominating the average hashrate, perhaps autorun could automatically detect the actual average hashrate from all log files and store it in the config.bat file.
Happy to discuss this with you if the issue isn't clear from my description. Sorry that my input is not in the form of code change suggestions, it's beyond my capability.
That said, using this script has been educational and I'm thankful that you have released it open source.
Thanks again.
Thanks for your excellent work here.
I am finding that I am experiencing a couple of issues with this using DSTM's miner 0.5.6 with Autorun ver 1.8.1.
Issue 1:
When the server changes difficulty on several GPU's at once, there is sometimes a significant, temporary hashrate drop which autorun incorrectly identifies as a real problem and restarts the miner.
Issue 2:
I regularly receive the "Loaded too many GPUs" report on only one of my rigs.
This is a 7 card rig but for some reason Autorun is detecting 14/7 cards despite the problem not actually existing in the miner.
I suspect that this is related to an erroneous log output from the miner as follows; note that the miner has reported two iterations of each card before outputting the "average" line (the last line of the extract below)
2017-12-07 9:39:51 AM| ========== Sol/s: 2898.4 Sol/W: 3.89 Avg: 2874.0 I/s: 1565.8 Sh: 39.13 1.00 357
2017-12-07 9:39:51 AM|# GPU4 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:53 AM|# GPU5 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:55 AM|# GPU6 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:58 AM| GPU0 63C Sol/s: 291.4 Sol/W: 3.94 Avg: 432.1 I/s: 158.8 Sh: 4.97 1.00 349
2017-12-07 9:39:59 AM| GPU1 67C Sol/s: 279.9 Sol/W: 3.80 Avg: 419.6 I/s: 149.5 Sh: 5.31 1.00 352 ++
2017-12-07 9:40:01 AM| GPU2 54C Sol/s: 295.4 Sol/W: 3.99 Avg: 424.5 I/s: 154.2 Sh: 3.82 1.00 344
2017-12-07 9:40:03 AM| GPU3 66C Sol/s: 284.6 Sol/W: 3.74 Avg: 421.5 I/s: 152.0 Sh: 6.15 1.00 375 +
2017-12-07 9:40:05 AM| GPU4 70C Sol/s: 298.7 Sol/W: 3.83 Avg: 435.5 I/s: 159.8 Sh: 6.31 1.00 416
2017-12-07 9:40:05 AM|> GPU0 62C Sol/s: 229.0 Sol/W: 2.06 Avg: 229.0 I/s: 121.5 Sh: 5.99 1.00 343 ++
2017-12-07 9:40:06 AM|> GPU1 67C Sol/s: 225.1 Sol/W: 2.02 Avg: 225.1 I/s: 120.1 Sh: 2.96 1.00 344 +
2017-12-07 9:40:08 AM|> GPU2 54C Sol/s: 219.8 Sol/W: 2.06 Avg: 219.8 I/s: 119.7 Sh: 5.99 1.00 352 ++
2017-12-07 9:40:09 AM| GPU5 71C Sol/s: 276.1 Sol/W: 3.73 Avg: 437.3 I/s: 148.8 Sh: 7.44 1.00 344 +
2017-12-07 9:40:10 AM|> GPU3 66C Sol/s: 222.7 Sol/W: 1.95 Avg: 222.7 I/s: 119.4 Sh: 5.81 1.00 351 ++
2017-12-07 9:40:11 AM| GPU6 49C Sol/s: 162.0 Sol/W: 3.69 Avg: 248.7 I/s: 84.8 Sh: 3.79 0.96 360 +
2017-12-07 9:40:11 AM| ========== Sol/s: 1888.2 Sol/W: 3.82 Avg: 2819.2 I/s: 1008.0 Sh: 37.79 1.00 362
As a side note;
Inputting the real "average" hashrate into the config.bat file tends to cause autorun to detect too many instances of low hashrate because any reported hashrate below the average appears to be considered an error.
I'd suggest this parameter would be better if named "minimum acceptable hashrate" or similar
or
Add a configurable tolerance to the acceptable range of hashrates. ie, within (say) 10% of the average is -not- considered to be a hashrate error.
Further, (just an idea) rather than the user nominating the average hashrate, perhaps autorun could automatically detect the actual average hashrate from all log files and store it in the config.bat file.
Happy to discuss this with you if the issue isn't clear from my description. Sorry that my input is not in the form of code change suggestions, it's beyond my capability.
That said, using this script has been educational and I'm thankful that you have released it open source.
Thanks again.
Hi
Firstly, I would like to thank you for this wonderful script. You are awesome.
I've been testing it for the past few hours and I came across the same problem as posted above.
I am using MiningPoolHub and auto-switching coins within the Equihash algorithm using DSTM on Windows 10 and Nvidia 1070s.
When the difficulty changes or when DSTM is switching from one coin to another, my hashrate temporarily drops by 2000 sol/s for about 15 seconds but the script recognizes it as an error and begins to restart the miner. If I change the "average hashrate" to something very low, it won't make any sense because then there would be no point in monitoring it. Is there anyway I can add a delay or a temporary buffer for those 15 seconds while the difficulty is changing or when it's changing the coin being mined?
I appreciate all of your help and thank you for making this script. Once this gets resolved, I will donate and go for the premium
Thank you for detailed report, I will think about it. But in generally it is hard to realyse because we cant predict hashrate drop timeout or value. So your suggestion may not work...
Hi,
I use the PhoenixMiner.exe ver 2.7b,
Link - https://bitcointalksearch.org/topic/phoenixminer-62c-fastest-ethereumethash-miner-with-lowest-devfee-winlinux-2647654
which of the scripts versions will fit, if any? if not, I would LOVE if you'll support those in the very near future
Thanks again for the great work!
I use the PhoenixMiner.exe ver 2.7b,
Link - https://bitcointalksearch.org/topic/phoenixminer-62c-fastest-ethereumethash-miner-with-lowest-devfee-winlinux-2647654
which of the scripts versions will fit, if any? if not, I would LOVE if you'll support those in the very near future
Thanks again for the great work!
+1
same here ..
if you can limit log file size,
i dont have big disk ...
Do not worry program self clean Logs and Screenshots folders.
March 01, 2018, 04:54:17 AM
Hi,
I use the PhoenixMiner.exe ver 2.7b,
Link - https://bitcointalksearch.org/topic/phoenixminer-62c-fastest-ethereumethash-miner-with-lowest-devfee-winlinux-2647654
which of the scripts versions will fit, if any? if not, I would LOVE if you'll support those in the very near future
Thanks again for the great work!
I use the PhoenixMiner.exe ver 2.7b,
Link - https://bitcointalksearch.org/topic/phoenixminer-62c-fastest-ethereumethash-miner-with-lowest-devfee-winlinux-2647654
which of the scripts versions will fit, if any? if not, I would LOVE if you'll support those in the very near future
Thanks again for the great work!
+1
same here ..
if you can limit log file size,
i dont have big disk ...
February 27, 2018, 10:18:21 PM
Hi Acrefawn,
Thanks for your excellent work here.
I am finding that I am experiencing a couple of issues with this using DSTM's miner 0.5.6 with Autorun ver 1.8.1.
Issue 1:
When the server changes difficulty on several GPU's at once, there is sometimes a significant, temporary hashrate drop which autorun incorrectly identifies as a real problem and restarts the miner.
Issue 2:
I regularly receive the "Loaded too many GPUs" report on only one of my rigs.
This is a 7 card rig but for some reason Autorun is detecting 14/7 cards despite the problem not actually existing in the miner.
I suspect that this is related to an erroneous log output from the miner as follows; note that the miner has reported two iterations of each card before outputting the "average" line (the last line of the extract below)
2017-12-07 9:39:51 AM| ========== Sol/s: 2898.4 Sol/W: 3.89 Avg: 2874.0 I/s: 1565.8 Sh: 39.13 1.00 357
2017-12-07 9:39:51 AM|# GPU4 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:53 AM|# GPU5 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:55 AM|# GPU6 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:58 AM| GPU0 63C Sol/s: 291.4 Sol/W: 3.94 Avg: 432.1 I/s: 158.8 Sh: 4.97 1.00 349
2017-12-07 9:39:59 AM| GPU1 67C Sol/s: 279.9 Sol/W: 3.80 Avg: 419.6 I/s: 149.5 Sh: 5.31 1.00 352 ++
2017-12-07 9:40:01 AM| GPU2 54C Sol/s: 295.4 Sol/W: 3.99 Avg: 424.5 I/s: 154.2 Sh: 3.82 1.00 344
2017-12-07 9:40:03 AM| GPU3 66C Sol/s: 284.6 Sol/W: 3.74 Avg: 421.5 I/s: 152.0 Sh: 6.15 1.00 375 +
2017-12-07 9:40:05 AM| GPU4 70C Sol/s: 298.7 Sol/W: 3.83 Avg: 435.5 I/s: 159.8 Sh: 6.31 1.00 416
2017-12-07 9:40:05 AM|> GPU0 62C Sol/s: 229.0 Sol/W: 2.06 Avg: 229.0 I/s: 121.5 Sh: 5.99 1.00 343 ++
2017-12-07 9:40:06 AM|> GPU1 67C Sol/s: 225.1 Sol/W: 2.02 Avg: 225.1 I/s: 120.1 Sh: 2.96 1.00 344 +
2017-12-07 9:40:08 AM|> GPU2 54C Sol/s: 219.8 Sol/W: 2.06 Avg: 219.8 I/s: 119.7 Sh: 5.99 1.00 352 ++
2017-12-07 9:40:09 AM| GPU5 71C Sol/s: 276.1 Sol/W: 3.73 Avg: 437.3 I/s: 148.8 Sh: 7.44 1.00 344 +
2017-12-07 9:40:10 AM|> GPU3 66C Sol/s: 222.7 Sol/W: 1.95 Avg: 222.7 I/s: 119.4 Sh: 5.81 1.00 351 ++
2017-12-07 9:40:11 AM| GPU6 49C Sol/s: 162.0 Sol/W: 3.69 Avg: 248.7 I/s: 84.8 Sh: 3.79 0.96 360 +
2017-12-07 9:40:11 AM| ========== Sol/s: 1888.2 Sol/W: 3.82 Avg: 2819.2 I/s: 1008.0 Sh: 37.79 1.00 362
As a side note;
Inputting the real "average" hashrate into the config.bat file tends to cause autorun to detect too many instances of low hashrate because any reported hashrate below the average appears to be considered an error.
I'd suggest this parameter would be better if named "minimum acceptable hashrate" or similar
or
Add a configurable tolerance to the acceptable range of hashrates. ie, within (say) 10% of the average is -not- considered to be a hashrate error.
Further, (just an idea) rather than the user nominating the average hashrate, perhaps autorun could automatically detect the actual average hashrate from all log files and store it in the config.bat file.
Happy to discuss this with you if the issue isn't clear from my description. Sorry that my input is not in the form of code change suggestions, it's beyond my capability.
That said, using this script has been educational and I'm thankful that you have released it open source.
Thanks again.
Thanks for your excellent work here.
I am finding that I am experiencing a couple of issues with this using DSTM's miner 0.5.6 with Autorun ver 1.8.1.
Issue 1:
When the server changes difficulty on several GPU's at once, there is sometimes a significant, temporary hashrate drop which autorun incorrectly identifies as a real problem and restarts the miner.
Issue 2:
I regularly receive the "Loaded too many GPUs" report on only one of my rigs.
This is a 7 card rig but for some reason Autorun is detecting 14/7 cards despite the problem not actually existing in the miner.
I suspect that this is related to an erroneous log output from the miner as follows; note that the miner has reported two iterations of each card before outputting the "average" line (the last line of the extract below)
2017-12-07 9:39:51 AM| ========== Sol/s: 2898.4 Sol/W: 3.89 Avg: 2874.0 I/s: 1565.8 Sh: 39.13 1.00 357
2017-12-07 9:39:51 AM|# GPU4 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:53 AM|# GPU5 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:55 AM|# GPU6 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:58 AM| GPU0 63C Sol/s: 291.4 Sol/W: 3.94 Avg: 432.1 I/s: 158.8 Sh: 4.97 1.00 349
2017-12-07 9:39:59 AM| GPU1 67C Sol/s: 279.9 Sol/W: 3.80 Avg: 419.6 I/s: 149.5 Sh: 5.31 1.00 352 ++
2017-12-07 9:40:01 AM| GPU2 54C Sol/s: 295.4 Sol/W: 3.99 Avg: 424.5 I/s: 154.2 Sh: 3.82 1.00 344
2017-12-07 9:40:03 AM| GPU3 66C Sol/s: 284.6 Sol/W: 3.74 Avg: 421.5 I/s: 152.0 Sh: 6.15 1.00 375 +
2017-12-07 9:40:05 AM| GPU4 70C Sol/s: 298.7 Sol/W: 3.83 Avg: 435.5 I/s: 159.8 Sh: 6.31 1.00 416
2017-12-07 9:40:05 AM|> GPU0 62C Sol/s: 229.0 Sol/W: 2.06 Avg: 229.0 I/s: 121.5 Sh: 5.99 1.00 343 ++
2017-12-07 9:40:06 AM|> GPU1 67C Sol/s: 225.1 Sol/W: 2.02 Avg: 225.1 I/s: 120.1 Sh: 2.96 1.00 344 +
2017-12-07 9:40:08 AM|> GPU2 54C Sol/s: 219.8 Sol/W: 2.06 Avg: 219.8 I/s: 119.7 Sh: 5.99 1.00 352 ++
2017-12-07 9:40:09 AM| GPU5 71C Sol/s: 276.1 Sol/W: 3.73 Avg: 437.3 I/s: 148.8 Sh: 7.44 1.00 344 +
2017-12-07 9:40:10 AM|> GPU3 66C Sol/s: 222.7 Sol/W: 1.95 Avg: 222.7 I/s: 119.4 Sh: 5.81 1.00 351 ++
2017-12-07 9:40:11 AM| GPU6 49C Sol/s: 162.0 Sol/W: 3.69 Avg: 248.7 I/s: 84.8 Sh: 3.79 0.96 360 +
2017-12-07 9:40:11 AM| ========== Sol/s: 1888.2 Sol/W: 3.82 Avg: 2819.2 I/s: 1008.0 Sh: 37.79 1.00 362
As a side note;
Inputting the real "average" hashrate into the config.bat file tends to cause autorun to detect too many instances of low hashrate because any reported hashrate below the average appears to be considered an error.
I'd suggest this parameter would be better if named "minimum acceptable hashrate" or similar
or
Add a configurable tolerance to the acceptable range of hashrates. ie, within (say) 10% of the average is -not- considered to be a hashrate error.
Further, (just an idea) rather than the user nominating the average hashrate, perhaps autorun could automatically detect the actual average hashrate from all log files and store it in the config.bat file.
Happy to discuss this with you if the issue isn't clear from my description. Sorry that my input is not in the form of code change suggestions, it's beyond my capability.
That said, using this script has been educational and I'm thankful that you have released it open source.
Thanks again.
Hi
Firstly, I would like to thank you for this wonderful script. You are awesome.
I've been testing it for the past few hours and I came across the same problem as posted above.
I am using MiningPoolHub and auto-switching coins within the Equihash algorithm using DSTM on Windows 10 and Nvidia 1070s.
When the difficulty changes or when DSTM is switching from one coin to another, my hashrate temporarily drops by 2000 sol/s for about 15 seconds but the script recognizes it as an error and begins to restart the miner. If I change the "average hashrate" to something very low, it won't make any sense because then there would be no point in monitoring it. Is there anyway I can add a delay or a temporary buffer for those 15 seconds while the difficulty is changing or when it's changing the coin being mined?
I appreciate all of your help and thank you for making this script. Once this gets resolved, I will donate and go for the premium
Jump to: