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

[patrike]

Awesome Miner version 7.2.5

 Awesome Miner Antminer firmware
  - Improved support for Antminer S9 running in Dual mode
  - Open the Antminer kernel log via the Firmware log tab for a selected miner
 GPU mining
  - Delay increases for Power Limit for the temperature controlled Power Limit feature
 Mining software
  - Nanominer integration improved to display CPU information when mining Monero
  - XmRig 5.5
  - CpuMiner-Opt 3.10.7
  - GMiner 1.92
 Changes
  - Dynamic update of coin statistics will not enforce certificates for HTTPS connections
 Corrections
  - Correction to NbMiner dual mining hashrate
  - Correction to Actual 24h display for Prohashing pool
  - Correction to 'Default Pools via web' configuration for Antminer Z9

[1715088408]

1715088408

[1715088408]

1715088408

[1715088408]

1715088408

[1715088408]

1715088408

[MoparMiningLLC]

@patrike - what can i do about this issue? I have a terminus R606 that I am monitoring on AM via port 4028

but now I cannot monitor my gpu rig on AM because it wants to use the same port so it mines but AM shows it as interface offline.

If I start the gpu rig first then the terminus it then cannot monitor the terminus

so I get that they are using the same port and that is the issue - is there a way to change this?

Awesome Miner allocates ports from 4028 and above for Managed Miners and this is not possible to change.

Are you running a local CgMiner process (or similar) for controlling the Terminus R606 miner? Does this one support running on another port (like --api-port 4123)?

yes - the terminus uses a local modified version of cgminer - i will check to see if it can run on another port

So yes I can change the port in cgminer for the terminus - simple actually - but how do I set AM to monitor it? Is it auto? If so why when running a managed miner thru AM does it not detect that AM is already listening to port and then use another one for my gpu rig?

[narousberg]

upd: Solved!

simple add a pause before service start. For my 8 GPU rig i needed extra 50 sec. delay to properly initialize all GPUs (if you guys have rigs with more cards or general slow system, simple increase delay)

I have added one string in [Service] section in awesome.service file:

[Service]
ExecStartPre=/bin/sleep 50
ExecStart=/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux

Thanks for all detailed feedback and good that you found a workaround. I will look into this scenario to find a better way for Remote Agent to handle it.

Hi patrike
looks like my solution not works always(( sometimes yes, sometimes no. I have increased delay time, but this caused other problem, service stuck in "pre-start" state after rebooting.
Looks like awesome.service code must better check GPU initialization before delegate control to AwesomeMiner main program.
Hope you solve this quickly. Till this only manual restarting helps.

Regards.

Thanks for letting me know. I will investigate how to resolve this in a good way.

looks like AwesomeMiner wrong identify a GPUs PCI_BUS_ID after rebooting linux. Maybe AM used old stored data.
if i try for example manualy change fan speed on selected card 7, awesome change randomly on other card. If i select all GPUs and try to set fan or power, changes only applied on first 4 of 8 cards. This simply dangerous how awesome.service manage GPUs overclocking.
I wont use Linux due correct GPU VRAM management, but looks like i must try using Win7 instead of Win10. Windows 10 is simply theft 20% of GPU memory for nothing (due new model of driver platform) https://social.technet.microsoft.com/Forums/Lync/en-US/15b9654e-5da7-45b7-93de-e8b63faef064/windows-10-does-not-let-cuda-applications-to-use-all-vram-on-especially-secondary-graphics-cards?forum=win10itprohardware
but for Linux is not so many mining software as for windows at the moment.

Is this on a 8 x 2080ti system?
If you run into this again, it would be interesting to know what the output of nvidia-smi looks like for these scenarios.

Code:

nvidia-smi --query-gpu=name,pci.bus,index,power.limit,power.min_limit,power.max_limit,power.default_limit,clocks.max.sm,clocks.max.memory --format=csv

Hi patrike
this is output:
root@hive2080TI:/awesomeminer-remoteagent# nvidia-smi --query-gpu=name,pci.bus,index,power.limit,power.min_limit,power.max_limit,power.default_limit,clocks.max.sm,clocks.max.memory --format=csv
name, pci.bus, index, power.limit [W], power.min_limit [W], power.max_limit [W], power.default_limit [W], clocks.max.sm [MHz], clocks.max.memory [MHz]
GeForce RTX 2080 Ti, 0x01, 0, 238.00 W, 100.00 W, 310.00 W, 250.00 W, 2100 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x02, 1, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x03, 2, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x05, 3, 238.00 W, 100.00 W, 310.00 W, 250.00 W, 2100 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x06, 4, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x07, 5, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x08, 6, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz
GeForce RTX 2080 Ti, 0x0A, 7, 247.00 W, 100.00 W, 330.00 W, 260.00 W, 2175 MHz, 7000 MHz

Maybe better use for GPU addressing pci.bus parameter like (0x07, 0x08 ...)  instead of simple GPU ID like 0, 1, 2 ...
But then i need to recreate all my GPU clocking profiles, where clocking parameters will be set for every GPU in rig.

Regards

[narousberg]

i have stoped miner, rebooted linux and run your nvidia-smi query. And i got the same  GPU pci-bus ordering result.
Problem is, that the after reboot value of clocking values which was showed in AM is not equal to values from Profit Profile for this rig. I have no idea where come this values after reboot.
In  Profit Profile set so:
START: Power 95%, Core 140, Memory 1200, Fan 100  (for all GPUs)
STOP: Reset to Default

After reboot (before i do manualy stop/start of awesome.service) AM in GPU Clocking Tab show my only sliders for Power and Fan
with this strange values:
GPU 0: Power 100, Fan 90
GPU 1: Power 96, Fan 90
GPU 2: Power 96, Fan 90
GPU 3: Power 100, Fan 90
GPU 4: Power 96, Fan 90
GPU 5: Power 96, Fan 90
GPU 6: Power 96, Fan 90
GPU 7: Power 96, Fan 90
Why linux set this wrong values, where they saved on ln system??? I can remember i have set this values during test phase, but logicaly after reboot i must see values from Profit Profile. I dont understand whats going on.

I checked GPU tab in AM, Memory set +1200 for all cards, that is ok. Core clocks looks good too.

Now i manualy restart awesome.service:
and i see:
Core 150, Memory 1200, Power 90, Fan 90   but in GPU clocking profile is : Core 140, Memory 1200, Power 95, Fan 100 !!!!
before rebbot i played with clocking and applied clocking profile with Core 150, Mem 1200, Pow 90, Fan 90
but at the and i applied profile with: Core 140, Memory 1200, Power 95, Fan 100
looks like AM saved clocking data on linux but not always and not before miner stop. Maybe Reset to default profile is a root of this chaos.

[narousberg]

I started agent manually (not as service) and in console output i see:

Code:

lockingProfile #96, 2080TIR_P92_C140_M400_F0, list count: 5
ClockingProfile #141, 2080TI_P70_C0_M500_F0, list count: 5
ClockingProfile #138, 2080TI_P70_C0_M600_F0, list count: 5
ClockingProfile #143, 2080TI_P70_C140_M0_F0, list count: 5
ClockingProfile #140, 2080TI_P70_C140_M600_F0, list count: 5
ClockingProfile #137, 2080TI_P70_C150_M0_F0, list count: 5
ClockingProfile #1
1/3/20 10:39:34 AM.496 [015] [S]Current list of Active Miners:
[25] IsAttached: True, PID: 11237, InstanceId: 1, Admin: True, EngineType:GMiner

1/3/20 10:39:34 AM.497 [015] [S]Saving configuration to: /home/user/.config/AwesomeMinerService/ServiceData.xml.tmp
1/3/20 10:39:34 AM.544 [015] [S]--> /home/user/.config/AwesomeMinerService/ServiceData.xml
1/3/20 10:43:01 AM.576 [010] [S]Monitoring running for 0 miners

Looks like agent not load all clocking profiles on start

[narousberg]

i try to set clocking for all cards and only for one (last card in list) and in console output i see:

Code:

1/3/20 10:52:43 AM.323 [005] [S]Current list of Active Miners:
[25] IsAttached: True, PID: 11237, InstanceId: 1, Admin: True, EngineType:GMiner

1/3/20 10:52:43 AM.323 [005] [S]Saving configuration to: /home/user/.config/AwesomeMinerService/ServiceData.xml.tmp
1/3/20 10:52:43 AM.370 [005] [S]--> /home/user/.config/AwesomeMinerService/ServiceData.xml
1/3/20 10:53:02 AM.252 [010] [S]Monitoring running for 0 miners
1/3/20 10:55:00 AM.970 [016] [S]ExecuteGpuSet: SetState for Gpu: 0:0
1/3/20 10:55:00 AM.970 [016] [S]NV:SetPowerLimit GPU: 0, PowerLimit: 238
1/3/20 10:55:00 AM.970 [016] [S]NV:ExecuteCommand Executing: nvidia-smi -i 0 -pl 238
1/3/20 10:55:00 AM.994 [016] [S]NV:SetValues GPU: 0, CoreClock: 140, MemoryClock: 1200, FanSpeed: 100, PerfLvl: False
1/3/20 10:55:00 AM.994 [016] [S]NV:ExecuteCommand Executing: nvidia-settings -a [GPU:0]/GPUGraphicsClockOffset[4]=140 -a [GPU:0]/GPUMemoryTransferRateOffset[4]=1200  -a [gpu:0]/GPUFanControlState=1 -a [fan:0]/GPUTargetFanSpeed=100
1/3/20 10:55:01 AM.353 [016] [S]Request to get clocking settings. Total GPU's: 8
1/3/20 10:55:01 AM.681 [016] [S]Request to get clocking settings completed. Returned GPU's: 8
1/3/20 11:03:02 AM.857 [010] [S]Monitoring running for 0 miners
1/3/20 11:04:57 AM.722 [016] [S]ExecuteGpuSet: SetState for Gpu: 0:0
1/3/20 11:04:57 AM.722 [016] [S]NV:SetPowerLimit GPU: 0, PowerLimit: 238
1/3/20 11:04:57 AM.722 [016] [S]NV:ExecuteCommand Executing: nvidia-smi -i 0 -pl 238
1/3/20 11:04:57 AM.751 [016] [S]NV:SetValues GPU: 0, CoreClock: 140, MemoryClock: 1200, FanSpeed: 100, PerfLvl: False
1/3/20 11:04:57 AM.751 [016] [S]NV:ExecuteCommand Executing: nvidia-settings -a [GPU:0]/GPUGraphicsClockOffset[4]=140 -a [GPU:0]/GPUMemoryTransferRateOffset[4]=1200  -a [gpu:0]/GPUFanControlState=1 -a [fan:0]/GPUTargetFanSpeed=100
1/3/20 11:04:58 AM.103 [016] [S]Request to get clocking settings. Total GPU's: 8
1/3/20 11:04:58 AM.423 [016] [S]Request to get clocking settings completed. Returned GPU's: 8

AM set clocking only for GPU 0

[narousberg]

if i call motd in HiveOS before and after clocking apply over AM i get same answer:

root@hive2080TI:/awesomeminer-remoteagent# motd
Linux 5.0.21-hiveos · H 0.6-108 · up 4 hours 11 minutes
hive2080TI · ID n/a · LA 0.10 0.29 0.36 · RAM 3.8G  available 1.4G (36%)
sda4  total 29G  used 8.3G  free 20G (70%) · ADATA USB Flash Drive 28.9G
eth0  routable  ip 192.168.1.101  gw 192.168.1.254  dns 192.168.1.254 · r8169

 0 01:00.0 GeForce RTX 2080 Ti 11016 MiB (90.02.17.40.9A)      64°C  100 %  238 W
 1 02:00.0 GeForce RTX 2080 Ti 11019 MiB (90.02.17.00.BF)      67°C  100 %  275 W
 2 03:00.0 GeForce RTX 2080 Ti 11019 MiB (90.02.17.00.BF)      68°C  100 %  237 W
 3 05:00.0 GeForce RTX 2080 Ti 11019 MiB (90.02.17.40.9A)      64°C  100 %  234 W
 4 06:00.0 GeForce RTX 2080 Ti 11019 MiB (90.02.17.00.BF)      64°C   90 %  211 W
 5 07:00.0 GeForce RTX 2080 Ti 11019 MiB (90.02.17.00.BF)      72°C   90 %  222 W
 6 08:00.0 GeForce RTX 2080 Ti 11019 MiB (90.02.17.00.BF)      70°C   91 %  240 W
 7 0a:00.0 GeForce RTX 2080 Ti 11019 MiB (90.02.17.00.BF)      70°C   90 %  271 W

but AM show me, that all GPUs have right settings! Looks like AM only show, but not set settings...
why for last 4 cards fan settings was not applied???

[GKumaran]

Issue :
Mining ETH with TeamRedMiner on eth-proxy based pool requires an additional --eth_worker parameter to set the worker name.

Suggested resolution :
Pool -> Advanced -> Add Pool specific commands -> --eth_worker [MinerWorker]

Current Implementaion :
The command line is taken as is instead of interpreting the [MinerWorker] into the variables.

[narousberg]

Gminer has crashed, AM restarted and i see inconsole output:

Code:

1/4/20 12:11:57 AM.181 [006] [S]Found Screen PID: '29386'
1/4/20 12:11:57 AM.186 [006] [S]Found Shell PID: 29387
1/4/20 12:11:57 AM.191 [006] [S]Found Miner PID: 0
1/4/20 12:11:57 AM.191 [006] [S]Saving configuration to: /home/user/.config/AwesomeMinerService/ServiceData.xml.tmp
1/4/20 12:11:57 AM.241 [006] [S]--> /home/user/.config/AwesomeMinerService/ServiceData.xml
1/4/20 12:11:57 AM.275 [006] [S][ManagedMiner#25 - 2080TI] Mining Engine Process started, PID: 29386
1/4/20 12:11:57 AM.275 [006] [S]Miner commands left to process: 0
1/4/20 12:11:59 AM.122 [015] [E]Failed to process API request (time: 1 ms): /api/v1/status
Connection refused Connection refused
1/4/20 12:11:59 AM.123 [015] [E]Failed to process API request (time: 1 ms): /api/v1/status
Connection refused Connection refused

some processes failed!

finally i can say that two things not work properly:
awsome.service initialization on startup
settings of fan speed (at least for 4 last cards in the list)

[HunterKiller]

I recently installed the newest version of AM (fresh install) and I ran the benchmark tests on algos and the algos all worked but when it finished my Benchmark column was still blank, it was like that it didn't post the results for each benchmark. I did about 5 different algos to start with then I randomly chose individual miners and benched them individually and all of them were not recorded in the "benchmark result" column once the benchmark finished.

Has anyone come across this problem before and how did you fix it, cheers.

[narousberg]

I recently installed the newest version of AM (fresh install) and I ran the benchmark tests on algos and the algos all worked but when it finished my Benchmark column was still blank, it was like that it didn't post the results for each benchmark. I did about 5 different algos to start with then I randomly chose individual miners and benched them individually and all of them were not recorded in the "benchmark result" column once the benchmark finished.

Has anyone come across this problem before and how did you fix it, cheers.

do not made any changes on Profit profile during test....

[HunterKiller]

I recently installed the newest version of AM (fresh install) and I ran the benchmark tests on algos and the algos all worked but when it finished my Benchmark column was still blank, it was like that it didn't post the results for each benchmark. I did about 5 different algos to start with then I randomly chose individual miners and benched them individually and all of them were not recorded in the "benchmark result" column once the benchmark finished.

Has anyone come across this problem before and how did you fix it, cheers.

do not made any changes on Profit profile during test....

No, I didn't make any changes of any kind during test.

I've uninstalled the program, deleted all profiles and folders in app data and installed AM again and still did the same thing in tests.

[narousberg]

I recently installed the newest version of AM (fresh install) and I ran the benchmark tests on algos and the algos all worked but when it finished my Benchmark column was still blank, it was like that it didn't post the results for each benchmark. I did about 5 different algos to start with then I randomly chose individual miners and benched them individually and all of them were not recorded in the "benchmark result" column once the benchmark finished.

Has anyone come across this problem before and how did you fix it, cheers.

do not made any changes on Profit profile during test....

No, I didn't make any changes of any kind during test.

I've uninstalled the program, deleted all profiles and folders in app data and installed AM again and still did the same thing in tests.

are .NET up to date? Better if you update windows before installing. Otherwise you must check .log file of AM, maybe you will find some error messages.

[patrike]

@patrike - what can i do about this issue? I have a terminus R606 that I am monitoring on AM via port 4028

but now I cannot monitor my gpu rig on AM because it wants to use the same port so it mines but AM shows it as interface offline.

If I start the gpu rig first then the terminus it then cannot monitor the terminus

so I get that they are using the same port and that is the issue - is there a way to change this?

Awesome Miner allocates ports from 4028 and above for Managed Miners and this is not possible to change.

Are you running a local CgMiner process (or similar) for controlling the Terminus R606 miner? Does this one support running on another port (like --api-port 4123)?

yes - the terminus uses a local modified version of cgminer - i will check to see if it can run on another port

So yes I can change the port in cgminer for the terminus - simple actually - but how do I set AM to monitor it? Is it auto? If so why when running a managed miner thru AM does it not detect that AM is already listening to port and then use another one for my gpu rig?

In Awesome Miner you have an External Miner that is representing your Terminus ASIC miner. In the properties of this External Miner, the Remote Host property is pointing to something like "192.168.1.123".

By default Awesome Miner will connect to port 4028 on this ASIC miner. In your case you should also include the port number you configured the Terminus miner to use, for example: "192.168.1.123:4001"

You can configure an External Miner to point to any port, but this is not an automatic process.

[patrike]

i have stoped miner, rebooted linux and run your nvidia-smi query. And i got the same  GPU pci-bus ordering result.
Problem is, that the after reboot value of clocking values which was showed in AM is not equal to values from Profit Profile for this rig. I have no idea where come this values after reboot.

Just to make sure I understand the full scenario here. In addition to the reboot, I assume you also start the mining before you look at the current clocking/fan of the GPUs? With just a reboot the GPU's may have undefined clock/fan settings.

I'm currently investigating the issue where Awesome Miner may start looking at the GPU's too early after a reboot where some may not have been initialized yet. I'm also working on reproducing the issues you have reported here.

i try to set clocking for all cards and only for one (last card in list) and in console output i see:

Code:

...

AM set clocking only for GPU 0

Is this when using the user interface in Awesome Miner to move the sliders and apply a certain GPU clocking/fan configuration? So no matter how many GPU's you do the change for or which GPU, the log file always indicates that GPU 0 is the only GPU where it's applied? (Or something via the Clocking Profiles when starting the mining?)

Gminer has crashed, AM restarted and i see inconsole output:

Code:

1/4/20 12:11:59 AM.122 [015] [E]Failed to process API request (time: 1 ms): /api/v1/status
Connection refused Connection refused
1/4/20 12:11:59 AM.123 [015] [E]Failed to process API request (time: 1 ms): /api/v1/status
Connection refused Connection refused

some processes failed!

The error "Failed to process API request" is expected a few times the first few seconds after a mining software is starting up - as it often takes a few seconds for the mining software to start responding to API calls from Awesome Miner.

[patrike]

I recently installed the newest version of AM (fresh install) and I ran the benchmark tests on algos and the algos all worked but when it finished my Benchmark column was still blank, it was like that it didn't post the results for each benchmark. I did about 5 different algos to start with then I randomly chose individual miners and benched them individually and all of them were not recorded in the "benchmark result" column once the benchmark finished.

Has anyone come across this problem before and how did you fix it, cheers.

do not made any changes on Profit profile during test....

No, I didn't make any changes of any kind during test.

I've uninstalled the program, deleted all profiles and folders in app data and installed AM again and still did the same thing in tests.

I wasn't able to reproduce this problem so I will have to ask a few questions to narrow down what the issue might be:
1) Based on your description it sounds like you tried this on many algorithms and I suppose multiple kinds of mining software was used as well. Is this a correct understanding that multiple mining software was used during the benchmark so the problem isn't only for a specific software?
2) Any change if you change the Duration setting to 3-5 minutes instead?
3) Are you using local mining/benchmarking on the same computer where Awesome Miner is installed or is the mining/benchmarking running on another computer via Remote Agent?
4) If this still fails to work, could you please send me your log file (toolbar: Tools->Log File), either via e-mail or the "Contact Us" section on the web site.
Thanks!

[patrike]

Issue :
Mining ETH with TeamRedMiner on eth-proxy based pool requires an additional --eth_worker parameter to set the worker name.

Suggested resolution :
Pool -> Advanced -> Add Pool specific commands -> --eth_worker [MinerWorker]

Current Implementaion :
The command line is taken as is instead of interpreting the [MinerWorker] into the variables.

Thanks for the suggestion. I agree that the pool command line should support variables. I will add this in the next release.

[HunterKiller]

I recently installed the newest version of AM (fresh install) and I ran the benchmark tests on algos and the algos all worked but when it finished my Benchmark column was still blank, it was like that it didn't post the results for each benchmark. I did about 5 different algos to start with then I randomly chose individual miners and benched them individually and all of them were not recorded in the "benchmark result" column once the benchmark finished.

Has anyone come across this problem before and how did you fix it, cheers.

do not made any changes on Profit profile during test....

No, I didn't make any changes of any kind during test.

I've uninstalled the program, deleted all profiles and folders in app data and installed AM again and still did the same thing in tests.

I wasn't able to reproduce this problem so I will have to ask a few questions to narrow down what the issue might be:
1) Based on your description it sounds like you tried this on many algorithms and I suppose multiple kinds of mining software was used as well. Is this a correct understanding that multiple mining software was used during the benchmark so the problem isn't only for a specific software?
2) Any change if you change the Duration setting to 3-5 minutes instead?
3) Are you using local mining/benchmarking on the same computer where Awesome Miner is installed or is the mining/benchmarking running on another computer via Remote Agent?
4) If this still fails to work, could you please send me your log file (toolbar: Tools->Log File), either via e-mail or the "Contact Us" section on the web site.
Thanks!

Hello, thanks for the reply.

1. That is correct, I did try it on multiple algorithms which used different mining software and I also tried different software for the same algorithm too.
2. I tried the fast one and also the 3-5 minute one and even the 10 minute one still no change.
3. I am using local mining so accessing the same PC locally to do the benchmark on.
4. Log file incoming, cheers.

To add I found a very old version of AM which was 4.2.2 and I ran the benchmark and it recorded it then I tried a version 6 update of AM, I ran the benchmark and it didnt record and same as the latest version.
I also have the latest drivers installed.

Its very weird because I have no issue in running the mining software itself, they work without any problems its just the AM software isnt recording the results in the benchmark columns.

[Binary100100]

I haven't posted in this thread for a while (sorry) but I was just playing around with "Balance" and attempted to set the address for my ETC address on my Ledger.
Unforuntately, it failed.
It appears that "Gastracker is shooting down its services" (ref: https://bye.gastracker.io/?page=)
What are our alternatives for the block explorer API URL and can a fix be implemented in a near update?

[GKumaran]

Would like to have the ability to run the miner with admin privilages an option during the benchmark.