[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[joseph32]

Hey Patrik,

sometimes rules like "Detect device hashrate, less than or equals: 0 kH/s" or "Detect device count, less than or equals: 2" or similar others will trigger, although actually not necessary because it is just a quick hashrate drop or a miner bug or anything else, but gone in the next second. But the rule is already triggered...

Is it possible to add a trigger like "For (at least): X Seconds"?

This doesnt make sense everywhere, but for a few rules it can be a great improvement. The 2 rules above would now look like:
"Detect device hashrate, less than or equals: 0 kH/s" "For: 10 Seconds"
"Detect device count, less than or equals: 2" "For: 30 Seconds"
In the case above the rules wouldn't have triggered because they are now in the limit.

[patrike]

Hey Patrik,

sometimes rules like "Detect device hashrate, less than or equals: 0 kH/s" or "Detect device count, less than or equals: 2" or similar others will trigger, although actually not necessary because it is just a quick hashrate drop or a miner bug or anything else, but gone in the next second. But the rule is already triggered...

Is it possible to add a trigger like "For X Seconds"?

This doesnt make sense everywhere, but for a few rules it can be a great improvement. The 2 rules above would now look like:
"Detect device hashrate, less than or equals: 0 kH/s" "For: 10 Seconds"
"Detect device count, less than or equals: 2" "For: 30 Seconds"
And it wouldn't have triggered in that case.

For the hashrate, you can actually add multiple "Check statistics" triggers - one that is looking at the current value and one that is looking at the hashrate value 1 or 2 minutes ago. You can then set your rule to only trigger if it matches both these conditions. This makes it possible to not trigger it too frequently.

For Device Count there are no feature like this, but I understand your suggestion for this one as well. Thanks!

[joseph32]

Hey Patrik,

sometimes rules like "Detect device hashrate, less than or equals: 0 kH/s" or "Detect device count, less than or equals: 2" or similar others will trigger, although actually not necessary because it is just a quick hashrate drop or a miner bug or anything else, but gone in the next second. But the rule is already triggered...

Is it possible to add a trigger like "For X Seconds"?

This doesnt make sense everywhere, but for a few rules it can be a great improvement. The 2 rules above would now look like:
"Detect device hashrate, less than or equals: 0 kH/s" "For: 10 Seconds"
"Detect device count, less than or equals: 2" "For: 30 Seconds"
And it wouldn't have triggered in that case.

For the hashrate, you can actually add multiple "Check statistics" triggers - one that is looking at the current value and one that is looking at the hashrate value 1 or 2 minutes ago. You can then set your rule to only trigger if it matches both these conditions. This makes it possible to not trigger it too frequently.

For Device Count there are no feature like this, but I understand your suggestion for this one as well. Thanks!

Ha, never thought about those tricky hashrate multi-check-rules, but will do now Thanks!

Sometimes if AM switch from one miner to another, one or some devices are "lost" for a second and all the alarm rules will trigger. Maybe you have a better solution for this scenario, would be great.

[patrike]

Awesome Miner version 6.6.2

 ASIC mining
  - Feature to send custom web commands to an Antminer
 Mining software
  - Added mining software: NoncerPro 3.0.2
  - Nanominer 1.4.1
  - Miniz miner 1.4o
  - CpuMiner-Opt 3.9.5.1
  - Lolminer 0.8.3

Please note that we make many of the mining software updates available even before these releases - via the 'Update mining software definitions' feature.

[NetfetMiningCompany]

Whats the easiest way to run the nano miner as admin through AM? when i turn the software on, it says i should do it.

im also getting 2 different power output readouts on the graphics card. AM says a card will be 90w, but nanominer says 67w. which would be more accurate?

To run a miner as administrator, please right click on the miner, select Properties and then go to the Environment section where you can enable the Admin setting.

AMD is not reporting as accurate power usage values as nVidia do. For this reason Awesome Miner is by default adding 35% to the power usage to make it a bit more realistic. You can change this in the Options dialog, GPU settings section. If you set it to 0%, Awesome Miner should show the same value as nanominer - but I also think that would be less realistic.

Makes sense. Thank you.

[buckrogers]

Does anyone know if awesome miner can support the futurebit apollo scrypt miner?

I can't seem to gain access to it as Apollos run bfgminer.

thanks!

[slysir]

Download URL changed for Gminer-1.50 and miniZ 1.4o

https://github.com/develsoftware/GMinerRelease/releases/download/1.50/gminer_1_50_windows64.zip

[patrike]

Does anyone know if awesome miner can support the futurebit apollo scrypt miner?

I can't seem to gain access to it as Apollos run bfgminer.

thanks!

I don't have any experience with this specific miner. Bfgminer should however be able to provide a monitoring interface where Awesome Miner can connect.

Are there any settings in the web interface called "API" or something with related to Bfgminer?
Is it possible to SSH to this miner?

[patrike]

Download URL changed for Gminer-1.50 and miniZ 1.4o

https://github.com/develsoftware/GMinerRelease/releases/download/1.50/gminer_1_50_windows64.zip

I will add Gminer 1.50 right away. It looks like version 1.48 and 1.49 was removed

For miniZ it looks like their SSL certificate on the website has expired for HTTPS. I will change all download URL's to HTTP instead.

In a few minutes from now you will be able to update the mining software definitions to get these changes.

[patrike]

Hi Patrike,

it's possible to change xmrig cpu miner with xmrigcc miner?

https://github.com/Bendr0id/xmrigCC

It support all cryptonight variant and auto core/thread.

Thanks

Is this a fork of XMrig CPU miner where it also includes a web interface? So from a mining point of view, it's identical to XMrig CPU miner?

If it's fully compatible, you can change the download URL for XMrig CPU miner via the Options dialog, Managed Software section.

[Lunga Chung]

It looks like on the latest version dashboard isn't updating coin value, I see old prices for coins selected on the bottom of the dashboard

[patrike]

It looks like on the latest version dashboard isn't updating coin value, I see old prices for coins selected on the bottom of the dashboard

Is the feature to check for software updates working? It's using the same Amazon cloud server for getting the information. In the past it downloaded it via other sources.

If you go to the Menu -> Update mining software definitions you should see GMiner 1.50 for example - unless you upgraded to it earlier today. GMiner 1.50 is not part of the latest release.

If you want you can send me your Awesome Miner log file via PM and I can review the case. Thanks!

[joseph32]

Hey Patrik,

TeamRedminer now supports MTP. Problem is, if I start it with AM, the miner always crashs right after building the scratchpad. If I start the same command line directly without AM, it works perfect. Can you check that please? Maybe AM dont like the 1-2 seconds to build the scratchpad. It also doesnt matter which pool, it always crashs everywhere.

The diagnostic doesnt tell much:

Code:

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.5.7
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 18.6.1
AMD OpenCL Platform ID: 1
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: TeamRedMiner, Auto Download: False, EnginePath: teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe, Subtype: Disabled, CustomExecutable: 
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\xxx\AppData\Local\AwesomeMinerService\UploadedSoftware\teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe  -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u xxx -p x --platform 1 --api_listen=0.0.0.0:4030
====================================================================================================
>           Team Red Miner version 0.5.3
> [2019-07-04 22:26:26] Note: failed to enable terminal color support, colors will be disabled.
Mining Engine Process started, PID: 2400
> [2019-07-04 22:26:27] Nicehash MTP mining detected, disabling ntime rolling.
> [2019-07-04 22:26:27] Initializing GPU 0.
> [2019-07-04 22:26:27] Initializing GPU 1.
> [2019-07-04 22:26:27] Initializing GPU 2.
> [2019-07-04 22:26:28] Watchdog thread starting.
> [2019-07-04 22:26:28] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
> [2019-07-04 22:26:28] API initialized on 0.0.0.0:4030
> [2019-07-04 22:26:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 06:00.0) 
> [2019-07-04 22:26:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0) 
> [2019-07-04 22:26:28] Successfully initialized GPU 2: Vega with 64 CU (PCIe 17:00.0) 
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com connecting to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully connected to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully subscribed. (93 ms)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com authorization succeeded.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com set difficulty to 4096.000000
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com received new job. (job_id: 0000023a71412d2b)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com extranonce subscribe succeeded. (111 ms)
> [2019-07-04 22:26:29] Dev pool connected and ready.
> [2019-07-04 22:26:30] GPU 0 - MTP scratchpad rebuilt in 1.73 secs.
> [2019-07-04 22:26:30] GPU 1 - MTP scratchpad rebuilt in 1.71 secs.
> [2019-07-04 22:26:30] GPU 2 - MTP scratchpad rebuilt in 1.74 secs.
> [2019-07-04 22:26:37] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:1 r:0) (258 ms)
> [2019-07-04 22:26:41] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:2 r:0) (208 ms)
> [2019-07-04 22:26:48] Pool mtp.eu.nicehash.com share accepted. (GPU1) (a:3 r:0) (175 ms)

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
> [2019-07-04 22:26:56] Shutting down...
> [2019-07-04 22:26:56] API thread exiting.
Diagnostics completed

Edit: This issue will be already discussed in the TRM thread starting with this post: https://bitcointalk.org/index.php?topic=5027811.msg51712911#msg51712911

[kerney666]

Hey Patrik,

TeamRedminer now supports MTP. Problem is, if I start it with AM, the miner always crashs right after building the scratchpad. If I start the same command line directly without AM, it works perfect. Can you check that please? Maybe AM dont like the 1-2 seconds to build the scratchpad. It also doesnt matter which pool, it always crashs everywhere.

The diagnostic doesnt tell much:

Code:

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.5.7
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 18.6.1
AMD OpenCL Platform ID: 1
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: TeamRedMiner, Auto Download: False, EnginePath: teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe, Subtype: Disabled, CustomExecutable: 
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\xxx\AppData\Local\AwesomeMinerService\UploadedSoftware\teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe  -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u xxx -p x --platform 1 --api_listen=0.0.0.0:4030
====================================================================================================
>           Team Red Miner version 0.5.3
> [2019-07-04 22:26:26] Note: failed to enable terminal color support, colors will be disabled.
Mining Engine Process started, PID: 2400
> [2019-07-04 22:26:27] Nicehash MTP mining detected, disabling ntime rolling.
> [2019-07-04 22:26:27] Initializing GPU 0.
> [2019-07-04 22:26:27] Initializing GPU 1.
> [2019-07-04 22:26:27] Initializing GPU 2.
> [2019-07-04 22:26:28] Watchdog thread starting.
> [2019-07-04 22:26:28] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
> [2019-07-04 22:26:28] API initialized on 0.0.0.0:4030
> [2019-07-04 22:26:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 06:00.0) 
> [2019-07-04 22:26:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0) 
> [2019-07-04 22:26:28] Successfully initialized GPU 2: Vega with 64 CU (PCIe 17:00.0) 
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com connecting to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully connected to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully subscribed. (93 ms)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com authorization succeeded.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com set difficulty to 4096.000000
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com received new job. (job_id: 0000023a71412d2b)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com extranonce subscribe succeeded. (111 ms)
> [2019-07-04 22:26:29] Dev pool connected and ready.
> [2019-07-04 22:26:30] GPU 0 - MTP scratchpad rebuilt in 1.73 secs.
> [2019-07-04 22:26:30] GPU 1 - MTP scratchpad rebuilt in 1.71 secs.
> [2019-07-04 22:26:30] GPU 2 - MTP scratchpad rebuilt in 1.74 secs.
> [2019-07-04 22:26:37] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:1 r:0) (258 ms)
> [2019-07-04 22:26:41] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:2 r:0) (208 ms)
> [2019-07-04 22:26:48] Pool mtp.eu.nicehash.com share accepted. (GPU1) (a:3 r:0) (175 ms)

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
> [2019-07-04 22:26:56] Shutting down...
> [2019-07-04 22:26:56] API thread exiting.
Diagnostics completed

Edit: This issue will be already discussed in the TRM thread starting with this post: https://bitcointalk.org/index.php?topic=5027811.msg51712911#msg51712911

Hi Patrik! Let me know if you need dev assistance sorting this out, a little surprising, not sure what we’re doing to confuse you when running in normal mode. Would be great to sort it out!

[patrike]

Hey Patrik,

TeamRedminer now supports MTP. Problem is, if I start it with AM, the miner always crashs right after building the scratchpad. If I start the same command line directly without AM, it works perfect. Can you check that please? Maybe AM dont like the 1-2 seconds to build the scratchpad. It also doesnt matter which pool, it always crashs everywhere.

The diagnostic doesnt tell much:

Code:

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.5.7
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 18.6.1
AMD OpenCL Platform ID: 1
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: TeamRedMiner, Auto Download: False, EnginePath: teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe, Subtype: Disabled, CustomExecutable: 
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\xxx\AppData\Local\AwesomeMinerService\UploadedSoftware\teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe  -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u xxx -p x --platform 1 --api_listen=0.0.0.0:4030
====================================================================================================
>           Team Red Miner version 0.5.3
> [2019-07-04 22:26:26] Note: failed to enable terminal color support, colors will be disabled.
Mining Engine Process started, PID: 2400
> [2019-07-04 22:26:27] Nicehash MTP mining detected, disabling ntime rolling.
> [2019-07-04 22:26:27] Initializing GPU 0.
> [2019-07-04 22:26:27] Initializing GPU 1.
> [2019-07-04 22:26:27] Initializing GPU 2.
> [2019-07-04 22:26:28] Watchdog thread starting.
> [2019-07-04 22:26:28] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
> [2019-07-04 22:26:28] API initialized on 0.0.0.0:4030
> [2019-07-04 22:26:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 06:00.0) 
> [2019-07-04 22:26:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0) 
> [2019-07-04 22:26:28] Successfully initialized GPU 2: Vega with 64 CU (PCIe 17:00.0) 
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com connecting to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully connected to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully subscribed. (93 ms)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com authorization succeeded.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com set difficulty to 4096.000000
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com received new job. (job_id: 0000023a71412d2b)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com extranonce subscribe succeeded. (111 ms)
> [2019-07-04 22:26:29] Dev pool connected and ready.
> [2019-07-04 22:26:30] GPU 0 - MTP scratchpad rebuilt in 1.73 secs.
> [2019-07-04 22:26:30] GPU 1 - MTP scratchpad rebuilt in 1.71 secs.
> [2019-07-04 22:26:30] GPU 2 - MTP scratchpad rebuilt in 1.74 secs.
> [2019-07-04 22:26:37] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:1 r:0) (258 ms)
> [2019-07-04 22:26:41] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:2 r:0) (208 ms)
> [2019-07-04 22:26:48] Pool mtp.eu.nicehash.com share accepted. (GPU1) (a:3 r:0) (175 ms)

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
> [2019-07-04 22:26:56] Shutting down...
> [2019-07-04 22:26:56] API thread exiting.
Diagnostics completed

Edit: This issue will be already discussed in the TRM thread starting with this post: https://bitcointalk.org/index.php?topic=5027811.msg51712911#msg51712911

Hi Patrik! Let me know if you need dev assistance sorting this out, a little surprising, not sure what we’re doing to confuse you when running in normal mode. Would be great to sort it out!

Thanks for your assistance. I think I was able to figure out the scenario here.

If Awesome Miner sends API requests to TeamRedMiner when doing MTP mining, TeamRedMiner will terminate. If I use any other algorithm, it looks fine.

So I think it's something with the API request processing inside TeamRedMiner specifically when doing MTP mining. Please let me know if it's anything else you want me to investigate. Thanks!

[kerney666]

Hey Patrik,

TeamRedminer now supports MTP. Problem is, if I start it with AM, the miner always crashs right after building the scratchpad. If I start the same command line directly without AM, it works perfect. Can you check that please? Maybe AM dont like the 1-2 seconds to build the scratchpad. It also doesnt matter which pool, it always crashs everywhere.

The diagnostic doesnt tell much:

Code:

Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.5.7
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 18.6.1
AMD OpenCL Platform ID: 1
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: TeamRedMiner, Auto Download: False, EnginePath: teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe, Subtype: Disabled, CustomExecutable: 
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\xxx\AppData\Local\AwesomeMinerService\UploadedSoftware\teamredminer-v0.5.3-win\teamredminer-v0.5.3-win\teamredminer.exe  -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u xxx -p x --platform 1 --api_listen=0.0.0.0:4030
====================================================================================================
>           Team Red Miner version 0.5.3
> [2019-07-04 22:26:26] Note: failed to enable terminal color support, colors will be disabled.
Mining Engine Process started, PID: 2400
> [2019-07-04 22:26:27] Nicehash MTP mining detected, disabling ntime rolling.
> [2019-07-04 22:26:27] Initializing GPU 0.
> [2019-07-04 22:26:27] Initializing GPU 1.
> [2019-07-04 22:26:27] Initializing GPU 2.
> [2019-07-04 22:26:28] Watchdog thread starting.
> [2019-07-04 22:26:28] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
> [2019-07-04 22:26:28] API initialized on 0.0.0.0:4030
> [2019-07-04 22:26:28] Successfully initialized GPU 0: Vega with 64 CU (PCIe 06:00.0) 
> [2019-07-04 22:26:28] Successfully initialized GPU 1: Vega with 64 CU (PCIe 03:00.0) 
> [2019-07-04 22:26:28] Successfully initialized GPU 2: Vega with 64 CU (PCIe 17:00.0) 
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com connecting to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully connected to address 172.65.195.77.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com successfully subscribed. (93 ms)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com authorization succeeded.
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com set difficulty to 4096.000000
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com received new job. (job_id: 0000023a71412d2b)
> [2019-07-04 22:26:28] Pool mtp.eu.nicehash.com extranonce subscribe succeeded. (111 ms)
> [2019-07-04 22:26:29] Dev pool connected and ready.
> [2019-07-04 22:26:30] GPU 0 - MTP scratchpad rebuilt in 1.73 secs.
> [2019-07-04 22:26:30] GPU 1 - MTP scratchpad rebuilt in 1.71 secs.
> [2019-07-04 22:26:30] GPU 2 - MTP scratchpad rebuilt in 1.74 secs.
> [2019-07-04 22:26:37] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:1 r:0) (258 ms)
> [2019-07-04 22:26:41] Pool mtp.eu.nicehash.com share accepted. (GPU0) (a:2 r:0) (208 ms)
> [2019-07-04 22:26:48] Pool mtp.eu.nicehash.com share accepted. (GPU1) (a:3 r:0) (175 ms)

