Hello, new here.
I'm having a very strange issue with AM. I am using a paid license for AM and my boss asked me to switch to mining ETH directly a couple of weeks ago. The easiest way to do what he requested was to recreate all of my miners as managed miners. To do this, I had used the network scan to bulk create all the miners based on any machines the manager found on the network running Awesome Miner Remote Agent. However, that plan was short lived and I was soon asked to switch it all back. After removing all of the managed miners I created, I am now having issues getting the original managed profit miners to start properly. I seem to only be able to get a few of them to start at a time and when I tell the ones that are stopped to start, it stops a bunch of the ones that were already mining and this just keeps going around in circles. I have recreated some of the miners but that has had little effect. I've RDP'd into each one and manually restarted the remote agent and I've rebooted each and every mining rig as well as the manager rig and nothing seems to be resolving this problem. Also. the Start and Stop buttons sometimes have absolutely no effect on the miner I actually have highlighted when I click the button. It is absolutely mind-boggling.
Does anyone have any suggestions?
Thanks.
EDIT: On closer examination, it appears that a some of these rigs that AM says are "stopped" are actually mining but it doesn't show up in AM.
If I could just get the Start/Stop buttons to stop appearing to control more than one rig at a time, that would be great.
EDIT AGAIN: It appears that simply changing the description of one of my miners can have a pretty big effect on the rest of the miners, making them stop or start. It makes no sense.
Please go to the Options dialog, Managed Hosts section. I think you have some duplicates of the hosts here (either duplicate IPs, or a combination of hostnames and IP addresses that points to the same Remote Agent). Can you please review this list and make sure there are no duplicate, and once you ensure this, please restart Awesome Miner once. For mining processes that already are running and no longer listed as Mining in Awesome Miner - please stop them manually before you proceed.
If the above didn't resolve the problem, please also make sure you only have a single Awesome Miner instance running controlling your Remote Agents.