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

[akadamson]

Patrike,

Finally got a switch that I could evaluate.

Process from the log looks correct,it was
Found the stop profile
Applied it

BUT HERE IS the problem

Code:

5/6/2018 1:01:26 PM.324 [016] [S]Number of GPU commands: 24
5/6/2018 1:01:26 PM.324 [016] [S]Executing GPU clocking command: /setmacm, powerLimit0=70&coreClockBoost0=70000&memoryClockBoost0=710000&fanSpeed0=auto&powerLimit1=70&coreClockBoost1=70000&memoryClockBoost1=710000&fanSpeed1=auto&powerLimit2=70&coreClockBoost2=70000&memoryClockBoost2=710000&fanSpeed2=auto&powerLimit3=70&coreClockBoost3=70000&memoryClockBoost3=710000&fanSpeed3=auto&powerLimit4=70&coreClockBoost4=70000&memoryClockBoost4=710000&fanSpeed4=auto&powerLimit5=70&coreClockBoost5=70000&memoryClockBoost5=710000&fanSpeed5=auto
5/6/2018 1:01:26 PM.324 [016] [S]Preparing authentication header for MSI Afterburner requests: MSIAfterburner:17cc95b4017d496f82
5/6/2018 1:01:26 PM.324 [016] [E]System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
5/6/2018 1:01:26 PM.324 [016] [E]   at System.Net.HttpWebRequest.GetResponse()
   at PE.Infrastructure.Web.HttpRequestHelper.GetResponseString(HttpWebRequest req)
   at PE.Infrastructure.Web.HttpRequestHelper.PerformPost(String url, String postData, WebProxy proxy, CookieContainer cookieContainer, Dictionary`2 headerDict, Boolean throwException, Boolean preventUnescapeOfSlash, String contentType, String requestMethod)
5/6/2018 1:01:26 PM.324 [016] [S]ApplyGroupProfile End
5/6/2018 1:01:26 PM.449 [007] [I2]Done processing: 0, Time: 0 ms

So it wasn't applied.  Same was true for the other miner.

However issuing a manual change works, and sometimes and automatic one does... But usually it doesn't.  Thoughts?

UPDATE: I did find one thing wrong on my side, but it wouldn't have effected the above.  i'll continue to watch a s profit switches happen, seems there is something that is preventing the request for running and maybe a simple return x times should be invoked if that happens?

[madmossy]

Excellent update Patrike, appreciate the SRBMiner support

One thing I wouldnt mind though, the ability to manually configure the intensity, threads settings that go into the config file that gets created.

Also for the pools file, rather than have all pools (in a pool group for profit switching) be added, could it be only the pools that have the same algo?

I had a recent issue where a pool become unresponsive so the miner automatically switched to another pool in the pool group that was the 2nd best profit, this pool had a different algo so obviously gave me a string of errors.

[soothaa]

AwesomeMiner Coin Updater 0.8

• Major cleanup to the console output. Hopefully this should make errors much easier to understand
• Added support for the stupid Iquidus explorers that modify their difficulty with "POW/POS
• BETA(as if this thing isn't beta enough): Added a difficulty sniffer. This should hopefully be able to find the difficulty from almost any BlockExplorer now without having to explicitly add support.

You can find the latest update in my sig.

[Bimmber]

0.1 and 0.15, does not match 

https://s14.postimg.cc/5ocq52iy9/scr.jpg

[patrike]

Hello.
I have some questions:
1) If I have some rigs separated with gray IPs, so that I cannot access them from outside by ip/port. Is is possible to force remote agent on them to connect to AM, which has static white IP?
2) Is it possible to measure and display GPU/CPU usage in case if I use completely different miners (not ccminer or cpuminer forks). Not by miner api, but directly check cpu/gpu load? And use this data for rules.
3) How to make a rule:
Check gpu has load.
If >90% - do nothing.
If >5 but <90 -> check active GPU quantity compare with installed on rig and if some are down - reboot (hard reset with watchdog)
If <5 -> check internet if
(a)no internet -> do nothing. Just wait.
(b)internet Ok -> start some preset miner from the list for emergency cases. In a preset time (60minutes) try to return to normal miner.

Hi,

1) It's only possible to initiate the connection from Awesome Miner to Remote Agent. It's quite common to setup VPN solutions for these scenarios. In the future, it will also be possible to use the Cloud Services to solve these networking scenarios.

2) You will find the CPU / GPU information on the System tab at the bottom of the screen for the selected miner. This information is always available, even when no API is available or the mining process is stopped

3) The rules doesn't support the concepts of GPU load and Internet connection. The GPU load reported by the system isn't always an accurate way to know if the system is performing well.

If you are running with the profit switcher, you can enable "Ignore pools with no accepted shares" in Options dialog, Profit switching section. Then Awesome Miner will automatically change to another pool in case the first isn't performing as it should. The pool will be marked as failed for the number of miners you have configured, and then it will be used again.

You can have a similar setup with the predefined rule "Accept Progres" in Options dialog, Rules section, where you can take action in case the miner isn't making any process on the hashing or the mining pool is down. In this scenario there are however no way of automatically adding back the first pool once available again.

[patrike]

What is the best tool for managing miners such is common websites?

Awesome Miner is of course the best software for the purpose, with built-in support for several of the popular mining pools. Please let me know if there is any specific feature you have more questions on. Thanks!

[patrike]

Patrike,

Finally got a switch that I could evaluate.

Process from the log looks correct,it was
Found the stop profile
Applied it

BUT HERE IS the problem

Code:

5/6/2018 1:01:26 PM.324 [016] [S]Number of GPU commands: 24
5/6/2018 1:01:26 PM.324 [016] [S]Executing GPU clocking command: /setmacm, powerLimit0=70&coreClockBoost0=70000&memoryClockBoost0=710000&fanSpeed0=auto&powerLimit1=70&coreClockBoost1=70000&memoryClockBoost1=710000&fanSpeed1=auto&powerLimit2=70&coreClockBoost2=70000&memoryClockBoost2=710000&fanSpeed2=auto&powerLimit3=70&coreClockBoost3=70000&memoryClockBoost3=710000&fanSpeed3=auto&powerLimit4=70&coreClockBoost4=70000&memoryClockBoost4=710000&fanSpeed4=auto&powerLimit5=70&coreClockBoost5=70000&memoryClockBoost5=710000&fanSpeed5=auto
5/6/2018 1:01:26 PM.324 [016] [S]Preparing authentication header for MSI Afterburner requests: MSIAfterburner:17cc95b4017d496f82
5/6/2018 1:01:26 PM.324 [016] [E]System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
5/6/2018 1:01:26 PM.324 [016] [E]   at System.Net.HttpWebRequest.GetResponse()
   at PE.Infrastructure.Web.HttpRequestHelper.GetResponseString(HttpWebRequest req)
   at PE.Infrastructure.Web.HttpRequestHelper.PerformPost(String url, String postData, WebProxy proxy, CookieContainer cookieContainer, Dictionary`2 headerDict, Boolean throwException, Boolean preventUnescapeOfSlash, String contentType, String requestMethod)
5/6/2018 1:01:26 PM.324 [016] [S]ApplyGroupProfile End
5/6/2018 1:01:26 PM.449 [007] [I2]Done processing: 0, Time: 0 ms

So it wasn't applied.  Same was true for the other miner.

However issuing a manual change works, and sometimes and automatic one does... But usually it doesn't.  Thoughts?

UPDATE: I did find one thing wrong on my side, but it wouldn't have effected the above.  i'll continue to watch a s profit switches happen, seems there is something that is preventing the request for running and maybe a simple return x times should be invoked if that happens?

In the scenario above, MSI Afterburner gives an error (Internal Server Error) trying to apply the clocking settings. Does all the GPU's in the system support the parameters listed on the line above?

[patrike]

Excellent update Patrike, appreciate the SRBMiner support

One thing I wouldnt mind though, the ability to manually configure the intensity, threads settings that go into the config file that gets created.

Also for the pools file, rather than have all pools (in a pool group for profit switching) be added, could it be only the pools that have the same algo?

I had a recent issue where a pool become unresponsive so the miner automatically switched to another pool in the pool group that was the 2nd best profit, this pool had a different algo so obviously gave me a string of errors.

Thanks! On a Managed Miner, you will find a section called SRBMiner in the properties where you can put your own config.txt template to use. For profit switching, this isn't configurable yet, but I will add that in one of the next releases.

SRBMiner defines the algorithm to use (Cryptonight, V7, Lite, Heavy, ...) in the configuration file, so I assume the pools.txt file only can use pools based on this single algorithm. Awesome Miner automatically fill in the algorithm name in the configuration file, based on the algorithm of the first pool.

I will verify so the profit switcher doesn't try to add multiple types of algorithms for the pools in SRBMiner at once.

[patrike]

0.1 and 0.15, does not match 

In the Options dialog you specify the global setting for power cost and this one is being used almost everywhere.

At the bottom of the other page you have the option to do custom calculations where you manually enter hashrates, power usage and custom power costs. It's basically a profitability calculator.

In your case, you have selected to use a profit profile, and then this custom power cost field isn't even used and the power cost value is the Options dialog is used.

[abudfv2008]

1) It's only possible to initiate the connection from Awesome Miner to Remote Agent. It's quite common to setup VPN solutions for these scenarios. In the future, it will also be possible to use the Cloud Services to solve these networking scenarios.

2) You will find the CPU / GPU information on the System tab at the bottom of the screen for the selected miner. This information is always available, even when no API is available or the mining process is stopped

3) The rules doesn't support the concepts of GPU load and Internet connection. The GPU load reported by the system isn't always an accurate way to know if the system is performing well.

If you are running with the profit switcher, you can enable "Ignore pools with no accepted shares" in Options dialog, Profit switching section. Then Awesome Miner will automatically change to another pool in case the first isn't performing as it should. The pool will be marked as failed for the number of miners you have configured, and then it will be used again.

You can have a similar setup with the predefined rule "Accept Progres" in Options dialog, Rules section, where you can take action in case the miner isn't making any process on the hashing or the mining pool is down. In this scenario there are however no way of automatically adding back the first pool once available again.

2) Yes I know it's there. But why not to show it on dedicated tab? If I have rigs with supported miners and without them - it would be better to see all needed info without switching tabs.

3) OK. Is there any way to run a simple script, that will return some value and then do some action based on that value?
(For example to run nvidia-smi - get GPU load - calculate average and return it to AM, so that AM could switch/restart the miner.

4) No. I don't need profit switching. But I need to make sure that rigs are working and correctly respond to different troubles automatically.
a) miner crashing. Count number of restarts and if it is greater than 2-3 within 2-3minutes switch to failover mining list.
b) miner hanging and doing nothing. Get GPU load and if idle for 2-5minutes switch to failover mining list.
b) GPUs down. If down -> hardreset.
c) pool down.
d) internet down.
etc.

[madmossy]

Excellent update Patrike, appreciate the SRBMiner support

One thing I wouldnt mind though, the ability to manually configure the intensity, threads settings that go into the config file that gets created.

Also for the pools file, rather than have all pools (in a pool group for profit switching) be added, could it be only the pools that have the same algo?

I had a recent issue where a pool become unresponsive so the miner automatically switched to another pool in the pool group that was the 2nd best profit, this pool had a different algo so obviously gave me a string of errors.

Thanks! On a Managed Miner, you will find a section called SRBMiner in the properties where you can put your own config.txt template to use. For profit switching, this isn't configurable yet, but I will add that in one of the next releases.

SRBMiner defines the algorithm to use (Cryptonight, V7, Lite, Heavy, ...) in the configuration file, so I assume the pools.txt file only can use pools based on this single algorithm. Awesome Miner automatically fill in the algorithm name in the configuration file, based on the algorithm of the first pool.

I will verify so the profit switcher doesn't try to add multiple types of algorithms for the pools in SRBMiner at once.

Cheers thanks, the dev of SRBMiner will hopefully be adding command line support for options like intensity/threads etc soon so that should help.

I just deleted and made a profit switching profile again and the pools.txt file created had multiple algos included in it.

the algo according to config.txt is cryptonight-heavy

but the pools file has all possible algos included in it. Available algos are also not complete as its missing the option for cryptonight-light turtlecoin and cryptonight IPBC which are supported by SRBMiner but not available in AM.

[tf2addict]

Many pools use the password field for worker name instead of appending it to the user name.  Is there a way to handle that in A.M.?  If not I would suggest making it an option in the pool configuration.

[Allo-4ka]

Patrick
When working on more than two monitors, the window with the settings opens not where the awesomeminer himself is opened but on the one that is main in windows

[patrike]

1) It's only possible to initiate the connection from Awesome Miner to Remote Agent. It's quite common to setup VPN solutions for these scenarios. In the future, it will also be possible to use the Cloud Services to solve these networking scenarios.

2) You will find the CPU / GPU information on the System tab at the bottom of the screen for the selected miner. This information is always available, even when no API is available or the mining process is stopped

3) The rules doesn't support the concepts of GPU load and Internet connection. The GPU load reported by the system isn't always an accurate way to know if the system is performing well.

If you are running with the profit switcher, you can enable "Ignore pools with no accepted shares" in Options dialog, Profit switching section. Then Awesome Miner will automatically change to another pool in case the first isn't performing as it should. The pool will be marked as failed for the number of miners you have configured, and then it will be used again.

You can have a similar setup with the predefined rule "Accept Progres" in Options dialog, Rules section, where you can take action in case the miner isn't making any process on the hashing or the mining pool is down. In this scenario there are however no way of automatically adding back the first pool once available again.

2) Yes I know it's there. But why not to show it on dedicated tab? If I have rigs with supported miners and without them - it would be better to see all needed info without switching tabs.

3) OK. Is there any way to run a simple script, that will return some value and then do some action based on that value?
(For example to run nvidia-smi - get GPU load - calculate average and return it to AM, so that AM could switch/restart the miner.

4) No. I don't need profit switching. But I need to make sure that rigs are working and correctly respond to different troubles automatically.
a) miner crashing. Count number of restarts and if it is greater than 2-3 within 2-3minutes switch to failover mining list.
b) miner hanging and doing nothing. Get GPU load and if idle for 2-5minutes switch to failover mining list.
b) GPUs down. If down -> hardreset.
c) pool down.
d) internet down.
etc.

2) The GPU tab is currently based on the number of GPU's with their hashrates reported by the mining software. Without an API to the mining software this list will be empty as Awesome Miner doesn't know how many GPU's you are using.

Awesome Miner could of course be improved here by introducing some new concept where you can select how many GPU's to bring in via the existing feature "Map to system monitoring" for the scenario where no GPU's are available via the mining software.

3) This would be some custom implementation required. It's possible to control Awesome Miner from external scripts and application using the HTTP API:
http://www.awesomeminer.com/help/api.aspx

4a) You can use the rule trigger "Process failure" with "Mining process not running and too many failed attempts to restart". This will trigger after 3 crashes within a short period of time. The number 3 can be configured via the Options dialog, Advanced section, "Restart attempts on process crash".

4b - 4d) "Accept progress" should find these. Except "GPU's down", where it will depend on if the mining software can report this correctly. If it can, the predefined rule "Dead device detection" can be used.

[patrike]

Excellent update Patrike, appreciate the SRBMiner support

One thing I wouldnt mind though, the ability to manually configure the intensity, threads settings that go into the config file that gets created.

Also for the pools file, rather than have all pools (in a pool group for profit switching) be added, could it be only the pools that have the same algo?

I had a recent issue where a pool become unresponsive so the miner automatically switched to another pool in the pool group that was the 2nd best profit, this pool had a different algo so obviously gave me a string of errors.

Thanks! On a Managed Miner, you will find a section called SRBMiner in the properties where you can put your own config.txt template to use. For profit switching, this isn't configurable yet, but I will add that in one of the next releases.

SRBMiner defines the algorithm to use (Cryptonight, V7, Lite, Heavy, ...) in the configuration file, so I assume the pools.txt file only can use pools based on this single algorithm. Awesome Miner automatically fill in the algorithm name in the configuration file, based on the algorithm of the first pool.

I will verify so the profit switcher doesn't try to add multiple types of algorithms for the pools in SRBMiner at once.

Cheers thanks, the dev of SRBMiner will hopefully be adding command line support for options like intensity/threads etc soon so that should help.

I just deleted and made a profit switching profile again and the pools.txt file created had multiple algos included in it.

the algo according to config.txt is cryptonight-heavy

but the pools file has all possible algos included in it. Available algos are also not complete as its missing the option for cryptonight-light turtlecoin and cryptonight IPBC which are supported by SRBMiner but not available in AM.

I will include support for Cryptonight-LiteV7 and Cryptonight IPBC in the next release.

[patrike]

Many pools use the password field for worker name instead of appending it to the user name.  Is there a way to handle that in A.M.?  If not I would suggest making it an option in the pool configuration.

This is currently not supported in a good way, but will be in the future.

[patrike]

Patrick
When working on more than two monitors, the window with the settings opens not where the awesomeminer himself is opened but on the one that is main in windows

I think most dialogs uses Center Screen for their position. I noticed that the View Details dialog has a different behavior and should be centered relative the main window. Can you right click on a miner and select View Details, and see if this positioning mode works fine in your setup as well?

[patrike]

Awesome Miner Version 5.0

GPU mining
--- GPU selection in the Properties for Managed Miners and Managed Profit Miners to only include specific GPU's when mining
--- Display power usage on GPU tab when using Ccminer
--- Adjustment to XMRig miner command line by forcing either Cryptonight or CryptonightV7 as the auto detection in XMRig isn't always working
--- Automatically set command line argument --gpu-platform for Sgminer when AMD OpenCL platform isn't the only platform
--- Improved benchmarking to apply GPU clocking according to profit profile settings
ASIC mining
--- Antminer X3 Cryptonight ASIC support
--- Antminer B3 Tensority/Bytom ASIC support
--- Antminer T9+ chip temperature support
--- Innosilicon A8+ Cryptonight ASIC support
--- DragonMint B29 ASIC miner temperature support
--- Show Antminer chip temperature on the ASIC tab in addition to PCB temperature
--- Show both standard temperature and Antminer chip temperature on the Summary tab
Configuration
--- Prevent Windows from going into sleep mode while the application is running
--- Managed Templates can be configured with multiple exceptions in the new section Template settings
--- Managed Miners supports the same IP variables for worker name as External Miners
--- Additional settings for specifying duration of benchmarks
--- Bulk edit for configuration of algorithms in profit profiles
--- Bulk edit for Managed Miners and Managed Profit Miners
--- Improved bulk edit for External Miners where the setting to enable or disable 'Add to worker name' can be changed without modifying the worker name
--- Add support for variable [MinerDescription] in worker name field, to be replaced with the Description of the miner
--- Added a test button in dialog for wallet balance to verify the configuration
--- Added a default Block Explorer for BTCP for wallet balance
--- Default miner API timeout changed to 5 seconds and the graceful termination timeout for Managed Miners are also set to 5 seconds
--- Added Tensority, Blake256r8, Cryptonight-LiteV7 and Cryptonight IPBC algorithms
Rules and API
--- Added new rule action for applying GPU clocking profiles
--- Added API for listing all GPU's for a specific host
--- Added API for listing, adding and updating Managed Hosts
--- Added API for listing all algorithms
--- Added API for listing all mining software
--- Added API for listing all Pool Groups
--- Added API for listing, adding and updating Managed Miners
Profit switching
--- Improved profit switching to take pool priority into consideration for Custom Pools and use as secondary sort order after profitability
--- Profit switching information in the View Details dialog lists the configured hashrate per algorithm
User interface
--- The operations to start a miner, stop a miner and perform pool changes are enabled even if some of the selected miners are in a state where not available
--- Improved failure messages when a miner cannot start, to show more information about mining software and algorithm used
--- Improved sorting in the lists on the Balance tab
--- Multiple temperatures are displayed with a space instead of slash as separator to increase readability
--- Add two additional configurable coins with exchange rate in the status bar
--- Allow Remote Agent to be started automatically after installation
--- More detailed error messages from SMTP server when testing mail settings
--- Added link to the Awesome Miner Affiliate Program from the main menu
Mining software
--- SRBMiner 1.5.1 for Cryptonight algorithms
--- CastXMR 1.0 with Cryptonight-Lite support
--- Claymore Dual Ethereum Miner 11.7
--- Claymore NeoScrypt AMD Miner 1.2
--- Bminer 7.0
--- CpuMiner-Opt 3.8.8
Corrections
--- Correction to Block Masters API integration, to use HTTP as HTTPS is no longer supported
--- Correction to custom online services where multiple services uses the same algorithm
--- Correction to Pool Balance total value when using specific display currencies
--- Correction to display of Mining Dutch X11 profit information
--- Correction to display of hashrates in the case a miner reports extreme hashrates due to internal failures
--- Correction to network scan to allow including IP addresses ending with 0
--- Minor corrections and improvements

Happy mining!

[RsvTu]

Nice updates Is there way to have API access for Dragonmint B29 ASIC on AwesomeMiner?

[Allo-4ka]

I think most dialogs uses Center Screen for their position. I noticed that the View Details dialog has a different behavior and should be centered relative the main window. Can you right click on a miner and select View Details, and see if this positioning mode works fine in your setup as well?

If click "view details", then the window opens on the monitor where awesomeminer is open, but the settings always open on the main monitor (which is specified in windows)