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

crazydane

full member

Activity: 558

Merit: 194

Quote from: patrike on August 08, 2018, 10:53:35 AM

If Awesome Miner is unable to load ConfigData.xml, for example because of version incompatibilities, it will go for any of the backup files instead. I would suggest to first exit Awesome Miner completely on the target computer, then remove all files in the folder %appdata%\AwesomeMiner\, and finally put the ConfigData.xml in there and start Awesome Miner again. Then there are only two possibilities:
1) Either Awesome Miner load the exact content of ConfigData.xml and what you see on the screen is what the file contains
2) Or you will see a completely empty Awesome Miner window with no miners because it failed to load the configuration file.

Something in between is not possible.

Please also note that you cannot have two Awesome Miner main applications running at the same time controlling the same Remote Agents - that will result in miners showing up as stopped. It's only ASIC miners (External Miners) that can be monitored from multiple instances of Awesome Miner as the same time.

I exited/stopped Awesome Miner on the target.

I deleted everything in %appdata%\AwesomeMiner\

I copied in the ConfigData.xml file

I started up Awesome Miner and get a completely empty Awesome Miner window now. Source is running latest pre-release and Target is running latest release I was able to download, which is 3.3.3. So I guess what I need to to is to manually register the version on the target and upgrade it to the latest pre-release and try again? (after clearing out %appdata%\AwesomeMiner\ again and copy in ConfigData.xml again)

EDIT: I did what I suggested in the last paragraph and that did the trick!

dasch

newbie

Activity: 21

Merit: 0

Quote from: patrike on August 08, 2018, 05:51:58 AM

Quote from: dasch on August 07, 2018, 10:09:34 PM

Hi patrike,

I'm experiencing an issue mining with excavator through AM.

I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well.
With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this

It looks like Awesome Miner think you are using Excavator 1.5, as it will try to connect to "nhmp.eu.nicehash.com:3200". It might be the detection in Awesome Miner isn't perfect for this scenario. Do you want to use 1.4 or is 1.5 an option?

I prefer keeping 1.4 version so I can use any server and not only nicehash's one.

soothaa

hero member

Activity: 1151

Merit: 528

Quote from: dasch on August 07, 2018, 10:09:34 PM

Hi patrike,

I'm experiencing an issue mining with excavator through AM.

I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well.
With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this

Code:

=========================== www.nicehash.com =========================
   Excavator v1.4.4a_nvidia GPU Miner for NiceHash.
   Copyright (C) 2018 NiceHash. All rights reserved.
   Developed by
   djeZo, dropky, voidstar, and agiz
   with help and contributions from
   zawawa, pallas, Vorksholk, bitbandi, ocminer, and Genoil.
=========================== www.nicehash.com =========================

Build time: 2018-02-16 13:11:25
Build number: 4645
Provided startup commandline:
   "C:\Users\MINEUR\AppData\Local\AwesomeMinerService\UploadedSoftware\excavator\excavator.exe" -c awesome.json -p 4028

[05:05:15][0x00000fc0][info] Log started
[05:05:15][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] api | Listening on 127.0.0.1:4028
[05:05:16][0x00000fc0][info] core | Initialized!
[05:05:19][0x000007d4][warning] core | Command exec: invalid stoi argument
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy

The awesome.json file generated in excavator folder look like this

Code:

[
{"time":0,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.eu.nicehash.com:3200","my.btc.address"]}
]},
{"time":1,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["equihash","0"]},
{"id":1,"method":"worker.add","params":["equihash","1"]},
{"id":1,"method":"worker.add","params":["equihash","2"]},
{"id":1,"method":"worker.add","params":["equihash","3"]},
{"id":1,"method":"worker.add","params":["equihash","4"]},
{"id":1,"method":"worker.add","params":["equihash","5"]},
{"id":1,"method":"worker.add","params":["equihash","6"]},
{"id":1,"method":"worker.add","params":["equihash","7"]},
{"id":1,"method":"worker.add","params":["equihash","8"]},
{"id":1,"method":"worker.add","params":["equihash","9"]},
{"id":1,"method":"worker.add","params":["equihash","10"]},
{"id":1,"method":"worker.add","params":["equihash","11"]},
{"id":1,"method":"worker.add","params":["equihash","12"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"worker.print.speed","params":["2"]},
{"id":1,"method":"worker.print.speed","params":["3"]},
{"id":1,"method":"worker.print.speed","params":["4"]},
{"id":1,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"worker.print.speed","params":["6"]},
{"id":1,"method":"worker.print.speed","params":["7"]},
{"id":1,"method":"worker.print.speed","params":["8"]},
{"id":1,"method":"worker.print.speed","params":["9"]},
{"id":1,"method":"worker.print.speed","params":["10"]},
{"id":1,"method":"worker.print.speed","params":["11"]},
{"id":1,"method":"worker.print.speed","params":["12"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
]

I don't understand why there's this "invalid stoi argument"
Thanks !

I'm getting this as well.. I think something broke that miner in the CUDA 9.2 upgrade...

soothaa

hero member

Activity: 1151

Merit: 528

Quote from: patrike on August 08, 2018, 04:27:55 AM

Quote from: soothaa on August 07, 2018, 06:26:05 AM

Good morning Patrike quick question for you.

I am always on the bleeding edge of miners and using betas hours after they are released. When trying to benchmark many of them, I simply get a "unknown option --benchmark" message and then the software just mines on some random pool and usually the wrong algo (z-enemy) is the latest one doing this.

It would be really nice if the benchmark page could be reworked to have a dropdown to choose:

1) Select the software you wish to benchmark
2) Select the algo you wish to benchmark
3) The pool for a matching coin is selected from the profit switching section so I don't have to be constantly maintaining random pools for that info

This would be a huge help and improvement over the current dialog as it is not even sortable by software..

As always, thank you for your work!

In the recent versions of Awesome Miner, the benchmark dialog has a checkbox for "Benchmark without a pool". When checked, Awesome Miner will tell the mining software to run in benchmark mode when supported, which for some software results in adding "--benchmark" to the command line. If you uncheck this setting, the benchmarking will be using a pool and no "--benchmark" should be added.

Thanks for your feedback for the benchmark feature. These are good points and can for sure be input to future improvements.

Yes, this behavior is specifically when using that feature.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: crazydane on August 08, 2018, 07:21:29 AM

Quote from: patrike on August 08, 2018, 04:30:03 AM

ConfigData.xml (located in %appdata%\AwesomeMiner\ folder) is the only configuration file for Awesome Miner. You can copy this one between your computers, but please make sure that Awesome Miner isn't running (Menu -> Exit) before you replace the configuration on the target computer. Can you please check this one more time?

I tried again with the same result. Here's AM running on the source computer:

Size of the ConfigData.xml file is ~1,100 KB.

Here's what AM looks like after copying that 1,100 KB file to the target computer and waiting a couple of minutes :

So only miners that are working are the external ones. None of the managed miners show up (they are still running).

Also, after running for a few minutes the size of the ConfigData.xml file is reduced to ~800 KB.

All the profit profiles and hosts are missing from the target computer after starting up AM there. (which explains why they don't show up as running) So this is likely what accounts for the ~300 KK worth of metadata that gets deleted from the xml file upon startup. It is also interesting to note that the miner "antminer 103 - S9" is showing up on the target computer even though that was deleted from the source computer about a week ago.

Thanks for the update.

The miner lists are not the same, so the configuration must have been either loaded or taken from a backup file. Do you use the same version of Awesome Miner? Recent versions actually store the data a bit more efficient so they have smaller file size compared to older versions.

If Awesome Miner is unable to load ConfigData.xml, for example because of version incompatibilities, it will go for any of the backup files instead. I would suggest to first exit Awesome Miner completely on the target computer, then remove all files in the folder %appdata%\AwesomeMiner\, and finally put the ConfigData.xml in there and start Awesome Miner again. Then there are only two possibilities:
1) Either Awesome Miner load the exact content of ConfigData.xml and what you see on the screen is what the file contains
2) Or you will see a completely empty Awesome Miner window with no miners because it failed to load the configuration file.

Something in between is not possible.

Please also note that you cannot have two Awesome Miner main applications running at the same time controlling the same Remote Agents - that will result in miners showing up as stopped. It's only ASIC miners (External Miners) that can be monitored from multiple instances of Awesome Miner as the same time.

crazydane

full member

Activity: 558

Merit: 194

Quote from: patrike on August 08, 2018, 04:30:03 AM

ConfigData.xml (located in %appdata%\AwesomeMiner\ folder) is the only configuration file for Awesome Miner. You can copy this one between your computers, but please make sure that Awesome Miner isn't running (Menu -> Exit) before you replace the configuration on the target computer. Can you please check this one more time?

I tried again with the same result. Here's AM running on the source computer:

Size of the ConfigData.xml file is ~1,100 KB.

Here's what AM looks like after copying that 1,100 KB file to the target computer and waiting a couple of minutes :

So only miners that are working are the external ones. None of the managed miners show up (they are still running).

Also, after running for a few minutes the size of the ConfigData.xml file is reduced to ~800 KB.

All the profit profiles and hosts are missing from the target computer after starting up AM there. (which explains why they don't show up as running) So this is likely what accounts for the ~300 KK worth of metadata that gets deleted from the xml file upon startup. It is also interesting to note that the miner "antminer 103 - S9" is showing up on the target computer even though that was deleted from the source computer about a week ago.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: dasch on August 07, 2018, 10:09:34 PM

Hi patrike,

I'm experiencing an issue mining with excavator through AM.

I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well.
With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this

It looks like Awesome Miner think you are using Excavator 1.5, as it will try to connect to "nhmp.eu.nicehash.com:3200". It might be the detection in Awesome Miner isn't perfect for this scenario. Do you want to use 1.4 or is 1.5 an option?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: NotFuzzyWarm on August 07, 2018, 08:20:47 PM

@ patrike
Any chance you can can have the Avalons deliver full reports on each miner attached to their controller? Currently stats break down to each AUC device reporting the miners attached to it as 1 big miner.

The stats *are* in the api so here's the API log:

Awesome Miner is currently only displaying the information based on the devices in the API's. Each devices can then have 4 - 5 sub devices that is reported in a vendor specific way in these API's. Each of these sub devices represent a physical miner. With the current version of Awesome Miner, it uses the same device concept as for any other miner, and you might get 3 - 4 devices listed on the ASIC tab - even if the number of physical miners are 12 or more.

I would be possible for Awesome Miner to use the vendor specific information in the API's to dig deeper into the information and list all physical miners as a device on the ASIC tab - with individual hashrates and temperature information for each.

From a management point of view it's however still a only single large miner in Awesome Miner, as pool operations and similar are only set to the R-Pi controller. Each physical miner is only made available with monitoring information over the API's, but all of them are still controlled like single miner.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Finnsk3 on August 07, 2018, 08:16:02 PM

Hi all,

Quick suggestion for the devs:

I have my time period for statistics set to 24 hours average because I mine to some Yiimp pools with shit coins and on current it mines shit coins that peak in profitability for only a couple of minutes then crash hard so I end up earning less.

24 hours average works well to fix this but I want to use current for nicehash and 24 hour average for everything else obviously because you actually get paid current rate for nicehash.

I am hoping the ability to select this could be added.

Also coincalculators.io has the ability to show profitability for 24h/6h/3h/current, maybe you could add those options if using coincalculators.io

Thanks for the feedback. I've had some similar requests for the current vs 24h settings, so this will be supported in the future.

For coincalculators, they only provide the current and 24h values over the API's, but it's probably possible to have a discussion with them to provide the 3h and 6h values as well.

trucobit

jr. member

Activity: 756

Merit: 2

Quote from: patrike on August 08, 2018, 04:36:30 AM

Quote from: trucobit on August 07, 2018, 02:39:25 PM

https://www.dropbox.com/s/vz70h4vxrxhjekp/Captura%20de%20pantalla%202018-08-07%20a%20las%2021.32.54.png?dl=0

I have a little problem, which must be my fault, because nobody else in the telegram group happens to him.

If you look at the capture you will see that the rig4 is undermining Nicehash, but it does not mark profit, down in the console you see that everything is correct, and if I go to the nicehash page it detects everything well and gives me the benefits.

It happens to me in all the miners, and only happens to me with Nicehash, in the other Pools if it marks the profit of what I am undermining.

I've been asking my telegram colleagues and asking about the options and I have not seen anything wrong. I have even added cryptodredge 0.8.3 the latest version to AM and nothing, I still can not see the profit of the mined in nicehash in real time.

I'm using an external Nicehash address, I've also used the BTC address that gives me nicehash when you login, it just does not work. It's very strange ... any advice?

Could it be by cryptodredge?

Is it the same issue if you look on the Online Services tab, as this is the data Awesome Miner uses to calculate the profit during mining? Is Nicehash showing any profit for Lyra2z? Are any Nicehash algorithms showing up correctly on the Online Services tab?

That's the weird thing, that in online services the profit appears correctly, but not when it is mined. It even makes changes to the Auto switch because it is based on service onlines. But when I'm mining it does not appear.

It does not matter what miner you use, cryptodredge or zenemy, it does not matter, it just does not appear. I have reviewed all the options in Options, and it only happens with nicehash, they are of these rare errors that you do not know where to start.

I hope that in the next update it will be fixed alone, or I hope so, I recognize that it is something quite strange and curious.

I leave another capture where you will see some miners with nicehash with 00, and with zpool that marks correctly

[url]https://www.dropbox.com/s/eef2zhs8dl9gr2w/Captura%20de%20pantalla%202018-08-08%20a%20las%2012.23.15.png?dl=0]https://www.dropbox.com/s/7ayq7qjk5d5mxye/Captura%20de%20pantalla%202018-08-08%20a%20las%2012.19.21.png?dl=0/url]

That's the weird thing, that in online services the profit appears correctly, but not when it is mined. It even makes changes to the Auto switch because it is based on service onlines. But when I'm mining it does not appear.

It does not matter what miner you use, cryptodredge or zenemy, it does not matter, it just does not appear. I have reviewed all the options in Options, and it only happens with nicehash, they are of these rare errors that you do not know where to start.

I hope that in the next update it will be fixed alone, or I hope so, I recognize that it is something quite strange and curious.

I leave another capture where you will see some miners with nicehash with 00, and with zpool that marks correctly

[url]https://www.dropbox.com/s/eef2zhs8dl9gr2w/Captura%20de%20pantalla%202018-08-08%20a%20las%2012.23.15.png?dl=0

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on August 07, 2018, 02:39:25 PM

https://www.dropbox.com/s/vz70h4vxrxhjekp/Captura%20de%20pantalla%202018-08-07%20a%20las%2021.32.54.png?dl=0

I have a little problem, which must be my fault, because nobody else in the telegram group happens to him.

If you look at the capture you will see that the rig4 is undermining Nicehash, but it does not mark profit, down in the console you see that everything is correct, and if I go to the nicehash page it detects everything well and gives me the benefits.

It happens to me in all the miners, and only happens to me with Nicehash, in the other Pools if it marks the profit of what I am undermining.

I've been asking my telegram colleagues and asking about the options and I have not seen anything wrong. I have even added cryptodredge 0.8.3 the latest version to AM and nothing, I still can not see the profit of the mined in nicehash in real time.

I'm using an external Nicehash address, I've also used the BTC address that gives me nicehash when you login, it just does not work. It's very strange ... any advice?

Could it be by cryptodredge?

Is it the same issue if you look on the Online Services tab, as this is the data Awesome Miner uses to calculate the profit during mining? Is Nicehash showing any profit for Lyra2z? Are any Nicehash algorithms showing up correctly on the Online Services tab?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Dalba on August 07, 2018, 12:37:17 PM

Hello Patrike,
In managed software section, i tried to set a local share as a custom url but it doesn't seem to work. Rigs don't download software.
In custom url field i tried something like this : \\NAS\myshare\software-1.0.zip
Could you enable this ? For software not on github like z-enemy miner, it can be useful to update this way instead of waiting you update AM.

Currently only URL's (like http) that's supported, but it will look into this case as well. It should be quite easy to support from what I can see right now.

Update: I've just implemented support for file shares like in your example. It will be part of the next release.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: jmarm on August 07, 2018, 01:52:00 PM

Are there plans to update SRB Miner to V 1.6.5? Its been out for a while but no update in Awesome Miner. Thanks!

It's included in the development release 5.3.9. To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: crazydane on August 07, 2018, 10:59:49 AM

I'm trying to move my Awesome Miner install to a different computer but no matter which method I try, what I end up with on the target system is not complete.

I have tried using the built-in Export function and selecting everything (Pools, Group Pools, External Miners, Managed Miners), but after import on the target computer, many of the pools are missing, as are all the miner hosts.

I also tried moving the ConfigData.xml file over to the new computer, but that still did not provide a ready to run environment.

Has anyone else run into this issue, or am I missing some obvious step(s)?

ConfigData.xml (located in %appdata%\AwesomeMiner\ folder) is the only configuration file for Awesome Miner. You can copy this one between your computers, but please make sure that Awesome Miner isn't running (Menu -> Exit) before you replace the configuration on the target computer. Can you please check this one more time?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: soothaa on August 07, 2018, 06:26:05 AM

Good morning Patrike quick question for you.

I am always on the bleeding edge of miners and using betas hours after they are released. When trying to benchmark many of them, I simply get a "unknown option --benchmark" message and then the software just mines on some random pool and usually the wrong algo (z-enemy) is the latest one doing this.

It would be really nice if the benchmark page could be reworked to have a dropdown to choose:

1) Select the software you wish to benchmark
2) Select the algo you wish to benchmark
3) The pool for a matching coin is selected from the profit switching section so I don't have to be constantly maintaining random pools for that info

This would be a huge help and improvement over the current dialog as it is not even sortable by software..

As always, thank you for your work!

In the recent versions of Awesome Miner, the benchmark dialog has a checkbox for "Benchmark without a pool". When checked, Awesome Miner will tell the mining software to run in benchmark mode when supported, which for some software results in adding "--benchmark" to the command line. If you uncheck this setting, the benchmarking will be using a pool and no "--benchmark" should be added.

Thanks for your feedback for the benchmark feature. These are good points and can for sure be input to future improvements.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: ?? on ??

CryptoDredge v0.8.3

Fix TCP and WebSocket connections used for API
Fix Lyra2z performance on 1070 Ti and P104-100 graphics cards

https://github.com/technobyl/CryptoDredge/releases/download/v0.8.3/CryptoDredge_0.8.3_cuda_9.1_linux.tar.gz
https://github.com/technobyl/CryptoDredge/releases/download/v0.8.3/CryptoDredge_0.8.3_cuda_9.1_windows.zip
https://github.com/technobyl/CryptoDredge/releases/download/v0.8.3/CryptoDredge_0.8.3_cuda_9.2_windows.zip

Thanks! I will include this one in the next update.

With the recent versions of Awesome Miner, it's also possible to manually enter this URL in the Options dialog, Managed Software section, for CryptoDredge. That could be useful for those that want to use the latest mining software versions right away without having to wait for the next Awesome Miner update.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: principino1984 on August 06, 2018, 11:35:11 AM

@patrike will you implement this miner for bytom on AM? https://github.com/NebuTech/BTMiner_NebuTech/releases

one feature I'd like to see on AM... usually I set the hashrate and power consumption of a complete rig on the algo page, but it happens that sometimes I have a two or three gpu rig and AM keep showing in the miner page the consumption of a complete rig and not the real consumption. Do you think it can be added as a new features that in the miners tab, in the "Coin" column we will be able to see the real $USD costs calculated with the actual consumption of the rig?

thanks
marco

This one got an API very recently, so can probably be supported in one of the new few versions.

Using real power consumption is planned to be supported in future. It would also make sense to detect that when benchmarking.

EvilMonkey

full member

Activity: 192

Merit: 100

dasch

newbie

Activity: 21

Merit: 0

Hi patrike,

I'm experiencing an issue mining with excavator through AM.

I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well.
With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this

Code:

=========================== www.nicehash.com =========================
   Excavator v1.4.4a_nvidia GPU Miner for NiceHash.
   Copyright (C) 2018 NiceHash. All rights reserved.
   Developed by
   djeZo, dropky, voidstar, and agiz
   with help and contributions from
   zawawa, pallas, Vorksholk, bitbandi, ocminer, and Genoil.
=========================== www.nicehash.com =========================

Build time: 2018-02-16 13:11:25
Build number: 4645
Provided startup commandline:
   "C:\Users\MINEUR\AppData\Local\AwesomeMinerService\UploadedSoftware\excavator\excavator.exe" -c awesome.json -p 4028

[05:05:15][0x00000fc0][info] Log started
[05:05:15][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] api | Listening on 127.0.0.1:4028
[05:05:16][0x00000fc0][info] core | Initialized!
[05:05:19][0x000007d4][warning] core | Command exec: invalid stoi argument
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy

The awesome.json file generated in excavator folder look like this

Code:

[
{"time":0,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.eu.nicehash.com:3200","my.btc.address"]}
]},
{"time":1,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["equihash","0"]},
{"id":1,"method":"worker.add","params":["equihash","1"]},
{"id":1,"method":"worker.add","params":["equihash","2"]},
{"id":1,"method":"worker.add","params":["equihash","3"]},
{"id":1,"method":"worker.add","params":["equihash","4"]},
{"id":1,"method":"worker.add","params":["equihash","5"]},
{"id":1,"method":"worker.add","params":["equihash","6"]},
{"id":1,"method":"worker.add","params":["equihash","7"]},
{"id":1,"method":"worker.add","params":["equihash","8"]},
{"id":1,"method":"worker.add","params":["equihash","9"]},
{"id":1,"method":"worker.add","params":["equihash","10"]},
{"id":1,"method":"worker.add","params":["equihash","11"]},
{"id":1,"method":"worker.add","params":["equihash","12"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"worker.print.speed","params":["2"]},
{"id":1,"method":"worker.print.speed","params":["3"]},
{"id":1,"method":"worker.print.speed","params":["4"]},
{"id":1,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"worker.print.speed","params":["6"]},
{"id":1,"method":"worker.print.speed","params":["7"]},
{"id":1,"method":"worker.print.speed","params":["8"]},
{"id":1,"method":"worker.print.speed","params":["9"]},
{"id":1,"method":"worker.print.speed","params":["10"]},
{"id":1,"method":"worker.print.speed","params":["11"]},
{"id":1,"method":"worker.print.speed","params":["12"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
]

I don't understand why there's this "invalid stoi argument"
Thanks !

philipma1957

legendary

Activity: 4354

Merit: 9201

'The right to privacy matters'

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