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

[patrike]

Patrike,

Would it be possible to add blazepool support for manged profit miners? With all the issues with some of the pools lately it would be nice to have more options available.

Thanks for the suggestion. This pool is on my todo-list so it will probably be added.

It should also be possible to manually add these Yiimp-compatible pools, if they have a standard API available:
http://www.awesomeminer.com/help/onlineservices.aspx

[patrike]

Thanks Moppidoo, very relevant feedback and thanks for the further clarifications.

Hi Patrick, thanks for the update!

Regarding the new rule: New rule trigger for miner revenue and profit levels
Its quite a simple rule to setup and I setup a rule for profit (and later revenue) where the miner stops mining when the profit is less 5 South African Rand (then I later put in 500 South African Rand to test this), the time was set to 5 seconds to stop the miner. Unfortunately the rule wouldnt trigger on any of my miners but did work when I manually ran the rule.
If the above rule worked would it also start the miner automatically when the miner is above the profit or revenue threshold specified or do I need to setup an additional rule to start the miner after X amount of profit or revenue?

@Smartieee, I believe the  rule only looks at the current miner's profit/revenue per day in action! rather than the overall profile and periodic calculated overall profit rank, thus right at this moment, it probably doesn't do the auto starting since once your miner stopped, it probably will not be monitored by the rule when idle. I'm pretty sure Patrike can gradually expand this function further in future releases upon how useful ppl find the function to be for them and giving feedback and ideas. Right now for starters, it is already showing signs of great improvement with the first release of the feature.

It's correct that the rule currently can look at:
- Miner Revenue
- Miner Profit

The plan is to improve this rule to also look at:
- Profit Profile Revenue
- Profit Profile Profit

For a Managed Profit Miner, the rule may not trigger within the first minute the miner is running, to ensure that it's really up and running before any action is taken. The rule requires the miner to be running at the moment. Once I've implemented support for the rule to look at the Profit Profiles as well, it will be possible to take action on a miner that isn't running - for example to start it once the profit reach a specific level.

Already today it should be possible to use the Miner Profit rule to give notification warnings if a miner is claiming to generate a profit that is very high for example - which could be an indication that a pool is reporting incorrect profit values. (There will also be a built-in feature in Awesome Miner to detect this in the future).

[patrike]

Hi Patrike,

For those of us that have filled out electrical costs and watts per algo/rig would it be possible to add an estimated overall daily/monthly electrical amount for all my rigs on the dashboard (or wherever makes sense)?  The information is already there in Awesome Miner within the Online Services where I manually look at the difference between revenue and profit which I add manually across the rigs, but an automated way or checking this in realtime would be ideal.

I added BlazePool algos to Options - Online Services - User defined online services and its working well for profit switching however there are some improvements that can be made here.
- Firstly in Options - Profit Switching there isnt a way to enable and disable only using the services setup in User defined online services, currently i enable Nicehash but manually exclude each Nicehash aogo from the Online Services - Predefined online services section for it to just focus on the User defined online services
- The Predefined online services allow for bulk editing whereas the User defined online services dont allow for this, can this be added please?
- When algos are added to the User defined online services section, does AM benchmarking include/look at algos that have been setup in that section?

I fully agree that it would make sense to also display the total power usage / cost on the dashboard. Awesome Miner should know this information per miner already.

Thanks for your suggestion on improving the Online Services as well. Awesome Miner doesn't use the user defined pools for the benchmarks yet, but it probably should.

[patrike]

Why is Monero profitabilitly displayed as 0.000 ? I have external miner and the hash rate is properly calculated for Monero but it looks like AW can't get the value of monero (added json manualy still displays value 0)

You may have to manually select CryptonightV7->Monero, if it was selected as the coin Cryptonight->Monero before. I've already made a change in the new release that is about to be made available to remove any old entries of Cryptonight-Monero

[patrike]

Does anyone else have an issue with MiningDutch and the skein algorithm?

If I start Awesome Miner and I have all of my pools enabled in the profit switching menu, then Awesome Miner switches to Mining Dutch to mine the skein algo, it will instead start mining x11 (always the same, always x11).... and that is not profitable at all.... BUT, if I have only Mining Dutch selected in the profit switching menu, then start the miner, it mines skein normally with no problems.



The other problem that I have is that when I have all my pools enabled in the profit switching menu, AwesomeMiner will be mining the most profitable algo, and there will be no errors, no rejected shares, no hardware errors, but it will randomly just start mining the next most profitable algo in the list while the other algo is still the most profitable.

Also, when this happens, stopping the miner and restarting it will not make it start mining the top algo again... I have to completely close AwesomeMiner, and then it will start mining the most profitable algo again.


Does anyone else experience these issues, and what can I do to fix this?

1) Which of these pools are most profitable according to the View Details dialog (right click on the miner and select View Details)? The hashrates defined in the profit profile is what the profit switcher is looking at

2) I think you may not get any accepted shares for a period of time, and then Awesome Miner will mark the pool as "Failed" for this reason. You can disable this behavior in the Options dialog, Profit Switching section where you can uncheck "Ignore pools with no accepted shares".

Please keep an eye on this miner to make sure that it eventually starts to produce accepted shares.

[patrike]

Why AM is not showing in Miners window name of active pool? It is diffcult to see which pool is in use right now, sometimes it is showing pool name under Local text, but 99% of the time there is nothing under Local. This is what i hate most.

Is this a Managed Miner / Managed Profit Miner? Which mining software and algorithm is running when you experience this? The different mining software (Claymore miner, Ccminer, ...) reports the pool information a bit differently and in some instances all information may not be available over their API's. Awesome Miner is still trying to figure out what pool you are most likely to mine on, but there could be some scenario here where it cannot figure it out.

[patrike]

how do I display the name of the employee in the pool (zergpool.com)? on older versions of AM, the name of the employee could be prescribed in the properties of the miner. now it does not work. Thank you.

Is it the "Add to worker name" setting in the Properties of a miner? That one needs to be filled in manually. Please let me know if I misunderstood your question here.

[patrike]

Awesome Miner version 4.7

- Added new algorithms: X16r, X16s, Cryptonight-Lite and Cryptonight-Heavy

To mine Cryptonight-Heavy with XMRig 2.6+ (AMD, CPU and probably nVidia) and AM 4.7, we need to put '-a cryptonight-heavy' as an additional command line parameter.
Putting it in miner algos definition doesn't add it when launching the miner.
(Some pools continue to accept standard CN shares for CN-H. Result is that reported hashrate is great but income is about 15% of total expected)

Patrike, can you plan to activate command line algo (-a) for XMRigs miners in a future release ?

I see that the latest Beta versions of XMRig includes CN-H. I will not include it in the release that I'm planning to make available today, but this will be added to the release after that. Probably within the next few days.

[patrike]

Hey Bro,

I have been using Awesome Miner professional edition for last 6 weeks mining altcoins using my rig of 12 1080Ti GPU. Last evening I updated to V4.7 and since then whilst the mining is on I get an error "interface offline" see screenshot attached. https://www.dropbox.com/s/sdavsw1amoubuij/Capture.JPG?dl=0

Have tried restart, reboot etc. Doesn't seem to work.

The log of the miner has this error: 11-04-2018 10:16:45.484 [011] [E]Failed to process API request (time: 1005 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstat1"} 
No connection could be made because the target machine actively refused it 127.0.0.1:4028

How do I solve this?

This error indicates that the Claymore mining software isn't responding to API calls from Awesome Miner. It simply not have this port open for connections.

Can you start the miner with the Diagnostics button in the toolbar so we can verify if the command line and startup of the Claymore miner looks correct?

[coinminer-2018]

Hey Bro,

I have been using Awesome Miner professional edition for last 6 weeks mining altcoins using my rig of 12 1080Ti GPU. Last evening I updated to V4.7 and since then whilst the mining is on I get an error "interface offline" see screenshot attached. https://www.dropbox.com/s/sdavsw1amoubuij/Capture.JPG?dl=0

Have tried restart, reboot etc. Doesn't seem to work.

The log of the miner has this error: 11-04-2018 10:16:45.484 [011] [E]Failed to process API request (time: 1005 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstat1"} 
No connection could be made because the target machine actively refused it 127.0.0.1:4028

How do I solve this?

This error indicates that the Claymore mining software isn't responding to API calls from Awesome Miner. It simply not have this port open for connections.

Can you start the miner with the Diagnostics button in the toolbar so we can verify if the command line and startup of the Claymore miner looks correct?

Hey Patrike,

I did, below is the log of diagnostics. Have replaced my worker name and passwords with ##

______________________________

______________________________
Starting Diagnostics. Awesome Miner version: 4.7
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: EthClayMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Mining\AppData\Local\AwesomeMiner\EthDcrMiner64_1\Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v11.6\EthDcrMiner64.exe
C:\Users\Mining\AppData\Local\AwesomeMiner\EthDcrMiner64_1\Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v11.6\EthDcrMiner64.exe  -platform 2 -mport 0 -mode 1 -wd 1 -r -1 -logfile C:\Users\Mining\AppData\Local\AwesomeMiner\claylog.txt -allcoins 1   (WindowMode: ConsoleFormat, EngineType: EthClayMiner, IsProfitMiner: True)
Configuration:
POOL: stratum+tcp://asia.ethash-hub.miningpoolhub.com:20536, PSW: ####, WORKER: ####, ESM: 0, ALLPOOLS: 1
POOL: startum+tcp://asia.ethash-hub.miningpoolhub.com:20556, PSW: ####, WORKER: ####, ESM: 0, ALLPOOLS: 1

Secondary:

Configured command line:
-platform 2 -mport 0
Mining Engine Process started, PID: 4816

====================================================================================================
13:40:41:799   e9c   Check and remove old log files...
13:40:41:801   e9c   args: -platform 2 -mport 0 -mode 1 -wd 1 -r -1 -logfile C:\Users\Mining\AppData\Local\AwesomeMiner\claylog.txt -allcoins 1
13:40:41:801   e9c   
13:40:41:802   e9c   ����������������������������������������������������������������ͻ
13:40:41:803   e9c   �                Claymore's Dual GPU Miner - v11.6               �
13:40:41:803   e9c   �              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             �
13:40:41:804   e9c   ����������������������������������������������������������������ͼ
13:40:41:804   e9c   
13:40:41:805   e9c   b571
13:40:42:006   e9c   ETH: 2 pools are specified
13:40:42:007   e9c   Main Ethereum pool is asia.ethash-hub.miningpoolhub.com:20536
13:40:44:040   e9c   CUDA initializing...

13:40:44:042   e9c   NVIDIA Cards available: 12
13:40:44:043   e9c   CUDA Driver Version/Runtime Version: 9.1/8.0
13:40:44:842   e9c   GPU #0: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 1:0:0)

13:40:44:878   e9c   GPU #1: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 2:0:0)

13:40:44:904   e9c   GPU #2: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 3:0:0)

13:40:44:939   e9c   GPU #3: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 4:0:0)

13:40:44:965   e9c   GPU #4: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 5:0:0)

13:40:44:990   e9c   GPU #5: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 7:0:0)

13:40:45:019   e9c   GPU #6: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 8:0:0)

13:40:45:044   e9c   GPU #7: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 9:0:0)

13:40:45:074   e9c   GPU #8: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 10:0:0)

13:40:45:102   e9c   GPU #9: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 11:0:0)

13:40:45:131   e9c   GPU #10: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 12:0:0)

13:40:45:159   e9c   GPU #11: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 13:0:0)

13:40:45:160   e9c   Total cards: 12
13:40:47:162   e9c   
You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.

13:40:48:163   e9c   No AMD cards in the list, ADL library will not be used.
13:40:48:173   e9c   NVML version: 9.390.77
13:40:51:779   e9c   SSL: Imported 37 certificates from local storage
13:40:51:881   e9c   ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

13:40:51:881   e9c   ETH: eth-proxy stratum mode
13:40:51:882   e9c   "-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details.
13:40:51:882   e9c   Watchdog enabled
13:40:51:883   e9c   

13:40:51:949   23e8   ETH: Stratum - connecting to 'asia.ethash-hub.miningpoolhub.com' <172.104.95.242> port 20536 (unsecure)
13:40:52:097   23e8   sent: {"worker": "###", "jsonrpc": "2.0", "params": ["", "x"], "id": 2, "method": "eth_submitLogin"}

13:40:52:098   23e8   ETH: Stratum - Connected (asia.ethash-hub.miningpoolhub.com:20536) (unsecure)
13:40:52:248   23e8   buf: {"id":2,"jsonrpc":"2.0","result":true}

13:40:52:248   23e8   ETH: Authorized
13:40:52:249   23e8   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

13:40:52:399   23e8   buf: {"id":3,"jsonrpc":"2.0","result":["0x873eb838f3bc8248d68ad97ea8d762c07c859fc05a2cfbbff3f639024150f151","0xf14c514effe89b62170940fc9de2265eb7e0d18aae7c8198ee5788b20b90e2af","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}

13:40:52:478   1bbc   Setting DAG epoch #180...
13:40:54:461   23e8   buf: {"id":0,"jsonrpc":"2.0","result":["0x5c2236c15b39704d8bc57f3e90cd3678a21ddef27c838118ec7427ea6e036777","0xf14c514effe89b62170940fc9de2265eb7e0d18aae7c8198ee5788b20b90e2af","0x00000000ffb34c02420e9948eacd78cf33b059a88ade1ff0614f7f3c303cf3a7"]}

13:40:54:462   23e8   ETH: 04/11/18-13:40:54 - New job from asia.ethash-hub.miningpoolhub.com:20536
13:40:54:463   23e8   target: 0x00000000ffb34c02 (diff: 4300MH), epoch 180(2.41GB)
13:40:54:464   23e8   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
13:40:54:464   23e8   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s, GPU6 0.000 Mh/s, GPU7 0.000 Mh/s, GPU8 0.000 Mh/s, GPU9 0.000 Mh/s, GPU10 0.000 Mh/s, GPU11 0.000 Mh/s
13:40:54:745   1470   Setting DAG epoch #180 for GPU3
13:40:54:745   a1c   Setting DAG epoch #180 for GPU2
13:40:54:747   1c24   Setting DAG epoch #180 for GPU8
13:40:54:747   91c   Setting DAG epoch #180 for GPU6
13:40:54:745   12e4   Setting DAG epoch #180 for GPU5
13:40:54:749   19f4   Setting DAG epoch #180 for GPU4
13:40:54:750   89c   Setting DAG epoch #180 for GPU7
13:40:54:750   3e4   Setting DAG epoch #180 for GPU0
13:40:54:751   238c   Setting DAG epoch #180 for GPU11
13:40:54:748   24e8   Setting DAG epoch #180 for GPU9
13:40:54:752   a1c   Create GPU buffer for GPU2
13:40:54:753   19f4   Create GPU buffer for GPU4
13:40:54:751   1c24   Create GPU buffer for GPU8
13:40:54:750   1470   Create GPU buffer for GPU3
13:40:54:746   1bbc   Setting DAG epoch #180 for GPU10
13:40:54:756   91c   Create GPU buffer for GPU6
13:40:54:757   89c   Create GPU buffer for GPU7
13:40:54:747   23c4   Setting DAG epoch #180 for GPU1
13:40:54:755   12e4   Create GPU buffer for GPU5
13:40:54:756   3e4   Create GPU buffer for GPU0
13:40:54:760   238c   Create GPU buffer for GPU11
13:40:54:760   1bbc   Create GPU buffer for GPU10
13:40:54:761   23c4   Create GPU buffer for GPU1
13:40:54:762   24e8   Create GPU buffer for GPU9

====================================================================================================
Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
>
> ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
> º                Claymore's Dual GPU Miner - v11.6               º
> º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
> ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
>
> ETH: 2 pools are specified
> Main Ethereum pool is asia.ethash-hub.miningpoolhub.com:20536
> Be careful with overclocking, use default clocks for first tests
> Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU
> CUDA initializing...
>
> NVIDIA Cards available: 12
> CUDA Driver Version/Runtime Version: 9.1/8.0
> GPU #0: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 1:0:0)
>
> GPU #1: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 2:0:0)
>
> GPU #2: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 3:0:0)
>
> GPU #3: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 4:0:0)
>
> GPU #4: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 5:0:0)
>
> GPU #5: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 7:0:0)
>
> GPU #6: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 8:0:0)
>
> GPU #7: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 9:0:0)
>
> GPU #8: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 10:0:0)
>
> GPU #9: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 11:0:0)
>
> GPU #10: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 12:0:0)
>
> GPU #11: GeForce GTX 1080 Ti, 11264 MB available, 28 compute units, capability: 6.1  (pci bus 13:0:0)
>
> Total cards: 12
>
> You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.
>
> ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
>
> ETH: eth-proxy stratum mode
> "-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details.
> Watchdog enabled
>
>
> ETH: Stratum - connecting to 'asia.ethash-hub.miningpoolhub.com' <172.104.95.242> port 20536 (unsecure)
> ETH: Stratum - Connected (asia.ethash-hub.miningpoolhub.com:20536) (unsecure)
> ETH: Authorized
> Setting DAG epoch #180...
> ETH: 04/11/18-13:40:54 - New job from asia.ethash-hub.miningpoolhub.com:20536
> ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
> ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s, GPU6 0.000 Mh/s, GPU7 0.000 Mh/s, GPU8 0.000 Mh/s, GPU9 0.000 Mh/s, GPU10 0.000 Mh/s, GPU11 0.000 Mh/s
> Setting DAG epoch #180 for GPU10
> Setting DAG epoch #180 for GPU3
> Setting DAG epoch #180 for GPU5
> Setting DAG epoch #180 for GPU2
> Setting DAG epoch #180 for GPU8
> Setting DAG epoch #180 for GPU1
> Setting DAG epoch #180 for GPU6
> Setting DAG epoch #180 for GPU9
> Setting DAG epoch #180 for GPU4
> Setting DAG epoch #180 for GPU7
> Create GPU buffer for GPU3
> Setting DAG epoch #180 for GPU0
> Setting DAG epoch #180 for GPU11
> Create GPU buffer for GPU8
> Create GPU buffer for GPU2
> Create GPU buffer for GPU4
> Create GPU buffer for GPU5
> Create GPU buffer for GPU6
> Create GPU buffer for GPU0
> Create GPU buffer for GPU7
> Create GPU buffer for GPU11
> Create GPU buffer for GPU10
> Create GPU buffer for GPU1
> Create GPU buffer for GPU9
> Quit, please wait...
> GPU3 DAG creation time - 5648 ms
> Setting DAG epoch #180 for GPU3 done
> GPU0 DAG creation time - 5637 ms
> Setting DAG epoch #180 for GPU0 done
> GPU6 DAG creation time - 5634 ms
> Setting DAG epoch #180 for GPU6 done
> GPU5 DAG creation time - 5643 ms
> Setting DAG epoch #180 for GPU5 done
> GPU1 DAG creation time - 5639 ms
> Setting DAG epoch #180 for GPU1 done
> GPU8 DAG creation time - 5646 ms
> Setting DAG epoch #180 for GPU8 done
> GPU7 DAG creation time - 5636 ms
> Setting DAG epoch #180 for GPU7 done
> GPU9 DAG creation time - 5639 ms
> Setting DAG epoch #180 for GPU9 done
> GPU2 DAG creation time - 56
Diagnostics completed

[patrike]

Hey Bro,

I have been using Awesome Miner professional edition for last 6 weeks mining altcoins using my rig of 12 1080Ti GPU. Last evening I updated to V4.7 and since then whilst the mining is on I get an error "interface offline" see screenshot attached. https://www.dropbox.com/s/sdavsw1amoubuij/Capture.JPG?dl=0

Have tried restart, reboot etc. Doesn't seem to work.

The log of the miner has this error: 11-04-2018 10:16:45.484 [011] [E]Failed to process API request (time: 1005 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstat1"} 
No connection could be made because the target machine actively refused it 127.0.0.1:4028

How do I solve this?

This error indicates that the Claymore mining software isn't responding to API calls from Awesome Miner. It simply not have this port open for connections.

Can you start the miner with the Diagnostics button in the toolbar so we can verify if the command line and startup of the Claymore miner looks correct?

Hey Patrike,

I did, below is the log of diagnostics. Have replaced my worker name and passwords with ##

______________________________

______________________________
Starting Diagnostics. Awesome Miner version: 4.7
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: EthClayMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Mining\AppData\Local\AwesomeMiner\EthDcrMiner64_1\Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v11.6\EthDcrMiner64.exe
C:\Users\Mining\AppData\Local\AwesomeMiner\EthDcrMiner64_1\Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v11.6\EthDcrMiner64.exe  -platform 2 -mport 0 -mode 1 -wd 1 -r -1 -logfile C:\Users\Mining\AppData\Local\AwesomeMiner\claylog.txt -allcoins 1   (WindowMode: ConsoleFormat, EngineType: EthClayMiner, IsProfitMiner: True)
Configuration:
POOL: stratum+tcp://asia.ethash-hub.miningpoolhub.com:20536, PSW: ####, WORKER: ####, ESM: 0, ALLPOOLS: 1
POOL: startum+tcp://asia.ethash-hub.miningpoolhub.com:20556, PSW: ####, WORKER: ####, ESM: 0, ALLPOOLS: 1

Secondary:

Configured command line:
-platform 2 -mport 0
Mining Engine Process started, PID: 4816

Thanks for sharing the details.

It looks like you manually added this command line "-mport 0". This will disable the API of the Claymore software. If you simply remove this part it should work.

[coinminer-2018]

Hey Bro,

I have been using Awesome Miner professional edition for last 6 weeks mining altcoins using my rig of 12 1080Ti GPU. Last evening I updated to V4.7 and since then whilst the mining is on I get an error "interface offline" see screenshot attached. https://www.dropbox.com/s/sdavsw1amoubuij/Capture.JPG?dl=0

Have tried restart, reboot etc. Doesn't seem to work.

The log of the miner has this error: 11-04-2018 10:16:45.484 [011] [E]Failed to process API request (time: 1005 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstat1"} 
No connection could be made because the target machine actively refused it 127.0.0.1:4028

How do I solve this?

This error indicates that the Claymore mining software isn't responding to API calls from Awesome Miner. It simply not have this port open for connections.

Can you start the miner with the Diagnostics button in the toolbar so we can verify if the command line and startup of the Claymore miner looks correct?

Hey Patrike,

I did, below is the log of diagnostics. Have replaced my worker name and passwords with ##

______________________________

______________________________
Starting Diagnostics. Awesome Miner version: 4.7
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: EthClayMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Mining\AppData\Local\AwesomeMiner\EthDcrMiner64_1\Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v11.6\EthDcrMiner64.exe
C:\Users\Mining\AppData\Local\AwesomeMiner\EthDcrMiner64_1\Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v11.6\EthDcrMiner64.exe  -platform 2 -mport 0 -mode 1 -wd 1 -r -1 -logfile C:\Users\Mining\AppData\Local\AwesomeMiner\claylog.txt -allcoins 1   (WindowMode: ConsoleFormat, EngineType: EthClayMiner, IsProfitMiner: True)
Configuration:
POOL: stratum+tcp://asia.ethash-hub.miningpoolhub.com:20536, PSW: ####, WORKER: ####, ESM: 0, ALLPOOLS: 1
POOL: startum+tcp://asia.ethash-hub.miningpoolhub.com:20556, PSW: ####, WORKER: ####, ESM: 0, ALLPOOLS: 1

Secondary:

Configured command line:
-platform 2 -mport 0
Mining Engine Process started, PID: 4816

Thanks for sharing the details.

It looks like you manually added this command line "-mport 0". This will disable the API of the Claymore software. If you simply remove this part it should work.

Thanks a ton. Problem solved. you are a star :-) !

[vitlab]

how do I display the name of the employee in the pool (zergpool.com)? on older versions of AM, the name of the employee could be prescribed in the properties of the miner. now it does not work. Thank you.

Is it the "Add to worker name" setting in the Properties of a miner? That one needs to be filled in manually. Please let me know if I misunderstood your question here.

я имeл ввидy этo...
1 https://drive.google.com/open?id=1hnQtiqUBCDnyPG1K5uz3UtP5BR2RKBGX
2 https://drive.google.com/open?id=1DKk4RoHEFOtUQzZjRyF-jEiczbiTx2lv
why there is no picture insertion (((

[vitlab]

@patrike
I understood with "X16r"
now can not run "skein" (sgminer) on MPH. I copied various variants. Help!!! There is no speed. Only "HW Errors"
Thank you

[Panzar]

6xRX480 "x16r" sgminer on zergpool, does not work.
help

Hi. Please share more details what the error is. It's also recommended to start the miner with the Diagnostics button, and use the GPU mining troubleshooting guide to resolve some of the common problems:
http://www.awesomeminer.com/help/troubleshooting-gpu.aspx

lots of HW Error. shows not the correct speed. 380kh/s.
6RX480 8Gb. there must be a minimum of 42Mh/s

For the speed, try setting intensity via command line, like:
-I 19

Try this: -I 19 --gpu-platform 1

[moppidoo]

how do I display the name of the employee in the pool (zergpool.com)? on older versions of AM, the name of the employee could be prescribed in the properties of the miner. now it does not work. Thank you.

Is it the "Add to worker name" setting in the Properties of a miner? That one needs to be filled in manually. Please let me know if I misunderstood your question here.

я имeл ввидy этo...
1 https://drive.google.com/open?id=1hnQtiqUBCDnyPG1K5uz3UtP5BR2RKBGX
2 https://drive.google.com/open?id=1DKk4RoHEFOtUQzZjRyF-jEiczbiTx2lv
why there is no picture insertion (((

Most Yiimp pools that I've came across don't support -u wallet.rigname format, instead you have to define rigname (worker name) in the password field. Just for example, something like -p ID=rig1,c=BTC, I highly doubt going through the gui add worker name does what you want, but I never used it so can't say for sure. What I thought it does is it adds worker name based on conventional wallet(delimiter)rigname format in the -u field and not the -p field.

[patrike]

Awesome Miner version 4.7.1

- Antminer diagnostics feature improved to test the API connection
- Updated Mining Pool Hub pool for CryptonightV7
- Correction to MSI Afterburner integration to wait longer for the UI application to start after a reboot
- Correction to remove old Monero Cryptonight reference in favor of the new CryptonightV7 version
- Correction to Remote Proxy feature for connecting to correct hostnames

Thanks to the recent performance improvements in the software, it can now manage up to 10,000 miners.

[patrike]

Another update: There are a number of people that are running Youtube channels, blogs and also discuss a lot on the forums on the topic of mining and Awesome Miner. I've been receiving a number of requests about introducing an affiliate program.

The idea is that if you sign up for the Awesome Miner Affiliate Program, you can get a referral link that you can put on your blog or in your forum signature. For each Awesome Miner license sale that is made where you referred the customer to the Awesome Miner web site, you will get a commission (for example 8 - 12 % of the license cost). The commission will only be provided for new license sales, not for upgrades or Cloud Services.

The Affiliate Program is not fully ready to go public yet, but I want to let you know what's in the pipeline. Thanks!

[textb0ok]

Does anyone else have an issue with MiningDutch and the skein algorithm?

If I start Awesome Miner and I have all of my pools enabled in the profit switching menu, then Awesome Miner switches to Mining Dutch to mine the skein algo, it will instead start mining x11 (always the same, always x11).... and that is not profitable at all.... BUT, if I have only Mining Dutch selected in the profit switching menu, then start the miner, it mines skein normally with no problems.



The other problem that I have is that when I have all my pools enabled in the profit switching menu, AwesomeMiner will be mining the most profitable algo, and there will be no errors, no rejected shares, no hardware errors, but it will randomly just start mining the next most profitable algo in the list while the other algo is still the most profitable.

Also, when this happens, stopping the miner and restarting it will not make it start mining the top algo again... I have to completely close AwesomeMiner, and then it will start mining the most profitable algo again.


Does anyone else experience these issues, and what can I do to fix this?

1) Which of these pools are most profitable according to the View Details dialog (right click on the miner and select View Details)? The hashrates defined in the profit profile is what the profit switcher is looking at

2) I think you may not get any accepted shares for a period of time, and then Awesome Miner will mark the pool as "Failed" for this reason. You can disable this behavior in the Options dialog, Profit Switching section where you can uncheck "Ignore pools with no accepted shares".


Please keep an eye on this miner to make sure that it eventually starts to produce accepted shares.

1) I am using the nvidia profile (fully benchmarked and saved to profile) in my online services tab. When skein algo on Mining Dutch is most profitable.... It's because your software is telling me it is the most profitable. Clicking view details to see the most profitable gives me the same information as the online services tab.
The issue is that it's not actually mining skein like I said. (Unless I uncheck all pools in profit switching menu and only allow Mining Dutch)

At the very least, if there is no fix for me... Is there at least a way to disable just 1 specific algo for 1 specific pool??? If that is not possible, could you please add that in an update? I believe the ability to disable specific algos for specific pools would help a lot of people. I looked around but never found any option to do this.

2) Again, like I said.... AwesomeMiner will be mining the most profitable algo, and there will be no errors, no rejected shares, no hardware errors, but it will randomly just start mining the next most profitable algo in the list while the other algo is still the most profitable.


Could the shares just be taking too long? I have ignore pools with no accepted shares set to 5 minutes. 

EDIT: Yes I believe I had the setting "Ignore pools with no accepted shares (in minutes)" set too low. Setting this number higher or disabling it appears to keep miners mining when they are working harder for shares in certain cases. But this still does not explain why AwesomeMiner starts mining x11 on Mining Dutch when it is supposed to be mining skein.... and it is only with skein, like right now I have some rigs mining Nist5 on Mining Dutch, and none of them are having any issues and they are all mining the correct algo.

[moppidoo]

Does anyone else have an issue with MiningDutch and the skein algorithm?

If I start Awesome Miner and I have all of my pools enabled in the profit switching menu, then Awesome Miner switches to Mining Dutch to mine the skein algo, it will instead start mining x11 (always the same, always x11).... and that is not profitable at all.... BUT, if I have only Mining Dutch selected in the profit switching menu, then start the miner, it mines skein normally with no problems.



The other problem that I have is that when I have all my pools enabled in the profit switching menu, AwesomeMiner will be mining the most profitable algo, and there will be no errors, no rejected shares, no hardware errors, but it will randomly just start mining the next most profitable algo in the list while the other algo is still the most profitable.

Also, when this happens, stopping the miner and restarting it will not make it start mining the top algo again... I have to completely close AwesomeMiner, and then it will start mining the most profitable algo again.


Does anyone else experience these issues, and what can I do to fix this?

1) Which of these pools are most profitable according to the View Details dialog (right click on the miner and select View Details)? The hashrates defined in the profit profile is what the profit switcher is looking at

2) I think you may not get any accepted shares for a period of time, and then Awesome Miner will mark the pool as "Failed" for this reason. You can disable this behavior in the Options dialog, Profit Switching section where you can uncheck "Ignore pools with no accepted shares".


Please keep an eye on this miner to make sure that it eventually starts to produce accepted shares.

1) I am using the nvidia profile (fully benchmarked and saved to profile) in my online services tab. When skein algo on Mining Dutch is most profitable.... It's because your software is telling me it is the most profitable. Clicking view details to see the most profitable gives me the same information as the online services tab.
The issue is that it's not actually mining skein like I said. (Unless I uncheck all pools in profit switching menu and only allow Mining Dutch)

At the very least, if there is no fix for me... Is there at least a way to disable just 1 specific algo for 1 specific pool??? If that is not possible, could you please add that in an update? I believe the ability to disable specific algos for specific pools would help a lot of people. I looked around but never found any option to do this.

2) Again, like I said.... AwesomeMiner will be mining the most profitable algo, and there will be no errors, no rejected shares, no hardware errors, but it will randomly just start mining the next most profitable algo in the list while the other algo is still the most profitable.


Could the shares just be taking too long? I have ignore pools with no accepted shares set to 5 minutes.  

EDIT: Yes I believe I had the setting "Ignore pools with no accepted shares (in minutes)" set too low. Setting this number higher or disabling it appears to keep miners mining when they are working harder for shares in certain cases. But this still does not explain why AwesomeMiner starts mining x11 on Mining Dutch when it is supposed to be mining skein.... and it is only with skein, like right now I have some rigs mining Nist5 on Mining Dutch, and none of them are having any issues and they are all mining the correct algo.

1) I assume you are using built-in Online Services, in this case, yes you can disable algo per pool just by Online Services -> Select one(s) you want to edit (multi select with shift/ctrl possible) and press Edit/Buik Edit -> Uncheck the Include in Managed Profit Switcher box, this part was pretty straight forward hence not easy to search for posts with similar issue

2) If you are having the problem of pools deactivated due to no accepted shares, check the port you are using, and read the getting started page @ Mining-Dutch on which port to use for your hardware. In fact, the default Online Services currently in AM v4.7 is probably using the wrong port for most hobby miners (9998 is High Diff on Skein Multiport at MD) hence you are not getting accepted shares fast enough. Just change the port to Vardiff and try again. since I believe you have quite capable HW, you might not need to use the Low Diff port.

***
PS, if you have no ASICs or ASICs for certain ASIC algos, I suggest you disable most of the ASIC algos since no point mining them with GPUs/CPUs, disable via 1) ....above.

***
PPS.
While you might be experienced miner, I guess you are relatively new to AM or Profit Switching. My suggestion is to test various online services and find out which one suits you and filter out the ones that doesn't. If you don't do Auto Exchange at all, I suggest you look away from the Built-In Yiimp pools and manually add only the ones you like to use via Pool Groups.