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

I have just let AM start updating to the newer version (4.4.1).  It removed my installed version (btw, Premium License, only computer installed).  I had to download the installer again, but it couldnt install (some error while installing a service).  After the computer restared, the installation proceeded correctly and, thankfully, it didnt lose the configuration.

Being polite to people who try to help you might give you better results. Jus sayin'.

Now, onto your question - the AM is not particularly clear on what you need to put into your managed software "User defined command line argument". What it should be is the line that starts with the algorithm. So if you want to change intensity for your phi algo, your command line arguments should read (no quotes), "phi --intensity 25" or "phi -i 25". I saw a few people on this thread (and myself at the first attempt) to putting just "-i 25" to the user defined command line argument and wondering why ccminer shuts down right after the start. If you try to diagnose it, you'll see that it throws an error "unknown algorithm" and the command line after -a parameter is missing "phi".

I've seen a number of discussions about the Excavator miner, and I've just implemented initial support for the recent versions of Excavator as an External Miner. It's included in the latest Awesome Miner release where it's at least possible to monitor it.

I do have an implementation for it as a Managed Miner in the pipeline as well, but that one needs a bit more testing before I will release it. More operations will also be made available later on.

The Excavator mining software is a bit special, and it looks like the configuration file needs to be specified with the number of workers you want for each GPU (the worker.add command). From an Awesome Miner point of view it would be great if Excavator simply could use all GPU's by default, because having Awesome Miner detecting GPU's first and then launch Excavator with a configuration based on this is a possible source of error.

The Excavator miner also provides very few configuration options via the command line, making it difficult to override any behaviors that Awesome Miner will enforce by default. I will try to come up with a good way to support this software anyway, but it's has a "unique" design.

In addition to the above, the Excavator miner will never be downloaded automatically due to the restrictions in the Nicehash EULA.

Its not crashing, Im asking just in case


Thats it. That works flawlessly.

Also, where do I specify the OC settings for my Gpus that should be applied after system restart ? 

Anyhow.... I found the correct solution.

The "User Defined command line argument" replaces the command line argument to the left of it.

In my case I was trying to modify the intensity for phi in CcMiner. the existing "default" command line argument was simply "phi"

to get "User Defined command line argument" to work, I first needed to include phi, such that the "User Defined command line argument"  became: "phi -i 20" without the quotes.

Hope this helps someone in the future.

I don't believe I called anyone lazy or said that AM was cheating me out of my right to make millions per day, mining.

 

your advice is a "work-around" that frankly, shouldn't have to be used.

First, I'm not eminer001. Second, I'm a paying customer. Third, the functionality is documented here https://www.awesomeminer.com/help/managedsoftware.aspx
in my case it does not work in a manner that would be expected.

I'm asking if this is a known bug? am I doing it incorrectly? Is intensity a command line argument that cannot be set in the algo section of the managed software? your work around does not address any of those.

Hi,

If this is for the auto start of a miner after reboot, there is actually a setting in the Options dialog, Advanced section, that I added quite recently for this. "Delay auto start of miner after reboot".

One thing I can think of is delaying AM service start - you can achieve it in a variety of ways with the simplest being setting it start option to Autostart (Delayed). I use AlwaysUp to keep several pieces of software running as services and starting up at the machine boot and there you can have better control of what starts when. But apparently none of these solutions have anything to do with AM - it'll try to start a miner the moment it detects the connection to AM service, so I guess the trick is to delay the availability of the latter.

Are you saying that your whole rig crashes because a misconfigured mining software?  That's a bad situation.  There's a couple of things you can do.  Disable the rule that initiates the reboot sequence with the smart plugs until you can troubleshoot the problem.  When done, turn the rule back on.  Another thing you can do is hover your mouse over the stop button and as soon as AM kicks on the mining software click stop immediately... to keep the mining software from progressing to the point where it crashes the whole rig.  You can also disable the autostart miner from the managed miner or profit miner.

Hello eminer001. 

Guys, is there any way how to add delay before "autostart miner" kicks in ?

What I mean is, lets say, you do overclocking or something that may cause the mining to become unstable. System freezes, you restart it with "smart plug", system boots, but will load unstable profiles and start miner = crash again.
Is there any way how to add timer(delay) before the miner starts automatically so meantime you can make changes if needed. (using AM + EWBF for zclassic).
When I wasnt using AM, i had this "timeout 120" in the miners .bat file.

His suggestion does work - if you're using a pool that is phi only, or a multi-algo pool with a phi specific port, just set the intensity at either the pool or multi-algo pool.

That said, I believe you're trying to do as the picture shows here (set user defined command line arguments) at the miner level. If that isn't working then it indeed is a bug. https://www.awesomeminer.com/help/managedsoftware.aspx

but your solution/advice is not what I need or want.


Background: In Awesome Miner > Managed Software, there exists the ability to add a "User Defined command line argument"  for each supported Algo of the mining software. (in my case Ccminer/Phi)

Expectation:adding -i 20 or --intensity=20 to the "User Defined command line argument" results in CcMiner using an intensity of 20 for Phi algo

Result: CcMiner launches and closes within seconds, red error message shown too quickly to read. Log shows that the default -i 25 is included in the command line argument along with my user defined -i 20, causing CcMiner to crash

Resolution: user defined intensity should replace the default intensity

Right, I'm trying to help you diagnose the problem so we can see if it's a bug that Patrike needs to address.

You are kind of a jerk... so... good luck.

In this case, does CC miner still register accepted shares (not talking about hash rate)? If not, the accepted shares rule would address your problem. If you unplug your router and had no internet, a rule if a miner is offline would also address this problem. 


You can set a custom intensity per pool which would solve your problem if you're using a managed miner. If you're using a multi algo pool under a multi profit miner, you can set intensity per pool port which would give you a unique intensity per algorithm for CC miner.

You can also set intensity individually per card with cc miner.

I think the developer is doing a great job and it's the tone you use throughout this thread isn't helping you.  

Hi, i've been using the miner and i have  some ideas about improving the graphical interface:

- when you search for awesome miner agents put a field in the wizard to enter the password, so you don't have to enter the password for each host - if you add lots of miner it is tiresome to modify each one.
- add a checkmark in miner properties to get the worker name from the description, so you don't have to always check "add to worker name" and type the worker for each miner
- make a "clone" button for the managed hosts section
- make the hw errors text color in webserver red so it pops out and see it better
- make a button to map all the selected miner gpus to system monitoring
- maybe add a tooltip so when you hover with the mouse above the miner after 2 you can see the  details ( command line arguments and configuration )
- in the right click menu add an option to rdp ( remote desktop ) to the miner
- important - add an option to remove all income/revenue data in the dashboard  from the view only / control view user roles

I've done this also. The problem is that you can not specify intensity for each algo for ccminer or every other miner.  
The window was closing in my case with the error "out of memory" for a part of the algos and i was able to view this with "Diagnostics" function from toolbar.

Having custom intensity settings specially for your GPU will increase your income by 30%. Default intensity values varies from one different chip to another but for example for Nvidia 1080 chip used on Gigabyte AORUS that is made from copper plate you will be able to get 20% more hash rate than a low end KFA2 1080 GPU that does not have copper pipes or copper plate, it has a small steel radiator.  So, ccminer does not know you have AORUS and it starts with minimal intensity settings for 1080, the same happens if you have water cooled gpu or the gpu rig submersed in mineral oil that offers huge overclocking advantage.

I believe this should be considered a priority by the developer of AM, instead of answering emails he should focus on fixing all issues with the software that are critical, because not taking an action and loosing money is as bad as AM crashing and being useles.

Have a great day.  

You did not understand the question.

Read again and test it yourself.

Try and unplug network cable to check in the simplest way. 

The problem is that if zpool is under DDOS attack, when ccminer tries to submit the shares it shows "connection refused" error. During this period AM does not update hashing rate and remains with the old hashrate for minutes or even hours. This is a big mistake from implementation algorithm because AM waits for updates from a miner that could be broken instead of AM having a computed hash rate per second that will solve a lot of problems like the one from above, when if you have 24 hours statistics you could have ccminer stucked for 12  hours or more instead of having it restarted (or switching to next one from statistics list) by AM like it suppose to do in a correct way.

Dear puwaha , next time try and understand and test things before writing wrong and misleading answers.

Have a nice day.
   

I haven't tried that, because that would apply it to any miner/algo. I just need it for one specific case