====================================================================================================
Diagnostics done. Stopping miner process ...
Prepare stopping Mining Software
Stopping Mining Software
> [2019-07-04 22:26:56] Shutting down...
> [2019-07-04 22:26:56] API thread exiting.
Diagnostics completed

Edit: This issue will be already discussed in the TRM thread starting with this post: https://bitcointalk.org/index.php?topic=5027811.msg51712911#msg51712911

Hi Patrik! Let me know if you need dev assistance sorting this out, a little surprising, not sure what we’re doing to confuse you when running in normal mode. Would be great to sort it out!

Thanks for your assistance. I think I was able to figure out the scenario here.

If Awesome Miner sends API requests to TeamRedMiner when doing MTP mining, TeamRedMiner will terminate. If I use any other algorithm, it looks fine.

So I think it's something with the API request processing inside TeamRedMiner specifically when doing MTP mining. Please let me know if it's anything else you want me to investigate. Thanks!

Got it, so we have a seg fault for MTP API calls, we’ll address it ASAP.

[patrike]

Awesome Miner version 6.6.3

 ASIC mining
  - Configure API access on Innosilicon A9 and similar miners
 Mining software
  - Added mining software: CcMiner Zcoin Official 1.1.3 for MTP algorithm
  - Gminer 1.50
  - CpuMiner-Opt 3.9.5.2
  - CryptoDredge 0.20.2

[GKumaran]

Hey, please look into TeamRedMiner MTP algo. Its still broken in AM.

[joseph32]

Hey, please look into TeamRedMiner MTP algo. Its still broken in AM.

Just a few lines above is the answer... Just wait a bit mate.

[GKumaran]

Hey, please look into TeamRedMiner MTP algo. Its still broken in AM.

Just a few lines above is the answer... Just wait a bit mate.

sorry lazy me !! i was chatting yday in dm posted here without reading !!