Quote from: darius510 on December 23, 2018, 02:07:16 AM

Quote from: patrike on December 22, 2018, 10:00:16 PM

Quote from: darius510 on December 22, 2018, 02:52:58 PM

Quote from: patrike on December 22, 2018, 10:37:53 AM

Quote from: darius510 on December 22, 2018, 12:13:26 AM

I've been having a very frustrating problem the last couple of weeks - every few hours a miner randomly "fails to start", and then I get the modal dialog asking me to run diagnostics. Every single time I run diagnostics absolutely nothing is wrong. So one by one my miners are stopping, and I have to check every few hours, clear 5-10 of these dialogs, start the miners back up, and they work every single time. So there has to be some bug in AM causing this, because there's certainly not a problem with the miners or the rigs if the miner starts right up every time.

Quote from: darius510 on December 22, 2018, 03:02:50 AM

Nope, that's definitely not it. Something must have changed in awesome miner, because this only started happening recently.

If you get the dialog that the miner failed to start, it's because the mining software has crashed a number of times over the last few minutes. After a number of attempts of restarting it, Awesome Miner will give up and show this error.

You can configure Awesome Miner to continue trying to restart the crashed mining software via the Options dialog, Mining Settings section, where you can set the restart attempts to 99. As the number of attempts are based on the last few minutes, a value of 99 will basically make Awesome Miner trying to restart the mining every time it's crashes and never give up.

There are no recent changes in Awesome Miner to this behavior.

There can be instances where mining software crashes a number of times for a while, but when starting it with the exact same settings a little later, it will no longer crash. Temperature is a common cause why the problem resolves itself, but I suppose there can be many other reasons why mining software don't give consistent behaviors with the crashes.

For the crashes you may have to do general troubleshooting to find out if it's a specific algorithm or mining software or mining rig or clocking settings that causes the problem.

I've set it to restart as many as 10 times, and while I'm using the program if the dialog pops up, I can click it *immediately* and it always still works. Furthermore, I tried to set a rule where it would wait 10 seconds before starting the miner again, but the modal dialogs seem to block that rule from executing (and who knows what else). For instance this morning I had 3 of those dialogs on top of each other, I clicked no to all of them, and then a few seconds later, the rule triggered and all three started up just fine. There at least has to be some way to turn this blocking dialog off if it's going to prevent me from setting rules to correct this inexplicable behavior.

Thanks for the update, I understand your point.

Do you get any entry on the Notifications tab about this issue?

Could you please send me the log file for this Remote Agent and also for the Awesome Miner main application - and let me know the time and the name of the miner? I will investigate to find out what the scenario looks like. Thanks!

Code:

12/22/2018 6:16:22 PM.152 [009] [S][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Starting...
12/22/2018 6:16:23 PM.167 [009] [S][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Starting Mining Software
12/22/2018 6:16:23 PM.167 [009] [S][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Setting up Miner Engine. Instance: 1
12/22/2018 6:16:23 PM.167 [009] [S][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Engine Type: CcCryptoDredgeEngine, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
12/22/2018 6:16:23 PM.167 [009] [S]EngineSetup: CcCryptoDredgeEngine
12/22/2018 6:16:23 PM.167 [009] [S][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Set clocking start profile: 59, 60%/+100/0/Auto (when stopping, the following will be used: -1, type: Single, Use: False)
12/22/2018 6:16:23 PM.167 [022] [S]ApplySingleProfile Begin
12/22/2018 6:16:23 PM.167 [022] [S]Preparing authentication header for MSI Afterburner requests: MSIAfterburner:17cc95b4017d496f82
12/22/2018 6:16:23 PM.199 [022] [S]Number of GPU commands: 20
12/22/2018 6:16:23 PM.199 [022] [S]Executing GPU clocking command: /setmacm, powerLimit0=60&coreClockBoost0=100000&memoryClockBoost0=0&fanSpeed0=auto&powerLimit1=60&coreClockBoost1=100000&memoryClockBoost1=0&fanSpeed1=auto&powerLimit2=60&coreClockBoost2=100000&memoryClockBoost2=0&fanSpeed2=auto&powerLimit3=60&coreClockBoost3=100000&memoryClockBoost3=0&fanSpeed3=auto&powerLimit4=60&coreClockBoost4=100000&memoryClockBoost4=0&fanSpeed4=auto
12/22/2018 6:16:23 PM.199 [022] [S]Preparing authentication header for MSI Afterburner requests: MSIAfterburner:17cc95b4017d496f82
12/22/2018 6:16:24 PM.183 [020] [I][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:24 PM.183 [009] [E]System.NullReferenceException: Object reference not set to an instance of an object.
12/22/2018 6:16:24 PM.183 [009] [E] at AwesomeMiner.Service.Core.Engines.EnginePrepareBase.GetStaticSortedPools()
   at AwesomeMiner.Service.Core.Engines.EnginePrepareBase.ProcessVirtualEffectivePoolList()
   at AwesomeMiner.Service.Core.Engines.CcMiner.CcEnginePrepare.BuildArguments()
   at AwesomeMiner.Service.Core.Engines.MinerEngine.Start(Int32 #=znFEPBq4WhQQq, Boolean #=zm8OVyhw=, Boolean #=z3_DDggA=, BenchmarkCommand #=zG2LTkxarwMBnUeaT5w==)
[b]12/22/2018 6:16:24 PM.183 [009] [E][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] Failed to start miner process: Object reference not set to an instance of an object.[/b]
12/22/2018 6:16:24 PM.183 [009] [E][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X]Failed to start miner
12/22/2018 6:16:25 PM.199 [020] [I][ManagedMiner#531 - CPU-J7] : ProcessMiner
12/22/2018 6:16:27 PM.027 [022] [S]ApplySingleProfile End
12/22/2018 6:16:29 PM.246 [038] [I][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:30 PM.262 [038] [I][ManagedMiner#531 - CPU-J7] : ProcessMiner
12/22/2018 6:16:34 PM.325 [020] [I][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:35 PM.341 [020] [I][ManagedMiner#531 - CPU-J7] : ProcessMiner
12/22/2018 6:16:39 PM.388 [022] [I][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:40 PM.404 [016] [I][ManagedMiner#531 - CPU-J7] : ProcessMiner
12/22/2018 6:16:44 PM.435 [007] [I][ManagedMiner#290 - J7 4x 1070 GB 2x 1080TI MSI-X] : ProcessMiner
12/22/2018 6:16:45 PM.451 [038] [I][ManagedMiner#531 - CPU-J7] : ProcessMiner[/quote]

Thanks for the details. I can see the method where it goes wrong and I'm about to make it a bit more fail safe and also add additional logging to explain why it's going wrong. However, I cannot verify the solution without fully understanding what caused it.

If possible, please provide me with both the log files so I can see the full scenario so I understand why you ended up with this issue to begin with. Thanks!