Installed new version of AM and added excavator. Benchmark runs fine but when I start the rig on multipool hub it seems to show several algos in blue with speeds all 0.00000
What did I do wrong?
I just learned that Excavator and Mining Pool Hub doesn't work together. After doing more research, it looks like the Excavator miner is explicitly blocking connections to Mining Pool Hub because of some disagreements between Nicehash and Mining Pool Hub. I will have to implement something in Awesome Miner that prevents the profit switcher from selecting the combination of Excavator and MPH. For the moment, please disable one of them. |
|
|
|
third it . me to it is faster then Claymore ETH Miner just tested it by about 2 MH or was for me . I think patrike indeed said a while back he was looking at a way to add any custom miner with full stats or what we need to run it in AM and Other OC options that AM can use but that's gonna take some time it's more involved to add. if I understood him wrong ,then I'm being it up again  or hint, hint it will make life a lot easier but only if i misunderstood....if there needs to be a one time add on fee i will be then glad to pay for it or any thing to make AM more Universals then it all ready is . .. or Improve it , there is always room for improvement . Thanks for the suggestions on this. Until it's officially supported, it can be added as a user defined Managed Software. This is what I tried: 1) Via Options dialog, Managed Software, add a new software called "Phoenix Miner" 2) Set it as API compatible with Claymore Ethereum and use API port 3333 3) You can disable the algorithms not supported but no further configuration is required in this dialog 4) Add a new Managed Miner and set software to the new "Phoenix Miner". Point the path to the location of the Phoenix miner exe-file. 5) All command line parameters needs to be manually specified in the Command Line section of the Managed Miner, and it's important to specify API port like "-cdmport 3333". Example command line: -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001 -cdmport 3333 Now it should be possible to start the miner and get monitoring information. I did however notice that the Pools tab is empty with this setup, but I will implement support for that in the next release. For general information on the Managed Software feature, please see: http://www.awesomeminer.com/help/managedsoftware.aspx |
|
|
|
Now i have upgraded, my custom Phoenix miner doesn't connect to the interface. Can anyone help please?
I just downloaded the Phoenix miner and made sure I started it with the flag -cdmport 3333 to have the API enabled. From Awesome Miner I added it as an External Miner of type Claymore Ethereum and then I was able to see the monitoring information. Can you send me the API report for this miner you had? |
|
|
|
Hi, question regarding switching mining pools:
I have several Antminer S9 ASICs in awesomeminer, I configured 2 pools: antpool and BTC.com, i configured API access on S9, when i try to switch pools it disables 1st pool, then switches 2nd and 3rd pools, as result miner not working because 1st pool - disabled, anybody faces similar issues?
The existing pool show be removed after a few seconds and be replaced by the two new pools. What's the pool status of the two new pools, are they enabled and working? |
|
|
|
Awesome Miner version 4.4.2- Excavator 1.4 supported as both Managed Miner and Managed Profit Miner. Please note that automatic download isn't supported. - Performance improvements when performing opertions on many Antminers over SSH, for example setting default pools or configuring the API access. - Antminer diagnostics, where the cgminer/bmminer configuration of the Antminer can be displayed - The Managed profit switcher can be configured to detect pool failures and move on to the next pool - Added support for a total of three modes for profit statistics from pools like zpool, Hash Refinery and AHashpool: Current, 24h average estimate, 24h average actual. - Notification actions can specify a custom Webhook POST body - New notification variable to get the Notification ID - The system notifications can be disabled with a new setting - Claymore Dual Ethereum Miner 11.0, including the new dual mining algorithms - Minor corrections Awesome Miner cannot automatically download the Excavator mining software because of the Nicehash end user license agreement where redistribution of their software isn't allowed. The Excavator mining software needs to be downloaded manually from: https://github.com/nicehash/excavator/releasesThe Excavator software can be downloaded and extracted to any path. To use it from the profit switcher, edit the Profit profile and enable it in the list of software, then click the configure button to specify the path. The new profit switching feature to detect pools that doesn't give any accepted share can be enabled in the Options dialog, Profit switching section. To see if any pools are listed as a failed, right click on the miner and select View Details to view the profit calculations per pool and also if any of these pools have failed to give accepted shares. Please note that the pool is listed as failed per miner - it's not global to all miners. The reason is that if a single miner is unstable and doesn't produce any accepted shares, it will not ban the pool for all the other miners. If it's a pool problem, it will be detected for each individual miner about the same time anyway, and each miner will mark the pool as failed. There are now three modes for profit statistics: Current, 24h average estimate, 24h average actual - configurable in Options dialog, Statistics section. Please note that all of these numbers are still taken directly from the pools, so it's still the responsibility of the pool to provide as accurate numbers as possible.
|
|
|
|
This is a permission failure, where Awesome Miner isn't allowed to listen to port 17790 for HTTP purposes. You could try to run Awesome Miner with Administrator privileges once, to see if it setup everything properly. Then you should be able to run it normally again.
Tried running it as Admin, but same errors still in the log I'm afraid  Anything else I can try? 07/02/2018 17:10:09.310 [013] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.ISecurityService
07/02/2018 17:10:09.311 [013] [E]ChannelFactoryProvider: Channel faulted
07/02/2018 17:10:09.312 [013] [E] Failed remote: net.pipe://localhost/IntelliBreezeService/Security
07/02/2018 17:10:09.316 [013] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.ISecurityService
07/02/2018 17:10:09.316 [013] [E]ChannelFactoryProvider: Channel faulted
07/02/2018 17:10:09.318 [013] [E] Failed remote: net.pipe://localhost/IntelliBreezeService/Security
07/02/2018 17:10:09.321 [013] [S]Web Server prepare port 17790, Result: False
07/02/2018 17:10:09.321 [013] [S]Stopping Web Server The error message also indicates that the Windows service IntelliBreeze Maintenance Service isn’t running correctly. Can you please correct and verify? You could also try to change the port via Options dialog, Web section. |
|
|
|
FEATURE REQUEST:
On these Canaan Miners, an rPi3 acts as a controller for up to 20 different miners.
Would it be possible to take the API information from cgminer, which appears to support all the miners on the rpi, broken out into their own section and show them as individual as opposed to one monolithic miner.
Each with their own temp, stats, etc. Similar to how you break down GPU cards in a miner?
Thanks
do you have the A721/741 showing in awesome miner ? ... I'm assuming you mean the avalon 7series . yes, 721/741/821/841 all use the same basic approach and yes I have 4 miner on one rPi and it's only showing one AV7 which is an aggregated view of the 4, and I'd like to see the 4 individually, they are each reported in the cgminer API In general, Awesome Miner display what the API is reporting. You will not get 4 individual miners as you only have a single Cgminer API running, if I understood your setup correctly. If you want you can send me the API report (toolbar Tools-> Api Report) for this miner and I can verify |
|
|
|
Hi, thanks for great software and support If I have two separate farms (with two separate computers )100 Asics each, can I install on each of those two computers Awesome miner using one registration code for 200 miners? Also is there a way to get alarms if miners change their current working pool (like if first pool became unavailable)? Thanks a lot. Yes, you can use the same license as long as you don’t exceed a total of 200 miner as the license allows. There is currently no feature to detect if one pool goes down and the miner automatically fallback to the next |
|
|
|
Hi, i've been using the miner and i have some ideas about improving the graphical interface:
- when you search for awesome miner agents put a field in the wizard to enter the password, so you don't have to enter the password for each host - if you add lots of miner it is tiresome to modify each one.
- add a checkmark in miner properties to get the worker name from the description, so you don't have to always check "add to worker name" and type the worker for each miner
- make a "clone" button for the managed hosts section
- make the hw errors text color in webserver red so it pops out and see it better
- make a button to map all the selected miner gpus to system monitoring
- maybe add a tooltip so when you hover with the mouse above the miner after 2 you can see the details ( command line arguments and configuration )
- in the right click menu add an option to rdp ( remote desktop ) to the miner
- important - add an option to remove all income/revenue data in the dashboard from the view only / control view user roles
patrike, any feedback on this, especially the last one as i want to give access to employees to monitor the miners without them seeing the revenue Thank you Thanks for your feedback. For the RDP, it's already supported via the rules, where you can create a toolbar button to launch Remote Desktop to the selected miner. Please see "Example: Launch Remote Desktop for selected Managed Miner": http://www.awesomeminer.com/help/rules.aspxAbout the dashboard revenue information. The dashboard will only include the income for the miners that the users are allowed to see. If you only are allowed to see two miners, you will see the revenue for these miners on the Miners page, and on the Dashboard you just see the total revenue for these two miners - not for the entire system. Is your request also about not showing revenue in the miner list? |
|
|
|
|
Here is a small update about what's in the pipeline and the plan is to include it in a new release within the next 24 hours.
* Claymore 11.0 with the new dual mining algorithms
* Excavator 1.4.3 supported as Managed Miner and Managed Profit Miner
* A new profit switching feature where the profit switcher looks at the accepted shares of the mining to try to figure out if the current pool is failing. If there are no accepted shares for 8 minutes (configurable), the pool will be ignored by the profit switcher for 5 hours (configurable). The feature will be disabled by default.
Please note that if the pool is reporting that the shares are accepted, but still fail in some other way (payouts not as good as expected, shares not counted although reported as accepted, ...) it will be impossible for Awesome Miner to detect. Awesome Miner will not be able to solve all pool issues, but hopefully help a bit.
The release will contain more than the items above, but I think these three items are the most requested and discussed right now. Thanks for all feedback.
I can also point out that Bminer probably will be the next mining software for me to explore.
|
|
|
|
When can we expect to see support for Bminer? It's easily the fastest equihash miner available right now for CUDA mining. https://bitcointalk.org/index.php?topic=2519271.0Has anyone else gotten this working as external software? I've added it by following all of the steps in the documentation but when AwesomeMiner tries to run it the cmd prompt opens then closes right away. Bminer works correctly on this system if I run it on it's own. Thanks for your feedback. This one is on my todo-list. After the Excavator mining software is fully supported (not finalized yet), the next mining software to support might very well be Bminer. |
|
|
|
Awesome Miner version 4.4.1
- Cloud Services: Multiple Telegram clients can sign in and get notifications from Awesome Miner
- Cloud Services: Heartbeat feature includes support for Telegram notifications
- Display of Accepted and Rejected shares per GPU for Claymore Ethereum miner
- Configuration of automatic restart of crashed miner can be disabled by setting 0 restart attempts in the Options dialog, Advanced section
- Trigger for Check Statistics adds support for evaluating Rejected shares in addition to Accepted shares.
- Trigger for Computer Idle adds support for specifying time in seconds instead of minutes
- Notification list support keyboard shortcut Ctrl+A and Ctrl+C to copy all notifications to clipboard
- Awesome Miner API for miners includes hashrate value specified as a number
- Profit switcher will show error message if no pool can fulfill the requirements of the selected combination of algorithms and mining software
- Excavator 1.4 supported as External Miner
- Alexis Ccminer version updated
- Corrected hashrate summary when moving miners between groups
- Minor corrections
Thanks for the Excavator support! I want to configure excavator and I added external miner excavator (latest) but I am undable to benchmark or start mining with excavator. Do you have any tutorial about how to configure the latest version of excavator ? Why can't we use excavator with "managed profit miner" by adding excavator to "user defined mining software" and select compatibility "excavator latest" ? Trying to figure out. No luck as yet... Awesome Miner v4.4.1 included support for the latest Excavator software as an External Miner only. It was intended as a preview and the idea is of course to add it as a Managed Miner and for the profit switcher in the next release. I'm current working on this and I fully understand the importance of it. For more details on Excavator support, please see my notes about this in the previous post: https://bitcointalk.org/index.php?topic=676942.msg29615042#msg29615042 |
|
|
|
Can anyone help getting the webserver to work remotely? Works fine on localhost, but not on other machines on the same network! I see these errors in the log, which I suspect is the issue, but no idea how to fix it! 06/02/2018 10:18:23.047 [023] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.ISecurityService
06/02/2018 10:18:23.048 [023] [E]ChannelFactoryProvider: Channel faulted
06/02/2018 10:18:23.052 [023] [E] Failed remote: net.pipe://localhost/IntelliBreezeService/Security
06/02/2018 10:18:23.057 [023] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.ISecurityService
06/02/2018 10:18:23.058 [023] [E]ChannelFactoryProvider: Channel faulted
06/02/2018 10:18:23.060 [023] [E] Failed remote: net.pipe://localhost/IntelliBreezeService/Security
06/02/2018 10:18:23.065 [023] [S]Web Server prepare port 17790, Result: False
06/02/2018 10:18:23.065 [023] [S]Stopping Web Server This is a permission failure, where Awesome Miner isn't allowed to listen to port 17790 for HTTP purposes. You could try to run Awesome Miner with Administrator privileges once, to see if it setup everything properly. Then you should be able to run it normally again. |
|
|
|
Glad to see the continual support and evolution of AM. You guys are doing a great job.
Any thoughts or ETA on better support for the Bitmain AntRouter R1LTC? I know its probably not a major in-demand thing, but we're having fun with these to speculate on various coins, and they're pretty neat units considering. I'd hope its not too much on your end to bring in full support.
Thanks in advance.
Thanks! Antmienr R1LTC should already be supported. I don't have this device myself so I can't really verify. Is there a specific feature not working? |
|
|
|
I've noted your request, and I fully understand your requirement. |
|
|
|
Recently I had an issue with Awesome Miner and I wanted to do a clean uninstall and reinstall. I uninstalled the program using the Control Panel and now when I attempt to reinstall I get an error message stating that "The older version of Awesome Minor could not be removed." Can anyone help me get this reinstalled? This is on a windows 10 system if that helps.
Microsoft has a tool for removing software where the Windows Installer (used for MSI based installations) isn't behaving as it should: https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removedPlease give it a try. |
|
|
|
I've seen a number of discussions about the Excavator miner, and I've just implemented initial support for the recent versions of Excavator as an External Miner. It's included in the latest Awesome Miner release where it's at least possible to monitor it.
I do have an implementation for it as a Managed Miner in the pipeline as well, but that one needs a bit more testing before I will release it. More operations will also be made available later on.
The Excavator mining software is a bit special, and it looks like the configuration file needs to be specified with the number of workers you want for each GPU (the worker.add command). From an Awesome Miner point of view it would be great if Excavator simply could use all GPU's by default, because having Awesome Miner detecting GPU's first and then launch Excavator with a configuration based on this is a possible source of error.
The Excavator miner also provides very few configuration options via the command line, making it difficult to override any behaviors that Awesome Miner will enforce by default. I will try to come up with a good way to support this software anyway, but it's has a "unique" design.
In addition to the above, the Excavator miner will never be downloaded automatically due to the restrictions in the Nicehash EULA.
Thank you for adding Excavator support and for the effort to integrate new api from it. I want to propose to you some improvements : 1) I think it would be very useful for all AM users to see also the hash-rate a pool records for us. Lately almost all pools had connection problems, was stopped or they are simply recording a lower hashrate than the one that we see on miner's window. To achieve this you have to call pool's API : https://www.ahashpool.com/api/walletEx/?address= and you have the list of all miners. You have to uniquely identify each AM instance by assigning a uniquely generated random ID (that appears also in API json from the pool) that remains the same for a RIG (do not generate a new id when starting a new miner to track past values). Now that you have uniquely identified each instance you will have to download every 1 minute a new JSON from the link above and add values together with timestamp in an array you store for each pool and algo. By making the difference between 2 consecutive different values and divide to the number of seconds between the 2 values you have the real HashRate per second from the Pool. You also can show values like : unsold, balance and unpaid for that pool. The implementation from above will give us very useful insight about each pool performance and can help us earn more, now that BTC has a very low value, every optimization is really useful. 2) Sometimes when pools have too many connections they disable new connections for a period of time for a specific algo. In this case AM remains stucked with the last value AM received from the mining instance of ccminer and does nothing to fix that. I believe it would be better to show income statistics based on submitted (and also accepted shares) , instead AM now remains without any refresh to the last hash rate that was submitted by ccminer even hours ago. If AM waits for hours for an updated hashrate from ccminer and does not take time into consideration it is not the correct behavior. It should have a timer that checks every x seconds the received hashrate from the miner (if there isn't an updated value - identical values could also be a problem - , the for several checks, that miner has an issue) with one minute delay when miner is started to allow all GPUs to be started and send hash rates. Like this if one pool / algo server is offline, it will change to the next most profitable algo from the list. What do you think, Patrike ? Thanks for your feedback. 1) I'm planning to add the pool balance on the Balance tab, just below the existing list of wallet addres balances. This item is quite high on my priority list, but the implementation has not yet started. Hopefully I will have it done before the end of this month. 2) I've already started the implementation for detecting pool failures as part of the profit switcher. What I've implemented so far is that the profit switcher looks at the number of Accepted Shares. If it's not moving for 5 - 10 minutes (configurable), the pool will be marked as "failed" and will be ignored by the profit switcher for 2 - 24 hours (configurable). The profit switcher would then move on to the next pool that isn't marked as "failed". What I've implemented so far should at least partially solve the case you describe. Hopefully I will be able to have a first release with this feature later this week. |
|
|
|
|
Awesome Miner version 4.4.1
- Cloud Services: Multiple Telegram clients can sign in and get notifications from Awesome Miner
- Cloud Services: Heartbeat feature includes support for Telegram notifications
- Display of Accepted and Rejected shares per GPU for Claymore Ethereum miner
- Configuration of automatic restart of crashed miner can be disabled by setting 0 restart attempts in the Options dialog, Advanced section
- Trigger for Check Statistics adds support for evaluating Rejected shares in addition to Accepted shares.
- Trigger for Computer Idle adds support for specifying time in seconds instead of minutes
- Notification list support keyboard shortcut Ctrl+A and Ctrl+C to copy all notifications to clipboard
- Awesome Miner API for miners includes hashrate value specified as a number
- Profit switcher will show error message if no pool can fulfill the requirements of the selected combination of algorithms and mining software
- Excavator 1.4 supported as External Miner
- Alexis Ccminer version updated
- Corrected hashrate summary when moving miners between groups
- Minor corrections
|
|
|
|
I've been having troubles trying to set up a remote miner on the same local network. I've installed the remote service agent program on my remote PC.
I've added a new miner using the "New Managed Profit Miner" option, specifying my "Miner Host" as my remote rig's local IP, and performed a "test connection" option, which works successfully.
Yet when all of this is done and I right click "Start Miner", my main (host) PC just shows the remote miner as greyed out when I right click, not letting me stop it, along with not actually mining/starting anything on the remote rig.
Any thoughts/ideas?
The first step is to try the Diagnostics button to see if it indicates any specific issues. If not, please send me the log files for Awesome Miner and Remote Agent, and indicate the time of the issue. |
|
|
|
every so often one of my versions of ccminer will crash. Is there a setting that will detect this and restart it?
I have to close the miner window and then it will auto restart.
thx
The recommendation is to configure Windows to not display those crash dialogs, because it prevents the ccminer process from terminating correctly. Once you configure Windows to terminate the process instead, Awesome Miner will detect it and take care of it. Please see "Terminate crashed mining software": http://www.awesomeminer.com/help/windowsenvironment.aspx |
|
|
|
|
Show Posts
