[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[zloyneo]

Version 6.4.5 (Development preview of 6.5)

 ASIC mining
  - Feature to display MAC address of External Miners without using ARP cache. Can be enabled via the Options dialog, Mining Settings section.
 Integration
  - Added Block Explorer for JEM
 User interface
  - Web interface: Sorting by column in the miner list
  - Web interface: Better column width used for notifications
 Mining software
  - Claymore Ethereum Miner 14.6
  - Z-enemy miner 2.0
  - SrbMiner 1.8.9
  - WildRig Miner 0.17.2


To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates.

Direct download links if needed:
https://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
https://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi

Good afternoon. automatic agent update does not work.

There are no logs in the new Claymore.

Hi,
1) If the automatic update fail you can try to manually use the link above to upgrade. If it still doesn't work because of the uninstallation process, you can force the uninstallation using this tool from Microsoft:
https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed

2) If you run Claymore miner with Administrator privileges, Awesome Miner should still be able to show the log on the Console tab. The log file is also written to the file 'console_output.txt' located in the same folder as the Claymore software.

1) If I click "Upgrade Remote Agent" is upgrade previous version

2) Yes, but Claymore Old logs are not saved

Thanks for the updated details:
1) I would actually recommend a reboot of this remote computer to begin with. In case there are pending Windows Updates to be installed on next reboot, these can prevent other installers from running correctly.
If this didn't solve the problem, please uninstall Remote Agent manually and then install it again using the links above.

2) Right now the log file will only contain the latest log of the most recently started Claymore process. Once you start the process the next time it will clear the log. This behavior cannot be changed in Awesome Miner right now.

2) How do I diagnose which graphics card has failed? if I do not see the old log, as the miner program automatically restarts?

3) How to configure so that when unsuccessful restarts of the miner program, awesome rebooted rig ?

[JimBrown462]

Hi Patrike,

I've been away for a couple of weeks. Awesome Miner happily churned away without any issues. Love the program!

Just updated everything to the latest versions and ran into a small issue when benchmarking. It seems that the long term benchmarks (10 minutes, 20 minutes, 1 hour, etc) are quitting after a few minutes, similar to the "Fast" or "Precise" benchmarks.

The following is (I think) the relevant log entries:

Code:

2019-06-02 9:39:21 AM.202 [001] [S]Running benchmark for miner: [ManagedMiner#5 - Desktop]
2019-06-02 9:39:21 AM.206 [057] [S]PoolServiceManager.GetAsPools, pools: 339
2019-06-02 9:39:21 AM.206 [057] [S]PoolServiceManager.GetAsPools, disabled for profit switching: nicehash.com:3334, SHA256
2019-06-02 9:39:21 AM.206 [057] [S]PoolServiceManager.GetAllEnabledPools, pools: 35
2019-06-02 9:39:21 AM.206 [057] [S]PoolServiceManager.GetAllEnabledPools, SinglePoolCM predefined count: 342
2019-06-02 9:39:21 AM.221 [057] [S]Prepare benchmarking X16r. Engine Type: CcCryptoDredgeEngine, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable: 
2019-06-02 9:39:21 AM.226 [057] [S][ManagedMiner#5 - Desktop] Run Miner Command: Benchmark
2019-06-02 9:39:21 AM.226 [037] [S]Command request: Benchmark
2019-06-02 9:39:21 AM.226 [007] [S][ManagedMiner#5 - Desktop] Execute command: Benchmark
2019-06-02 9:39:21 AM.226 [059] [S]Benchmark: Starting Engine Type: CcCryptoDredgeEngine, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable: , Timeout: 600
2019-06-02 9:39:21 AM.226 [059] [S][ManagedMiner#5 - Desktop] Starting Mining Software
2019-06-02 9:39:21 AM.226 [059] [S][ManagedMiner#5 - Desktop] Setting up Miner Engine. Instance: 1
2019-06-02 9:39:21 AM.226 [059] [S][ManagedMiner#5 - Desktop] Engine Type: CcCryptoDredgeEngine, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable: 
2019-06-02 9:39:21 AM.226 [059] [S]EngineSetup: CcCryptoDredgeEngine
2019-06-02 9:39:21 AM.233 [059] [S][ManagedMiner#5 - Desktop] Executing batch commands as admin: "C:\Program Files (x86)\MSI Afterburner\MSIAfterburner.exe" -Profile1
2019-06-02 9:39:21 AM.234 [059] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.IMaintenanceService
2019-06-02 9:39:21 AM.248 [059] [S]Execute task successfully registered: C:\Users\jbwin\AppData\Local\AwesomeMiner\cryptodredge_0.19.1_cuda_10.0_windows_1\CryptoDredge_0.19.1\awesome.bat
2019-06-02 9:39:21 AM.305 [059] [S]Executed task successfully: C:\Users\jbwin\AppData\Local\AwesomeMiner\cryptodredge_0.19.1_cuda_10.0_windows_1\CryptoDredge_0.19.1\awesome.bat
2019-06-02 9:39:22 AM.324 [059] [S][ManagedMiner#5 - Desktop] Sucessfully executed batch commands
2019-06-02 9:39:22 AM.324 [059] [S][ManagedMiner#5 - Desktop] : GetStaticSortedPools, Enginetype: CcCryptoDredgeEngine, Algorithms: Allium, Argon2dDyn, Argon2d250, Argon2d4096, Bcd, Bitcore, Blake2s, CryptoNightLiteV7, CryptoNightFast2, CryptoNightGpu, CryptoNightHaven, CryptoNightHeavy, CryptoNightV8, CryptoNightSaber, CryptoNightStelliteV4, CryptoNightTurtle, CuckaRoo29, Cuckoo, Hmq1725, Lyra2REv3, Lyra2z, Lyra2zz, Mtp, NeoScrypt, Phi2, Skunkhash, Tribus, X16r, X16rt, X16s, X17, X21s, X22i
2019-06-02 9:39:22 AM.324 [059] [S][ManagedMiner#5 - Desktop] : Adding pool: stratum+tcp://x16r.usa.nicehash.com:3366
2019-06-02 9:39:22 AM.341 [059] [S]Device nVidia, GlobalId: 0, VendorId:0, PciBusId: 1, Name: GeForce RTX 2080 Ti
2019-06-02 9:39:22 AM.341 [059] [S]Select devices 0
2019-06-02 9:39:22 AM.341 [059] [S]Device selection ordering: Standard Device ID
2019-06-02 9:39:22 AM.341 [059] [S]Device selection input: Nvidia, ID type: VendorId, GlobalID List: 
2019-06-02 9:39:22 AM.341 [059] [S]Device selection, VendorID List: 0
2019-06-02 9:39:22 AM.343 [059] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.ISecurityService
2019-06-02 9:39:22 AM.379 [059] [S]Added rule for: C:\Users\jbwin\AppData\Local\AwesomeMiner\cryptodredge_0.19.1_cuda_10.0_windows_1\CryptoDredge_0.19.1\CryptoDredge.exe
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] Properties: (WindowMode: NoWindow, EngineType: CcCryptoDredgeEngine, IsProfitMiner: True)
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] ====================================================================================================
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] C:\Users\jbwin\AppData\Local\AwesomeMiner\cryptodredge_0.19.1_cuda_10.0_windows_1\CryptoDredge_0.19.1\CryptoDredge.exe  -R 5 -r 2 --timeout 65   -p c=BTC,d=10 -a x16r -i 7 -d 0 -o stratum+tcp://x16r.usa.nicehash.com:3366 -u 175TRmpBHbmnjhSkAydoDiqkdGnfGpMXpU --no-watchdog -b 0.0.0.0:4028
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] Configured command line: 
-R 5 -r 2 --timeout 65   -p c=BTC,d=10
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] ====================================================================================================
2019-06-02 9:39:22 AM.692 [059] [S]Saving configuration to: C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml.tmp
2019-06-02 9:39:22 AM.704 [059] [S]--> C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml
2019-06-02 9:39:22 AM.707 [059] [S][ManagedMiner#5 - Desktop] Mining Engine Process started, PID: 13208
2019-06-02 9:42:05 AM.707 [059] [E]System.NullReferenceException: Object reference not set to an instance of an object.
2019-06-02 9:42:05 AM.707 [059] [E]   at #=zemuLnLwVEmJAeDku1zK6N4B_dmsCMAzdJ2Q87w8le3sN.#=zYIfDucFn62epe5yedA==()
2019-06-02 9:42:05 AM.707 [059] [S]Benchmark: Stopping miner process ...
2019-06-02 9:42:05 AM.707 [059] [S][ManagedMiner#5 - Desktop] Prepare stopping Mining Software
2019-06-02 9:42:05 AM.707 [059] [S][ManagedMiner#5 - Desktop] Stopping Mining Software
2019-06-02 9:42:05 AM.707 [059] [S]  Closing process: 13208
2019-06-02 9:42:06 AM.209 [059] [S]  Process closed
2019-06-02 9:42:06 AM.209 [059] [S]Benchmark: Completed

Thanks,
...jim

EDIT: It also occurs on the "Fast" and "Precise" benchmarks, sometimes. Depends on how quickly the error occurs.

[patrike]

Hey Patrike,
Is there a way to set the Global Electricity Price (per kWh) via HTTP API?
Thank you!

There are no feature to set the value via API today.

You can set the price via the Rules, where you can use the Action called Set Property. You can for example use the rules to define different electricity prices depending on time or day. Rule actions can also be triggered via the API if needed.

I do understand this doesn't give as much flexibility as having an API method for setting an exact price from an external application. Please let me know if you still prefer the API method and I will look into supporting it when possible. Thanks!

[patrike]

Great update, I was wondering can you add feature to send keystrokes on console window on GPU miners?

(for example a Z command in claymor to initiate automatic drci)

This can come handy when doing diagnostics on rigs without a need to leave AM

Thanks for the suggestion - I've noted your request and will explore this.

[patrike]

Think there is a bug on tool "default pools via web"

When ever i apply a new default pool on reboot of S9 it activates ELPM

The most recent development versions of Awesome Miner has some internal changes to how the default pools are set on the Antminer via the web interface. It should also be a bit better at avoiding these kind of side effects. Can you please try if version 6.4.4 works better?

Got the latest version, still the same issue

Also it looks like its filling pool 3 config file with some part of command



I guess there is no chance to implement for the latest s9 firmware change pool option in AM?

Thanks for the update. I will take another look at this.

It's basically the difficulty to set only specific properties on this Antminer web page - as the page itself requires you to construct about 15 parameters with correct values and if any value is blank it can affect other parameters. Did you have 1, 2 or 3 default pools defined before you run into this issue?

[patrike]

1) If I click "Upgrade Remote Agent" is upgrade previous version

2) Yes, but Claymore Old logs are not saved

Thanks for the updated details:
1) I would actually recommend a reboot of this remote computer to begin with. In case there are pending Windows Updates to be installed on next reboot, these can prevent other installers from running correctly.
If this didn't solve the problem, please uninstall Remote Agent manually and then install it again using the links above.

2) Right now the log file will only contain the latest log of the most recently started Claymore process. Once you start the process the next time it will clear the log. This behavior cannot be changed in Awesome Miner right now.

2) How do I diagnose which graphics card has failed? if I do not see the old log, as the miner program automatically restarts?

3) How to configure so that when unsuccessful restarts of the miner program, awesome rebooted rig ?

2) I understand your point and I will add a new property for keeping these logs. This will make it possible to go back to older mining software log files and review what happend.

3) Please see "Example: Reboot GPU miner after several mining software crashes":
https://support.awesomeminer.com/a/solutions/articles/35000085907-rules-detect-mining-issues-and-automate-tasks

[patrike]

Hey Patrik,

I think I already asked this sometime before, but couldnt show a picture and details because this happens very rare.

- One or more cards are crashed. The mining window is still open, but isnt mining anymore.
- In AM it still shows "mining", but without any informations. AM will not restart that miner.
- The "GPU" tab is empty, also the "Pools" tab.

Is it possible to setup a rule to catch this? Or maybe AM can handle this automatically? I already tried some rules, but none works. Neither a single rule, or combined rules. For example:

- The trigger "Detect Miner State -> Mining" doesnt work.
- "Detect Device Count -> 0" doesnt work.
- "Power Usage -> 0" doesnt work.

I think because there is no miner API established because of the crash, even if the mining window is still open?

Is the predefined rule "Offline detection" also unable to find this case?

Next time this happens, could you please save the API report for me and I can review this scenario in more detail? You can generate the API report via the toolbar Tools -> API Report. Thanks!

[patrike]

Hi

It's currently only ASIC miners running the custom firmware AsicFW that can report power usage to Awesome Miner.

is there a way to see the total for each ASIC ?

I only see power for each board but no total for all three boards.

Thank you

Hi and thanks for your question.

It should be possible to see the miner total power usage in the Performance column for each miner in the Miners tab.
Can you please open the Options dialog, Profitability section and review the setting "Power usage mode". Can you please select the first or second item in the list here about "Actual usage"?

[patrike]

Thank you for adding SINOVATE X25X algorithm.

Keep up the good work, you are doing great Patrike.

Thanks for the nice feedback!

[patrike]

Hi Patrike,

I've been away for a couple of weeks. Awesome Miner happily churned away without any issues. Love the program!

Just updated everything to the latest versions and ran into a small issue when benchmarking. It seems that the long term benchmarks (10 minutes, 20 minutes, 1 hour, etc) are quitting after a few minutes, similar to the "Fast" or "Precise" benchmarks.

The following is (I think) the relevant log entries:

Thanks,
...jim

EDIT: It also occurs on the "Fast" and "Precise" benchmarks, sometimes. Depends on how quickly the error occurs.

Thanks Jim - I think I understand the scenario and will make a correction.

[Ferris419]

This is great to see you that you keep replying every feedbacks from 2014 to till now! Sad for me that I haven't tried the Awesome Miner, but today in a gossip, One of my friends suggested me to look at the Awesome Miner! So, I am here to learn about this miner and I will let you know my feedback after using it!

[GKumaran]

When I stop TeamRedMiner via Awesome Miner, the console window of TeamRedMiner says "Shutting down..." and then it will exit right away. Don't you get any console message at all?

Awesome Miner do have a behavior to kill the mining process if it didn't resond to the first request to shutdown. Maybe you can increase the time Awesome Miner will wait to see if TeamRedMiner just needed a bit more time to close down in a nice manner? Increase the value of: Options -> Mining Settings -> Wait for process before terminating.

Thanks for describing the case about dev fee as well. Awesome Miner doesn't have any feature today to do this on a mining software basis. Some mining software also have different dev fee depending on algorithm.

Yeah in my case, awesome miner does an insta-kill, i tried the timeout but no avail.
I tried closing TRM with a ctrl+c, works normally, the thread shudown and miner closes

I'm not able to reproduce the problem - although I do see that TeamRedMiner terminate very fast, it says "Shutting down" for a very show moment before doing so. Not easy to see that message because the process is so fast.

The fact that TeamRedMiner terminates very fast in your case as welll indicates that it did respond to the friendly Window close message from Awesome Miner. If it didn't respond, the close process would have taken about 5 seconds (configurable) before Awesome Miner took the next action where the process is killed.

To compare with SrbMiner, it says "Releasing GPU resources", but it takes 2 seconds so it's easier to see that message.

Awesome Miner is first sending a friendly request to close the mining window to the mining software - and this is the same for all mining software. You can try the same behavior by closing the mining software with the X-button in the  mining window. When you click X to close the window, it should be the same concept as when Awesome Miner requests to close the mining window. When I try this with TeamRedMiner and SrbMiner, I do get the exact same behavior as when Awesome Miner do it. Could you compare with this as well?

I tried logging the exit process, and confirm that the TRM isnt shutting down normally.
TRM shutdown works only with Ctrl+C and not when clicking close in the CMD windows.

Feature Request : Allow Total miner power usage value as a property in the status object.
https://support.awesomeminer.com/support/solutions/articles/35000086023-customize-progress-field
Trying to bring this value to Progess Field

Code:

"Efficiency: " + Math.Round(status.KHashAvg / {{{status.PowerUsage}}}, 2) +" KHash/Watt"

Thanks !!

[joseph32]

Hey Patrik,

I think I already asked this sometime before, but couldnt show a picture and details because this happens very rare.

- One or more cards are crashed. The mining window is still open, but isnt mining anymore.
- In AM it still shows "mining", but without any informations. AM will not restart that miner.
- The "GPU" tab is empty, also the "Pools" tab.

Is it possible to setup a rule to catch this? Or maybe AM can handle this automatically? I already tried some rules, but none works. Neither a single rule, or combined rules. For example:

- The trigger "Detect Miner State -> Mining" doesnt work.
- "Detect Device Count -> 0" doesnt work.
- "Power Usage -> 0" doesnt work.

I think because there is no miner API established because of the crash, even if the mining window is still open?

Is the predefined rule "Offline detection" also unable to find this case?

Next time this happens, could you please save the API report for me and I can review this scenario in more detail? You can generate the API report via the toolbar Tools -> API Report. Thanks!

Hey Patrik,

yes, Offline Detection is also unable to find this. I tried every rule. If I see this again someday, I will send you the API report.

[sxemini]

Hi Patrike,
the blockchain driver will be unrecognized again.

[patrike]

When I stop TeamRedMiner via Awesome Miner, the console window of TeamRedMiner says "Shutting down..." and then it will exit right away. Don't you get any console message at all?

Awesome Miner do have a behavior to kill the mining process if it didn't resond to the first request to shutdown. Maybe you can increase the time Awesome Miner will wait to see if TeamRedMiner just needed a bit more time to close down in a nice manner? Increase the value of: Options -> Mining Settings -> Wait for process before terminating.

Thanks for describing the case about dev fee as well. Awesome Miner doesn't have any feature today to do this on a mining software basis. Some mining software also have different dev fee depending on algorithm.

Yeah in my case, awesome miner does an insta-kill, i tried the timeout but no avail.
I tried closing TRM with a ctrl+c, works normally, the thread shudown and miner closes

I'm not able to reproduce the problem - although I do see that TeamRedMiner terminate very fast, it says "Shutting down" for a very show moment before doing so. Not easy to see that message because the process is so fast.

The fact that TeamRedMiner terminates very fast in your case as welll indicates that it did respond to the friendly Window close message from Awesome Miner. If it didn't respond, the close process would have taken about 5 seconds (configurable) before Awesome Miner took the next action where the process is killed.

To compare with SrbMiner, it says "Releasing GPU resources", but it takes 2 seconds so it's easier to see that message.

Awesome Miner is first sending a friendly request to close the mining window to the mining software - and this is the same for all mining software. You can try the same behavior by closing the mining software with the X-button in the  mining window. When you click X to close the window, it should be the same concept as when Awesome Miner requests to close the mining window. When I try this with TeamRedMiner and SrbMiner, I do get the exact same behavior as when Awesome Miner do it. Could you compare with this as well?

I tried logging the exit process, and confirm that the TRM isnt shutting down normally.
TRM shutdown works only with Ctrl+C and not when clicking close in the CMD windows.

Feature Request : Allow Total miner power usage value as a property in the status object.
https://support.awesomeminer.com/support/solutions/articles/35000086023-customize-progress-field
Trying to bring this value to Progess Field

Code:

