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

STSMiner

full member

Activity: 270

Merit: 115

Quote from: patrike on November 02, 2021, 05:32:45 AM

Quote from: STSMiner on November 01, 2021, 02:20:25 PM

Quote from: patrike on November 01, 2021, 08:02:58 AM

Quote from: STSMiner on October 30, 2021, 12:40:51 AM

Hi Patrike,

Can you fix MiniZ again for the next release, the commands issued to this miner are not working again.

Thanks.

Thanks for your report. Can you please share more details about the scenario where the command line arguments are incorrect? This will help me to track down any issues.

Hi Patrike,

Hope this helps...

The miner (Miniz) fails to start on first run and sometimes fails altogether, this is the report from the fail.

It's not limited to just one algo either with this issue on any pool.

Code:

ID: 1, PID: 15184
Start time: 11/1/2021 3:10:37 PM
Command line parameters:  --url Removed @kawpow.na.mine.zpool.ca:1325 -p c=BTC --pers auto --telemetry 0.0.0.0:4028

Hope you can find the issue here.

Thanks for the details. I noticed that Kawpow wasn't enabled for Miniz at all, so by default Awesome Miner shoudn't even have tried it. I've pushed an updated software definition for Miniz now, to ensure Kawpow is working.

For the other algorithms in your screenshot, they should be working fine and I suspect it could be crashes in the Miniz mining software. If possible, can you share a similar command line for any of those and I can confirm if Awesome Miner launches Miniz correctly in your setup?

This seems to have fixed the issue I was having here.

toptek12

member

Activity: 126

Merit: 10

Hi Patrike

could you add a coin called Raptoreum https://raptoreum.com/

MooChoo

newbie

Activity: 3

Merit: 0

Thanks for the help before!

How can I find out why a pool was temporarily disabled from a profit switching miner?
I used the links on the AwesomeMiner website to setup the Kawpow pool at 2Miners but the pool randomly seems to be disabled after a while and I cannot find the reason why.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: sxemini on November 02, 2021, 04:50:26 AM

is it possible to show the installed cuda version in summary tab? I think it is useful.

I will look into this.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: STSMiner on November 01, 2021, 02:20:25 PM

Quote from: patrike on November 01, 2021, 08:02:58 AM

Quote from: STSMiner on October 30, 2021, 12:40:51 AM

Hi Patrike,

Can you fix MiniZ again for the next release, the commands issued to this miner are not working again.

Thanks.

Thanks for your report. Can you please share more details about the scenario where the command line arguments are incorrect? This will help me to track down any issues.

Hi Patrike,

Hope this helps...

The miner (Miniz) fails to start on first run and sometimes fails altogether, this is the report from the fail.

It's not limited to just one algo either with this issue on any pool.

Code:

ID: 1, PID: 15184
Start time: 11/1/2021 3:10:37 PM
Command line parameters:  --url Removed @kawpow.na.mine.zpool.ca:1325 -p c=BTC --pers auto --telemetry 0.0.0.0:4028

Hope you can find the issue here.

Thanks for the details. I noticed that Kawpow wasn't enabled for Miniz at all, so by default Awesome Miner shoudn't even have tried it. I've pushed an updated software definition for Miniz now, to ensure Kawpow is working.

For the other algorithms in your screenshot, they should be working fine and I suspect it could be crashes in the Miniz mining software. If possible, can you share a similar command line for any of those and I can confirm if Awesome Miner launches Miniz correctly in your setup?

sxemini

member

Activity: 1558

Merit: 69

Quote from: STSMiner on November 01, 2021, 02:20:25 PM

Quote from: patrike on November 01, 2021, 08:02:58 AM

Quote from: STSMiner on October 30, 2021, 12:40:51 AM

Hi Patrike,

Can you fix MiniZ again for the next release, the commands issued to this miner are not working again.

Thanks.

Thanks for your report. Can you please share more details about the scenario where the command line arguments are incorrect? This will help me to track down any issues.

Hi Patrike,

Hope this helps...

The miner (Miniz) fails to start on first run and sometimes fails altogether, this is the report from the fail.

It's not limited to just one algo either with this issue on any pool.

Code:

ID: 1, PID: 15184
Start time: 11/1/2021 3:10:37 PM
Command line parameters:  --url Removed @kawpow.na.mine.zpool.ca:1325 -p c=BTC --pers auto --telemetry 0.0.0.0:4028

Hope you can find the issue here.

Can you please run the diagnostics for this miner? Maybe we can see an error or so.

@patrike

is it possible to show the installed cuda version in summary tab? I think it is useful.

STSMiner

full member

Activity: 270

Merit: 115

Quote from: patrike on November 01, 2021, 08:02:58 AM

Quote from: STSMiner on October 30, 2021, 12:40:51 AM

Hi Patrike,

Can you fix MiniZ again for the next release, the commands issued to this miner are not working again.

Thanks.

Thanks for your report. Can you please share more details about the scenario where the command line arguments are incorrect? This will help me to track down any issues.

Hi Patrike,

Hope this helps...

The miner (Miniz) fails to start on first run and sometimes fails altogether, this is the report from the fail.

It's not limited to just one algo either with this issue on any pool.

Code:

ID: 1, PID: 15184
Start time: 11/1/2021 3:10:37 PM
Command line parameters:  --url Removed @kawpow.na.mine.zpool.ca:1325 -p c=BTC --pers auto --telemetry 0.0.0.0:4028

Hope you can find the issue here.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: MooChoo on November 01, 2021, 04:28:52 AM

I believe it was trying on Prohashing and Nicehash

I agree with the point made by sxemini above. When mining on for example on Nicehash the actual coin you are mining can change over time and for this reason a 4 GB GPU may work for some time, but not all the time.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: STSMiner on October 30, 2021, 12:40:51 AM

Hi Patrike,

Can you fix MiniZ again for the next release, the commands issued to this miner are not working again.

Thanks.

Thanks for your report. Can you please share more details about the scenario where the command line arguments are incorrect? This will help me to track down any issues.

MooChoo

newbie

Activity: 3

Merit: 0

I believe it was trying on Prohashing and Nicehash

sxemini

member

Activity: 1558

Merit: 69

Quote from: MooChoo on November 01, 2021, 02:40:14 AM

Hoping someone might have an idea whats going on.

Bought the premium version today so I could control the family computers from my machine.
Moved from the standard free install to the agent install on one machine which has a GTX1650 4GB in it.

Setup a profit miner and created a new Nvidia Profile for it and ran some benchmarks.
Noticed it was getting around 17MH/s on Ethereum with NBMiner in the benchmark.

When I was finished with benchmarking, I tried to start the Mining and it defaulted to Ethereum but would continually fail as it was running out of memory.
Tried a few different miners and even tried setting some of those miners to the 4GB Card mode. On 4GB mode, it says its running but at 0.00MH/s.
Tested Argon2d-4096 and its running fine without issue.

Unsure why Ethereum would benchmark fine but then not mine at all when not benchmarking?

Benchmark run on what pool? I think on some profit switching pools, so you need less than 4GB, but for Mining ETH you need over 4GB, because the DAG must fit in the VRam of your card.

MooChoo

newbie

Activity: 3

Merit: 0

Hoping someone might have an idea whats going on.

Bought the premium version today so I could control the family computers from my machine.
Moved from the standard free install to the agent install on one machine which has a GTX1650 4GB in it.

Setup a profit miner and created a new Nvidia Profile for it and ran some benchmarks.
Noticed it was getting around 17MH/s on Ethereum with NBMiner in the benchmark.

When I was finished with benchmarking, I tried to start the Mining and it defaulted to Ethereum but would continually fail as it was running out of memory.
Tried a few different miners and even tried setting some of those miners to the 4GB Card mode. On 4GB mode, it says its running but at 0.00MH/s.
Tested Argon2d-4096 and its running fine without issue.

Unsure why Ethereum would benchmark fine but then not mine at all when not benchmarking?

STSMiner

full member

Activity: 270

Merit: 115

Hi Patrike,

Can you fix MiniZ again for the next release, the commands issued to this miner are not working again.

Thanks.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: narousberg on October 28, 2021, 06:36:45 PM

Hi Patrike, now is imposible to use benchmark function with T-Rex miner. Benchmark module not recive a hashrate data.

Thanks for the report. I wasn't able to reproduce when I just tried but I will look into this.

narousberg

legendary

Activity: 1753

Merit: 1007

Hi Patrike, now is imposible to use benchmark function with T-Rex miner. Benchmark module not recive a hashrate data.

nordmann666

member

Activity: 363

Merit: 16

Quote from: patrike on October 28, 2021, 09:15:52 AM

Quote from: nordmann666 on October 28, 2021, 06:58:58 AM

Quote from: patrike on October 28, 2021, 06:36:08 AM

Quote from: nordmann666 on October 28, 2021, 06:18:09 AM

after the last (or maybe last 2 updates) my network scan shows me allready added miners again as new miners
there are a handfull "existing" miners and he found many many miners that if i add them, i find them as duplicate in the "find miners" tab via IP

The network scan can be configured to either include only new or all miners. Can you verify this via the "Settings" button on the Network scan page, where you will find "Scan for new miners only"?

We do have another network scan correction in the pipeline, but that's related to when you use a cloud connected Remote Proxy.

it is set to only new - and 7 miners out of 87 external are ignored cause existing

Thanks for the details. Can you please verify if the changes to the network scan in the new v9.0.4 resolves this?

thanks for update and yes...it is fixed for me

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: nordmann666 on October 28, 2021, 06:58:58 AM

Quote from: patrike on October 28, 2021, 06:36:08 AM

Quote from: nordmann666 on October 28, 2021, 06:18:09 AM

after the last (or maybe last 2 updates) my network scan shows me allready added miners again as new miners
there are a handfull "existing" miners and he found many many miners that if i add them, i find them as duplicate in the "find miners" tab via IP

The network scan can be configured to either include only new or all miners. Can you verify this via the "Settings" button on the Network scan page, where you will find "Scan for new miners only"?

We do have another network scan correction in the pipeline, but that's related to when you use a cloud connected Remote Proxy.

it is set to only new - and 7 miners out of 87 external are ignored cause existing

Thanks for the details. Can you please verify if the changes to the network scan in the new v9.0.4 resolves this?

patrike

legendary

Activity: 3346

Merit: 1094

Awesome Miner version 9.0.4

User interface
- Improved text colors for dark mode
Mining software
- NbMiner 39.6
- TeamBlackMiner 1.21
Corrections
- Correction to duplication issue with network scan and auto miner discovery

nordmann666

member

Activity: 363

Merit: 16

Quote from: patrike on October 28, 2021, 06:36:08 AM

Quote from: nordmann666 on October 28, 2021, 06:18:09 AM

after the last (or maybe last 2 updates) my network scan shows me allready added miners again as new miners
there are a handfull "existing" miners and he found many many miners that if i add them, i find them as duplicate in the "find miners" tab via IP

The network scan can be configured to either include only new or all miners. Can you verify this via the "Settings" button on the Network scan page, where you will find "Scan for new miners only"?

We do have another network scan correction in the pipeline, but that's related to when you use a cloud connected Remote Proxy.

it is set to only new - and 7 miners out of 87 external are ignored cause existing

sxemini

member

Activity: 1558

Merit: 69

Quote from: patrike on October 28, 2021, 06:36:08 AM

Quote from: nordmann666 on October 28, 2021, 06:18:09 AM

after the last (or maybe last 2 updates) my network scan shows me allready added miners again as new miners
there are a handfull "existing" miners and he found many many miners that if i add them, i find them as duplicate in the "find miners" tab via IP

The network scan can be configured to either include only new or all miners. Can you verify this via the "Settings" button on the Network scan page, where you will find "Scan for new miners only"?

We do have another network scan correction in the pipeline, but that's related to when you use a cloud connected Remote Proxy.

I can verify the same problem, Scan for new miners only is checked. But it only happens if we scan for external miners.

Scan for Awesomeminer Remote Agents works normal.

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