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

patrike

legendary

Activity: 3556

Merit: 1095

Is there any more description than this https://support.awesomeminer.com/support/solutions/articles/35000188785-dual-mining-with-t-rex-gminer-and-lolminer on Dual mining for Managed Profit Miner?
Is there even more functionality than just eth + some other coin? Or some easy way to benchmark the different dual mining for auto-switching?

Remember in the claymore days this worked in Awesome Miner. But have not used auto switch and dual in a while.
Manually settings a miner to dual mine seems to work fine. But the auto part I do not get.

Thanks for your questions. The profit switcher is currently limited to EtHash + secondary coin but we have received a number of requests to improve this and make it more flexible. The plan is to improve the profit switcher to consider all available combinations for dual mining.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: slysir on November 12, 2022, 11:19:59 AM

When trying to run SRBMiner (cpu miner) the _awesome-start.bat_ file has by default included '-p minpayout=20' into the command line parameters. This causes SRBMiner to exit with error " incorrect configuration".

If i remove the parameter '-p minpayout=20' from the bat file and then in terminal run _awesome-start.bat_ then SRBMiner runs.

However the next time i auto start the miner the unwanted parameter is automatically re-inserted into the _awesome-start.bat_.

How to permanently remove this unwanted parameter!

Hi,
Awesome Miner doesn't add any "minpayout" parameter unless you manually configure it do to so. Can you please check the Properties of both your Managed Miner and your Pool to ensure you didn't add this as a custom command line argument. If you are using the profit switcher, please right click on the miner and select Edit Profit Profile and check here as well.

slysir

newbie

Activity: 52

Merit: 0

When trying to run SRBMiner (cpu miner) the _awesome-start.bat_ file has by default included '-p minpayout=20' into the command line parameters. This causes SRBMiner to exit with error " incorrect configuration".

If i remove the parameter '-p minpayout=20' from the bat file and then in terminal run _awesome-start.bat_ then SRBMiner runs.

However the next time i auto start the miner the unwanted parameter is automatically re-inserted into the _awesome-start.bat_.

How to permanently remove this unwanted parameter!

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: narousberg on November 10, 2022, 11:34:58 AM

Quote from: patrike on November 10, 2022, 10:20:41 AM

Quote from: narousberg on November 10, 2022, 06:01:15 AM

Hi Patrike
if mining rig is overclocked with "sudo nvidia-smi -lmc 810" in batch command "before starting" section, in situation when mining process has crashed, this overclocking settings still active and need to be reseted manualy or over rig reboot. My question is, have AM any sollution how to catch this crash situation and execute other "nvidia-smi" command?

Regards

Hello. Just like you have "Before starting" you should be able to make use of "After stopping" as well in order to execute some reset command. The "After stopping" commands will be executed in case you stop the mining software and also in the case when the mining software simply crash by itself.

i filled "After stopping" with reset commands, but in case of crash, this commands will not be executed.

It should be possible to verify the actions taken by Remote Agent when this happens. Please check the Remote Agent log file and search for "process not running". This is when Remote Agent detected the crash (missing mining software process). A few lines below you should be able to see "Executing batch commands" where it's states your reset commands. Can you please check if you see this information in the log file?

narousberg

legendary

Activity: 1754

Merit: 1007

Quote from: patrike on November 10, 2022, 10:20:41 AM

Quote from: narousberg on November 10, 2022, 06:01:15 AM

Hi Patrike
if mining rig is overclocked with "sudo nvidia-smi -lmc 810" in batch command "before starting" section, in situation when mining process has crashed, this overclocking settings still active and need to be reseted manualy or over rig reboot. My question is, have AM any sollution how to catch this crash situation and execute other "nvidia-smi" command?

Regards

Hello. Just like you have "Before starting" you should be able to make use of "After stopping" as well in order to execute some reset command. The "After stopping" commands will be executed in case you stop the mining software and also in the case when the mining software simply crash by itself.

i filled "After stopping" with reset commands, but in case of crash, this commands will not be executed.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: JimBrown462 on November 10, 2022, 07:19:46 AM

Quote from: patrike on November 09, 2022, 09:20:51 AM

Thanks for the feedback Jim. Your Awesome Miner will soon pick up the Nicehash Kaspa pool and list it.

Got it. Thanks!

Bit of an issue though, could not benchmark it initially. It would run fine with manually entered hashrate and power without a benchmark using this command line:

Code:

C:\Users\[user]\AppData\Local\AwesomeMiner\gminer_3_12_windows64_1\miner.exe --opencl 0 -a kas -s kheavyhash.auto.nicehash.com -n 9200 -u [walletAddress].Desktop -p x --pers auto -w 0 --api 4028

However, according to the log, it was trying to benchmark Kaspa as a dual algorithm benchmark with daggerhashimoto using this command line:

Code:

C:\Users\[user]\AppData\Local\AwesomeMiner\gminer_3_12_windows64_1\miner.exe --opencl 0 -a kas -d 0 -s daggerhashimoto.auto.nicehash.com -u [walletAddress].Desktop -p x --pers auto -w 0 -n 9200 --proto stratum --dalgo kas --dserver stratum+tcp://kheavyhash.auto.nicehash.com:9200 --duser [walletAddress] --dworker Desktop --dpass x --dproto stratum --api 4028

I had to re-enable Ethereum in the Profitablility -> Algorithms list, then disable it in the Managed Miners -> Managed Software -> GMiner algorithm list, then disable it again in the Profitablility -> Algorithms list. After that, it benchmarked normally using the above command line.

I had never attempted to set up dual mining before, so not sure why it was trying to benchmark it that way.

All of the above is FYI. ;-)

Thanks,
...jim

Thanks for all feedback. It looks like the benchmark feature favors dual mining in a way that causes some issues. I will look for improvements here.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: narousberg on November 10, 2022, 06:01:15 AM

Hi Patrike
if mining rig is overclocked with "sudo nvidia-smi -lmc 810" in batch command "before starting" section, in situation when mining process has crashed, this overclocking settings still active and need to be reseted manualy or over rig reboot. My question is, have AM any sollution how to catch this crash situation and execute other "nvidia-smi" command?

Regards

Hello. Just like you have "Before starting" you should be able to make use of "After stopping" as well in order to execute some reset command. The "After stopping" commands will be executed in case you stop the mining software and also in the case when the mining software simply crash by itself.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: sxemini on November 09, 2022, 11:33:18 AM

When Intel ARC support? I can´t choose this cards. Nanominer and BZminer support it.

Intel Arc will be supported at some point and I will get one of these soon in order to investigate.

JimBrown462

newbie

Activity: 59

Merit: 0

Quote from: patrike on November 09, 2022, 09:20:51 AM

Thanks for the feedback Jim. Your Awesome Miner will soon pick up the Nicehash Kaspa pool and list it.

Got it. Thanks!

Bit of an issue though, could not benchmark it initially. It would run fine with manually entered hashrate and power without a benchmark using this command line:

Code:

C:\Users\[user]\AppData\Local\AwesomeMiner\gminer_3_12_windows64_1\miner.exe --opencl 0 -a kas -s kheavyhash.auto.nicehash.com -n 9200 -u [walletAddress].Desktop -p x --pers auto -w 0 --api 4028

However, according to the log, it was trying to benchmark Kaspa as a dual algorithm benchmark with daggerhashimoto using this command line:

Code:

C:\Users\[user]\AppData\Local\AwesomeMiner\gminer_3_12_windows64_1\miner.exe --opencl 0 -a kas -d 0 -s daggerhashimoto.auto.nicehash.com -u [walletAddress].Desktop -p x --pers auto -w 0 -n 9200 --proto stratum --dalgo kas --dserver stratum+tcp://kheavyhash.auto.nicehash.com:9200 --duser [walletAddress] --dworker Desktop --dpass x --dproto stratum --api 4028

I had to re-enable Ethereum in the Profitablility -> Algorithms list, then disable it in the Managed Miners -> Managed Software -> GMiner algorithm list, then disable it again in the Profitablility -> Algorithms list. After that, it benchmarked normally using the above command line.

I had never attempted to set up dual mining before, so not sure why it was trying to benchmark it that way.

All of the above is FYI. ;-)

Thanks,
...jim

narousberg

legendary

Activity: 1754

Merit: 1007

Hi Patrike
if mining rig is overclocked with "sudo nvidia-smi -lmc 810" in batch command "before starting" section, in situation when mining process has crashed, this overclocking settings still active and need to be reseted manualy or over rig reboot. My question is, have AM any sollution how to catch this crash situation and execute other "nvidia-smi" command?

Regards

sxemini

member

Activity: 1558

Merit: 69

When Intel ARC support? I can´t choose this cards. Nanominer and BZminer support it.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: JimBrown462 on November 09, 2022, 07:16:56 AM

Hi Patrike,

Nicehash has added a new algorithm. I presume it will be added to Awesome Miner in due course?

https://www.nicehash.com/blog/post/kaspa-kheavyhash-is-now-supported-on-nicehash

Thanks!
...jim

Thanks for the feedback Jim. Your Awesome Miner will soon pick up the Nicehash Kaspa pool and list it.

patrike

legendary

Activity: 3556

Merit: 1095

Awesome Miner version 9.7.6

Features
- Rule action for Firmware Mining Profile can now configure the mining fee region
- Property filter for Device Count (number of hash boards or GPUs)
- Include ASIC fan speed in the miner part of the Awesome Miner HTTP API
- Miner status filter for finding disabled miners. The existing filter for finding offline miners will no longer show disabled miners.
User interface
- Tab visiblility configurable in the Windows application, via the Appearance toolbar
- Configurable permission for User Interface adjustments
Mining software
- BzMiner 12.1.0
- WildRig Miner 0.33.6
Corrections
- Correction to Whatsminer monitoring of hash rate in case the miner ends up in a certain state where it produces 0 H/s
- Correction to SrbMiner-Multi dual mining pool password

JimBrown462

newbie

Activity: 59

Merit: 0

Hi Patrike,

Nicehash has added a new algorithm. I presume it will be added to Awesome Miner in due course?

https://www.nicehash.com/blog/post/kaspa-kheavyhash-is-now-supported-on-nicehash

Thanks!
...jim

ojmalik

newbie

Activity: 40

Merit: 0

Quote from: patrike on November 04, 2022, 07:14:04 AM

I will review this scenario. On more recent OS versions, Awesome Miner can successfully connect to and get the details from Nicehash without this error.

When you load this link with Chrome, can you please press F12 to open the Developer Tools? Go to the Security tab and see the "Connection" section. This one will state the TLS version. It could however be that Google tries to connect with QUIC.

You are correct, it was showing QUIC. I review the log file again to look for other such errors, and noticed it would not connect to prohashing (https://prohashing.com/api/v1/status) either, with the same error. checked in developer tools and it is connecting there with TLS 1.3.

I ran both sites (prohashing.com and api2.nicehash.com) through Qualys SSL (https://www.ssllabs.com/ssltest/) test just to be sure they support TLS 1.2, which they do.

I have since upgraded the OS to 2019 and the problem seems to be resolved, which is strange, since 2019 only supports up to tls 1.2, same as 2012r2. Could be a user agent string problem perhaps. Thanks again for your help, problem solved for now!

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: ojmalik on November 03, 2022, 05:09:19 PM

Hello Patrike, hoping you can help with Awesome Miner not updating Nicehash profitability properly. I'm not sure when it started, but the profitability on NiceHash has not been updating like the other pools. I first noticed this after Eth merge when we started looking for other coins to mine. Nicehash has been stuck on the same profitibility stats since at least then. I've found entries like this in the log file:

[089] [E]Failed to download string from: https://api2.nicehash.com/main/api/v2/public/stats/global/24h/
System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.

If I browse to that address with Chrome on the same machine, I do receive a valid response. OS is Windows Server 2012 R2, and TLS 1.2 is enabled in SCHANNEL registry settings.

Any insight you could provide?

I will review this scenario. On more recent OS versions, Awesome Miner can successfully connect to and get the details from Nicehash without this error.

When you load this link with Chrome, can you please press F12 to open the Developer Tools? Go to the Security tab and see the "Connection" section. This one will state the TLS version. It could however be that Google tries to connect with QUIC.

ojmalik

newbie

Activity: 40

Merit: 0

Hello Patrike, hoping you can help with Awesome Miner not updating Nicehash profitability properly. I'm not sure when it started, but the profitability on NiceHash has not been updating like the other pools. I first noticed this after Eth merge when we started looking for other coins to mine. Nicehash has been stuck on the same profitibility stats since at least then. I've found entries like this in the log file:

[089] [E]Failed to download string from: https://api2.nicehash.com/main/api/v2/public/stats/global/24h/
System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.

If I browse to that address with Chrome on the same machine, I do receive a valid response. OS is Windows Server 2012 R2, and TLS 1.2 is enabled in SCHANNEL registry settings.

Any insight you could provide?

patrike

legendary

Activity: 3556

Merit: 1095

Awesome Miner version 9.7.5

Features
- Improved web dashboard flexibility by allowing configuration of which information to display
- Rule action for updating ASIC firmware
Mining software
- Gminer 3.12
- SrbMiner-Multi 1.1.1
- WildRig Miner 0.33.5
Corrections
- Correction to rule scenario where global triggers are used in combination with other triggers in order to include relevant miner details in notification messages

patrike

legendary

Activity: 3556

Merit: 1095

Awesome Miner version 9.7.4

ASIC mining
- iPollo V1 ASIC miner integration improved with temperature reading
Mining software
- CpuMiner-Opt 3.20.3
- Gminer 3.11
- Miniz Miner 1.9z4
- NoncerPro 3.4.1
- TeamBlackMiner 1.72
- XmRig 6.18.1
Corrections
- Correction to display of dashboard page in web
- Correction to pool display for BzMiner

sxemini

member

Activity: 1558

Merit: 69

Quote from: GoRdiE on October 27, 2022, 07:15:51 AM

Quote from: patrike on October 26, 2022, 10:00:42 PM

Quote from: GoRdiE on October 26, 2022, 05:32:57 AM

hi Patrike

Could it be that in rules->Actions there was an action to ignore the current pool when a condition were met? I want to set a rule that when a miner's profit or renevue is determined, it locks the current pool for a certain time

Hi and thanks for your request.

Is this a profit switching miner (Managed Profit Miner) where you don't want the profit switcher to automatically change the pool if it finds anything more profitable?

If the purpose is simply to reduce the number of switches you can define two thresholds in the Options dialog, Profit switching section. You can have one "Switching interval" and one "Additional switching interval", where you can use them in combination with a threshold to not switch unless there is something significantly more profitable available.

Thanks for your answer. The idea arises because many of us are mining at a loss. The idea is to have a kind of Revenue Profit Switcher. This does not exist. I know that if we put the expense=0 we have it, but I am also interested in AM telling me my expense/income. It is only a way to discriminate the low income pools within the current profit switcher system. Or have the option of instead of profit switcher a revenue switch per miner

You can set different profit profiles (with different pools) and you can switch to it via rules if the revenue is down. You can switch back after a certain time. All is possible, but you must be creative.

And you have an profit switcher per miner if you want. If you configure it right the profit switcher is a "revenue switcher" but i don´t understand what is the different between both for your?

Mining at a loss is nonsense - buy coins instead of mining at a loss - than you have no loss Wink

If you really mining at a loss to hold the coins - revenue switching also senseless - you never know what happen in 1 or 2 years.
Or do you think it change much if you change your mining coin several times a day when you sell it in 2 years?
You mine for example 5 different coins via profitswitching - in 2 years 1 coin go up 10%, the other 20%..... you really think it doesn´t matter that you make 20 cent more today on this coin and tomorrow on the other coin?

So i don´t see the point of the revenue switch at the moment. Profitswitching is only good if you sell it in shorttime.

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