"Efficiency: " + Math.Round(status.KHashAvg / {{{status.PowerUsage}}}, 2) +" KHash/Watt"

Thanks !!

I think this is a TRM issue about not being consistent in how it closes down when using the X-button. I do get a close down message on my system when I do this - while you don't.

It's quite easy to expose the power usage so I can do that in one of the next versions. You can expect the following to work once available:
status.KHashAvg * 1000 / Math.Max(miningHelper.GetPowerUsage(), 1), 2)

As the Power Usage might be 0 in the very beginning, using the Math.Max operation will ensure that we never go below '1' in assumed power usage.

[patrike]

This is great to see you that you keep replying every feedbacks from 2014 to till now! Sad for me that I haven't tried the Awesome Miner, but today in a gossip, One of my friends suggested me to look at the Awesome Miner! So, I am here to learn about this miner and I will let you know my feedback after using it!

Thanks! All feedback and feature suggestions are of course welcome.

[patrike]

Hi Patrike,
the blockchain driver will be unrecognized again.

Although I don't recommend to use the AMD Blockchain Beta drivers in general, from what I can see you do get the AMD GPU's listed in Awesome Miner system tab even with this driver. The Native Overclocking will however not work.

Can you please let me know if it's a specific AMD GPU I should verify with, where it's not working in your case? Thanks!

[slysir]

https://github.com/technobyl/CryptoDredge/releases/tag/v0.20.1

CryptoDredge v0.20.1
@CryptoDredge CryptoDredge released this 13 hours ago

Fix MTP issue related to many rejected shares
Improve Argon2d algorithms
Other minor fixes
Assets
10
Pre-release
 v0.20.0
 d26110d
CryptoDredge v0.20.0
@CryptoDredge CryptoDredge released this 7 days ago · 2 commits to master since this release

Improve MTP algorithm
Improve Argon2d algorithm
New Argon2d (NIM) algorithm (Dumb mode only)
Add --hashrate option to set expected hashrate in kh/s and calculate start difficulty (Argon2d (NIM) only)
Add watchdog for Linux
Other minor fixes

[Lunga Chung]

Thanks for the update. I will take another look at this.

It's basically the difficulty to set only specific properties on this Antminer web page - as the page itself requires you to construct about 15 parameters with correct values and if any value is blank it can affect other parameters. Did you have 1, 2 or 3 default pools defined before you run into this issue?

I see the btc.com app for Antminer setup works fine (it can change LPM,ELPM mode and on latest firmware even OC) so until we  resolve this in AM this tool can be handy.

Yes all pools previously where defined via SSH, and after new firmware via web it just the web tool for default mining pools fill's in this data at pool 3 if you left it blank (no need for 3 pools anyway).

The part that I miss the most is ability to manually change mining pools on the fly or via profit switching rule. From this perspective on the latest firmware every time I would need to apply new default and reboot the miner  

[patrike]

Thanks for the update. I will take another look at this.

It's basically the difficulty to set only specific properties on this Antminer web page - as the page itself requires you to construct about 15 parameters with correct values and if any value is blank it can affect other parameters. Did you have 1, 2 or 3 default pools defined before you run into this issue?

I see the btc.com app for Antminer setup works fine (it can change LPM,ELPM mode and on latest firmware even OC) so until we  resolve this in AM this tool can be handy.

Yes all pools previously where defined via SSH, and after new firmware via web it just the web tool for default mining pools fill's in this data at pool 3 if you left it blank (no need for 3 pools anyway).

The part that I miss the most is ability to manually change mining pools on the fly or via profit switching rule. From this perspective on the latest firmware every time I would need to apply new default and reboot the miner  

Thanks for the details.

I just noticed that the Antminer S9 firmware from May 31st has a new concept for the low power mode settings as well. It's not configured the same was as the previous firmware.

Update: I did identify a case with the Antminer S9 firmware from March where Awesome Miner didn't set the parameters correctly if you only had 1 or 2 default pools defined. I will correct that scenario.