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

Hi,

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

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

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

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

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

0.1 and 0.15, does not match 

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

AwesomeMiner Coin Updater 0.8

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

You can find the latest update in my sig.

Excellent update Patrike, appreciate the SRBMiner support

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

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

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

Patrike,

Finally got a switch that I could evaluate.

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

BUT HERE IS the problem

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

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

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

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

http://prntscr.com/jegwar

There is no sol/s for Equihash algo 

https://cdn.discordapp.com/attachments/434599369606692865/442733619036028928/unknown.png

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

nevermind i just deleted everything out of the registry.

How can I remove all traces of Awesome Miner?  One of my computers has a corrupted installation of the remote agent.  Windows remove doesn't let me uninstall it.  Trying to install Awesome miner over top of it says it's already installed (it isn't).  Trying to install the remote agent tries to uninstall the existing one, which fails.

Awesome Miner version 4.7.7 ( Development preview of 5.0 )

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

This development release will be released as Awesome Miner 5.0 during next week.

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates

Direct download links:
http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
http://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi

Yes, it should. So "Start clocking for first algorithm" -> "Stop clocking for first algorithm" -> "Start clocking for second algorithm" should be the work flow for executing the clocking profiles during profit switching.

If you don't make any progress, you could send me the details via mail and let me know the exact time where it failed - and also what the expected behavior was. Thanks!

Ok, thanks, I'll check that... at first blush, on each change, I'm only seeing the start commands being executed never the stop.

Shouldn't it do a start before it starts mining and a stop *before* it changes to something else, and then the associated start for the new algo?

I think this needs to be investigated via the Remote Agent log file on the computers where you run the mining. It's possible to search for "Executing GPU clocking command" to see what commands Awesome Miner sends to MSI Afterburner.

The closest feature that's available today is the Performance History, where you can export the hashrate (that will be 0 in case the mining isn't working) if all miners for analysis in Excel and similar applications:
http://www.awesomeminer.com/help/performancehistory.aspx

Having that said, I do agree that it can be useful to see the information you request in an easier way. I've also received similar requests about logging how long a miner has been on a specific pool or algorithm.

The plan is to support some kind of networking over the Cloud Services for Remote Agent in the future. The idea is to make it easier to use than a VPN network. Both Awesome Miner and Remote Agent would connect to the Awesome Miner Cloud Services to exchange information.

Thanks for your feedback!

Patrike,

I'm still getting about 50% on automatically changing OC between algos when I'm profit mining.

Sometimes it does, sometimes it doesn't.

Here's how I basically have it setup.

I created a
1080Ti - Normal ( this is for most everything and is used as the stop OC )
1080Ti - x16r
1080ti - Phi

1070ti - Normal
1070ti - x16r
1070ti - Phi

Then I have these groups
am1r - normal
    - 1080ti - Normal
       - devices 0-5
am1r - Phi
   - 1080ti - Phi
       - devices 0-5

am2r - normal
    - 1070ti - Normal
        - devices 0-5
am2r - Phi
    - 1070ti - phi
        - devices 0-5

I had to do the groups because there is a non-gpu video driver and it would crash when the AB tried to update it

For a phi algo in the profite profile
I would set the am(1/2)r - phi as start and am(1/2)r - normal as the stop

it's a similar thing for x16r

But what is happening is that if it switches to Phi and sets that OC, then the next switch is to x16r, it never sets the am(1/2)r - x16r group and so the miner runs on the phi OC.  it's true the other way as well.

And also about 50% of the time, it never switches back to normal on a stop.

I looked at the log and I see no reference to the start or the stop there, but occasionally I need a enumeration of the GPU setups/groups.

anyone else doing this and have ideas/suggestions, etc.  I'm running the latest AB 4.5.0 with the updated AB remote so I could change this to card names instead of devices, but I suspect the same would occur.

UPDATE:
it appears that the first miner (am1r) gets set *mostly* right, but the second one (am2r) does not, could there need to be a programmable delay betweeen the OC command changes from miner a to miner b?

Good afternoon
Need such a function as the work counter separately for each miner
ie how long was he in the uptime and how many are offline
With the ability to reset the timer.
Ie start the timer for 10 miners and looked after three days how many of them have worked without failures and at what time.
How much it took to reboot and how many reboots.
How long was the downtime.

It would also be very convenient to have a built-in vpn server to connect external miners located geographically far away from the main farm.

Great, thx for support

Answer to your question exactly word by word, here on the same page when you posting this question

https://bitcointalksearch.org/topic/m.36113506