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

I have been trying to setup Awesome Miner for a custom pool like altminer, but I just keep getting HTTP Request failed when the miner start. Am I missing something in the pool setup? Pasted the server url like this:eu1.altminer.net:10000, for GoByte coins. Im missing something?

You are not right. Try to see what happens if one pool is under DDOS attack and no shares are submitted. AwesomeMiner remains stuck for hours with the last value submitted from the report instead of stopping that miner. An option with a value we can configure to disconnect that miner / pool if it does not report any new values for a number of minutes or is reporting the same value, will help us stop loosing thousands of dollars every minute. You have a big responsibility, you know?

What pools do you use that are reliable and with good 24h stat profit ?

Can you please integrate into to software other bigger and more reliable pools?

Also I think price statistics could be improved to take prices from more exchang s with more volume on various less known coins that lead to bad coin mining, is it possible ?

To get insight why the profit switcher selects a specific algorithm, right click on the miner and select View Details and go to the Profit switching tab. Please note that these hashrates and profit estimates are based on what is defined in the Profit profile. They may not match the actual hashrate and profit. If they are not matching, please use the Benchmark feature or manually edit the profit profile to ensure they match, otherwise the profit switcher may select a less profitable pool.

Awesome Miner didn't process this algorithm correctly from WhatToMine. I've made a correction for it now that will be included in the next release.

The general answer first:
A later version of Awesome Miner often includes later versions of the mining software as well and these kind of crashes that happens after a while has often very little to do with Awesome Miner. To troubleshoot, is it a specific software like EWBF or Claymore Cryptonight that is crashing? Is it the only software that is instable, or what about the others?

I did see your previous post that you could see this for both CPU and GPU mining. I would recommend to take a look at the rules you have in Awesome Miner. Also, is this on a remote computer via Remote Agent?

I also noticed few lines of the log file in a previous post, but it was a little too short of information what happend just before those lines. Was it a crash that Awesome Miner detected and simply restarted the mining software? Was it a rule that triggered and forced a restart?

Fan speed is possible. Please use:

Individual hash rate is not supported.

Awesome Miner generates a sgminer configuration file and inside all the API parameters are specified together with pool information. For that reason it's not passed via the command line.

Thanks,
I am used to ASCIs and it's perfect, I just added some GPUs and dealing with them now

edited:
I would like to play around with profit switching a bit and was wondering if I can do testing only on one selected rig, or all of them are affected once set up?

Yes. Please go to Options dialog, General section and set "Temperature display" to "All devices temperatures".

When reading the thread it mainly looks like the pool didn't report the full hashrate, while it from a mining software point of view looked perfectly fine with the hashrate. If the pool also reports that the shares are accepted to the mining software, it will be even more difficult for Awesome Miner to detect that something is wrong.

Awesome Miner itself doesn't have any connection to the pool. It uses the API's for profit information, but often this is a separate server compared to what the mining software connect to. If the API is down is not always the same as the pool itself is down.

Looking at the actual money you make at the pool isn't a fully stable solution either. You can mine a coin where you don't find any blocks for a long time, so you will not get any payouts for a long period of time and it's still fine because when you eventually find a block you get a high payout. In the past it also happens that these pools changes their unit (MH/s vs GH/s) of reporting in their API's, so it's yet another scenario that makes it less stable to react on that from the pool API.

I fully agree that it would make sense if Awesome Miner could detect these scenarios and take action, but we also need to keep in mind that it can be a quite difficult scenario to detect. If Awesome Miner tries to be "too smart", it may give unexpected behaviors as well. I will investigate this further and I'm open for any suggestions. Thanks!

is there a way to see each and every GPU temp on this screen?

Thanks for reporting this

I will correct the User Defined coins for the USD scenario together with the profit switcher

I will also include Cast XMR 0.8.1. I actually didn't see that one before as their Bitcointalk thread only listed 0.8. It will also be possible to include in the profit switcher, even if it isn't included by default.

A lot of users of AwesomeMiner lost money because miners are not switched if they are not returning anything.

If a miner does not report new hasrate it shoudl be stopped.

A few thousands users of AwesomeMiner are porting that lost a lot of money because NIST5 HASREFINERY bad reporting or unresponsive pools:

https://bitcointalksearch.org/topic/hashrefinery-nist5-mining-hashrate-issue-2736744

Solution would be to have an ability to switch the mining program if it is not responsive (could not connect because of DDOS or overloaded pool or other hardware errors from the miner).

Also Awesome miner is reporting a lot more than we can actually see in our real daily income fromt he pools. I advise anyone to compute teh real money from the pool every day because the values from Awesome Miner are not the real ones, and you do a lot less money !

I am asking the developers what is their solution on situations like these?

Thank you

Thanks for the reply. I promise I did all that stuff. The bug is actually that if you specify the value in USD and leave the value in BTC as Zero, the profit miner still uses the 0 BTC to calculate profit, while the coins tab correctly uses the USD. Please verify and fix if possible -- USD has more digits for shitcoins, so I assume it's more accurate to use that.
ex. ITNS: $0.053555 USD / 0.00000386 BTC

Also please let us use cast_xmr in the profit miner in the next release, and update it to 0.81 to fix the bug with the latest AMD drivers. It helps me get rid of one extra template, at least. 0.81 is available on the official website.

http://www.gandalph3000.com/download/cast_xmr-vega-win64_081.zip

Profit Miners will use the Online Services tab statistics for services like Nicehash, MPH, zpool, etc.  It's only if you activate the custom pool option and of course, a pool group with the coins you want to switch between that AM will use the Coins tab statistics.

User-defined coins need to have all the appropriate data setup in the User Defined Coins section of the Coins & Statistics tab of the Options.  AM depends on this data to help it calculate how much revenue you potentially will generate based upon your hashrate.

Also, if you are going to do profit switching, it's important to do benchmarking so that AM can make some decisions on how much hashrate your rigs will run and compare that to the various coins and algos.

Can you right-click your stopped miner and run diagnostics?  Post them here, we can help.  I use cast-xmr with no issue, but your pool definition may need some tweaking.

Let's run through some basics.  Did you install the Remote Service on the other machine?  Did you setup a managed host in AM, then linked the managed miner or profit miner to the host?

The 127.0.0.1 is a loopback IP address seems to indicate that there is some configuration issue with your managed host, managed miner, or you are missing the Remote Service on the other machine.

sgminer and compatible templates aren't setting up the api automatically and need  --api-listen added to the command line. Seems to be a bug.

Make sure its called phi, not phi1612

I think I've configured everything correctly:

https://i.imgur.com/cfFSqmj.png
https://i.imgur.com/nukxNVG.png
https://i.imgur.com/CwU223i.png
https://i.imgur.com/HppbqcD.png
https://i.imgur.com/e5eCeoC.png

However:

https://i.imgur.com/bttQAgk.png

And yeah, I've tried restarting it.

EDIT: Added TimeTravel10/Bitcore, seems to have the same problem.