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

[patrike]

Awesome Miner version 9.5.3 (Development preview of 9.6)

 Features
  - Remote Proxies can be configured with another proxy as failover
  - Rule configuration page redesigned with support for groups of rules (right click to create) and more details about each rule
  - Activity log includes the name of the rule performing an action
  - Activity log includes more details for Miner Tag operations
  - Property filter for Temperature and Chip temperature
 Improvements
  - Detect Not Hashing trigger has been improved for Antminer S19
  - Performance optimizations
 Mining software
  - BzMiner 9.2.1, incl. dual mining support
  - Nanominer 3.6.7
  - Lolminer 1.52a
  - WildRig miner 0.31.5

[1715187854]

1715187854

[1715187854]

1715187854

[1715187854]

1715187854

[1715187854]

1715187854

[1715187854]

1715187854

[1715187854]

1715187854

[narousberg]

Hi Patrike, maybe this is a good idea, to add a electricity price input field in "Coins" and "Online services" tabs. So can user quick check profit with different prices
Thanks for tip with profile groups, very helpful.
Heat map "chip temp", "temp", "hashrate" will not be displayed if i try to call over Awesome Miner web in different web browsers. Not work on ver. 9.5.1 & 9.5.2
Regards.

Thanks for the feedback.

I'm not able to reproduce the heatmap issue. Is this for the local web interface or the cloud web interface? Do you see empty boxes or all zeros?

its a local web interface, i see only grey boxes with "-"

[sxemini]

Hi patrike,
can you change the OC settings for Nvidia cards to set locked core clock and locked core voltage? I hope it is possible.
And any plans for more voltage settings for the newer AMD cards (RX5700, RX6800 for example) like SoC Voltage, Mem Voltage?

The dualmining in SRBMiner has changed a littlebit and need a extra argument and it is also possible to dual mine with Kaspa (KHeavyhash). Can you take a look in it?

Thanks for updating the activity log  but can you change the colors for the dark mode? 

[patrike]

Hi Patrike, maybe this is a good idea, to add a electricity price input field in "Coins" and "Online services" tabs. So can user quick check profit with different prices
Thanks for tip with profile groups, very helpful.
Heat map "chip temp", "temp", "hashrate" will not be displayed if i try to call over Awesome Miner web in different web browsers. Not work on ver. 9.5.1 & 9.5.2
Regards.

Thanks for the feedback.

I'm not able to reproduce the heatmap issue. Is this for the local web interface or the cloud web interface? Do you see empty boxes or all zeros?

its a local web interface, i see only grey boxes with "-"

Thanks - I was able to reproduce and identify this issue. It will be corrected in the next release.

[patrike]

Hi patrike,
can you change the OC settings for Nvidia cards to set locked core clock and locked core voltage? I hope it is possible.
And any plans for more voltage settings for the newer AMD cards (RX5700, RX6800 for example) like SoC Voltage, Mem Voltage?

The dualmining in SRBMiner has changed a littlebit and need a extra argument and it is also possible to dual mine with Kaspa (KHeavyhash). Can you take a look in it?

Thanks for updating the activity log  but can you change the colors for the dark mode? 

The current method Awesome Miner uses for the lock is only able to lock one of these properties.

Remote Agent on Linux actually supports these properties - I will investigate how to support it on Windows as well.

Thanks for your comments about the activity log as well.

[patrike]

Hello. Got a weird issue here. This is on my main awesome miner rig that runs the main A.M. host(?). 5x 3080ti asus tuf LHR v512.59 using t-rex mining ETH. When i stop mining, the pc will crash. Sometimes just a soft crash with just a black screen flicker a couple times and some settings are not found like fan or power level in settings, or sometimes it will do a full restart, or a complete black screen hang. This happens ONLY when A.M. is open and running and i try to "stop" mining. Even when hitting stop using the web gui on my phone. If i close A.M. completely, wait a few seconds, then close the miner window, all is well, no crash. This crash will happen even at a 0 overclock. I can recreate this with a minute or 2 of mining. I used to have the 2 options in overclocking enabled, "reset gpu parameters" and "global fan control", but thought that may have something to do with it since i could hear the fans reset at the same time as the crash. But i now have those off and it still happens. Any ideas?

Hi and thanks for your report.

When stopping the mining software, Awesome Miner will by default reset all overclocking properties. Can you please try to disable this by going to the Options dialog, GPU Settings section and uncheck "Automatically reset GPU clocking parameters"?

[patrike]

Hello. Got a weird issue here. This is on my main awesome miner rig that runs the main A.M. host(?). 5x 3080ti asus tuf LHR v512.59 using t-rex mining ETH. When i stop mining, the pc will crash. Sometimes just a soft crash with just a black screen flicker a couple times and some settings are not found like fan or power level in settings, or sometimes it will do a full restart, or a complete black screen hang. This happens ONLY when A.M. is open and running and i try to "stop" mining. Even when hitting stop using the web gui on my phone. If i close A.M. completely, wait a few seconds, then close the miner window, all is well, no crash. This crash will happen even at a 0 overclock. I can recreate this with a minute or 2 of mining. I used to have the 2 options in overclocking enabled, "reset gpu parameters" and "global fan control", but thought that may have something to do with it since i could hear the fans reset at the same time as the crash. But i now have those off and it still happens. Any ideas?

Hi and thanks for your report.

When stopping the mining software, Awesome Miner will by default reset all overclocking properties. Can you please try to disable this by going to the Options dialog, GPU Settings section and uncheck "Automatically reset GPU clocking parameters"?

That was the setting that i already disabled as i thought that was the cause.

Thanks for the update.

Please try these two changes as well, both located in the Options dialog, Mining settings section:
1) Increase the value for "Wait for process stop before terminating" to be significantly higher than the default value.
2) Check the box for "Use Ctrl+C event for closing mining process"

[patrike]

Awesome Miner version 9.5.4 (Development preview of 9.6)

 GPU mining
  - Improved overclocking compatibility for Radeon RX 6600 on Linux
 Features
  - Rule actions to Pause all rules and Resume all rules (found in the action sub menu Set Properties)
  - Rule filter to find only enabled rules
  - Improved filtering in the global activity log
  - Expose temperature data to the Progress field scripts
  - Miner property filter for uptime
  - Remote Proxy failover feature can be configured with a rule to be executed when the proxy connection is restored after a failover
 Improvements
  - Performance optimizations
  - Increase the maximum number of notifications to 8000 (previously 2000).
 Mining software
  - Gminer 3.02
  - SrbMiner Multi 0.9.8, incl updated dual mining support
  - WildRig miner 0.31.8
 Correction
  - Correction to dark theme for activity log
  - Correction to heat maps for Managed Miners in the web interface

[sxemini]

That was the setting that i already disabled as i thought that was the cause.

You have to high OC on your cards. I have the same problem on some GTX1660S - with to high mem oc the rig must restart after stop mining - but it can run for days if i don´t restart it.

Hi patrike,
can you change the OC settings for Nvidia cards to set locked core clock and locked core voltage? I hope it is possible.
And any plans for more voltage settings for the newer AMD cards (RX5700, RX6800 for example) like SoC Voltage, Mem Voltage?

The dualmining in SRBMiner has changed a littlebit and need a extra argument and it is also possible to dual mine with Kaspa (KHeavyhash). Can you take a look in it?

Thanks for updating the activity log  but can you change the colors for the dark mode? 

The current method Awesome Miner uses for the lock is only able to lock one of these properties.

Remote Agent on Linux actually supports these properties - I will investigate how to support it on Windows as well.

Thanks for your comments about the activity log as well.

Thanks for the explanation, i appreciate your work 

[patrike]

Hello. Got a weird issue here. This is on my main awesome miner rig that runs the main A.M. host(?). 5x 3080ti asus tuf LHR v512.59 using t-rex mining ETH. When i stop mining, the pc will crash. Sometimes just a soft crash with just a black screen flicker a couple times and some settings are not found like fan or power level in settings, or sometimes it will do a full restart, or a complete black screen hang. This happens ONLY when A.M. is open and running and i try to "stop" mining. Even when hitting stop using the web gui on my phone. If i close A.M. completely, wait a few seconds, then close the miner window, all is well, no crash. This crash will happen even at a 0 overclock. I can recreate this with a minute or 2 of mining. I used to have the 2 options in overclocking enabled, "reset gpu parameters" and "global fan control", but thought that may have something to do with it since i could hear the fans reset at the same time as the crash. But i now have those off and it still happens. Any ideas?

Hi and thanks for your report.

When stopping the mining software, Awesome Miner will by default reset all overclocking properties. Can you please try to disable this by going to the Options dialog, GPU Settings section and uncheck "Automatically reset GPU clocking parameters"?

That was the setting that i already disabled as i thought that was the cause.

Thanks for the update.

Please try these two changes as well, both located in the Options dialog, Mining settings section:
1) Increase the value for "Wait for process stop before terminating" to be significantly higher than the default value.
2) Check the box for "Use Ctrl+C event for closing mining process"

i applied both the ctrl+c and made the wait time longer, now it just takes longer to crash. I have found that i can manually "x" close t-rex with A.M. open and all is well, a.m. just sees it as a "miner not running" and will restart it. so its def something in the "stop" command causing the crash. Again, as long as i dont use a.m. to "stop" it, it never blackscreen reboots.

There is likely a small difference between the behavior when the mining software notice you close the mining console window compared to when Awesome Miner sending the close signal to the mining software.

I assume you run T-Rex as Administrator in order to get the LHR unlock feature. Do you get the same crash behavior if you uncheck the box for Administrator and also try with the Ctrl+C mode enabled?

[patrike]

Awesome Miner version 9.6

 GPU mining
  - Improved overclocking compatibility for Radeon RX 6600 on Linux
 Features
  - Heat map: Folder based view, to organize in folders and sub folders
  - Remote Proxies can be configured with another proxy as failover
  - Rules: Rule configuration page redesigned with support for groups of rules (right click to create) and more details about each rule
  - Rules: Rule actions to Pause all rules and Resume all rules (found in the action sub menu Set Properties)
  - Rules: Rule filter to find only enabled rules
  - Rules: Device hashrate trigger can compare the current hashrate with the reported ASIC miner ideal hashrate. Duration for how long the conditions must be met can be specified.
  - Rules: Test rule triggers and indicate for how many miners they are true
  - Rules: Make variable selection easier by providing a list of currently user variables as suggestions
  - Activity log: Includes the name of the rule performing an action
  - Activity log: Includes more details for Miner Tag operations
  - Activity log: Improved filtering in the global activity log
  - Property filter: Temperature, Chip temperature, Uptime, Variables
  - Information column: Display of ASIC miner ideal hashrate
  - Expose temperature data to the Progress field scripts
 Improvements
  - Performance optimizations
  - Detect Not Hashing trigger has been improved for Antminer S19
  - Increase the maximum number of notifications to 8000 (previously 2000).
 Changes
  - Consistent use of /var/log/awesome as log folder for Remote Agent on Linux
 Mining software
  - BzMiner 9.2.1, incl. dual mining support
  - Gminer 3.02
  - Lolminer 1.52a
  - Nanominer 3.6.7
  - SrbMiner Multi 0.9.8, incl updated dual mining support
  - TeamBlackMiner 1.65
  - TeamRedMiner 0.10.2
  - WildRig miner 0.32.0
  - XmRig Miner 6.17
 Correction
  - Correction to dark theme for activity log
  - Correction to MAC address identification for network discovery
  - Correction to reading MAC address for Antminer S19 running the Awesome Miner firmware
  - Correction to default pools configuration for Antminer S19 running the Awesome Miner firmware

[patrike]

Hello. Got a weird issue here. This is on my main awesome miner rig that runs the main A.M. host(?). 5x 3080ti asus tuf LHR v512.59 using t-rex mining ETH. When i stop mining, the pc will crash. Sometimes just a soft crash with just a black screen flicker a couple times and some settings are not found like fan or power level in settings, or sometimes it will do a full restart, or a complete black screen hang. This happens ONLY when A.M. is open and running and i try to "stop" mining. Even when hitting stop using the web gui on my phone. If i close A.M. completely, wait a few seconds, then close the miner window, all is well, no crash. This crash will happen even at a 0 overclock. I can recreate this with a minute or 2 of mining. I used to have the 2 options in overclocking enabled, "reset gpu parameters" and "global fan control", but thought that may have something to do with it since i could hear the fans reset at the same time as the crash. But i now have those off and it still happens. Any ideas?

Hi and thanks for your report.

When stopping the mining software, Awesome Miner will by default reset all overclocking properties. Can you please try to disable this by going to the Options dialog, GPU Settings section and uncheck "Automatically reset GPU clocking parameters"?

That was the setting that i already disabled as i thought that was the cause.

Thanks for the update.

Please try these two changes as well, both located in the Options dialog, Mining settings section:
1) Increase the value for "Wait for process stop before terminating" to be significantly higher than the default value.
2) Check the box for "Use Ctrl+C event for closing mining process"

i applied both the ctrl+c and made the wait time longer, now it just takes longer to crash. I have found that i can manually "x" close t-rex with A.M. open and all is well, a.m. just sees it as a "miner not running" and will restart it. so its def something in the "stop" command causing the crash. Again, as long as i dont use a.m. to "stop" it, it never blackscreen reboots.

There is likely a small difference between the behavior when the mining software notice you close the mining console window compared to when Awesome Miner sending the close signal to the mining software.

I assume you run T-Rex as Administrator in order to get the LHR unlock feature. Do you get the same crash behavior if you uncheck the box for Administrator and also try with the Ctrl+C mode enabled?

I tried to uncheck "run as admin" but trex just errors out asking to be run as admin to unlock gpu.

There is actually one more scenario that would be of interest to test here. What happens if you first click the Stop button in Awesome Miner, then click the X-button to close the T-Rex mining within within the next 1-2 seconds. Do you still get the same issue?

Was it only with T-Rex you run into this issue?

[narousberg]

Hi Patrike, it looks like AM (ver. 9.6) is not capturing hashrate data from MiniZ miner (linux rig). In those moments when MiniZ is running, the data of the nashrate is not displayed in the history in the "Graph" tab. Temperature data is not affected.  Please check. Regards.

upd: it show hashrate on 5 min timespan, but no hashrate history data on bigger timespans.

[patrike]

Hi Patrike, it looks like AM (ver. 9.6) is not capturing hashrate data from MiniZ miner (linux rig). In those moments when MiniZ is running, the data of the nashrate is not displayed in the history in the "Graph" tab. Temperature data is not affected.  Please check. Regards.

upd: it show hashrate on 5 min timespan, but no hashrate history data on bigger timespans.

Thanks for the report. This was a bit strange case as the specific mining software shouldn't have any impact on the hashrate graphs, as long as the hashrate is reported. I've not been able to reproduce it.
Are you consistently getting this behavior on a specific mining rig? Does a change of mining software resolve the problem and as soon as you go back to Miniz, you run into this problem while Awesome Miner do display a valid hashrate (in the miner list) during this period of time?

[patrike]

i applied both the ctrl+c and made the wait time longer, now it just takes longer to crash. I have found that i can manually "x" close t-rex with A.M. open and all is well, a.m. just sees it as a "miner not running" and will restart it. so its def something in the "stop" command causing the crash. Again, as long as i dont use a.m. to "stop" it, it never blackscreen reboots.

There is likely a small difference between the behavior when the mining software notice you close the mining console window compared to when Awesome Miner sending the close signal to the mining software.

I assume you run T-Rex as Administrator in order to get the LHR unlock feature. Do you get the same crash behavior if you uncheck the box for Administrator and also try with the Ctrl+C mode enabled?

I tried to uncheck "run as admin" but trex just errors out asking to be run as admin to unlock gpu.

There is actually one more scenario that would be of interest to test here. What happens if you first click the Stop button in Awesome Miner, then click the X-button to close the T-Rex mining within within the next 1-2 seconds. Do you still get the same issue?

Was it only with T-Rex you run into this issue?

rig did not crash after hitting "stop" then jumping right over and clicking the "x". Have not tried with other miners.

There will be a new implementation for the close down behavior of mining software running with Admin permissions in the next release. Once available, please enable the "Ctrl+C mode" in the Options dialog, Mining Settings section, and give it a try.

[patrike]

Awesome Miner version 9.6.1

 GPU mining
  - Improved voltage control for Radeon RX 6000-series on Linux
 Features
  - Include or exclude miner groups from rule via the Groups context menu on the Miners tab
 Improvements
  - Improve how mining processes running with Administrator permissions are terminated
 Mining software
  - CpuMiner-Opt 3.19.9
  - SrbMiner Multi 1.0.1
 Corrections
  - Correction to rule testing feature for specific triggers where a duration is specified

[patrike]

Awesome Miner version 9.6.2

Version 9.6.2
 Mining software
  - CpuMiner-Opt 3.20.0
  - Nanominer 3.6.8
  - SrbMiner Multi 1.0.2
  - WildRig 0.32.1
 Corrections
  - Correction to Apply Clocking Profile for a selected GPU
  - Correction to fan curve settings for AMD

[patrike]

i applied both the ctrl+c and made the wait time longer, now it just takes longer to crash. I have found that i can manually "x" close t-rex with A.M. open and all is well, a.m. just sees it as a "miner not running" and will restart it. so its def something in the "stop" command causing the crash. Again, as long as i dont use a.m. to "stop" it, it never blackscreen reboots.

There is likely a small difference between the behavior when the mining software notice you close the mining console window compared to when Awesome Miner sending the close signal to the mining software.

I assume you run T-Rex as Administrator in order to get the LHR unlock feature. Do you get the same crash behavior if you uncheck the box for Administrator and also try with the Ctrl+C mode enabled?

I tried to uncheck "run as admin" but trex just errors out asking to be run as admin to unlock gpu.

There is actually one more scenario that would be of interest to test here. What happens if you first click the Stop button in Awesome Miner, then click the X-button to close the T-Rex mining within within the next 1-2 seconds. Do you still get the same issue?

Was it only with T-Rex you run into this issue?

rig did not crash after hitting "stop" then jumping right over and clicking the "x". Have not tried with other miners.

There will be a new implementation for the close down behavior of mining software running with Admin permissions in the next release. Once available, please enable the "Ctrl+C mode" in the Options dialog, Mining Settings section, and give it a try.

While i am very appreciative to have seen the update notes about terminating the mining process, unfortunately it is still crashing.

Thanks for the feedback. I've made one final attempt to address this in the most recent release, v9.6.2. Please make sure you enable the "Ctrl+C" mode as well.

[narousberg]

Hi Patrike, its impossible to start XMRigNvidia Miner in linux rig, the default download link is not defined. If i try to configure a custom link and executable file, i get error:
Mining software executable is not defined
Failed to start miner process: Value cannot be null. (Parameter 'path1')
Failed to start miner in Diagnostics mode
Diagnostics completed

Downloading of miner .tar.gz to /root/.config/AwesomeMinerService also not help, same error. Whats wrong? AM ver. 9.6.2
Regards

[patrike]

Hi Patrike, its impossible to start XMRigNvidia Miner in linux rig, the default download link is not defined. If i try to configure a custom link and executable file, i get error:
Mining software executable is not defined
Failed to start miner process: Value cannot be null. (Parameter 'path1')
Failed to start miner in Diagnostics mode
Diagnostics completed

Downloading of miner .tar.gz to /root/.config/AwesomeMinerService also not help, same error. Whats wrong? AM ver. 9.6.2
Regards

The "XmRig Nvidia Miner" is an old and outdated miner that by default is hidden on all new installations as it isn't intended to be used. For existing installations that has been around for a while, you will still see it unless you manually hide it.

These days it's only the "XmRig CPU Miner" that should be used. This one can be executed with "--cuda --no-cpu" to make it use your nVidia GPUs for mining instead of the CPU.

Unfortunately it isn't that easy on Linux as nVidia isn't supported out-of-the-box and requires some manual steps. See:
https://github.com/xmrig/xmrig-cuda