Author

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

legendary
Activity: 3346
Merit: 1094
Anyone else have Awesome Miner not report revenue?

As you can see here:

It's also not just nicehash, I have seen miningpoolhub also report $0 for some algos.

Any ideas? it's ruining all my stats Sad
Please check the following:

1) For nicehash, please check Options dialog, Online Services section, and make sure the "Nicehash domain matching field" uses the default value nicehash.com and nothing else.
2) For the entries on this page, also check that the profit factor is set to 1 (or at least not 0).
3) Are the correct information showing up on the Online Services tab in Awesome Miner?
legendary
Activity: 3346
Merit: 1094
Anychance you can add the cuda 9.2 version of Enemy Miner instead of only the Cuda 9.1. Supposedly Cuda 9.2 version is slightly faster.

Just change the url in managed software

Well i could download it too and upload to all my rigs, but was hoping it could be implemented so i dont have to do it everytime.
The reason why Cuda 9.1 is included by default for the moment is that all users are not running with the latest drivers. In the past when Ccminer changed to a later Cuda version, I had quite a number of upset e-mail messages about that the mining didn't start (due to old GPU drivers).

The plan is of course to move to the Cuda 9.2 versions later on.

The most recent version of Awesome Miner is presenting the GPU driver versions on the Summary tab, and I've been thinking of using this information to give warnings if too old GPU drivers are being used.

Thanks for the feedback!
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 5.4.5 (Development preview of 5.5) is now available. It's a smaller update to the previous development version that address issues related to:
- Configuration not received correctly for Remote Agent on Linux
- Execution of rules based on failed process trigger corrected, to prevent blocking user interface updates
- T-Rex miner launched again (a second instance) after restarting Remote Agent


When I try to upgrade the linux remote agent, it fails:
Thanks for your comments on this. I found out that the permission on the file AwesomeMiner.RemoteAgent.Linux wasn't set with executable flag after the upgrade. If you manually do chmod 755 on this file it should start fine after the upgrade.

Please note that even if I correct this upgrade issue in the next release, it will not be until you upgrade to the next-next release the new upgrade changes will be used.
legendary
Activity: 3346
Merit: 1094
Was trying to set it for the Managed Software but it would not take. Going into each device profile and having to add it is not ideal, but can work for now.

It runs, but still does not coy the benchmark result back to the test page for saving to the profile. Hum ...

Thank you.
Is the scenario that the mining software window is opened and that you can see that it's hashing, but once completed, the hashrate isn't showing up in the benchmark window?
Correct.
Can you please send me your log file by mail and indicate the time of the issue. I can then review the command line Awesome Miner used to launch the mining software in benchmark mode to see if there are any issues there.

Was it only sgminer benchmark that didn't work as expected or was it any other mining software as well that failed? Is Sgminer working fine when when you use it outside the benchmark, at show up with hashrate in the list of miners in Awesome Miner?
member
Activity: 273
Merit: 12
Anychance you can add the cuda 9.2 version of Enemy Miner instead of only the Cuda 9.1. Supposedly Cuda 9.2 version is slightly faster.

Just change the url in managed software

Well i could download it too and upload to all my rigs, but was hoping it could be implemented so i dont have to do it everytime.
newbie
Activity: 13
Merit: 0
Anychance you can add the cuda 9.2 version of Enemy Miner instead of only the Cuda 9.1. Supposedly Cuda 9.2 version is slightly faster.

Just change the url in managed software
member
Activity: 273
Merit: 12
Anychance you can add the cuda 9.2 version of Enemy Miner instead of only the Cuda 9.1. Supposedly Cuda 9.2 version is slightly faster.
newbie
Activity: 13
Merit: 0
Anyone else have Awesome Miner not report revenue?

As you can see here:
http://stats.finnsk3.com/am.png

It's also not just nicehash, I have seen miningpoolhub also report $0 for some algos.

Any ideas? it's ruining all my stats Sad
newbie
Activity: 32
Merit: 0
Updated miners Smiley

Z-Enemy 1.18
https://bitcointalksearch.org/topic/zealotenemy-z-enemy-nvidia-gpu-miner-ver262-kawpow-ravencoin-3378390

- Major performance improvements: 10-15% for Xevan (+ fixed reduced hashrate issue from 1.17)
- Minor performance improvements for other algos
- Stability improvements for XDNA

CryptoDredge 0.9.1
https://github.com/technobyl/CryptoDredge/releases/

New CryptoNightHaven algorithm
Fix issue related to many rejected shares on NiceHash pool when used CryptoNight-like algorithms

It would be nice to get these updates in for 4.6, but also could Cryptonight be enabled for CryptoDredge? Right now it won't show up in the benchmark for several algos that Dredge (and other miners, iirc) support.
newbie
Activity: 36
Merit: 0
Updated miners Smiley

Z-Enemy 1.18
https://bitcointalksearch.org/topic/zealotenemy-z-enemy-nvidia-gpu-miner-ver262-kawpow-ravencoin-3378390

- Major performance improvements: 10-15% for Xevan (+ fixed reduced hashrate issue from 1.17)
- Minor performance improvements for other algos
- Stability improvements for XDNA

CryptoDredge 0.9.1
https://github.com/technobyl/CryptoDredge/releases/

New CryptoNightHaven algorithm
Fix issue related to many rejected shares on NiceHash pool when used CryptoNight-like algorithms
newbie
Activity: 59
Merit: 0
Awesome Miner version 5.4.5 (Development preview of 5.5) is now available. It's a smaller update to the previous development version that address issues related to:
- Configuration not received correctly for Remote Agent on Linux
- Execution of rules based on failed process trigger corrected, to prevent blocking user interface updates
- T-Rex miner launched again (a second instance) after restarting Remote Agent


Can confirm that T-Rex was found already mining after update.

...jim
newbie
Activity: 72
Merit: 0
The problem with the calculators is that they are based on what you are getting right now this instant. So if you are just an individual mining on a small scale you probably can't take advantage of the swings up before they swing back down and you've wasted time mining at lower profit.

I'd pick 3 or 4 coins you think are good and set up the auto switch to only do those ones.
newbie
Activity: 45
Merit: 0
Awesome Miner version 5.4.5 (Development preview of 5.5) is now available. It's a smaller update to the previous development version that address issues related to:
- Configuration not received correctly for Remote Agent on Linux
- Execution of rules based on failed process trigger corrected, to prevent blocking user interface updates
- T-Rex miner launched again (a second instance) after restarting Remote Agent


When I try to upgrade the linux remote agent, it fails:

Sep 04 18:30:50 worker systemd[1]: awesome.service: Service hold-off time over, scheduling restart.
Sep 04 18:30:50 worker systemd[1]: Stopped Awesome Miner Remote Agent.
Sep 04 18:30:50 worker systemd[1]: Started Awesome Miner Remote Agent.
Sep 04 18:30:50 worker systemd[1]: awesome.service: Main process exited, code=exited, status=203/EXEC
Sep 04 18:30:50 worker systemd[1]: awesome.service: Unit entered failed state.
Sep 04 18:30:50 worker systemd[1]: awesome.service: Failed with result 'exit-code'.
Sep 04 18:30:50 worker systemd[1]: awesome.service: Service hold-off time over, scheduling restart.
Sep 04 18:30:50 worker systemd[1]: Stopped Awesome Miner Remote Agent.
Sep 04 18:30:50 worker systemd[1]: awesome.service: Start request repeated too quickly.
Sep 04 18:30:50 worker systemd[1]: Failed to start Awesome Miner Remote Agent.
newbie
Activity: 49
Merit: 0
Was trying to set it for the Managed Software but it would not take. Going into each device profile and having to add it is not ideal, but can work for now.

It runs, but still does not coy the benchmark result back to the test page for saving to the profile. Hum ...

Thank you.
Is the scenario that the mining software window is opened and that you can see that it's hashing, but once completed, the hashrate isn't showing up in the benchmark window?
Correct.
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 5.4.5 (Development preview of 5.5) is now available. It's a smaller update to the previous development version that address issues related to:
- Configuration not received correctly for Remote Agent on Linux
- Execution of rules based on failed process trigger corrected, to prevent blocking user interface updates
- T-Rex miner launched again (a second instance) after restarting Remote Agent
legendary
Activity: 3346
Merit: 1094
umm, you can add that to the profit profile specifically for sgminer (and forks)

also, you need to specify the correct number, 0, 1 or 2 for the --gpu-platform, it's rig specific.

check sgminer --help for details.

***
worst come to worst, just use command line and mine to someone else's address using examples for starters, there you should see all the error messages in the console. of course, if you are familiar with command line, then just replace the command, addresses as you see fit. Else, consider it a tiny donation.
Was trying to set it for the Managed Software but it would not take. Going into each device profile and having to add it is not ideal, but can work for now.

It runs, but still does not coy the benchmark result back to the test page for saving to the profile. Hum ...

Thank you.
Is the scenario that the mining software window is opened and that you can see that it's hashing, but once completed, the hashrate isn't showing up in the benchmark window?
legendary
Activity: 3346
Merit: 1094
Hello
There is something wrong with T-Rex miner when i try to use it throug "managed templates" and definied pool. It alwasy eats first two letters from pool adress.
I tried to add random two letters to push through the correct adress but it's not connectting too. The problem exists all the time when i started use your software, im unable to use T-Rex through Awsomeminer. Other miner like z-enemy, ccminer works fine.
I wasn't able to reproduce this issue, but I would like to learn more as it be a very specific scenario where this doesn't work correctly.

Can you share the diagnostics output (the Diagnostics button in the toolbar) where the first two letters are missing? Thanks!
legendary
Activity: 3346
Merit: 1094
I'm really eager to test out the linux remote agent. I'd like to use as stripped down a distro as possible, basically just the bare minimum needed to mine in linux via command line, preferably off of a USB stick.

Can anyone recommend a pre-packaged distro with the bare minimum required for mining, specifically the drivers? Or a up to date guide that outlines the bare minimum steps to making ubuntu server mining ready?

Also, are there any limitations to the current linux agent aside from the mining software that can be automatically downloaded? Can we still upload custom software? What if any methods are available to control GPU clocks?
The list of supported mining software for automatic download is currently limited to the list you can find on the page below:
https://support.awesomeminer.com/support/solutions/articles/35000086210-remote-agent-for-linux-beta-

You will also able to upload your own software, like you do on Windows.

GPU clocking is not yet supported, but will be in the future. Right now you need to manually define any commands to be running before starting a miner if you want to do clocking.

I'm not too experienced in running mining on Linux myself, but I had some other users running early tests of Remote Agent on Linux on HiveOS, where they simply disabled the HiveOS mining and installed Awesome Miner Remote Agent instead.

So my initial test with the linux agent was a semi-fail. I got AM to recognize the agent, but it refuses to mine.
The settings wasn't send correctly to the Remote Agent in this scenario. This will be corrected in the next update that soon will be made available.
legendary
Activity: 3346
Merit: 1094
Just wanted to let you know that I've isolated the UI freezing problem to a scenario where I have a remote client that I am connecting to via port forwarding, and their internet connectivity is spotty. I imagine the freeze is happening when the thread is hanging because it is expecting a timely response from the remote client and not getting it. Is there a setting already in place to deal with such a scenario?
Thanks for the update on this. I will try to reproduce the scenario.

I would actually recommend you to check the setting for the connection timeout. Although it might sound attractive to increase the timeout to wait longer, in this case I think we should try to make it fail faster with a short timeout instead. Can you make sure that the setting "Increase connection timeout for Remote Agent" is unchecked, which is actually the default value?

It is unchecked, and its still pretty bad.
When Awesome Miner is in this state where it's running slow, can you please create a process dump file and send me by mail (the file will be large). Use Windows Task Manager, Details tab, right click on AwesomeMiner and select "Create dump file". With the information in this file, I will be able to see the current Awesome Miner process state and hopefully be able to identify why it's running slow. Thanks!

One quick question - are you using the automatic console screen update on the Console tab (bottom of the screen in Awesome Miner), Settings -> Auto Refresh? If that's the case, please try to set it to Disabled.

Yes, Ill do this soon. The freezing state seems to come and go, but I definitely still experience it with auto refresh disabled. Ive also tried disabling system monitoring, logging, all my rules, just about everything. I've added many more GB of memory as well - the only thing I'm sure of is that it's actually the UI thread of AM freezing, because if I click a little too much while the mouse cursor is a blue circle, the entire UI greys out and it asks me if I want to wait for AM to start responding again.
I will include a correction to the scenario we discussed via mail - when rules with a Process Failure trigger could cause the rules to execute on the UI thread. Just get back to me with any feedback.
legendary
Activity: 3346
Merit: 1094
Small issue when using the built in update.

If updating AM while a miner is running, after the update and AM restarts, it does not see that there is already a miner running and starts a new instance of a miner.


I have also noticed this for the last two dev releases.
The problem seemed each time to be with remote agent (win) and t-rex.

Your observations are correct about T-Rex. When Remote Agent is starting it's looking at the running processes and figure out of a mining process is still running. For T-Rex this wasn't working correctly. I've implemented a correction for this that will be available in the next release.
Jump to: