Author

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 511. (Read 703113 times)

legendary
Activity: 3346
Merit: 1094
I've implemented support for the Dstm Zcash Miner.

You can expect a new release of Awesome Miner within the next 1 - 2 days with this support included.


thanks Smiley ...
o yea don't know if honor it   

Happy Thanksgiving

sense your based in Sweden if not i hope you had a nice

Thanksgiving.

I'm not trying to find out were your from i don't care were you come from I'm just being seasonal for the time of year .......
Yes, I'm located in Sweden. Although Thanksgiving isn't a national holiday here, I appreciate your kindness and hope that you had a nice Thanksgiving!
legendary
Activity: 3346
Merit: 1094
Can you support Innosilicon A5 miner? Thanx
Awesome Miner supports a few other Innosilicon miners. I don't know about A5 yet, but it will probably work fine. Do you have this miner already?
I do, and it does not shown as an external miner.
The previous Innosilicon miners where running Cgminer, that had an API enabled that Awesome Miner could connect to. Is this something that needs to be enabled in the configuration of this miner?

If you add this as a miner in Awesome Miner as an External Miner, is it showing up as Disconnected?
newbie
Activity: 10
Merit: 0
How do I get SgMiner to work in AwesomeMiner? I have no issue with Claymore, but when I try to use SgMiner I get this error:

> [20:50:17] All devices disabled, cannot mine!
> [20:50:15] Started sgminer 5.5.4-gm                    
> [20:50:15] * using Jansson 2.7                    
> [20:50:15] Loaded configuration file awesome.conf                    
> [20:50:17] clDevicesNum returned error, no GPUs usable                    
> [20:50:17] All devices disabled, cannot mine!

This is on a 13 x RX570 rig. Using SgMiner in the NiceHash miner works fine.
Two troubleshooting tips here:
1) Try to disable sgminer-gm and only use the standard sgminer. If this is in a profit switcher, please go to Options dialog, Profit profile, Edit AMD, the uncheck sgminer-gm.
2) See if Nicehash adds any custom command line parameters for sgminer on your system that makes it more stable. You can then enter those command line parameters in Awesome Miner itself.

Thanks! I figured it out. I needed to add --gpu-platform 1 to the command line parameters.
newbie
Activity: 92
Merit: 0
Hello Patrike,
I would have a suggestion regarding profit switching.
As you can see in the picture below, i defined a profit profile for each type of graphic card i own in my rigs.

I then defined a profile group for each of my rig to have exact stats regarding income.
In profit group window, can you add an option to set up a specific profit switching profile.

This way it could be possible to have one rig that switch mining between nicehash and an ethereum pool, another rig that switch between zpool and a zcash pool.

It would be a great addition !
Today the pools for the profit switcher are defined on a global level (Options dialog, Profit switching). I assume want want this per profile (or group profile)?
I've had similar requests in the past to have have the profit switcher working on multiple set of pools, where not all miners would use the same pools.

Hello,
Yes, you assume right ! We're already able to create multiple pools groups. What i would like is the possibility to create profit switcher for different group profile ! Doing this, it would be possible for example to create a group profile that switch between pools defined in pool group 1, and create another group profile that would switch pools defined in pool group 2.
I would be a really great feature to manage multiple rigs dedicated to specific coins or algorithms.

Hello Patrike,
I don't want to be considered insistent regarding this feature, but do you think it's technically possible to add to awesome miner the possibility to have a specific profit switcher for one group profile ?
newbie
Activity: 12
Merit: 0

Does it run with out using Awesome miner ? ....if not what is the popup error it gives with out Awesome miner you may need to install something like:  vc_redist.x64.exe I have noticed in the past if something is not installed  on your PC Awesome won't work with some soft ware miner an not tell you why or everything, you many need to run it directly to see if there is a error of some kind the miner may still shut down without awesome running, if it does then it's a setting you need to find out what that is ... i have also had some pools not work well with awesome miner running but that same pool will if i don't use awesome miner with the same settings i used with awesome miner ..

This problem only happen to my GTX1070 Rigs (Rig 1 and 2) and not for GTX1060 Rig (Rig3)below could be why the two PC don't have everything they need and the new one does ? .

Does it run with out using Awesome miner ? ....if not what is the popup error it may give with out Awesome miner you may need to install something like:  vc_redist.x64.exe on those two pc.

or wait for the next update of Awesome to come out with Dstm Zcash Miner support that software miner does work  better then EWBF software miner or seems to, the only reason i don't use it now is I like Using Awesome miner more .

I have a mix of 4 Nv cards with a 1070 ti coming some time next week.
an i have  two AMD rigs with 4 cards each i may add one more card each to sense the prices for Amd cards are dropping in the US again .


Hi,
It runs smooth even with AM when run manually. It only happen when Profit switcher changes from a coin to another with Equihash (not everytime).
Therefore I asked Patrike for his help.
But anyway thanks for your suggestion !!
legendary
Activity: 1274
Merit: 1000
newbie
Activity: 12
Merit: 0
Hi Patrike,

When using profit switcher and switch to Equihash coin, often my miner goes "Interface offline" and never switch to another coin until I restart miner manually.
It happen when EWBF return "ERROR: API bind error".
I tried to set rule to restart miner when it detect Offlne, but it doesn't help.
I set Trigger;
- Detect offline, 30 second,
- Time interval: 0hours, 1munutes, 0seconds
and Actions;
- Stop miner
- wait 5 seconds
- Start miner

As I just added new computer to mine (my 3rd Rig), I'm planning to buy Standard version but I want to make sure this problem to be solved before purchase.
This problem only happen to my GTX1070 Rigs (Rig 1 and 2) and not for GTX1060 Rig (Rig3).
Any suggestions?
First verify that the rule is Enabled (the checkbox). Next, please send me the log file (toolbar: Tools -> Log File) and let me know the name of the miner that didn't trigger the rule as expected. Thanks!
Yes, the rule is Enabled.
Regarding Log file, please see below,
Code:
2017/11/19 7:23:02.615 [019] [S]Managed Profit Switching processing: Rig01 Local, IsRunning: False
2017/11/19 7:23:02.615 [019] [S]  Profitability, poolChanged: True, Algorithm: Equihash -> Equihash, EngineType: ZecEwbfMiner ->ZecEwbfMiner, EngineSubType: Disabled ->Disabled, AutoDownload: True, EnginePath:
2017/11/19 7:23:02.615 [001] [S]CoinStore, Built in coin dictionary updated
2017/11/19 7:23:02.677 [001] [S]ServiceAdapter, trigger send settings
2017/11/19 7:23:02.771 [008] [S]Sending Miner Settings to Host: localhost
2017/11/19 7:23:02.771 [011] [S]Updating settings
2017/11/19 7:23:02.771 [011] [S]Current list of Managed Miners:
[ManagedMiner#2 - Rig01 Local]

2017/11/19 7:23:02.771 [011] [S]Current list of Clocking Profile:

2017/11/19 7:23:02.771 [011] [S]Current list of Active Miners:
[2] IsAttached: True, PID: 6488, InstanceId: 2

2017/11/19 7:23:02.771 [011] [S]Saving configuration to: C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml.tmp
2017/11/19 7:23:02.802 [011] [S]--> C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml
2017/11/19 7:23:04.490 [027] [E]Failed to process API request (time: 1188 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:23:08.100 [021] [E]Failed to download string from: https://granatgas-pool.info/api/status
 System.Net.WebException: リモート サーバーに接続できません。
2017/11/19 7:23:22.883 [009] [E]Failed to process API request (time: 1063 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:23:29.072 [027] [E]Failed to process API request (time: 1141 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:23:59.660 [010] [E]Failed to process API request (time: 1281 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:24:12.068 [024] [E]Failed to process API request (time: 1250 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:24:27.851 [001] [S]CoinStore, Built in coin dictionary updated
2017/11/19 7:24:30.571 [023] [E]Failed to process API request (time: 1219 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:25:07.389 [023] [E]Failed to process API request (time: 1172 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:25:19.578 [011] [E]Failed to process API request (time: 1063 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:25:25.860 [001] [S]Updating wallet statistics
2017/11/19 7:25:31.423 [009] [E]Failed to download string from: https://granatgas-pool.info/api/status
 System.Net.WebException: リモート サーバーに接続できません。
2017/11/19 7:25:44.285 [024] [E]Failed to process API request (time: 1281 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:25:50.661 [025] [E]Failed to process API request (time: 1344 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:25:56.880 [011] [E]Failed to process API request (time: 1172 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:26:03.069 [027] [E]Failed to process API request (time: 1141 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:26:39.699 [023] [E]Failed to process API request (time: 1094 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
2017/11/19 7:27:28.581 [009] [E]Failed to process API request (time: 1047 ms): {"id":1, "method":"getstat"}

対象のコンピューターによって拒否されたため、接続できませんでした。 127.0.0.1:4029
"リモート サーバーに接続できません。" means cannot connect to remote server
"対象のコンピューターによって拒否されたため、接続できませんでした。" means Access denied by target computer
My miner name is Rig01 Local.

If there are any suggestions, it would be highly appreciated !!
legendary
Activity: 1274
Merit: 1000
I've implemented support for the Dstm Zcash Miner.

You can expect a new release of Awesome Miner within the next 1 - 2 days with this support included.


thanks Smiley ...


o yea don't know if honor it   

Happy Thanksgiving

sense your based in Sweden if not i hope you had a nice

Thanksgiving.

I'm not trying to find out were your from i don't care were you come from I'm just being seasonal for the time of year .......

cya

full member
Activity: 270
Merit: 100
Can you support Innosilicon A5 miner? Thanx
Awesome Miner supports a few other Innosilicon miners. I don't know about A5 yet, but it will probably work fine. Do you have this miner already?
I do, and it does not shown as an external miner.
legendary
Activity: 3346
Merit: 1094
Is there a way to get Awesome Miner to mine three different coins on the game rig? Three different miner programs on the same rig (three algorithms on two GPU's each).
You need to have three different mining processes running for this. Please create three separate Managed Miners, but keep in mind that you need to pass command line parameters to the mining software to instruct that only 2 specific GPU's should be used. The exact command line parameters for this depends on the mining software you run - please refer to their readme files. For Claymore miners it's "-di 0,1" to use GPU0 and GPU1 for example
legendary
Activity: 3346
Merit: 1094
I've implemented support for the Dstm Zcash Miner.

You can expect a new release of Awesome Miner within the next 1 - 2 days with this support included.
legendary
Activity: 3346
Merit: 1094
How do I get SgMiner to work in AwesomeMiner? I have no issue with Claymore, but when I try to use SgMiner I get this error:

> [20:50:17] All devices disabled, cannot mine!
> [20:50:15] Started sgminer 5.5.4-gm                    
> [20:50:15] * using Jansson 2.7                    
> [20:50:15] Loaded configuration file awesome.conf                    
> [20:50:17] clDevicesNum returned error, no GPUs usable                    
> [20:50:17] All devices disabled, cannot mine!

This is on a 13 x RX570 rig. Using SgMiner in the NiceHash miner works fine.
Two troubleshooting tips here:
1) Try to disable sgminer-gm and only use the standard sgminer. If this is in a profit switcher, please go to Options dialog, Profit profile, Edit AMD, the uncheck sgminer-gm.
2) See if Nicehash adds any custom command line parameters for sgminer on your system that makes it more stable. You can then enter those command line parameters in Awesome Miner itself.
legendary
Activity: 3346
Merit: 1094
Recently AwesomeMiner began to stop mining after switching to sgminer (I'm on AMDs). From logs it seems to try and restart it a few times, each time complaining about

 Process already closed

and

  No connection could be made because the target machine actively refused it 127.0.0.1:4028

and then it just gives up. Restart on offline detection didn't help.

From the logs, it doesn't try to switch back to other miners, like EthDcrMiner, it just keeps pounding at the Sgminer until it gives up. I am able to start Sgminer manually using the same command from the log and it works fine. Also I've seen it working fine before with AwesomeMiner. I've checked and Firewall isn't a problem. Access to sgminer.exe is allowed on all ports and I see it listening on 4028 when running.

I didn't find much on this on the net, so coming to the source. It goes down every day, with a 100% repro rate, so I'm loosing hours of mining. Any ideas? Here is the log snippet.

Can you use the Diagnostics button in the toolbar to get more output information from sgminer itself? It may give some hint about what is wrong. In general, Sgminer is the most difficult mining software to configure because it has so many parameters and they depend very much on the GPU's being used, making it difficult to give general recommendations.

All other mining software run stable on your system except Sgminer? What about if you try to disable the Neoscrypt algorithm, if it's only that one?

Yes, only Sgminer and Sgminer-GM. I disabled both in the AMD profit profile and the mining hasn't stopped ever since, but that defeats the purpose of profit switching. My cards are R9 290s and R9 Fury X. In both cases the same repro.

I've caught Sgminer crash process one one of the systems, but don't see similar crashes on other machines where AwesomeMiner just gave up. Here's what it logged:

Faulting application name: sgminer.exe, version: 0.0.0.0, time stamp: 0x001dc4e4
Faulting module name: amdocl64.dll, version: 22.19.685.0, time stamp: 0x59d6a487
Exception code: 0xc0000005
Fault offset: 0x000000000049e606
Faulting process id: 0x1d64
Faulting application start time: 0x01d3633675ea8bbb
Faulting application path: C:\Users\Michael\AppData\Local\AwesomeMiner\sgminer-gm-5.5.4_1\sgminer-gm\sgminer.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\c0318724.inf_amd64_3e17b73ae627ea03\amdocl64.dll
Report Id: 0678aba1-075a-43b9-9b9d-c5d29519691d
Faulting package full name:
Faulting package-relative application ID:

Which looks like a one-off display driver induced bug (17.10.1 radeon drivers).

I think the root cause for this AwesomeMiner giving up is its inability to connect to port 4028 on localhost for Sgminer(-gm). I assume that's the control port it uses for manage all miners. It looks like sgminer process dies, and AwesomeMiner doesn't realize that and keeps trying to talk to it, instead of switching to another miner.

What would I be looking for in the Diagnostics log?
I cannot do much about the crashes in sgminer itself, but I do have a recommendation here. I think that you might have a scenario where Sgminer is crashing, but your system is showing a crash dialog that is preventing the sgminer process from terminating.

In this scenario, both Windows and Awesome Miner will think that sgminer is still running and cannot do anything about it. The solution is to disable this dialog in Windows and simply let the process terminate right away. Awesome Miner will detect that as a crash and try to recover. Please see this link for instructions: https://superuser.com/a/715645

legendary
Activity: 3346
Merit: 1094
Would you know why I see everything set to 0Mhz even if I can talk to MSI Remote Server ?

https://ibb.co/ipOzCm
Can you try to enable "Map to system monitoring" feature?
http://www.awesomeminer.com/help/gpumapping.aspx
legendary
Activity: 3346
Merit: 1094
Hi, first of all, thanks for awesome software Smiley I use it mostly for ASIC Antminer monitoring, and I have a some question.

I made a rule, which reboots asic on trigger "chip failure". However if asic has a "chip failure" right after reboot, there is a infinite reboot.
Please give a tip of advice how to make rule with automatic reboot in case of critical failures but not more than 3 times in a row.

Thanks a lot.
Thanks for your feedback. Today there are no way of counting number of times an action has triggered and have a limit on that.

What if you configure your rule to have two triggers? First you check if chip failure, second you have a Time trigger that goes off for example every hour. Then your reboot action will happen at most one time per hour. Your miner will then still do some work in between and you can disable the rule for this specific miner later on if you see that it never recovers.
legendary
Activity: 3346
Merit: 1094
Hi Patrike,

When this happens :

it leads to this issue :

Miner doesn't gets restarted as AwesomeMiner did not detect the crash.

Offline rules don't do anything, it just stays offline like this forever.
It's not a crash, but it should trigger the offline detection rule. It could probably be detected by the "Accept Progress" rule as well if enabled.

Can you please share some details of how the Offline Detection rule is configured? That will help me understand why it didn't work as expected. Thanks!

Here you go ! Not sure why even the hashrate 10min doesn't catch it ..

https://ibb.co/kNAWa6
I have identified a scenario where Offline Detection didn't work correctly for Managed Miners in the "Interface offline" scenario. A correction will be included in the next release.
sr. member
Activity: 378
Merit: 250
Is there a way to get Awesome Miner to mine three different coins on the game rig? Three different miner programs on the same rig (three algorithms on two GPU's each).
member
Activity: 114
Merit: 10
newbie
Activity: 29
Merit: 0
The command is --telemetry=0.0.0.0:4029 instead of --api ...

Then you can query it via browser or json query.

It would take somebody from Awesome Miner, to add support for stats, patrike?
There is a sample json-rpc.txt file in the folder:

Request:
-->{"id":1, "method":"getstat"}

Response:
<--{
    "id": 1,
    "result": [{
        "gpu_id":          0,         // GPU CUDA id
        "temperature":     0,         // current GPU temperature
        "sol_ps":          0.00,      // current Sol/s
        "avg_sol_ps":      0.00,      // average Sol/s
        "sol_pw":          0.00,      // current Sol/s / Watt
        "avg_sol_pw":      0.00,      // average Sol/s / Watt
        "power_usage":     0.00,      // current power usage
        "avg_power_usage": 0.00,      // average power usage
        "accepted_shares": 0,         // total amount of accepted shares
        "rejected_shares": 0,         // total amount of rejected shares
        "latency":         0          // network latency
    }],

    "uptime":   0,                    // uptime in seconds
    "contime":  0,                    // connection time in seconds (gets reset on reconnect)
    "server":   "myserver.com",       // server name
    "port":     0000,                 // port
    "user":     "username",           // username
    "version":  "0.5.4",              // zm version
    "error":    null
}


IS IT POSSIBLE TO ADD SUPPORT OF "dstm-zcash" MINER ?

I can get this to work, but only by using it as a custom miner within Awesome Miner, the problem is Awesome Miner does not get any data back from the miner so no stats are displayed.

Patrike,

Below is the diagnostic output...  I hope you can fix / add this in Awesome Miner soon.



Starting Diagnostics
Starting Mining Software
Setting up Miner Engine. Instance: 2
Engine Type: 7, Auto Download: False, EnginePath: D:\NiceHashMiner\zm_0.5.5_win\zm.exe, Subtype: Disabled, CustomExecutable:
Added rule for: D:\NiceHashMiner\zm_0.5.5_win\zm.exe
D:\NiceHashMiner\zm_0.5.5_win\zm.exe  --server equihash.mine.zpool.ca --port 2142 --user --pass c=BTC --api 0.0.0.0:4029   (WindowMode: ConsoleFormat, EngineType: 7, IsProfitMiner: True)
Configuration:

Mining Engine Process started, PID: 10476

====================================================================================================
> #  zm 0.5.5
> #  GPU0 + GeForce GTX 1070         MB: 8192 PCI: 1:0
> #  GPU1 + GeForce GTX 1070         MB: 8192 PCI: 8:0
>
> #  GPU0  connected to: equihash.mine.zpool.ca:2142
> #  GPU1  connected to: equihash.mine.zpool.ca:2142
> #  GPU0  server supports extranonce
> #  GPU1  server supports extranonce
> #  GPU0  server set difficulty to: 00002003e07c0f81f0000000...
> #  GPU1  server set difficulty to: 00002003e07c0f81f0000000...

====================================================================================================
Stopping miner process ...
Stopping Mining Software
> D:\NiceHashMiner\zm_0.5.5_win\zm.exe: unknown option -- api
Diagnostics completed



full member
Activity: 270
Merit: 115
IS IT POSSIBLE TO ADD SUPPORT OF "dstm-zcash" MINER ?

I can get this to work, but only by using it as a custom miner within Awesome Miner, the problem is Awesome Miner does not get any data back from the miner so no stats are displayed.

Patrike,

Below is the diagnostic output...  I hope you can fix / add this in Awesome Miner soon.



Starting Diagnostics
Starting Mining Software
Setting up Miner Engine. Instance: 2
Engine Type: 7, Auto Download: False, EnginePath: D:\NiceHashMiner\zm_0.5.5_win\zm.exe, Subtype: Disabled, CustomExecutable:
Added rule for: D:\NiceHashMiner\zm_0.5.5_win\zm.exe
D:\NiceHashMiner\zm_0.5.5_win\zm.exe  --server equihash.mine.zpool.ca --port 2142 --user --pass c=BTC --api 0.0.0.0:4029   (WindowMode: ConsoleFormat, EngineType: 7, IsProfitMiner: True)
Configuration:

Mining Engine Process started, PID: 10476

====================================================================================================
> #  zm 0.5.5
> #  GPU0 + GeForce GTX 1070         MB: 8192 PCI: 1:0
> #  GPU1 + GeForce GTX 1070         MB: 8192 PCI: 8:0
>
> #  GPU0  connected to: equihash.mine.zpool.ca:2142
> #  GPU1  connected to: equihash.mine.zpool.ca:2142
> #  GPU0  server supports extranonce
> #  GPU1  server supports extranonce
> #  GPU0  server set difficulty to: 00002003e07c0f81f0000000...
> #  GPU1  server set difficulty to: 00002003e07c0f81f0000000...

====================================================================================================
Stopping miner process ...
Stopping Mining Software
> D:\NiceHashMiner\zm_0.5.5_win\zm.exe: unknown option -- api
Diagnostics completed


Jump to: