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.
Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 282. (Read 703547 times)
September 04, 2018, 02:22:46 PM
September 04, 2018, 01:31:53 PM
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
- 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.
September 04, 2018, 12:42:21 PM
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?It runs, but still does not coy the benchmark result back to the test page for saving to the profile. Hum ...
Thank you.
September 04, 2018, 07:37:41 AM
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
- 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
September 04, 2018, 06:36:10 AM
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.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.
It runs, but still does not coy the benchmark result back to the test page for saving to the profile. Hum ...
Thank you.
September 04, 2018, 06:32:46 AM
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.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.
Can you share the diagnostics output (the Diagnostics button in the toolbar) where the first two letters are missing? Thanks!
September 04, 2018, 06:18:35 AM
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: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?
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. September 04, 2018, 06:13:01 AM
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.
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.
September 04, 2018, 06:10:20 AM
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.
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.
September 04, 2018, 06:00:45 AM
Since updating to the latest version my main server is completely freezing and not responding to remote desktop or web connections.
This is happening daily.
Looking in the log all I see at the end is:
Is the computer where you are running Awesome Miner also running mining - or is it only used to monitor other Remote Agents? A complete computer freeze isn't likely to be caused by Awesome Miner itself.This is happening daily.
Looking in the log all I see at the end is:
Code:
02/09/2018 02:20:49.491 [024] [S]Managed Profit Switching processing: HP GPU Study, IsRunning: False
02/09/2018 02:20:49.491 [024] [S] Profitability, poolChanged: False, Algorithm: CryptoNightV7 -> CryptoNightV7, EngineType: CnClayMiner ->CnClayMiner, EngineSubType: Disabled ->Disabled, AutoDownload: True, EnginePath:
02/09/2018 02:20:56.117 [031] [E]ChannelFactoryProvider: Channel faulted
02/09/2018 02:20:56.118 [031] [E] Failed remote: net.tcp://192.168.1.15:9630/AM/MinerService
02/09/2018 02:21:01.123 [035] [S]ChannelFactoryProvider: Create Channel Factory: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService
02/09/2018 02:21:22.128 [035] [E]ChannelFactoryProvider: Channel faulted
02/09/2018 02:21:22.129 [035] [E] Failed remote: net.tcp://192.168.1.15:9630/AM/MinerService
02/09/2018 02:21:22.129 [035] [S]ChannelFactoryProvider: Create Channel Factory: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService
And then nothing in the logs until lunchtime today when I had to hard crash and restart the server.
02/09/2018 02:20:49.491 [024] [S] Profitability, poolChanged: False, Algorithm: CryptoNightV7 -> CryptoNightV7, EngineType: CnClayMiner ->CnClayMiner, EngineSubType: Disabled ->Disabled, AutoDownload: True, EnginePath:
02/09/2018 02:20:56.117 [031] [E]ChannelFactoryProvider: Channel faulted
02/09/2018 02:20:56.118 [031] [E] Failed remote: net.tcp://192.168.1.15:9630/AM/MinerService
02/09/2018 02:21:01.123 [035] [S]ChannelFactoryProvider: Create Channel Factory: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService
02/09/2018 02:21:22.128 [035] [E]ChannelFactoryProvider: Channel faulted
02/09/2018 02:21:22.129 [035] [E] Failed remote: net.tcp://192.168.1.15:9630/AM/MinerService
02/09/2018 02:21:22.129 [035] [S]ChannelFactoryProvider: Create Channel Factory: AwesomeMiner.Service.Contracts.ServiceContracts.IMinerService
And then nothing in the logs until lunchtime today when I had to hard crash and restart the server.
It is mining as well and has been running fine for many months, it's a dedicated machine, doing nothing else at all.
It's happening at least daily. Is there anyway to narrow down what is causing it?
It might be possible to find a pattern here, that it's for example always Claymore Cryptonight miner that was the last started mining software before a crash.
September 04, 2018, 03:14:36 AM
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.
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.
September 04, 2018, 02:32:29 AM
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.
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.
September 03, 2018, 08:57:11 PM
So my initial test with the linux agent was a semi-fail. I got AM to recognize the agent, but it refuses to mine.
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.077 [001]Starting service
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.088 [003]Updating settings
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.088 [003] [W]Warning - Settings is null
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.088 [003]Current list of Active Miners:
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.089 [003]Saving configuration to: /root/.config/AwesomeMinerSe rvice/ServiceData.xml.tmp
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.099 [003]--> /root/.config/AwesomeMinerService/ServiceData.xml
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.105 [003]Starting Service Manager...
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.112 [003]IntelliServer::Start - Will listen on Port: 9630
Sep 04 01:53:41 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:41 AM.110 [008]Running Discovery Thread
Sep 04 01:55:45 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:55:45 AM.912 [016]Setting callback channel
Sep 04 01:55:52 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:55:52 AM.304 [016]Command request: Start
Sep 04 01:55:52 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:55:52 AM.305 [016] [E]Miner not found: 284
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.077 [001]
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.088 [003]
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.088 [003] [W]Warning - Settings is null
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.088 [003]
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.089 [003]
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.099 [003]
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.105 [003]
Sep 04 01:53:11 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:11 AM.112 [003]
Sep 04 01:53:41 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:53:41 AM.110 [008]
Sep 04 01:55:45 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:55:45 AM.912 [016]
Sep 04 01:55:52 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:55:52 AM.304 [016]
Sep 04 01:55:52 worker AwesomeMiner.RemoteAgent.Linux[2412]: 9/4/18 1:55:52 AM.305 [016] [E]Miner not found: 284
September 03, 2018, 08:19:07 PM
Hey Patrike,
another suggestion for the Benchmark:
Is it possible to add Benchmark for different "-i" intensity's? I think the easiest way could be we set the Start and Stop intensity and the benchmark does all the steps between and show the results in different colums. Or maybe you have a different and more brilliant idea how to do that
another suggestion for the Benchmark:
Is it possible to add Benchmark for different "-i" intensity's? I think the easiest way could be we set the Start and Stop intensity and the benchmark does all the steps between and show the results in different colums. Or maybe you have a different and more brilliant idea how to do that
September 03, 2018, 07:43:13 PM
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.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.
It runs, but still does not coy the benchmark result back to the test page for saving to the profile. Hum ...
Thank you.
September 03, 2018, 06:46:34 PM
Please try to use --gpu-platform directive to resolve the igpu/discreet gpu issue in sgminer
Benchmark doesn't really give much details about error feedback, to see those, you need to mine directly to a working pool and right click on miner -> diagnostics, there you can see more detailed error captured in the output dialogue window
How would I go about doing that? I tried adding it to the user defined command line option in the Managed Software section, but it only flashes and will not load when running a benchmark using sgminer.Benchmark doesn't really give much details about error feedback, to see those, you need to mine directly to a working pool and right click on miner -> diagnostics, there you can see more detailed error captured in the output dialogue window
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.
September 03, 2018, 05:58:06 PM
Please try to use --gpu-platform directive to resolve the igpu/discreet gpu issue in sgminer
Benchmark doesn't really give much details about error feedback, to see those, you need to mine directly to a working pool and right click on miner -> diagnostics, there you can see more detailed error captured in the output dialogue window
How would I go about doing that? I tried adding it to the user defined command line option in the Managed Software section, but it only flashes and will not load when running a benchmark using sgminer. Benchmark doesn't really give much details about error feedback, to see those, you need to mine directly to a working pool and right click on miner -> diagnostics, there you can see more detailed error captured in the output dialogue window
September 03, 2018, 04:54:21 PM
Am I the only one who has issues running benchmarks? Trying Nicehash automatically disconnects from the pool. I have tried different regions but it does the same thing. I can only benchmark a couple algos due to this issue. Any ideas?
Which mining software is this? Is mining on the same pool with the same mining software working fine, and it's only the benchmark that is failing?If you still run into this problem, could you please also send me your log file and I can review the command line parameters Awesome Miner uses to launch the mining software to make sure it's correct. Thanks!
I do not mine to Nicehash. So do not know if direct mining to it is failing or just the benchmark somehow.
EDIT:
Ok, Nicehash is now working. Decided to try a different BTC address and it worked. Do not know what happened to the other one and why no error, but it works.
Now, sgminer is having issues. The Benchmark setup say use GPU 0 for the RX 580 card. However, when it runs it detects the built-in Intel HD graphics as GPU 0 and benchmarks that instead. The drop down does not allow any other selection to be made on the local machine I am testing with. Even when that does run, it does not save the "benchmark" to the test report.
Please try to use --gpu-platform directive to resolve the igpu/discreet gpu issue in sgminer
Benchmark doesn't really give much details about error feedback, to see those, you need to mine directly to a working pool and right click on miner -> diagnostics, there you can see more detailed error captured in the output dialogue window
September 03, 2018, 01:56:43 PM
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?
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?
September 03, 2018, 01:28:43 PM
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.
Two things that may have an influence on this: I have a 60 second delay after AM starts before it starts a miner. And, the miner that was running when the update was started is one of the miners that the update, um, updated. After the update, it starts a new instance of the updated miner, leaving the old miner still running. Today, the miner was T-Rex.
Thanks for the awesome software!
...jim
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.
Two things that may have an influence on this: I have a 60 second delay after AM starts before it starts a miner. And, the miner that was running when the update was started is one of the miners that the update, um, updated. After the update, it starts a new instance of the updated miner, leaving the old miner still running. Today, the miner was T-Rex.
Thanks for the awesome software!
...jim
Jump to: