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

you have to use AM as a monitor and use any of the miners ethOS offers but that miner has to offer some kind of API access and set up AM as a network miner, i use Ethos and monitor two rigs using CM 12.4 as the miner . I don't think you can set up a managed miner in Linux with AM it only runs with windows in remote or as the main controller, you may be able to run it in Linux with boot camp, i think it's called can't say,I  never used that and don't care to .....I only use Ethos because it is more stable then windows and not because of AM ..


The same thing should work if your are using the free version of  ethos  the miner has to allow some form of API access or it won't work or use the Generic miner way in AM if it doesn't  but that doesn't  do much but let you see what the miner is doing with  AM ... if that's all you need you set  that up with managed miner but it is very very limited in what it does but you can see the miner or GPUs .I'M not sure if that works with Linux only tried it with windows..

Is there a way to use awesome miner with ethos ethminer? Do I need to enable api?

so far so good ::: i didn't even know there was a 12.4 cm out yet, i hadn't looked, it down loaded over to the remote PC, everything seems good now .

Thanks again i still plan to max out my copy of AM, taking care of some others things first ... any issues, i will let you know in a email as requested.

Awesome Miner verison 2.4.1 has been released:
- Added rule trigger for Ping timeout
- Display miner API response time on summary tab
- Claymore's Zcash Miner 12.4 and Claymore's Ethereum Miner 8.1
- Corrections to Managed Template implementation and connection stability

Please upgrade to version 2.4.1 and let's continue the discussion about the log files by mail.

You need to define a coin (specifying Ethereum) for the pool in Awesome Miner. If you select a miner, and then look at the Pools tab, you should be able to define a Coin for the pool. If the pool isn't defined in Awesome Miner, you may have to import it first.

patrike  did you get my logs just making sure ... I'm  still having some issue using 2.3 on a remote PC while using 2.4 on the main PC  or even using 2.4 on the main rig with 2.4 remote but was fine using 2.3.1 on all rigs ...I would go back to 2.3.1 on all Rigs but i only saved the remote version for 2.3.1 ...


The issue are still the same as posted above 2.4 remote won't load on the remote PC well even if it does and some times it can be a bear getting 2.3.1 to work with 2.4 on the main rig ..


and atm on two remote RIGS  use ethos i have found Linux is more stable then win 10 using 3 or more GPU's  per rig ... not faster just a lot more stable ......and use awesome still to monitor those RIGS it's the other rigs having issue that I have windows on still with awesome miner ...My main PC will all ways use windows (because i would rather use windows ) and have two cards in it but it gets used for everything including mining ... the other windows rig has two cards and is kind of like my main PC but used mostly for mining.Right now the two ethos rig have three cards each, one has all 470 and the other one has two r7 370 and one r9 280, is used mostly for ZEC amd xmr  mining the 470 rig is used for eth mostly and some ZEc depends on the prices ..next month i plan to get at least one more 470 for the 470 rigs it is slowly building it's a hobby for me and i just bought a 136 MH A4 in two month should be able to buy A L3 i may never go back to direct BTC mining.

Pools is coinotron for ETH + coinmine.pl for DCR

What kind of pool/coin is it?

if i setup to watch on external miners working on Claymore Dual miner, how i can setup to see day and month profit on Dashboard ?



in miner settings i chose Dual miner

Additional Feature Request:

Add a counter for 'failed' or 'crashed' instances on each rig. Basically each instance is essentially a miner right now, listing how many times the miner has crashed on the system or restarted would be helpful.

I went back to 2.3.1 on the remotes for now still having issue 2.4 seems ok on the main RIG/PC . !! the post above this one says it all .....!!! by  bensam1231

Looks like a nice jerry-rigged fix, there is a lot of overlap between multiple categories (pools, hosts, templates, and miners), but it looks like a nice dirty fix.

Somethings that definitely are needed.

Right now you need to be able to upload a piece of mining software to a template. IE the machine will search to see if the software is already uploaded in the upload directory and use it OR it will auto-upload the software. Since I can only currently use two instances, it's hard to figure out if it already does this since I've been uploading to multiple machines. Also right now when you first add a template you can't select via uploaded software (perhaps this pertains to what I mentioned earlier). Once the template is made you can select a custom miner though.


Is there a way to add a wait time between killing a mining instance and starting a new one for when you're switching templates?

Also ending each mining instance with ctrl+c can sometimes prevent miner hangs (instead of outright killing the process). If there is a way to execute this and waiting like 10 seconds for the miner to exit before killing the process would be nice.

Error handling on the miner end also seems to not be handled very well. IE if a miner is killed and one of the drivers hangs, it starts the new process and it doesn't launch right away (because the system is issuing a driver reset), AM will simply list the device as 'mining' even though it's not. If AM can read when a 'driver resets' and tells you on the AM management console, that would be helpful for diagnosing problems remotely. A automatic restart would also be useful in this case.

not sure why but it started working after a few reboots and re installs, of the main software and remote agent,  so far on 2 rigs, i shut off the other two rigs sense they showed the same thing in the logs and only run the main PC rig and one rig online I have 4 GPU rigs im slowly building  with 2 Script miners and a A6 which was off  in my very small farm  and i left on one of the script miners (136 MH miner), i know has nothing to do with it, i had that miner shut off in AM in the net work part, that miner is on its own Linux controller...

I sent the logs any way hope they help for later on to help avoid it if possible ...... or it could have been my network not adjusting to the updates at first and I didn't wait long enough ...

Thanks, it works perfect !

Yes, Awesome Miner works fine with both Antminer R4 and T9.

Please send the log files to info[at]awesomeminer.com
Thanks!

Thanks for the reply. I tought it was the miner IP and not the computer IP. It works now.

Does it works with R4 and T9 ?

what email the log is to big to post in a PM to many character's and  i can't figure out how to send attachments on the forums or if it is even Poss  .. even went to Awesome miners site looking for a support email , I 'm sure I missed it if there is one ....

Could you please send me the log file (preferrably both from Awesome Miner and for the Remote Agent) by mail, and I will have a look.