Ok it just happened again.  Here's what I see under details:



As stated before, all my other miners (which only have Ethereum selected as available algo) continue to mine just fine against the NiceHash Ethereum pool.

When I click "Reset failed pools", it immediately switches back to Ethereum and all as well again.

I have zipped up the log files and will forward them to you shortly.

EDIT:  Increasing the "Ignore pools with no accepted shares" from 8 minutes to 10 minutes (the max), seems to have resolved the issue.  I suppose a rig with a single 1050Ti just doesn't hash ETH fash enough to produce a share in 8 minutes?

I sure will.  Just cleared the logs on both AM and AM Agent on my test miner and restarted with 5 algos selected.  Once it acts up (switches to a less profitable algo), I'll uncheck all but Ethereum and start miner to get that false positive error message about the pool not being configured correctly.


Everything here looks good as far as I can tell when I first start out.  Here's what it looks like atm and the listed hash rates are based on actual benchmarks I ran.




I understand, I'm not trying to use those pool definitions for the profit switcher, I'm only using the one defined here (if I understand correctly since I don't currently have any Pool Groups defined):



Thanks

I have started experimenting with the Profit Switching functionality, but am having an odd issue.  Again I'm only doing this on a single small rig with a single 1050Ti for now until I get the kinks worked out.  I have these algos configured in the profit switcher:



ETH is the most profitable (and what my other 13 GPU rigs controlled by AM mines, especially the 1080Ti rigs running the ETH pill).  At any rate, this test rigs starts out on ETH as expected, but after a while, it switches to one of the less profitable algos.  If I then stop the rig, un-check all but Ethereum under algos and restart, I get the following error:



Not sure why I would get that error.  All the other rigs are happily mining away on that same pool.  If I shutdown AM and restart it, it starts working again, but the same thing keeps happening.  I can stop and start mining on any of the other rigs, and they don't have this error.  The other rigs are also running Managed Profit Miner profiles, but only have the Ethereum algo selected atm due to this issue.

I only have the NiceHash pool configured under Options/Profit Switching although I do have various other pools defined under Options/Pools.  Here are some of them:



I used those when I was manually switching between algos using Regular Managed Miner profiles.  Could that be somehow causing the issue now that I'm using Managed Profit Miner profiles?  I'm running the latest 5.2.5 version btw, including the Remote Agents.

What is the reason for that?  The current version is 1.5.8, so 1.4.4 is quite old.  Perhaps some specific parameters needs to be passed to make the 1.5.x versions work?

I'm running benchmarks on a small single 1050Ti test rig, and it just hangs after core initialized in every algo using Excavator:

In my case I build a "room within a room" for force all incoming air through the rack holding all the miners.



Since the above pic was taken, both the left, right and ceiling have been dry-walled.  There is also a door behind that blue arrow to access the "inner room".  You can also see the 10,000 CFM exhaust fan in the top of the gable near the top of the pic.  Having an exhaust fan in addition to the intake fan is very important as you want to pull out the hot air generated by the miners.  I'm consuming right around 20 kW when the ASIC's are online as well.

View from the front:



Miners have been arranged a little differently since the above pic was taken and the open spaces have been sealed better to force the 10,000 CFM of air from the outside better.

Outside view of the intake without filters in place:



With 10 x 24x24 washable filters installed:



Even with very humid air, there is never any condensation issues since, no matter what, the GPUs are always hotter than ambient, even when it is 100F and humid outside.

I'm running about 2.8 GH/s (80 GPUs, all Nvidia, mostly 1080Ti's on the pill, but a good portion of 1070 and 1070Ti's as well).  I do have 3 1060 3GB rigs that are running HIVE,
 Total of 80 GPUs.

Here's a shot from 4:30pm today when outside temp was right at 98F and about as humid as it gets here in Central Virginia (which is very humid).  Temp inside the shop building was right at 100F.



I have a single 10,000 CFM intake fan, and a single 10,000 CFM exhaust fan.  I'm pretty pleased that temps stayed below 72C.  Some cards were running fans at close to 100% to maintain that, but only from about 2pm until 6pm.

This is exciting news!  I'm currently running a mix of Windows rigs controlled by AM and Linux rigs controlled by HIVE OS.  I also ran nvOC for a while, but the lack of central management with a lot of rigs was a challenge.  While HIVE has a nice dashboard and pushing changes to a lot of rigs at once is nice, there is no profit switching support, and the overall list of features compared to AM, is much smaller.

Is the Linux Remote Agent based on a particular distro?  Will be Agent be part of a complete image, or something the the user installs on top of an existing distro of their choice?  I would think the former would be preferred to "lock in" the environment and keep support enquirers down.

That did the trick.  Thanks!

Question on licensing.  I currently have the Premium edition licensing which allows for 20 miners.  I actually have 22 miners and don't see that going up significantly any time soon, given the current climate.  I can't see paying another $170 just to gain visibility to those last 2 miners.  I also don't care for multi-user access control as I'm the only one managing the rigs, which is the only additional feature I would gain by going to the Enterprise edition.

Have you considered offering like a 5-pack or something of just additional miners with no additional features?

Also curious if a Remote Agent for Ubuntu is on the road-map at all?

One thing I should mentioned through, is that the main temperature displayed for the Z9 is the PCB temp.  Shouldn't the Chip temp be the main one? (the temp displayed in the compact view)

Miner view from Z9 status page:



And summary view from AM:



AM ASIC tab:



The Chip temp is always higher than the PCB temp and is the more critical one to keep an eye on, no?

I have 3 Z9's that I monitor from AM.  Have had no issues to date.  I started out on MPH on 6/22 but have since switched to Luxor.

Here are my MPH stats:



I got my first Z9 on the 22nd and 2 more on the 25th.

I manually jumped around a bit the first 3 days, then enabled auto switching shortly after getting the 2nd and 3rd Z9s online.

I  have since switched to the Luxor pool (about 24 hours ago) and here are my current real-time earnings:



Pool side view:

Would the API support profit switching control from Awesome Miner?

Alternatively, will HIVE OS 2.0 support profit switching?

Uhh, Mr. MPH, you might want to do this:

https://blog.zencash.com/mandatory-upgrade-zen-2-0-14-super-nodes/

From the above link:

--- cut ---
We are pleased to announce ZenCash 2.0.14 upgrade is now available! All node operators, exchanges, and pool operators must update from the previous version before June 28th when the current version is deprecated and will stop working (at block 332576). Please follow the instructions below.
--- cut ---

My miners have been mining "air" for the last 8 hours or so on MPH since we hit block 332576.

Looks like the boys over at MPH are asleep at the wheel:

https://blog.zencash.com/mandatory-upgrade-zen-2-0-14-super-nodes/

From the above link:

--- cut ---
We are pleased to announce ZenCash 2.0.14 upgrade is now available! All node operators, exchanges, and pool operators must update from the previous version before June 28th when the current version is deprecated and will stop working (at block 332576). Please follow the instructions below.
--- cut ---

Got the same follow up response.  Updated original post.

Received the following response from NH this morning regarding Z9 support:

I know I'm late to the party (been doing Lyra2rev2 lately), but now ETH is more profitable on the pill.

Got 21 EVGA 1080Ti (SC and SC2) and they are all running around 50 MH's now.

Also working great on my 4x MSI 1080Ti Sea Hawk EK's and even my MSI 1080 Sea Hawk X.

Zotac 1080Ti Arcticstorm also swallowed the pill with no issue.

During this rough period, any edge helps!

Are you sure BTG is working on MPH?  When I look at the MPH Auto Exchange supported exchanges, it doesn't look like any of them are working with BTG:

So I have been running mine wide open at 750 MHz (the max you can set), is it seems to take it just fine.

Here's power consumption running at 750 MHz.  Note that there are peaks as high as 485 Watts, so keep that in mind if you plan to run several of these from a single PSU.  The baseline consumption running maxed out is 350 Watts.



After 5 hours 20 minutes, average KSol/S is 16.39 and 0 HW errors:



And things are looking great pool side as well:





From the above graph, you can see where I went from a 650 to a 750 OC setting.

Wish I had about a dozen of these last fall!