Author

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

jr. member
Activity: 756
Merit: 2
Of course PAtrike, I suggest, although it may be insistent, here the boss and decide is you.

But I see incongruous, to my way of working that I have to change the Profit in the pool and then again in the Coins tab.

I await your solution or your no solution, I adapt to what you program.
The good news is that the next release will have a new setting for applying the pool profit factor to the coins on the Coins tab. This behavior will be configurable in the Options dialog, Statistics Settings section.

If you have more than one pool for a coin, the pool with the lowest profit factor will be used. Once the new version is available, please give it a try to see if it works like you had in mind.



This is what I needed, now I just have to continue measuring pool / coins, add it in the currency pool and activating the new option, it is applied in Coins. It was just that. Thanks, it does not make sense that there are 2 profits at a time.
newbie
Activity: 22
Merit: 0
Any way to stop awesome miner from creating firewall rules for every mining software?
I don't want everyone on my LAN to have access to the mining software on my miners.

Local connections usually work even if you don't allow the program, is there any particular reason for awesome miner to create firewall rules?
There are currently no setting to prevent this behavior in Awesome Miner.

Awesome Miner is registering the mining software as an allowed application. Mining software must be able to make outgoing pool connections and also open an API port where Awesome Miner connects for monitoring information. If an application isn't registered to the Windows firewall it may be blocked and Windows almost always shows a dialog where the user must accept the application.

If you try to start almost any mining software outside of Awesome Miner (a software that Awesome Miner didn't register already) you will see that Windows Defender Firewall will show a warning dialog - unless Defender is completely disabled.

In Windows Defender Firewall you also have a setting called "Block all incoming connections, including those in the list of allowed apps". That might be the one you are looking for in your specific scenario.

As for the inbound rules, I understand is good to have them to prevent the popups but there is no need to have them as "allow the connection" rules, because the monitoring connections are local we could have them as "block the connection" rules and the monitoring would still work correctly(as far as I have tested over the years) without allowing other LAN devices access to the mining software.

The "Block all incoming connections, including those in the list of allowed apps" might seem enough for most use cases but I have mining computers that serve other content so I need access to some of their ports.

Please consider adding an option so we can decide whether to create the rules as allow or block rules, thank you.
Can this be solved by using the setting to block all incoming connections, but then explicitly configure Windows Defender to open up a few ports that you need?

Even if you only monitor mining software locally, Windows will still complain and show the Blocked dialog when you launch the mining software unless it's an allowed application. This is the reason why Awesome Miner adds the mining software as allowed as it's very difficult to run mining operations without it.
Block all incoming connections takes precedence over any other rule.

I manually changed the allow rules created by awesome miner for the mining software to block rules. Have been mining since I originally asked about this without any issue or popup (picture of my rules linked). The problem is that when new software is added/updated new rules will be created by awesome miner as allowed rules.
https://imgur.com/a/w7YBXdZ

If you make this an option you could just leave the default as it is now(allowed rules), just in case "blocked" rules might break anything for someone.
Thanks for the update.

I've made a quick implementation to support this case. I've introduced a new setting that you can set directly in the Awesome Miner configuration file as I don't want to expose this in the user interface.

1) Once the next version of Awesome Miner is available, install it, run it once and then exit the application.
2) Open the configuration file (%appdata%\AwesomeMiner\ConfigData.xml) and search for "ConfigureWindowsDefenderAllowedApps".
3) Change the property from true to false and save the file.
Thanks, I tried but it showed a popup the first time a mining software ran.
While testing further I found out 2 possible reasons why:
1 When creating a block rule the rule is created with Profile Private(current profile), while when creating an allow rule the rule is created with Profile All.
2 When creating a block rule the rule is added to the registry a couple of seconds after the miner software is launched, while when creating an allow rule the rule is added to the registry a few milliseconds before the miner software is launched.
I didn't test extensively but I'm guessing #1 has something to do with defaults, for #2 my guess is some firewall api limitation or maybe it is not the cause of the issue.
Hopefully you can take another look at it, otherwise I'll just create a script that runs now and then and modifies the rules as needed.
Even that my lan is relatively secure and have trustworthy people connecting to it, I don't want to leave my mining software open.

Thanks again.
The default behavior of Awesome Miner is to add this Allowed Apps rule. In that case things should just work and you shouldn't see any dialogs from Windows Defender. Is that correct according to your observations as well? I don't have any plans to change how these rules are set at the moment, as what Awesome Miner do works very well in a very large number of mining environments out there.

If you use the new property set to false, Awesome Miner will not do anything with the firewall configuration. I assume it's in only in this case you are getting the warnings from Defender? With the automatic configuration disabled in Awesome Miner, you are basically on your own here and you can manually configure (or not configure) the rules as you want.
I'm feeling that I'm failing to communicate what I want to say a lot, sorry about that and thank you for your patience. Maybe you make me nervous Wink

I meant that when configuring ConfigureWindowsDefenderAllowedApps as true the rules (allow rules) are being created with Profile=All, but when configuring ConfigureWindowsDefenderAllowedApps as false the rules(block rules) are being created with Profile=Private, I believe the difference in profile causes the popups to come up when ConfigureWindowsDefenderAllowedApps is set to false.
newbie
Activity: 5
Merit: 0
Awesome Miner version 6.1.6

 Features
  - A new setting for applying the pool profit factor to the coins on the Coins tab. Can be enabled in the Options dialog, Statistics Settings section.
 User interface
  - Performance improvements to the Coins tab when having a large number of coins
  - Added additional coin images
 Mining software
  - BMiner 13.2
  - Gminer 1.23
  - TT-Miner 2.1.7
  - XMRig miner 2.10.0 for AMD, nVidia and CPU
 Corrections
  - User interface correction to Profit Factor setting in Coin Properties
  - Adjusted exponential factor for calculating revenue of Equihash 96,5 coins
  - The rounding of the BMiner and NBMiner hashrate values was removed
  - BMiner to always use highest prioritized pool when there are several pools available
  - NBMiner command line correction for passing a password after the worker name

Hi Patrike
I just upgraded to this release and my issue with NBminer is corretly solved now, i.e. native miner working ok after logging in to the pool and all the relevant power and price info for GRIN is passed to the dashboard, thanks a lot.
newbie
Activity: 71
Merit: 0
This indicates that the download of the MSI file failed. Can you try the procedure one more time or download it from the web site if it still doesn't work?
Direct link from the site - it's works
legendary
Activity: 3346
Merit: 1094
This indicates that the download of the MSI file failed. Can you try the procedure one more time or download it from the web site if it still doesn't work?
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.1.6

 Features
  - A new setting for applying the pool profit factor to the coins on the Coins tab. Can be enabled in the Options dialog, Statistics Settings section.
 User interface
  - Performance improvements to the Coins tab when having a large number of coins
  - Added additional coin images
 Mining software
  - BMiner 13.2
  - Gminer 1.23
  - TT-Miner 2.1.7
  - XMRig miner 2.10.0 for AMD, nVidia and CPU
 Corrections
  - User interface correction to Profit Factor setting in Coin Properties
  - Adjusted exponential factor for calculating revenue of Equihash 96,5 coins
  - The rounding of the BMiner and NBMiner hashrate values was removed
  - BMiner to always use highest prioritized pool when there are several pools available
  - NBMiner command line correction for passing a password after the worker name
legendary
Activity: 3346
Merit: 1094
Of course PAtrike, I suggest, although it may be insistent, here the boss and decide is you.

But I see incongruous, to my way of working that I have to change the Profit in the pool and then again in the Coins tab.

I await your solution or your no solution, I adapt to what you program.
The good news is that the next release will have a new setting for applying the pool profit factor to the coins on the Coins tab. This behavior will be configurable in the Options dialog, Statistics Settings section.

If you have more than one pool for a coin, the pool with the lowest profit factor will be used. Once the new version is available, please give it a try to see if it works like you had in mind.
legendary
Activity: 3346
Merit: 1094
https://www.bminer.me/releases/

new version of Bminer optimized for Grin, you can directly use the url of your download and add the name of the folder.

Less Reject.

Bminer is a little delicate with Grin usually throw many cards, I recommend a soft OC in Windows
There will soon be a new Awesome Miner release where the latest BMiner is included.
legendary
Activity: 3346
Merit: 1094
Hi Patrike,

any plans for adding rhminer for randomhash?

https://github.com/polyminer1/rhminer

I integrate it at the moment as a ccminer, so i get pool information, but no hashrate or something else.
Maybe someone has an idea how I get the hashrate
Thanks for the suggestion. I will consider adding this one.
First on the list of mining software to support will however be some Grin miner for AMD. All I've looked at so far have a little special setup process with configuration files.
jr. member
Activity: 756
Merit: 2
Any way to stop awesome miner from creating firewall rules for every mining software?
I don't want everyone on my LAN to have access to the mining software on my miners.

Local connections usually work even if you don't allow the program, is there any particular reason for awesome miner to create firewall rules?
There are currently no setting to prevent this behavior in Awesome Miner.

Awesome Miner is registering the mining software as an allowed application. Mining software must be able to make outgoing pool connections and also open an API port where Awesome Miner connects for monitoring information. If an application isn't registered to the Windows firewall it may be blocked and Windows almost always shows a dialog where the user must accept the application.

If you try to start almost any mining software outside of Awesome Miner (a software that Awesome Miner didn't register already) you will see that Windows Defender Firewall will show a warning dialog - unless Defender is completely disabled.

In Windows Defender Firewall you also have a setting called "Block all incoming connections, including those in the list of allowed apps". That might be the one you are looking for in your specific scenario.

As for the inbound rules, I understand is good to have them to prevent the popups but there is no need to have them as "allow the connection" rules, because the monitoring connections are local we could have them as "block the connection" rules and the monitoring would still work correctly(as far as I have tested over the years) without allowing other LAN devices access to the mining software.

The "Block all incoming connections, including those in the list of allowed apps" might seem enough for most use cases but I have mining computers that serve other content so I need access to some of their ports.

Please consider adding an option so we can decide whether to create the rules as allow or block rules, thank you.
Can this be solved by using the setting to block all incoming connections, but then explicitly configure Windows Defender to open up a few ports that you need?

Even if you only monitor mining software locally, Windows will still complain and show the Blocked dialog when you launch the mining software unless it's an allowed application. This is the reason why Awesome Miner adds the mining software as allowed as it's very difficult to run mining operations without it.
Block all incoming connections takes precedence over any other rule.

I manually changed the allow rules created by awesome miner for the mining software to block rules. Have been mining since I originally asked about this without any issue or popup (picture of my rules linked). The problem is that when new software is added/updated new rules will be created by awesome miner as allowed rules.
https://imgur.com/a/w7YBXdZ

If you make this an option you could just leave the default as it is now(allowed rules), just in case "blocked" rules might break anything for someone.
Thanks for the update.

I've made a quick implementation to support this case. I've introduced a new setting that you can set directly in the Awesome Miner configuration file as I don't want to expose this in the user interface.

1) Once the next version of Awesome Miner is available, install it, run it once and then exit the application.
2) Open the configuration file (%appdata%\AwesomeMiner\ConfigData.xml) and search for "ConfigureWindowsDefenderAllowedApps".
3) Change the property from true to false and save the file.
Thanks, I tried but it showed a popup the first time a mining software ran.
While testing further I found out 2 possible reasons why:
1 When creating a block rule the rule is created with Profile Private(current profile), while when creating an allow rule the rule is created with Profile All.
2 When creating a block rule the rule is added to the registry a couple of seconds after the miner software is launched, while when creating an allow rule the rule is added to the registry a few milliseconds before the miner software is launched.
I didn't test extensively but I'm guessing #1 has something to do with defaults, for #2 my guess is some firewall api limitation or maybe it is not the cause of the issue.
Hopefully you can take another look at it, otherwise I'll just create a script that runs now and then and modifies the rules as needed.
Even that my lan is relatively secure and have trustworthy people connecting to it, I don't want to leave my mining software open.

Thanks again.
The default behavior of Awesome Miner is to add this Allowed Apps rule. In that case things should just work and you shouldn't see any dialogs from Windows Defender. Is that correct according to your observations as well? I don't have any plans to change how these rules are set at the moment, as what Awesome Miner do works very well in a very large number of mining environments out there.

If you use the new property set to false, Awesome Miner will not do anything with the firewall configuration. I assume it's in only in this case you are getting the warnings from Defender? With the automatic configuration disabled in Awesome Miner, you are basically on your own here and you can manually configure (or not configure) the rules as you want.

Of course PAtrike, I suggest, although it may be insistent, here the boss and decide is you.

But I see incongruous, to my way of working that I have to change the Profit in the pool and then again in the Coins tab.

I await your solution or your no solution, I adapt to what you program.
jr. member
Activity: 756
Merit: 2
https://www.bminer.me/releases/

new version of Bminer optimized for Grin, you can directly use the url of your download and add the name of the folder.

Less Reject.

Bminer is a little delicate with Grin usually throw many cards, I recommend a soft OC in Windows
member
Activity: 1558
Merit: 69
Hi Patrike,

any plans for adding rhminer for randomhash?

https://github.com/polyminer1/rhminer

I integrate it at the moment as a ccminer, so i get pool information, but no hashrate or something else.
Maybe someone has an idea how I get the hashrate

newbie
Activity: 117
Merit: 0
I observe a strange problem.
I chose 3 coins: Zcoin, Beam and Grin
AM sees Grin to be the most profitable, but launches the Beam.
If I add NiceHashe, it will be not these coins that are launched, but NiceHashe dagerhashimoto.
Each coin works separately, and together digs either a beam or NiceHashe ((( instead of green
What can be wrong?
Thanks for sharing the details. I found a scenario where Bminer in combination with the profit switcher and multiple pools (all supported by Bminer) could result in incorrect pool selection by Awesome Miner. This will be corrected in the next update.
Thanks

P.S.It seems to me that since AM 6.1.x there are a lot of problems in AM. Previously, everything worked much more stable.
legendary
Activity: 3346
Merit: 1094
I observe a strange problem.
I chose 3 coins: Zcoin, Beam and Grin
AM sees Grin to be the most profitable, but launches the Beam.
If I add NiceHashe, it will be not these coins that are launched, but NiceHashe dagerhashimoto.
Each coin works separately, and together digs either a beam or NiceHashe ((( instead of green
What can be wrong?
Thanks for sharing the details. I found a scenario where Bminer in combination with the profit switcher and multiple pools (all supported by Bminer) could result in incorrect pool selection by Awesome Miner. This will be corrected in the next update.
legendary
Activity: 3346
Merit: 1094
Using BMiner 13.1 on Grin, in the miner console it shows the hash rate as around 4.5, but in A.M. it shows as a steady 5.0.  When the hash rate in the console drops below 4.5 it shows as 4.0 in A.M.  Is A.M. rounding to an integer value or does it come like that from the BMiner API?

Yes, there was a rounding going on here. It will be removed in the next update. Thanks!
legendary
Activity: 3346
Merit: 1094
Hello Patrike,

I decided to give Grin a try, for he purpose I spared a small rig with four GTX 1060 6GB. Due to the RAM size, I have no other option left for the sw miner of choice than NBminer.  Both Gminer and Bminer require 8GB.

That said, I configured AM to mine GRIN-29 in f2pool.
When I triggered the newly created managed miner if failed to log in to the pool. I reviewed the parameters passed and found no mistakes and all seemed to be ok as per pool instructions.
Running diagnostics leads to the following:

...

My workaround was to copy the contents of the automatic download zipped folder for NBMiner to a new folder outside the AM path and run a bat file for the same task, which worked ok, i.e. this time it was able to log in my user grinworker to f2pool ands start mining grin.

The bat does this:
nbminer -a cuckaroo -o stratum+tcp://grin29.f2pool.com:13654 -u grinworker.001:x -long-format -log

(grinworker is a moke ID not the real one I use)


Then I tried to make AW leverage the working bat by changing the software location in the Managed miner properties - General from "Automatic download" to "specify existing installation path" and pointing the path to the bat file I had succesfully run before.

In this case AM is able to log in and mine but unable to pull any information and display in the Dashboard screen  i.e power usage, also in the Pools, and GPU tab for the miner, nothing is shown, so I am not very happy with the outcome, which is a semi-integration only.

What should I do to have NBminer up & running by just using the default automatic download which is not loging in properly?

Thanks in advance!
Thanks for letting me know of this issue. This pool was very sensitive about the default password 'x', and that was ignored for NBminer when used from Awesome Miner.

I will correct this in the next update, here Awesome Miner will pass 'grinworker.001:x' instead of only 'grinworker.001'
newbie
Activity: 117
Merit: 0
I observe a strange problem.
I chose 3 coins: Zcoin, Beam and Grin
AM sees Grin to be the most profitable, but launches the Beam.
If I add NiceHashe, it will be not these coins that are launched, but NiceHashe dagerhashimoto.
Each coin works separately, and together digs either a beam or NiceHashe ((( instead of green
What can be wrong?
https://yadi.sk/i/rP3Hqa7QYfkpUw
https://yadi.sk/i/Aofb_mxoJJ65Ag
Code:
25.01.2019 11:32:52.111 [028] [S]Managed Profit Switching processing: 4*1080ti, IsRunning: False
25.01.2019 11:32:52.111 [028] [S]  Profitability, poolChanged: False, Algorithm: CuckaRoo29 -> CuckaRoo29, EngineType: BMiner ->BMiner, EngineSubType: Disabled ->Disabled, AutoDownload: True, EnginePath:
25.01.2019 11:32:53.990 [001] [S]Command click: Start, Miners: 1
25.01.2019 11:32:53.990 [001] [S]AsyncManager called from UI. Actions: 1
25.01.2019 11:32:54.000 [037] [S]Managed Profit Switching. Profile: nVidia GPU - Copy, type: Single
25.01.2019 11:32:54.000 [037] [S]  Enabled mining software: EthClayMiner,GMiner,BMiner,CcCryptoDredgeEngine,ZecEwbfMiner,CcMiner,EwbfEquihashMiner,CcAlexisMiner,CcKlaustMiner,CcRavenMiner,CcRavenCoinMiner,CcZenemyEngine,CcZjazzEngine,DstmMiner,PhoenixMiner,XmRigNvidiaMiner,TrexMiner,ProgPowNvidiaMiner,EthMiner,LolMiner,TtMiner
25.01.2019 11:32:54.000 [037] [S]PoolServiceManager.GetAsPools, pools: 307
25.01.2019 11:32:54.001 [037] [S]PoolServiceManager.GetAllEnabledPools, pools: 0
25.01.2019 11:32:54.001 [037] [S]PoolServiceManager.GetAllEnabledPools, SinglePoolCM predefined count: 306
25.01.2019 11:32:54.002 [037] [S]  Enabled pools: count: 3, EnabledPools: None
25.01.2019 11:32:54.003 [037] [S]Ignore algorithms not supported by software:
25.01.2019 11:32:54.003 [037] [S]Ignore algorithms not enabled by profile:
25.01.2019 11:32:54.003 [037] [S]Profitability information:
  GRIN_F2pool [Grin (GRIN)], Url: grin29.f2pool.com:13654, Profit: 0,000462652753172557
  XZC_mintpond [ZCoin (XZC)], Url: zcoin-eu.mintpond.com:3000, Profit: 0,000391527541711744
  BEAM_Beepol [BEAM (BEAM)], Url: beam-pool.beepool.org:9507, Profit: 0,000389205571896253

25.01.2019 11:32:54.003 [037] [S]Managed Profit Switching processing: 4*1080ti, IsRunning: False
25.01.2019 11:32:54.003 [037] [S]  Profitability, poolChanged: False, Algorithm: CuckaRoo29 -> CuckaRoo29, EngineType: BMiner ->BMiner, EngineSubType: Disabled ->Disabled, AutoDownload: True, EnginePath:
25.01.2019 11:32:54.397 [003] [S]Saving configuration to: C:\Users\Home\AppData\Roaming\AwesomeMiner\ConfigData.xml.tmp
25.01.2019 11:32:54.417 [003] [S]--> C:\Users\Home\AppData\Roaming\AwesomeMiner\ConfigData.xml
25.01.2019 11:32:54.459 [001] [S]CoinStore, Built in coin dictionary updated
25.01.2019 11:32:54.469 [001] [S]ServiceAdapter, trigger send settings
25.01.2019 11:32:54.529 [011] [S]Sending Miner Settings to Host: localhost
25.01.2019 11:32:54.530 [019] [S]Updating settings
25.01.2019 11:32:54.531 [019] [S]Current list of Managed Miners:
[ManagedMiner#2 - 4*1080ti]: BMiner

25.01.2019 11:32:54.531 [019] [S]Current list of Clocking Profile:

25.01.2019 11:32:54.531 [019] [S]Current list of Active Miners:
[2] IsAttached: True, PID: 2364, InstanceId: 1

25.01.2019 11:32:54.531 [019] [S]Saving configuration to: C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml.tmp
25.01.2019 11:32:54.537 [019] [S]--> C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml
25.01.2019 11:32:55.014 [040] [S][ManagedMiner#2 - 4*1080ti] Run Miner Command: Start
25.01.2019 11:32:55.014 [037] [S]Command request: Start
25.01.2019 11:32:55.014 [037] [S][ManagedMiner#2 - 4*1080ti] Injecting settings
25.01.2019 11:32:55.014 [037] [S]Saving configuration to: C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml.tmp
25.01.2019 11:32:55.020 [037] [S]--> C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml
25.01.2019 11:32:55.021 [007] [S][ManagedMiner#2 - 4*1080ti] Execute command: Start
25.01.2019 11:32:55.021 [007] [S][ManagedMiner#2 - 4*1080ti] Starting...
25.01.2019 11:32:55.021 [007] [S][ManagedMiner#2 - 4*1080ti] Starting Mining Software
25.01.2019 11:32:55.021 [007] [S][ManagedMiner#2 - 4*1080ti] Setting up Miner Engine. Instance: 1
25.01.2019 11:32:55.021 [007] [S][ManagedMiner#2 - 4*1080ti] Engine Type: BMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
25.01.2019 11:32:55.021 [007] [S]EngineSetup: BMiner
25.01.2019 11:32:55.022 [007] [S][ManagedMiner#2 - 4*1080ti] : GetStaticSortedPools, Enginetype: BMiner, Algorithms: Equihash, Ethereum, Decred, Blake2b, Tensority, Cuckoo, Equihash150_5, CuckaRoo29
25.01.2019 11:32:55.022 [007] [S][ManagedMiner#2 - 4*1080ti] : GetStaticSortedPools, ignoring pools: zcoin-eu.mintpond.com:3000, Mtp.
25.01.2019 11:32:55.022 [007] [S][ManagedMiner#2 - 4*1080ti] : Adding pool: grin29.f2pool.com:13654, beam-pool.beepool.org:9507
25.01.2019 11:32:55.022 [007] [S]Device selection ordering: Standard Device ID
25.01.2019 11:32:55.023 [007] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.ISecurityService
25.01.2019 11:32:55.027 [007] [W]Failed to prepare firewall settings: C:\Users\Home\AppData\Local\AwesomeMiner\bminer-v13.1.0-8ae5450-amd64_1\bminer-v13.1.0-8ae5450\bminer.exe
25.01.2019 11:32:55.027 [007] [S][ManagedMiner#2 - 4*1080ti] Properties: (WindowMode: ConsoleFormat, EngineType: BMiner, IsProfitMiner: True)
25.01.2019 11:32:55.027 [007] [S][ManagedMiner#2 - 4*1080ti] C:\Users\Home\AppData\Local\AwesomeMiner\bminer-v13.1.0-8ae5450-amd64_1\bminer-v13.1.0-8ae5450\bminer.exe  -uri beam+ssl://229d764c85bfe0c9adf0ef40c3b71723184e9ebd96668b8f1e088e41bd1fa237791:[email protected]:9507 -watchdog=false -api=0.0.0.0:4028
25.01.2019 11:32:55.330 [007] [S]Saving configuration to: C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml.tmp
25.01.2019 11:32:55.356 [007] [S]--> C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml
25.01.2019 11:32:55.356 [007] [S][ManagedMiner#2 - 4*1080ti] Mining Engine Process started, PID: 2856
25.01.2019 11:32:57.823 [026] [S]CoinStore, Built in coin dictionary updated
25.01.2019 11:32:59.593 [038] [E]Failed to process API request (time: 1 ms): /api/v1/status/stratum
Удaлeнный cepвep вoзвpaтил oшибкy: (500) Bнyтpeнняя oшибкa cepвepa.
full member
Activity: 675
Merit: 100
Using BMiner 13.1 on Grin, in the miner console it shows the hash rate as around 4.5, but in A.M. it shows as a steady 5.0.  When the hash rate in the console drops below 4.5 it shows as 4.0 in A.M.  Is A.M. rounding to an integer value or does it come like that from the BMiner API?
newbie
Activity: 5
Merit: 0
Hello Patrike,

I decided to give Grin a try, for he purpose I spared a small rig with four GTX 1060 6GB. Due to the RAM size, I have no other option left for the sw miner of choice than NBminer.  Both Gminer and Bminer require 8GB.

That said, I configured AM to mine GRIN-29 in f2pool.
When I triggered the newly created managed miner if failed to log in to the pool. I reviewed the parameters passed and found no mistakes and all seemed to be ok as per pool instructions.
Running diagnostics leads to the following:

Initialize diagnostics (10)
Starting Diagnostics. Awesome Miner version: 6.1.5
OS: Microsoft Windows 10 Pro 64-bit
nVidia driver version: 417.01
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 7
Engine Type: BtMiner, Auto Download: True, EnginePath: C:\bote\NBMiner_Win\start_grin_f2pool getgrin.bat, Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: BtMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\GaoFuShuai\AppData\Local\AwesomeMiner\nbminer_13.2_win_7\NBMiner_Win\nbminer.exe  -a cuckaroo -o stratum+tcp://grin29.f2pool.com:13654 -u grinworker.001 --api 0.0.0.0:4034
====================================================================================================
Mining Engine Process started, PID: 6008
> [16:06:56] INFO - ----------------------------------------------
> [16:06:56] INFO - |                   NBMiner                  |
> [16:06:56] INFO - |              NVIDIA GPU Miner              |
> [16:06:56] INFO - |                    13.2                    |
> [16:06:56] INFO - ----------------------------------------------
> [16:06:56] INFO - ALGO:  cuckaroo
> [16:06:56] INFO - URL:   stratum+tcp://grin29.f2pool.com:13654
> [16:06:56] INFO - USER:  grinworker.001
> [16:06:56] INFO - ============= Device Information =============
> [16:06:56] INFO - ID 0: GeForce GTX 1060 6GB 6144 MB, CC 61
> [16:06:56] INFO - ID 1: GeForce GTX 1060 6GB 6144 MB, CC 61
> [16:06:56] INFO - ID 2: GeForce GTX 1060 6GB 6144 MB, CC 61
> [16:06:56] INFO - ID 3: GeForce GTX 1060 6GB 6144 MB, CC 61
> [16:06:56] INFO - ==============================================
> [16:06:56] INFO - NVML initialized.
> [16:06:58] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:06:59] WARN - Failed to login mining pool, please check mining pool username.
> [16:06:59] INFO - Logout.
> [16:06:59] INFO - API:  0.0.0.0:4034
> [16:06:59] INFO - API server started.
> [16:07:01] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:02] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:02] INFO - Logout.
> [16:07:03] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:04] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:04] INFO - Logout.
> [16:07:05] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:06] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:06] INFO - Logout.
> [16:07:07] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:08] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:08] INFO - Logout.
> [16:07:09] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:10] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:10] INFO - Logout.
> [16:07:11] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...
> [16:07:12] WARN - Failed to login mining pool, please check mining pool username.
> [16:07:12] INFO - Logout.
> [16:07:13] INFO - cuckaroo - Logging in to grin29.f2pool.com:13654 ...

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
Diagnostics completed

My workaround was to copy the contents of the automatic download zipped folder for NBMiner to a new folder outside the AM path and run a bat file for the same task, which worked ok, i.e. this time it was able to log in my user grinworker to f2pool ands start mining grin.

The bat does this:
nbminer -a cuckaroo -o stratum+tcp://grin29.f2pool.com:13654 -u grinworker.001:x -long-format -log

(grinworker is a moke ID not the real one I use)


Then I tried to make AW leverage the working bat by changing the software location in the Managed miner properties - General from "Automatic download" to "specify existing installation path" and pointing the path to the bat file I had succesfully run before.

In this case AM is able to log in and mine but unable to pull any information and display in the Dashboard screen  i.e power usage, also in the Pools, and GPU tab for the miner, nothing is shown, so I am not very happy with the outcome, which is a semi-integration only.

What should I do to have NBminer up & running by just using the default automatic download which is not loging in properly?

Thanks in advance!



Jump to: