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

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: haguiarm on June 27, 2019, 03:37:19 PM

Hello, I am presenting problems with my Awesome Miner since the last update. In the mining of NBMiner - Miniz to the minutes that is working I get that it is offline. Restarts by rule. But at the time it is lost time between reboots and offline. I already test with other miners and this error does not occur I have 1080ti.

Is the case that the mining software (NBMiner, Miniz) is crashing? No matter which algorithm is being used? Can you capture that with the Diagnostics button? Please note that the first time you run the Diagnostics it will only run the mining software for 30 seconds. You can then click the Advanced button to change it to 2 minutes and run again.

Quote from: ralf007at on June 28, 2019, 01:59:30 AM

Quote from: sxemini on June 28, 2019, 01:53:04 AM

Quote from: ralf007at on June 28, 2019, 12:35:18 AM

Hi Patrik,

another Problem with the new Version 6.5.8
i have to restart AM every morning because AM allocates all available RAM (over 13 GB - i have it running on a very fast PC with 16 GB Ram) after about 20 hours running. AM is not responding correct - i have to wait about 10 seconds for every click ...
after restart everything works fine again (AM needs 2.6 GB RAM) for about a day... then same procedure again...

BR Ralf

Then your AM installation is defect or with your windows is something wrong. I use AM on a windows pc with 4GB Ram and mining with CPU and GPU in backround, no impacts and it runs over month.

no - it's not defect... but maybe i have a few more miners than you? in the moment 733?! in former versions of AM i had no problems...

Hi Ralf,
I've sent you a message about this with some requests for more details. 2.6 GB for 733 miners sounds fine, but 13 GB does not. Let's investigate and resolve this.

Quote from: sxemini on June 28, 2019, 02:09:15 AM

And how you checked that your AM Installation is not defect? I think it is a problem with your PC, my Awesomeminer version use only 260mb RAM with 40 Miner and many rules.
A other Instance with 20 miner uses only 175mb Ram. So i can´t believe that 700 uses so much.
Maybe Patrike can say how much ram AM use per miner.

In general Awesome Miner doesn't consume that much more memory when adding a larger number of miners. Managed Miners will however consume more than External Miners and using features like mining history will increase the memory usage.

With 16 GB memory you should be able to run 20,000 ASIC miners.

sxemini

member

Activity: 1558

Merit: 69

And how you checked that your AM Installation is not defect? I think it is a problem with your PC, my Awesomeminer version use only 260mb RAM with 40 Miner and many rules.
A other Instance with 20 miner uses only 175mb Ram. So i can´t believe that 700 uses so much.
Maybe Patrike can say how much ram AM use per miner.

ralf007at

newbie

Activity: 52

Merit: 0

Quote from: sxemini on June 28, 2019, 01:53:04 AM

Quote from: ralf007at on June 28, 2019, 12:35:18 AM

Hi Patrik,

another Problem with the new Version 6.5.8
i have to restart AM every morning because AM allocates all available RAM (over 13 GB - i have it running on a very fast PC with 16 GB Ram) after about 20 hours running. AM is not responding correct - i have to wait about 10 seconds for every click ...
after restart everything works fine again (AM needs 2.6 GB RAM) for about a day... then same procedure again...

BR Ralf

Then your AM installation is defect or with your windows is something wrong. I use AM on a windows pc with 4GB Ram and mining with CPU and GPU in backround, no impacts and it runs over month.

no - it's not defect... but maybe i have a few more miners than you? in the moment 733?! in former versions of AM i had no problems...

sxemini

member

Activity: 1558

Merit: 69

Quote from: ralf007at on June 28, 2019, 12:35:18 AM

Hi Patrik,

another Problem with the new Version 6.5.8
i have to restart AM every morning because AM allocates all available RAM (over 13 GB - i have it running on a very fast PC with 16 GB Ram) after about 20 hours running. AM is not responding correct - i have to wait about 10 seconds for every click ...
after restart everything works fine again (AM needs 2.6 GB RAM) for about a day... then same procedure again...

BR Ralf

Then your AM installation is defect or with your windows is something wrong. I use AM on a windows pc with 4GB Ram and mining with CPU and GPU in backround, no impacts and it runs over month.

ralf007at

newbie

Activity: 52

Merit: 0

Hi Patrik,

another Problem with the new Version 6.5.8
i have to restart AM every morning because AM allocates all available RAM (over 13 GB - i have it running on a very fast PC with 16 GB Ram) after about 20 hours running. AM is not responding correct - i have to wait about 10 seconds for every click ...
after restart everything works fine again (AM needs 2.6 GB RAM) for about a day... then same procedure again...

BR Ralf

haguiarm

newbie

Activity: 6

Merit: 0

Hello, I am presenting problems with my Awesome Miner since the last update. In the mining of NBMiner - Miniz to the minutes that is working I get that it is offline. Restarts by rule. But at the time it is lost time between reboots and offline. I already test with other miners and this error does not occur I have 1080ti.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Mike_IG on June 27, 2019, 05:43:53 AM

Quote from: Asusrogmining on June 27, 2019, 02:16:54 AM

Hi, How can I update the miners to the latest version in Awesome miner. Usually Awesome miner alarms me that there is an available update, but I can see no update at this moment. Some miners have released updates such as Gminer 1.47, but latest version of Gminer in Awesome miner is 1.45. Please help me

Have you got both

check for new options automatically
check for development versions

ticked under options/general?

It's correct that you need to go for the development version in order to get to Gminer 1.47 at the moment.

This will however improve now when the feature 'Update mining software definitions' has been made available. This makes it possible to get mining software updates more frequently to all users, no matter if you run the public version or the development version.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Lunga Chung on June 27, 2019, 12:18:05 AM

pls add option to send keystrokes on console view and option to save OC profiles for the entire rig in 6.6 version

great work

Thanks for the feature suggestions - they are noted. It will unfortunately not be possible to include these in version 6.6 already as this release is planned for tomorrow and there are other feature to finalize first.

Saving the existing overclocking for a rig to a Clocking Group is likely to be implemented before the send key feature.

Mike_IG

member

Activity: 140

Merit: 12

Quote from: Asusrogmining on June 27, 2019, 02:16:54 AM

Hi, How can I update the miners to the latest version in Awesome miner. Usually Awesome miner alarms me that there is an available update, but I can see no update at this moment. Some miners have released updates such as Gminer 1.47, but latest version of Gminer in Awesome miner is 1.45. Please help me

Have you got both

check for new options automatically
check for development versions

ticked under options/general?

Asusrogmining

newbie

Activity: 24

Merit: 0

Hi, How can I update the miners to the latest version in Awesome miner. Usually Awesome miner alarms me that there is an available update, but I can see no update at this moment. Some miners have released updates such as Gminer 1.47, but latest version of Gminer in Awesome miner is 1.45. Please help me

Lunga Chung

member

Activity: 277

Merit: 23

pls add option to send keystrokes on console view and option to save OC profiles for the entire rig in 6.6 version

great work

patrike

legendary

Activity: 3346

Merit: 1094

Version 6.5.8 (Development preview of 6.6)

FPGA mining
- Blackminer F1 FPGA supported with temperature display
GPU mining
- Mining software definitions can be updated without upgrading the Awesome Miner or Remote Agent version
- GPU clocking groups can use exact GPU name mapping
- Added algorithm Lyra2z330
User interface
- Added additional coin images
- Description for Windows Uptime changed to System Uptime
Mining software
- CpuMiner-Opt 3.9.4
- SrbMiner 1.9.0
- Improved detection of when 'allcoins 1' needs to be added to the Claymore Ethereum miner command line
Corrections
- Correction to a timing issue where a miner group in Awesome Miner could be lost
- Correction to user defined mining software customization for Remote Agent on Linux

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.

Direct download links if needed:
https://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
https://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi

chuckinsuburbia

newbie

Activity: 11

Merit: 0

Quote from: patrike on June 25, 2019, 05:27:53 AM

Quote from: chuckinsuburbia on June 24, 2019, 09:04:36 AM

Quote from: patrike on June 24, 2019, 08:02:54 AM

Quote from: chuckinsuburbia on June 23, 2019, 12:44:42 PM

Quote from: patrike on June 21, 2019, 04:31:22 PM

Quote from: chuckinsuburbia on June 20, 2019, 07:05:23 PM

I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it?

Code:

6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"

Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon.

Unfortunately this still seems to be an issue in 6.5.7.

For this user defined Managed Software you added for CpuMiner - have you configured it to have the compatibility mode "Full" with CpuMinerOpt?

I might have identified one more issue specific to the Remote Agent on Linux here, but only related to custom algorithm parameters.

Yes, it is configured as Full (Command line and API). Sorry, I probably should have mentioned in my original post, but I saw some similar behavior with the Windows agent in 6.5.6 where it would not use the algorithm argument from the "Default command line argument" column, but would use an argument from the "User defined command line algorithm" column even if it was the same value. I worked around this by simply replicating all the default args as user defined args. But this workaround did not seem to work for the Linux agent. So this may be a combination of multiple issues.

I'm happy to provide any additional info you might need to track this down.

What I still could reproduce on Linux for 6.5.7 was that the "User defined command line" not being used correctly and I will of course correct that. It should however fallback to use the "Default command line argument" in 6.5.7 (didn't work in 6.5.6). Is it not even doing this fallback when you test it?

I'm away from my rigs for a day or so, but I will run through some more tests as soon as I can and post the results.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Ruso21 on June 25, 2019, 04:27:54 AM

like they said, deactivate the windows update and configure for mining.
you can't blame AM because of that, they are not windows developer and they are not going to create something to do "auto configure" just with 1 click.

Thanks for your comments. You are correct that Awesome Miner cannot do everything to secure that the mining environment is in good shape - but I'm actually open to suggestions about what Awesome Miner could do better in the future. It may not be a one-click that solves everything, but there might still be something to improve.

A feature to deploy some good configuration baseline for Windows could be a good feature to add in the future, where Awesome Miner can help you to disable Windows update, increase virtual memory if too low and so on.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on June 24, 2019, 10:39:56 PM

Quote from: patrike on June 24, 2019, 08:08:12 AM

I've heard about the forecasts of the warm weather in south Europe.

I do know that you have lowered your OC already because of the warm weather - can you please see if the people in your Telegram group consider that as well? It's quite often users start to experience GPU mining stability issues more frequently in May-June - I get those reports every year.

Two things you could try in Options dialog, Mining Settings:
1) Enable "Use Ctrl+C" as some mining software behave better with the enabled.
2) Consider increasing "Pause when profit switcher starts mining" and "Wait for process stop before terminating" a bit.

Point one that uses CTROL + C, where I activate that in AM, because I do not understand it in any other way. DOndende have to put it?

Please go to the Options dialog, Mining Settings section, where you will find this setting.

Have you been able to narrow down the issue with some troubleshooting - for example if you take one of your systems and only run it with one specific mining software and a single algorithm with no customization at all. Do you still get the same stability problems in that case?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Marvell2 on June 24, 2019, 10:53:24 AM

Bug - the gpu oc profiles by name , do not differentiate between say a 1660 and a 1660 Ti

Even throug the names are slightly different only the 1660 profile is applied

The name matching is based on partial matching right now. If you define to apply a profile to "1660" it will apply this to a GPU with the name "Geforce GTX 1660" although you didn't have to type the exact name.

The drawback is that it would also match "1660 Ti" as you point out, because of the partial matching. There will have to be a new matching rule like "GPU Name (exact)" for this scenario. I will look into that.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: chuckinsuburbia on June 24, 2019, 09:04:36 AM

Quote from: patrike on June 24, 2019, 08:02:54 AM

Quote from: chuckinsuburbia on June 23, 2019, 12:44:42 PM

Quote from: patrike on June 21, 2019, 04:31:22 PM

Quote from: chuckinsuburbia on June 20, 2019, 07:05:23 PM

I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it?

Code:

6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer  -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer"  -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"

Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon.

Unfortunately this still seems to be an issue in 6.5.7.

For this user defined Managed Software you added for CpuMiner - have you configured it to have the compatibility mode "Full" with CpuMinerOpt?

I might have identified one more issue specific to the Remote Agent on Linux here, but only related to custom algorithm parameters.

Yes, it is configured as Full (Command line and API). Sorry, I probably should have mentioned in my original post, but I saw some similar behavior with the Windows agent in 6.5.6 where it would not use the algorithm argument from the "Default command line argument" column, but would use an argument from the "User defined command line algorithm" column even if it was the same value. I worked around this by simply replicating all the default args as user defined args. But this workaround did not seem to work for the Linux agent. So this may be a combination of multiple issues.

I'm happy to provide any additional info you might need to track this down.

What I still could reproduce on Linux for 6.5.7 was that the "User defined command line" not being used correctly and I will of course correct that. It should however fallback to use the "Default command line argument" in 6.5.7 (didn't work in 6.5.6). Is it not even doing this fallback when you test it?

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: VParhom on June 24, 2019, 08:54:51 AM

Quote from: patrike on June 24, 2019, 08:21:12 AM

Thanks for the feedback.

It's correct that Linux on Remote Agent doesn't include all features and all mining software. For mining software it's about 20 of them supported and the Claymore miners should work fine.

Can you please let me know the main features you are missing? The goal is of course to continue improving Remote Agent on Linux so all feedback is of course welcome. Thanks!

Hi Patrik.
Thank you for paying attention to me.

I confirm that none of the Caymore`s miners work by default.
Only dances with a tambourine forced Dual miner to work and then only when I registered him completely the launch line in the profile.
With the rest so far did not suffer.

On the tab GPU there is no control of energy consumption.

Its utilites report from my test rig

Code:

========================ROCm System Management Interface========================
================================================================================
GPU  Temp   AvgPwr  SCLK     MCLK     Fan     Perf    PwrCap  SCLK OD  MCLK OD  GPU%
0    67.0c  80.0W   1140Mhz  2150Mhz  100.0%  manual  N/A     0%       0%       N/A
1    64.0c  83.0W   1140Mhz  2150Mhz  80.0%   manual  N/A     0%       0%       N/A
2    66.0c  82.0W   1140Mhz  2150Mhz  60.0%   manual  N/A     0%       0%       N/A
3    67.0c  88.0W   1140Mhz  2150Mhz  61.96%  manual  N/A     0%       0%       N/A
4    64.0c  80.0W   1140Mhz  2150Mhz  80.0%   manual  N/A     0%       0%       N/A
5    65.0c  84.0W   1140Mhz  2150Mhz  100.0%  manual  N/A     0%       0%       N/A
6    66.0c  77.0W   1140Mhz  2150Mhz  61.96%  manual  N/A     0%       0%       N/A
================================================================================
==============================End of ROCm SMI Log ==============================

I will be glad to provide all possible assistance in testing the Linux Agent, if necessary.

Sincerely, Vladimir.
p.s. I do not see the possibility to insert screenshots.

Remote Agent on Linux supports reporting GPU power usage, just like on Windows. On most Linux based mining systems, it should work out of the box. There are for example a number of users that run on other mining distributions like HiveOS, but just uses it as a Linux system with pre-installed drivers and everything - then installing Remote Agent on it and only use Awesome Miner. If you installed your own Linux system it might be something missing, so let's figure it out.

1) Could you please send me your Remote Agent log file (toolbar Tools -> Log File -> Remote Agent) for the Linux system where you don't see the power usage.
2) Please also use the Diagnostics button to start the Claymore miner and share the output with me.

Thanks!

Ruso21

member

Activity: 115

Merit: 12

Quote from: trucobit on June 24, 2019, 10:48:39 PM

Quote from: VParhom on June 24, 2019, 05:28:46 PM

Quote from: lthlspd on June 24, 2019, 03:57:49 PM

I've been using AwesomeMiner for a while and haven't had many issues but now I'm getting frequent crashes to the point where the PC just restarts. I'm having a hard time narrowing down which algorithms it's having trouble with. Is there an ideal place I should start to dig or does anyone have any advice?

Windows 10 Rig
5x 1070's

reduce overclocking and check risers
clean the oxide film from the contacts of the video card and risers

I already answer you. It's not the OC, nor are the risers. It is the damn windows and its updates, something has to improve in AM to control this.

You can not undermine and indicate "miner offline" and reboot rig. It also happens directly by mining, PLASH and reboot if notice. And this already reducing the OC a lot.

Insluso some miners of abnormal form occupy 100% of CPU, so much that it makes the system fail. I have seen several times already Intelibreeeze the remote AM program, hanging using more than 30% of CPU (depends on the model, this almost i3)

It's not me, it's not the other guy, there are many of us who are reporting these errors and it's not my first summer with AM undermining, I know what I'm talking about. Low OC, a lot of ventilation, air extractors, direct air to the platforms, but they can be at 50 degrees and suddenly reboot for no reason or stay in offline miner and restart by the rule.

like they said, deactivate the windows update and configure for mining.
you can't blame AM because of that, they are not windows developer and they are not going to create something to do "auto configure" just with 1 click.
here you have a tutorial...

https://www.youtube.com/watch?v=7Zsv-3QDzJQ

by the way, there are many possibilities for the crash, reboot, stopped, etc. I had that problem too....

VParhom

newbie

Activity: 6

Merit: 0

Quote from: trucobit on June 24, 2019, 10:48:39 PM

Quote from: VParhom on June 24, 2019, 05:28:46 PM

Quote from: lthlspd on June 24, 2019, 03:57:49 PM

I've been using AwesomeMiner for a while and haven't had many issues but now I'm getting frequent crashes to the point where the PC just restarts. I'm having a hard time narrowing down which algorithms it's having trouble with. Is there an ideal place I should start to dig or does anyone have any advice?

Windows 10 Rig
5x 1070's

reduce overclocking and check risers
clean the oxide film from the contacts of the video card and risers

I already answer you. It's not the OC, nor are the risers. It is the damn windows and its updates, something has to improve in AM to control this.

You can not undermine and indicate "miner offline" and reboot rig. It also happens directly by mining, PLASH and reboot if notice. And this already reducing the OC a lot.

Insluso some miners of abnormal form occupy 100% of CPU, so much that it makes the system fail. I have seen several times already Intelibreeeze the remote AM program, hanging using more than 30% of CPU (depends on the model, this almost i3)

It's not me, it's not the other guy, there are many of us who are reporting these errors and it's not my first summer with AM undermining, I know what I'm talking about. Low OC, a lot of ventilation, air extractors, direct air to the platforms, but they can be at 50 degrees and suddenly reboot for no reason or stay in offline miner and restart by the rule.

i have over 10 rigs on Win10 and for several years now I have not received updates from Microsoft on any of the rigs.
what am I doing wrong?

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