Author

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 146. (Read 703143 times)

member
Activity: 1558
Merit: 69
Version 6.7.3 ( Development preview of 6.8 )

 Awesome Miner Antminer S9 firmware
  - Better performance and flexible hashrate and power configuration when mining with Antminer S9
  - Integrates with Awesome Miner by providing: LED flash, pause and resume mining in a power efficient way, antivirus scan and apply mining profiles (hashrate and power usage).
  - The features are available via the ASIC tools menu and as rule actions in Awesome Miner
  - Display of power usage
  - SSH access to the Antminer
  - Mining fee 2%
  - Awesome Miner can install this firmware even when the Antminer is locked with signature check and SSH is disabled (contact us for instructions)
  - For more information, see the web site: https://www.awesomeminer.com/antminerfirmware
 GPU mining
  - GPU power limit control based on temperature, configurable in the Options dialog, GPU Settings section (Beta preview features)
 Features
  - Miner highlight feature includes 5 additional colors
  - Configurable if a double click on an External Miner should open the ASIC miner web interface. Configurable via the Options dialog, General section.
 User interface
  - Antminer&ASIC menu renamed to ASIC tools
  - Temperature sorting improved for miner list in compact mode
 Mining software
  - Bminer 15.7.6
  - CcMiner Zcoin Official 1.1.26
  - Z-enemy miner 2.1

-Thanks Patrike for more highlight colors. Can you change this feature that we can set our own description per color? Example i will set red = offline, yellow = temperature over 80°c. At the moment the names are Information 1, Information 2 and so on. I hope you understand my question  Cheesy

-Other stuff what i expect are groups for balance section. Because i use awesomeminer with a friend and so we can make our own groups or we can make several groups for exchange, wallet and so on.

-Dual Mining Support for Phönixminer must be also possible, it is not very different from claymore.

-And CPU only mode for Nanominer, at the moment i can´t mine only with CPU because Awesomeminer say it is for nvidia and amd not for cpu.

legendary
Activity: 3346
Merit: 1094
Version 6.7.3 ( Development preview of 6.8 )

 Awesome Miner Antminer S9 firmware
  - Better performance and flexible hashrate and power configuration when mining with Antminer S9
  - Integrates with Awesome Miner by providing: LED flash, pause and resume mining in a power efficient way, antivirus scan and apply mining profiles (hashrate and power usage).
  - The features are available via the ASIC tools menu and as rule actions in Awesome Miner
  - Display of power usage
  - SSH access to the Antminer
  - Mining fee 2%
  - Awesome Miner can install this firmware even when the Antminer is locked with signature check and SSH is disabled (contact us for instructions)
  - For more information, see the web site: https://www.awesomeminer.com/antminerfirmware
 GPU mining
  - GPU power limit control based on temperature, configurable in the Options dialog, GPU Settings section (Beta preview features)
 Features
  - Miner highlight feature includes 5 additional colors
  - Configurable if a double click on an External Miner should open the ASIC miner web interface. Configurable via the Options dialog, General section.
 User interface
  - Antminer&ASIC menu renamed to ASIC tools
  - Temperature sorting improved for miner list in compact mode
 Mining software
  - Bminer 15.7.6
  - CcMiner Zcoin Official 1.1.26
  - Z-enemy miner 2.1
member
Activity: 277
Merit: 23
I looked into this again - and you are actually correct. Thanks for being persistent.

In the past the Claymore miner only reported the total share information (total number of accepted and rejected shares, not per GPU). Then Claymore introduced a new API command that Awesome Miner could send to get per-GPU information as well. Back then it was something by Claymore and for the Claymore miner only.

Now I just tried to send the same updated API command to Phoenix Miner and it does indeed return per-GPU share information just like Claymore miner. This makes it fully possible to implement support for per-GPU display of accepted and rejected shares for Phoenix Miner as well.

I will not be able to test and finalize this for the development release that soon will be available, but I will plan it for the next release. Thanks!

U R welcome

now just to add keystroke option on console view and voile don't need to leave AM at all  Wink
jr. member
Activity: 756
Merit: 2
Patrike just tell you that with the last update you did on the remote improvement, the problems of "offline miner" have almost disappeared, it is very rare to happen. The program has returned to its former stability. In the end it was intelibreeze problem as long as sugeria

Congratulations for the job, cost to catch the ruling but it is mostly corrected, I have had dozens and dozens of failures a day to have 3 or 4 which I consider normal.
legendary
Activity: 3346
Merit: 1094
this is probably an old question, does any one know how to enable PhoenixMiner to display accepted/rejected shares and HW errors in AM ?


is this even possible?
Thanks for the question.

I assume you refer to if this can be reported per-GPU. It's only Claymore miner that supports reporting this information per GPU from what I've seen. For Phoenix Miner it's only a total number of accepted/rejected shares.

But in the console you can see it per GPU.

my point exactly, its in the log file...

Maybe Phoenix should provide the same API like Claymore for this info...

it's kinda annoying to watch on console view  which , sometimes btw, starts to strobe 
I looked into this again - and you are actually correct. Thanks for being persistent.

In the past the Claymore miner only reported the total share information (total number of accepted and rejected shares, not per GPU). Then Claymore introduced a new API command that Awesome Miner could send to get per-GPU information as well. Back then it was something by Claymore and for the Claymore miner only.

Now I just tried to send the same updated API command to Phoenix Miner and it does indeed return per-GPU share information just like Claymore miner. This makes it fully possible to implement support for per-GPU display of accepted and rejected shares for Phoenix Miner as well.

I will not be able to test and finalize this for the development release that soon will be available, but I will plan it for the next release. Thanks!
member
Activity: 277
Merit: 23
this is probably an old question, does any one know how to enable PhoenixMiner to display accepted/rejected shares and HW errors in AM ?


is this even possible?
Thanks for the question.

I assume you refer to if this can be reported per-GPU. It's only Claymore miner that supports reporting this information per GPU from what I've seen. For Phoenix Miner it's only a total number of accepted/rejected shares.

But in the console you can see it per GPU.

my point exactly, its in the log file...

Maybe Phoenix should provide the same API like Claymore for this info...

it's kinda annoying to watch on console view  which , sometimes btw, starts to strobe 
member
Activity: 1558
Merit: 69
this is probably an old question, does any one know how to enable PhoenixMiner to display accepted/rejected shares and HW errors in AM ?


is this even possible?
Thanks for the question.

I assume you refer to if this can be reported per-GPU. It's only Claymore miner that supports reporting this information per GPU from what I've seen. For Phoenix Miner it's only a total number of accepted/rejected shares.

But in the console you can see it per GPU.
legendary
Activity: 3346
Merit: 1094
this is probably an old question, does any one know how to enable PhoenixMiner to display accepted/rejected shares and HW errors in AM ?


is this even possible?
Thanks for the question.

I assume you refer to if this can be reported per-GPU. It's only Claymore miner that supports reporting this information per GPU from what I've seen. For Phoenix Miner it's only a total number of accepted/rejected shares.
legendary
Activity: 3346
Merit: 1094
Patrike, please, add nheqminer support.
At present nheqminer is the only CPU miner for high speed verus coin mining, I added it with command prompt command, but awesome miner can not see the current hashrate of this miner. That's why awesome miner watchdog stops this miner after 20 minutes and ban the pool. I can not disable watchdog, I need this function enabled, because it used for GPU miner also (awesome miner watchdog can not be set for the miners and miner software separatedly).

Sometimes pools have problems that can not be fixed for the next several hours (for example, if the problems happen when pool owner is sleeping and can not see discord messages from the users). In such cases the best solution is to ban the pool for the next several hours. I want to see the right click menu in online services tab with different options:
- start mining here for the next hh:mm
- ban this pool for the next hh:mm

Suggestions:
1) add nheqminer support (CPU and GPU modes)
2) add watchdog options for different miners and miner software
3) right click menu in "online services" tab with "mine here" and "ban this pool" commands.

Thanks Smiley
Thanks for the suggestions.

When you added the nheqminer, did you add it via the Options dialog, Managed Software section, and configured it with Command Line as compatibility mode? In that case Awesome Miner shouldn't try the API and should understand that it cannot get hashrate/share information.

Which nheqminer version is using by the mining community these days? This one looks very outdated:
https://github.com/nicehash/nheqminer/releases
member
Activity: 277
Merit: 23
this is probably an old question, does any one know how to enable PhoenixMiner to display accepted/rejected shares and HW errors in AM ?


is this even possible?
member
Activity: 277
Merit: 23
this is probably an old question, does any one know how to enable PhoenixMiner to display accepted/rejected shares and HW errors in AM ?
newbie
Activity: 21
Merit: 0
Patrike, please, add nheqminer support.
At present nheqminer is the only CPU miner for high speed verus coin mining, I added it with command prompt command, but awesome miner can not see the current hashrate of this miner. That's why awesome miner watchdog stops this miner after 20 minutes and ban the pool. I can not disable watchdog, I need this function enabled, because it used for GPU miner also (awesome miner watchdog can not be set for the miners and miner software separatedly).

Sometimes pools have problems that can not be fixed for the next several hours (for example, if the problems happen when pool owner is sleeping and can not see discord messages from the users). In such cases the best solution is to ban the pool for the next several hours. I want to see the right click menu in online services tab with different options:
- start mining here for the next hh:mm
- ban this pool for the next hh:mm

Suggestions:
1) add nheqminer support (CPU and GPU modes)
2) add watchdog options for different miners and miner software
3) right click menu in "online services" tab with "mine here" and "ban this pool" commands.

Thanks Smiley
member
Activity: 204
Merit: 10
Awesome Miner version 6.7.2

 User interface
  - Show difficulty for each pool in the Pools tab
 Mining software
  - SrbMiner 1.9.3
  - WildRig 0.19.0 preview
 Corrections
  - Correction to missing file on some Remote Agent installations

Thx issue resoved. Stats reporting successfully  Smiley
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.7.2

 User interface
  - Show difficulty for each pool in the Pools tab
 Mining software
  - SrbMiner 1.9.3
  - WildRig 0.19.0 preview
 Corrections
  - Correction to missing file on some Remote Agent installations
legendary
Activity: 3346
Merit: 1094
Code:
25-07-2019 09:49:58 PM.221 [009] [I][ManagedMiner#7 - Vega Rig] : ProcessMiner
25-07-2019 09:49:58 PM.221 [009] [E]System.IO.FileNotFoundException: Could not load file or assembly 'AwesomeMiner.ResourceAccess.Asic, Version=6.7.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
25-07-2019 09:49:58 PM.221 [009] [E]   at #=zgfBCWpQmeFuYIMGOw3SBNiW1m8UYcXNWa5nltMBwv6k3ddha60u44jHGa9ZJ..ctor()
   at #=zu7haAQa3AnJO2oyd$5pjMIpnxuzLHMJqw0a28NNQpdi$..ctor()
   at #=zQLN_D9ujnJv_wtRddKee5e8MY9FBncVKeKDobdE=.#=zOPdjUapFMX_$(String #=zvZcBBg4=)
   at #=zjqpSM22GL_x_QBYZCf4CAIUkj$Q2KzxdJpvcgbIFDm9a.#=z$Tye9fU=(MinerBase #=zbm34RMai5A4G, StatusUpdate& #=zH4K_FL0=)
25-07-2019 09:49:58 PM.659 [018] [S]Send service log file

Miner shows mining but no stats. Tried rebooting miner, windows, awesome miner.
Edit: Miner is TeamRedMiner 0.5.6, any seeing this same state on multiple miners.
Thanks for your report - I've identified the scenario when this happens. I will release a new version in about an hour to resolve this.

Let's see if this fixes the situation that occurs so much of online interface
Unfortunately I don't think it will solve any general issues with Interface Offline. This was a very specific case that didn't work correctly and this problem only exists in the most recent versions of Awesome Miner.

If you find another case where you run into a problem with miners no showing all stats - please send me the log files via PM and I can investigate. Thanks!
jr. member
Activity: 756
Merit: 2
Code:
25-07-2019 09:49:58 PM.221 [009] [I][ManagedMiner#7 - Vega Rig] : ProcessMiner
25-07-2019 09:49:58 PM.221 [009] [E]System.IO.FileNotFoundException: Could not load file or assembly 'AwesomeMiner.ResourceAccess.Asic, Version=6.7.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
25-07-2019 09:49:58 PM.221 [009] [E]   at #=zgfBCWpQmeFuYIMGOw3SBNiW1m8UYcXNWa5nltMBwv6k3ddha60u44jHGa9ZJ..ctor()
   at #=zu7haAQa3AnJO2oyd$5pjMIpnxuzLHMJqw0a28NNQpdi$..ctor()
   at #=zQLN_D9ujnJv_wtRddKee5e8MY9FBncVKeKDobdE=.#=zOPdjUapFMX_$(String #=zvZcBBg4=)
   at #=zjqpSM22GL_x_QBYZCf4CAIUkj$Q2KzxdJpvcgbIFDm9a.#=z$Tye9fU=(MinerBase #=zbm34RMai5A4G, StatusUpdate& #=zH4K_FL0=)
25-07-2019 09:49:58 PM.659 [018] [S]Send service log file

Miner shows mining but no stats. Tried rebooting miner, windows, awesome miner.
Edit: Miner is TeamRedMiner 0.5.6, any seeing this same state on multiple miners.
Thanks for your report - I've identified the scenario when this happens. I will release a new version in about an hour to resolve this.

Let's see if this fixes the situation that occurs so much of online interface
legendary
Activity: 3346
Merit: 1094
Code:
25-07-2019 09:49:58 PM.221 [009] [I][ManagedMiner#7 - Vega Rig] : ProcessMiner
25-07-2019 09:49:58 PM.221 [009] [E]System.IO.FileNotFoundException: Could not load file or assembly 'AwesomeMiner.ResourceAccess.Asic, Version=6.7.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
25-07-2019 09:49:58 PM.221 [009] [E]   at #=zgfBCWpQmeFuYIMGOw3SBNiW1m8UYcXNWa5nltMBwv6k3ddha60u44jHGa9ZJ..ctor()
   at #=zu7haAQa3AnJO2oyd$5pjMIpnxuzLHMJqw0a28NNQpdi$..ctor()
   at #=zQLN_D9ujnJv_wtRddKee5e8MY9FBncVKeKDobdE=.#=zOPdjUapFMX_$(String #=zvZcBBg4=)
   at #=zjqpSM22GL_x_QBYZCf4CAIUkj$Q2KzxdJpvcgbIFDm9a.#=z$Tye9fU=(MinerBase #=zbm34RMai5A4G, StatusUpdate& #=zH4K_FL0=)
25-07-2019 09:49:58 PM.659 [018] [S]Send service log file

Miner shows mining but no stats. Tried rebooting miner, windows, awesome miner.
Edit: Miner is TeamRedMiner 0.5.6, any seeing this same state on multiple miners.
Thanks for your report - I've identified the scenario when this happens. I will release a new version in about an hour to resolve this.
newbie
Activity: 11
Merit: 0
I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter.  See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails.  Has anyone else seen this and have an idea how to address it?

Code:
6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer  -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer"  -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"

Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon.

Unfortunately this still seems to be an issue in 6.5.7.
For this user defined Managed Software you added for CpuMiner - have you configured it to have the compatibility mode "Full" with CpuMinerOpt?

I might have identified one more issue specific to the Remote Agent on Linux here, but only related to custom algorithm parameters.
Yes, it is configured as Full (Command line and API).  Sorry, I probably should have mentioned in my original post, but I saw some similar behavior with the Windows agent in 6.5.6 where it would not use the algorithm argument from the "Default command line argument" column, but would use an argument from the "User defined command line algorithm" column even if it was the same value.  I worked around this by simply replicating all the default args as user defined args.  But this workaround did not seem to work for the Linux agent.  So this may be a combination of multiple issues.

I'm happy to provide any additional info you might need to track this down.
What I still could reproduce on Linux for 6.5.7 was that the "User defined command line" not being used correctly and I will of course correct that. It should however fallback to use the "Default command line argument" in 6.5.7 (didn't work in 6.5.6). Is it not even doing this fallback when you test it?

I'm away from my rigs for a day or so, but I will run through some more tests as soon as I can and post the results.

My apologies for the super delayed response, just wanted to say that whatever issue I was seeing before seems to have been resolved at this point.
member
Activity: 204
Merit: 10
Code:
25-07-2019 09:49:58 PM.221 [009] [I][ManagedMiner#7 - Vega Rig] : ProcessMiner
25-07-2019 09:49:58 PM.221 [009] [E]System.IO.FileNotFoundException: Could not load file or assembly 'AwesomeMiner.ResourceAccess.Asic, Version=6.7.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
25-07-2019 09:49:58 PM.221 [009] [E]   at #=zgfBCWpQmeFuYIMGOw3SBNiW1m8UYcXNWa5nltMBwv6k3ddha60u44jHGa9ZJ..ctor()
   at #=zu7haAQa3AnJO2oyd$5pjMIpnxuzLHMJqw0a28NNQpdi$..ctor()
   at #=zQLN_D9ujnJv_wtRddKee5e8MY9FBncVKeKDobdE=.#=zOPdjUapFMX_$(String #=zvZcBBg4=)
   at #=zjqpSM22GL_x_QBYZCf4CAIUkj$Q2KzxdJpvcgbIFDm9a.#=z$Tye9fU=(MinerBase #=zbm34RMai5A4G, StatusUpdate& #=zH4K_FL0=)
25-07-2019 09:49:58 PM.659 [018] [S]Send service log file

Miner shows mining but no stats. Tried rebooting miner, windows, awesome miner.
Edit: Miner is TeamRedMiner 0.5.6, any seeing this same state on multiple miners.
jr. member
Activity: 756
Merit: 2
The idea is as simple as putting another temperature limit option, that there are two, one for Core the current one and another for Power as I suggest, it has no more problem. Instead of 5 in 5 jumps it can be shorter steps like 2 in 2, or 3 in 3. But I tell you in tests that I have done by hand, many times the hash does not suffer just because the core is still intact and the temperature drops by power reduction. I also see it very interesting

As always I try to be constructive with my suggestions or criticisms, and I think that your system is the best in the market.
In a perfect world the existing Temperature Limit feature provided by the nVidia drivers would take care of this. You can already define the temperature limit and the nVidia drivers take action to keep it. The problem we agree on is that the nVidia drivers lowers the Core clock significantly and this results in much lower hashrate. So although the nVidia drivers keeps the temperature, it's not doing it in a good way for mining.

The nVidia drivers can however guarantee that you never go above the Temperature Limit as they enforce it so hard.

Awesome Miner could have it own Power-reducing Temperature Threshold feature in addition to what nVidia gives us. Awesome Miner could monitor the temperature and if it goes above 79C (configurable), it will reduce the Power Limit to 85% (configurable) and it it's above 82C (configurable) it will set the Power Limit to 65% (configurable). It's not that easy for Awesome Miner to guarantee a temperature here, but it could at least reduce the power usage and making it less likely that you hit the nVidia Temperature Limit that will do harder underclocking.

A concept where you are allowed to define two power reduction levels based on two temperatures should be realistic to implement in Awesome Miner. Would that make sense?

Finally, I still have some online interface problems but really if it is working, that is a direct problem with intelibrezee, I am already using windows 1903 which is quite stable. I have greatly reduced that error with this version but it still continues to appear and you have to restart once or several times until AM reads that remote well. Because I understand that this problem is remote.
I don't mind looking at the log files for this again - in case I can find out anything more. Please send me the logs via PM and let me know the time you did see the issues. Thanks!
I propose suggestions, you tell me if it makes sense that there are two different systems to control the temperature, the one that already exists of Nvidia and the one that I commented through reduction of power.

Well, I don't know, you can do some programming tests, and see if it's really worth it. It is those schedules, that until you do a test in production you do not know if it is valid or not.

When you can compare the existing one with the one I suggest, in a programming environment and do 3 or 4 tests, and see if it really controls the temperature well and if the hash really falls less ... After doing it in tests, you You can decide whether it is worth it or not.

I have checked by hand, testing only by varying TDP or power and the hash reduced me almost always.

It is in your hand to try it or not, it is in your hand not to do it if you do not want it, I only provide ideas, suggestions. The current system works very well, but at the cost of losing enough hash in the hot hours, you can live with it, you just have to have a moderate OC. But if it is true that I would like you to at least try it in your programming environment and draw your own conclusion.
Jump to: