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

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: narousberg on November 15, 2020, 04:51:18 AM

Patrike, for user defined coins if price will be dynamicly updated in USD, this price will not appear in bottom bar. Its appear if price will be defined in BTC. Is this normal or you can improve for both variants?
You can test it self for Conflux coin.

Thanks for the report. I will look into this case.

Quote from: narousberg on November 15, 2020, 04:51:18 AM

Pls. push updates for Bminer, T-Rex, Nanominer Regards

I've pushed a number of mining software updates now.

narousberg

legendary

Activity: 1753

Merit: 1007

Patrike, for user defined coins if price will be dynamicly updated in USD, this price will not appear in bottom bar. Its appear if price will be defined in BTC. Is this normal or you can improve for both variants?
You can test it self for Conflux coin.

https://www.confluxscan.io/v1/plot?interval=20&limit=1
difficulty json: list.[0].difficulty
hashrate json: list[0].hashRate
block time json: list[0].blockTime

for BTC price:
https://api.coingecko.com/api/v3/simple/price?ids=conflux-token&vs_currencies=btc
conflux-token.btc

or for USD price:
https://api.coingecko.com/api/v3/simple/price?ids=conflux-token&vs_currencies=usd
conflux-token.usd

Pls. push updates for Bminer, T-Rex, Nanominer Regards

narousberg

legendary

Activity: 1753

Merit: 1007

Quote from: patrike on November 09, 2020, 09:34:37 AM

Quote from: narousberg on November 09, 2020, 05:14:29 AM

Patrik, new T-Rex 0.18.7 awaiting new param -w for setting rig name. Can you implement this in next releases? Regards.

I will look into this. Was it only for three of the algorithms -w is supported?

Yes, only for this 3 algos (ethash, kawpow, progpow) . I have quick tested with HoneyComb algo and rig name appear on the pool. Hope design of AM allow this special chnanges.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: narousberg on November 09, 2020, 05:14:29 AM

Patrik, new T-Rex 0.18.7 awaiting new param -w for setting rig name. Can you implement this in next releases? Regards.

I will look into this. Was it only for three of the algorithms -w is supported?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: SCMining on November 08, 2020, 09:30:10 AM

Hi,

Can someone tell me exactly what does the Clean up all downloaded and uploaded mining software option on the System tools menu due?

Thank

Awesome Miner and Remote Agent downloads mining software (like Claymore Ethereum Miner, XmRig, ...) to your computer when needed. When you click on this menu item Awesome Miner will remove all downloaded mining software from disk.

In case some mining software file is corrupt (or removed by Anti-virus software), it can make sense to force a cleanup. Next time you start the mining Awesome Miner will automatically download the mining software again before trying to start it.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: sxemini on November 08, 2020, 03:57:38 AM

Quote from: patrike on November 02, 2020, 05:03:22 AM

Quote from: sxemini on October 30, 2020, 06:08:50 PM

Now i see no temps on all of my ryzen (1200, 1600, 2600x, G2400) In system tab it show me the temp, but status and the CPU tab give only 0°C, with v8.1.4 all works fine.

Thanks for the feedback. I will try to reproduce this.
Are you using XmRig or any other CPU mining software? Are all CPU cores reported with 0°C?

Hi patrike,

i use xmrig and srbminer multi, all show 0 for all cores.

And what do you mean:

User interface
- Organize rule actions with group labels to make it easier to find

Where i can organize the rules? Or what do you mean. I find no option or something else.

Thanks for the update. I will try to reproduce one more time.

About the release note entry about the rule. This is just a user interface change where the menu with all actions are re-structured (changed order, use labels to group different kinds of actions to make them easier to find). It's not a new way to organize the rules - although I do plan to allow for that in the future by introducing some group concept.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: cylshan on November 06, 2020, 04:17:27 PM

https://ibb.co/0YtxTcc

Is it possible to change the values of MEM and VDDCI?
And when rebooting, it does not keep the values of the fans, puts it on the machine all the time

These properties cannot be set explicitly by Remote Agent, but I can look into it as a future improvement.
In general, you can define a GPU Clocking Profile for your Managed Miner and it will apply your clocking settings as soon as the miner is started.

sxemini

member

Activity: 1558

Merit: 69

Quote from: SCMining on November 08, 2020, 09:30:10 AM

Hi,

Can someone tell me exactly what does the Clean up all downloaded and uploaded mining software option on the System tools menu due?

Thank

It does what it says. It delete all downloaded and uploaded mining software on the selected rig/miner.

narousberg

legendary

Activity: 1753

Merit: 1007

Patrik, new T-Rex 0.18.7 awaiting new param -w for setting rig name. Can you implement this in next releases? Regards.

SCMining

newbie

Activity: 23

Merit: 0

Hi,

Can someone tell me exactly what does the Clean up all downloaded and uploaded mining software option on the System tools menu due?

Thank

sxemini

member

Activity: 1558

Merit: 69

Quote from: patrike on November 02, 2020, 05:03:22 AM

Quote from: sxemini on October 30, 2020, 06:08:50 PM

Now i see no temps on all of my ryzen (1200, 1600, 2600x, G2400) In system tab it show me the temp, but status and the CPU tab give only 0°C, with v8.1.4 all works fine.

Thanks for the feedback. I will try to reproduce this.
Are you using XmRig or any other CPU mining software? Are all CPU cores reported with 0°C?

Hi patrike,

i use xmrig and srbminer multi, all show 0 for all cores.

And what do you mean:

User interface
- Organize rule actions with group labels to make it easier to find

Where i can organize the rules? Or what do you mean. I find no option or something else.

danielocdh

newbie

Activity: 22

Merit: 0

Quote from: patrike on November 06, 2020, 08:23:20 AM

Quote from: danielocdh on November 05, 2020, 10:13:27 AM

Quote from: patrike on November 04, 2020, 10:35:34 AM

Quote from: danielocdh on November 03, 2020, 09:17:01 PM

ethminer API timing out, but only on remote agent connections

I have hundreds of messages like this on the remote agent log per day on my miners(which eventually lead to false positive offline detection):

Code:

2020/11/01 6:51:23.796 [016] [E]Failed to process API request (localhost, time: 13006 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstatdetail"}

Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

48 hours ago I started running a script I made that reads the API on localhost every 5 seconds on every miner, I also ran the script 3 times on my machine with each instance pointing to the IP of each miner, the script instances never failed to connect and always took just a few milliseconds everywhere(only once in the 48 hours from my machine one instance took around one second to respond but responded correctly). I made this test with firewall disabled and freshly restarted miners.

I tried setting the priority of the remote agent process to high, I don't think it made a difference.

This is happening with ethminer 0.17.1 (chosen via awesome miner) and ethminer-0.19.0-7+commit.66186f1b (manually uploaded via awesome miner custom software). Although it seems to happen more on the updated version. I'm not using 0.18.0 (chosen via awesome miner) as it that version of ethminer has a bug that prevents the api from responding. I'm using the later version mainly because 0.17.1 won't show any data while mining, I believe the only data missing when using the later version is the individual progress details for each gpu.

Any suggestion on what else I could try? thanks

Thanks for the detailed description and for your analysis. So at the same time Remote Agent get a timeout after 13 seconds, your tool connecting to the same EthMiner API is receiving a response without any problems? Do you see a timeout error like this and then it works fine for a while and then another timeout and so on?

I will have to look into this a bit more because I cannot see any obvious reason why Remote Agent would timeout if the API is in fact working.

For the API data processing, I can make a few adjustments to make sure it parses the API response correctly once received.

Correct, my tool never failed to get the API data quickly, I'm using the same command I saw on the logs(miner_getstatdetail)

Update: I installed the latest updates for windows 1909 on windows update(security, servicing stack, cumulative and a .net 3.5 update but not edge), after about 10 hours the timeouts seem to be less common, one machine had 0, other 12 and other 16(6 consecutive timeouts once which triggered the offline detection that is set to 60 seconds now). The API was fully responsive all the time on all miners when requesting information from my computer with my tool (every 5 seconds never taking more than a few milliseconds).
I'll reformat one miner with latest windows to test when I can.

Thanks for the update.

If you look at the Windows Defender advanced settings, where all applications are listed - are there any difference between Awesome Miner and your tool? For example the Profile (Private, Public)?

I did the tests with firewall disabled but I normally have it set to not notify and not block all, so there are no extra rules. I only have the inbound rule for AwesomeMinerService (9630) which is private(as my network type). My tool (made in PHP and run locally via cli) doesn't listen on any port.

The updated 8.1.6 made awesome miner show more info for 0.17.1 but shows nothing for 0.19 (ethminer-0.19.0-7+commit.66186f1b). It seems those 2 versions APIs have different fields in the response. I haven't had any timeouts with 8.1.6 and 0.17.1 in a while so I'll just use that for now, thanks.

BitcoinBlaster51

newbie

Activity: 13

Merit: 0

Hello everyone,

If anyone here is mining on Mining Pool Hub, are you having issues mining the Ethash algorithm? When I try to mine in any of their Ethash pools, the miners usually close within a few seconds. I am not sure what the issue is after checking many settings within Awesome Miner.

cylshan

newbie

Activity: 18

Merit: 0

https://ibb.co/0YtxTcc

Is it possible to change the values of MEM and VDDCI?
And when rebooting, it does not keep the values of the fans, puts it on the machine all the time

patrike

legendary

Activity: 3346

Merit: 1094

Awesome Miner version 8.1.6

GPU mining
- Linux GPU mining: The AMD GPU model name will be displayed more exactly (like 'Radeon RX 5700XT' instead of' Radeon RX 5600/5700/5700XT'). Please check any GPU clocking rules based on device name after the upgrade.
Features
- Web interface includes the operation to Enable or Disable an External Miner
User interface
- Organize rule actions with group labels to make it easier to find
Mining software
- Bminer 16.3.4
- NbMiner 33.3
- SrbMiner 0.5.5
- TT-miner 6.0
- TeamRedMiner 0.7.17
Corrections
- Correction to GPU mapping for T-Rex miner
- Correction to API processing for EthMiner
- Correction to display of Core Voltage Limit for GPU Clocking Profiles in the Options dialog

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: danielocdh on November 05, 2020, 10:13:27 AM

Quote from: patrike on November 04, 2020, 10:35:34 AM

Quote from: danielocdh on November 03, 2020, 09:17:01 PM

ethminer API timing out, but only on remote agent connections

I have hundreds of messages like this on the remote agent log per day on my miners(which eventually lead to false positive offline detection):

Code:

2020/11/01 6:51:23.796 [016] [E]Failed to process API request (localhost, time: 13006 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstatdetail"}

Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

48 hours ago I started running a script I made that reads the API on localhost every 5 seconds on every miner, I also ran the script 3 times on my machine with each instance pointing to the IP of each miner, the script instances never failed to connect and always took just a few milliseconds everywhere(only once in the 48 hours from my machine one instance took around one second to respond but responded correctly). I made this test with firewall disabled and freshly restarted miners.

I tried setting the priority of the remote agent process to high, I don't think it made a difference.

This is happening with ethminer 0.17.1 (chosen via awesome miner) and ethminer-0.19.0-7+commit.66186f1b (manually uploaded via awesome miner custom software). Although it seems to happen more on the updated version. I'm not using 0.18.0 (chosen via awesome miner) as it that version of ethminer has a bug that prevents the api from responding. I'm using the later version mainly because 0.17.1 won't show any data while mining, I believe the only data missing when using the later version is the individual progress details for each gpu.

Any suggestion on what else I could try? thanks

Thanks for the detailed description and for your analysis. So at the same time Remote Agent get a timeout after 13 seconds, your tool connecting to the same EthMiner API is receiving a response without any problems? Do you see a timeout error like this and then it works fine for a while and then another timeout and so on?

I will have to look into this a bit more because I cannot see any obvious reason why Remote Agent would timeout if the API is in fact working.

For the API data processing, I can make a few adjustments to make sure it parses the API response correctly once received.

Correct, my tool never failed to get the API data quickly, I'm using the same command I saw on the logs(miner_getstatdetail)

Update: I installed the latest updates for windows 1909 on windows update(security, servicing stack, cumulative and a .net 3.5 update but not edge), after about 10 hours the timeouts seem to be less common, one machine had 0, other 12 and other 16(6 consecutive timeouts once which triggered the offline detection that is set to 60 seconds now). The API was fully responsive all the time on all miners when requesting information from my computer with my tool (every 5 seconds never taking more than a few milliseconds).
I'll reformat one miner with latest windows to test when I can.

Thanks for the update.

If you look at the Windows Defender advanced settings, where all applications are listed - are there any difference between Awesome Miner and your tool? For example the Profile (Private, Public)?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: narousberg on November 05, 2020, 06:28:37 AM

Patrike, pls add for Bminer for algo Octopus param conflux, in ver. 16.3.4 all works good.

I've pushed an update for this as well. Thanks for the feedback.

danielocdh

newbie

Activity: 22

Merit: 0

Quote from: patrike on November 04, 2020, 10:35:34 AM

Quote from: danielocdh on November 03, 2020, 09:17:01 PM

ethminer API timing out, but only on remote agent connections

I have hundreds of messages like this on the remote agent log per day on my miners(which eventually lead to false positive offline detection):

Code:

2020/11/01 6:51:23.796 [016] [E]Failed to process API request (localhost, time: 13006 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstatdetail"}

Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

48 hours ago I started running a script I made that reads the API on localhost every 5 seconds on every miner, I also ran the script 3 times on my machine with each instance pointing to the IP of each miner, the script instances never failed to connect and always took just a few milliseconds everywhere(only once in the 48 hours from my machine one instance took around one second to respond but responded correctly). I made this test with firewall disabled and freshly restarted miners.

I tried setting the priority of the remote agent process to high, I don't think it made a difference.

This is happening with ethminer 0.17.1 (chosen via awesome miner) and ethminer-0.19.0-7+commit.66186f1b (manually uploaded via awesome miner custom software). Although it seems to happen more on the updated version. I'm not using 0.18.0 (chosen via awesome miner) as it that version of ethminer has a bug that prevents the api from responding. I'm using the later version mainly because 0.17.1 won't show any data while mining, I believe the only data missing when using the later version is the individual progress details for each gpu.

Any suggestion on what else I could try? thanks

Thanks for the detailed description and for your analysis. So at the same time Remote Agent get a timeout after 13 seconds, your tool connecting to the same EthMiner API is receiving a response without any problems? Do you see a timeout error like this and then it works fine for a while and then another timeout and so on?

I will have to look into this a bit more because I cannot see any obvious reason why Remote Agent would timeout if the API is in fact working.

For the API data processing, I can make a few adjustments to make sure it parses the API response correctly once received.

Correct, my tool never failed to get the API data quickly, I'm using the same command I saw on the logs(miner_getstatdetail)

Update: I installed the latest updates for windows 1909 on windows update(security, servicing stack, cumulative and a .net 3.5 update but not edge), after about 10 hours the timeouts seem to be less common, one machine had 0, other 12 and other 16(6 consecutive timeouts once which triggered the offline detection that is set to 60 seconds now). The API was fully responsive all the time on all miners when requesting information from my computer with my tool (every 5 seconds never taking more than a few milliseconds).
I'll reformat one miner with latest windows to test when I can.

narousberg

legendary

Activity: 1753

Merit: 1007

Patrike, pls add for Bminer for algo Octopus param conflux, in ver. 16.3.4 all works good.

cylshan

newbie

Activity: 18

Merit: 0

Quote from: forato on November 04, 2020, 05:12:05 PM

I Know that we can use HIVEOS in free version with AM.

But i think it will be so nice to have an linux OS based on AM, I already read a lot of messages here with some user asking for it...

Nobody with skills here are interest in make an image for us?

Relevant for 4gb cards, on Windows 10 LTSC(LTSB), cards on TeamRedMiner and lolMiner fall off in random order. On Hive OS running AM TeamRedMiner works.
You can, of course, through the web interface Hive OS or RaveOS or others.
But it doesn't work that way, a lot of Stale Share, or something works crookedly, not stable

I did so if you correct something.
1.hiveos-0.6-156@200905
If on a USB flash drive then through balenaEtcher-Portable-1.5.109
2.hiveos-0.6-156@200905
If on SSD then via HDDRawCopy1.10Portable

Next, we connect to the rig via IP via
putty-0.73-ru-17-portable
The default login is user password. 1

and enter this:
sudo -s
ldconfig / hive / lib /
wget http://www.awesomeminer.com/download/setup/awesomeminer-remoteagent.tar.xz
tar xvJf awesomeminer-remoteagent.tar.xz
cd awesomeminer-remoteagent
./service-install.sh
./AwesomeMiner.RemoteAgent.Linux / setpassword = mypass

In the AwesomeMiner client
where is the host in IP
Next, put the Linux daw on the host
host = mypass

Connect and use

Or did I forget to write something here?
Add what I forgot to write or correct

Or a guide from "patrike".
Everything is step by step so that any person understands how it works.
Thanks !!!

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