For the past few updates the software shows wrong megahashes and profit. In example it says that my speed is 2.96 MH/s and the profit per day is $2.17, but in reality this is the hashpower of only 1 of the 6 gpus in that rig. It shows the 6 temps, no probs, but the hashrate and profit are wrong.
In the miner list, the profit per day is based on your actual hashrate you have right now. I assume this one is correct? It's only in the views that are based on the Profit profile hashrate that might be based on a single GPU (the Coins tab and Online Services tabs). The data you see in these tabs are not based on your current hashrate - as your miners typically have different hashrates anyway. You can define Profit profile groups in the Options dialog, Profit profile sectoin, if you want to create a profile that consists of all your 6 GPU's. See also: http://www.awesomeminer.com/help/profitswitching.aspx#profile |
|
|
|
That's probably because T-Rex is relatively new and only got introduced to most profit switching software recently, personally only seeing this issue appeared (on 1 card only in a 3 card rig) no more than 5 hours ago. To elaborate on the situation, it probably is due to Nvidia driver crash/reset, check your event log for possible errors from driver such as nvlddmkm ... etc. If you have these driver errors, tone down your OC would be the very first important step to try. *** @Patrike & T-Rex dev (if you are still following the thread) So what happens is that unlike some driver crashes, where the computer needed to be rebooted, or manually disable/enable individual GPU through device manager in order for Afterburner to recognise the card, the situation with T-Rex that I have seen today (probably related to @trucobit's anyway) is that the driver recovered from errors: \Device\UVMLiteProcess469
Graphics Exception: SKEDCHECK05_LOCAL_MEMORY_TOTAL_SIZE failed
\Device\UVMLiteProcess469
Graphics Exception: ESR 0x407020=0x1000 0x407028=0x0 0x40702c=0x900c064 0x407030=0x0 and Afterburner was able to pickup the card readings completely fine, so does T-Rex miner and AM having no trouble initialising and running mining sessions with all GPUs functional. Bear in mind that T-Rex's current implementation does not include GPU monitoring, so the temperature data has to come from the Remote Agent, the display in the Miner tab's glitch did not get away until I restarted the AM Remote Agent on the remote rig, please note that Map to system monitoring can only see 2/3 cards as well until the Remote Agent was restarted. It might very well be that some new kind of driver crash causes the monitoring that Awesome Miner do to not work correctly. Please select a miner and click the System tab to see what Awesome Miner is reporting for the system. When you don't get the temperature readings anymore, are the temperatures listed as 0 in the System tab, or are the GPU's no longer listed here at all? When using "Map to system monitoring" in Awesome Miner, the temperature readings and more will be taken from the System tab and map that into the GPU list on the GPU tab. This is the reason why Awesome Miner can get temperature information and more even if it isn't reported by the mining software. What I will do in the next development release is to add a new button "Reinitialize monitoring" on the System tab. Please give this one a try to see if it resolves the problem. |
|
|
|
Hi there - anybody an idea?!
i have a few Antminer L3+ running - this miners allow by default only 3 Pools (as all Antminer)
but i need more than 10 Pools for Profit-Switching Purposes
you can add the desired pools in AM and everything runs fine until the miner reboots (what's happening sometimes)
so i created a Pool Group and defined a User defined rule to change the group pool
my problem is in the Trigger to activate this Rule:
in the moment i use a Time intervall of 5 Minutes and a Detect Pool URL (i compare the URL of all pools of a miner with a URL that is not in the default pools and trigger it, if no pool URL contains the specific string)
- Problem 1 - it only works sometime?!
- Problem 2 - actually i would like to activate the trigger every time after a miner starts/comes online - not every 5 Minutes?!
thank you in advance!
To find out why it's not working all the time, a good first step would be to review the log file (toolbar: Tools -> Log File) and search for "rule execute". This would indicate if the rule isn't executed (something wrong with the trigger) or if it's executed but doesn't do what it should (something wrong with the action). You could also try to use the trigger "Detect mienr API connection established". That one should be triggered once when the miner is showing up in Awesome Miner after a reboot. |
|
|
|
Is there a way to exclude income from a specific group of miners (or specific miner) from the total earnings shown on dashboard?
This is currently not supported. For multi-user scenarios, it's possible to define multiple accounts for web accounts, where each account can be given access to a limited number of miners. Only the assigned miners will show up on the web dashboard. For the Awesome Miner main application, it's however not possible. |
|
|
|
Hello, I was wondering if I could add the option to switch mining locations for the zpool .and not just for him . Since the pool offered a different location of the data center in Central Europe. zpool ========================== @_zpool_ 5 ч. 5 часов назад Еще We've launched a beta EU based stratum server located in Central Europe. Please, if you are in EU give it a try. stratum+tcp://<algo>.eu.mine.zpool.ca:<PORT> http://zpool.ca #zpool #multipool #yaamp #bitcoin #litecoin #altcoin #wepay ================================= I understand that you can use "How do I add and configure my pool in Awesome Miner" a little awkward . Make an option to select a mining location ? That's possible.? Thanks It looks like zpool added their EU servers just a day ago. I will add support for this in one of the next versions of Awesome Miner to make it easier to select location. Are all their current servers in US right now? |
|
|
|
https://www.dropbox.com/s/1f08ml9w109kygq/IMG_2298.MOV?dl=0Hello patrike, I will try to be productive. I am using my time to try to identify the problem. You have already seen that I have had dozens of errors with lyra2z (other days is another protocol) and tried to reproduce it. IN the video that I send, I just recorded it when it started to give problems in lyra2z in blazepool, it looks perfectly as it fails. I created a pool, only with lyra2z in blazepool and nothing else, I add it to the same miner who failed seconds before, and I throw it. The surprise is that he does it correctly, enters blazepool in lyra2z. There is a problem in the autoswitch, because I have already shown that it fails when there are more protocols, but when it is just not, when mino gin in lyra2z does not fail, when I do the benchmark it works fine. I have not changed the miner nor the OC, I have only put mine directly blazepool in lyra2z These failures that I have been reporting for some time, happen randomly and in different protocols. It's a good thing that there are more people who have thought of reporting the same thing as me. gives the feeling that somehow and sometimes when a miner launches autoswitch change the OC or throw it with incorrect parameters, because I do not understand why it only happens in autoswitch, but does not fail mining with a single protocol or currency. So I do not expect to read more than it is a bad configuration of the miner, it is demonstrated that the miner works perfectly when he is not in autoswitch. Now it is happening in miner 2, 3 and 4, but not in 1 and 5. Why does it work well in some and poorly in others if it is the same pool and miner? Also to say that to those miners with T-rex that fail, I have lowered the OC a lot, but as it sees it fails in autoswitch but not alone. And I hope you have the courtesy to answer me. I think that the important point that Patrike highlighted is that the problem is a false error report. AM doesn't shuffle on his own algorithms, compatible software and pools. The real fact is that we have a miner that crash for a reason and AM report it sometimes badly depending on the speed of crash. As i do right now, you should first try different OC settings on your cards and see if there's a difference. Maybe stability problem come from the way AM launch mining softwares, but it may be also a bad configuration on our rigs... Agree that it is a bad error report. But, the problem is that it tells me that lyra2z does not work when it is in autoprofit mode, but it does when there is no autoprofit. In the video I just choose that protocol and it works perfectly, so it's not the miner's configuration, it's the problem of how the autoswtich launches the requests of some miners In this scenario, I would really recommend you to start the miner with the Diagnostics button. That would give us both the exact command line and settings Awesome Miner uses to launch the mining software, and also any error messages from the mining software (that it cannot initialize some GPU, that it cannot connect to the pool or anything else). With this information, it's easier to see if the issue is related to the command line that Awesome Miner uses to launch the mining software or if it's simply something going wrong inside the mining software after being launched. The fact that a miner doesn't start almost always requries the use of the Diagnostics to find out why. There are two more points 1) As you might have seen from my previous post, I did identify the issue with the incorrect error message where it displayed the incorrect pool name. This does however not explain or cause any real mining issues as it was just a display string that was wrong in the user interface. 2) I've also added another feature that should make Awesome Miner better at recovering from these scenarios where it keeps failing with a certain mining software or pool. In the next release you will find a new setting "Ignore pools after too many failed miner restart attempts". It's very similar to the feature where no accepted shares results in that a pool i marked as failed and the profit switcher will ignore it for some time. The result is that after a few restart attempts, where Awesome Miner eventually gives up, it will mark your Blazepool Lyra2z as failed and it will restart the miner and let the profit switcher pick the next pool in the list. In the end, you might end up with a completely different pool, mining software and algorithm, but at least the mining is still running. Please note that this will not resolve any issues with a specific mining software, you still need to figure that out with the Diagnostics, but it helps your miner to keep running during night even if there is either a specific pool or a specific mining software that is failing all the time. Then you can see from all the Notifications that there has been some issues and you could then investigate that in more detail. Both #1 and #2 will be part of the next development preview. |
|
|
|
Hi Patrike,
just some things:
- any chance the Ethash algo gets added as an option for external miners as currently it's not an option and not possible.
- integration of E3, not sure if there are some features different than the other antminers.
- some results from benchmarking seem to be totally messed up. for example on some algos with 1080ti i got huge better results with some miner software, in some cases double than with others. But when the actual mining than begins these perform way less and never get even near to the benchmark results. And here is the problem, because the other, not so good benchmarked mining software would do better, but
isn't choosen as the benchmarking favorites them.
- same goes for mining pools. I have some concern that some mining pools profit prediction are unreal, especially for blazepool and miningdutch. I could be wrong here, but i'am suspect that something isn't there like it should be.
- for some reason after last update the DGB icon for skein is gone on my end. Not sure if it's an issue on my end or the last AWM update.
Thx in advance for looking into these issues or considering them.
Thanks for your questions and feedback. 1) Ethash is actually listed as "Ethereum" in Awesome Miner. It's not fully correct today, but at least it's there. 2) Antminer E3 is supported. In order for the correct hashrate to show up, you need to be on the latest version of Awesome Miner. Please let me know if you find something unique to this miner that doesn't work like the other Antminers. 3) Some mining software like Ccminer allows offline benchmark, where you can benchmark it without a pool. There can be instances where this is nice as you don't have to have all pools defined in order to run the benchmark. In the benchmark dialog, please uncheck "Benchmark without a pool", which would force the mining software to benchmark using a real pool, as this is more likely to give accurate results. 4) The profit estimates are from the pools. Awesome Miner do have a feature that can adjust down these predictions from the pools based on past performance. Please see "Adjust reported revenue": http://www.awesomeminer.com/help/coinstats.aspx5) I do see the DGB icon both when prioritizing WhatToMine and when prioritizing Coincalculators.io as the coin source. For which of these sources isn't the DGB icon showing? Is the problem still present, or could it have been a temporary issue due to some change on one of these coin sites? |
|
|
|
Hey Patrike, you are doing a great job, thank you for that! I have a suggestion to the rules (or maybe it can be done something else). If I setup a rule with (for example) a temperature trigger greater than or equals 80C. As actions I have 1) A Notification with "Notifice once until acknowledged" and 2) Run Executable Whenever the rig got 80C+ I will get one notification only until I click Acknowledge or Clear. So far so good. But the programm will be loaded over and over again, as long as the rig got 80C+. Is it possible that the programm will be loaded only one time? Maybe with a mark-field like in Notifications "Start only once until Aknowledge". Or maybe you have a better idea  Edit: The reason behind is simple. I will turn off a smart socket as emergency stop. But so it receive unlimited turn off signals. I actually got an idea how scenarios like this could be resolved with Tags ( http://www.awesomeminer.com/help/tags.aspx) - but right now you can only have triggers that detects if a tag is present. For it to work in your scenario we would need the Detect Miner Tag trigger to not only trigger if a tag is present, but also if it's not present on a miner. I will add this in the next release. Once available, you can define a rule like this: Triggers (both must match) a) Temperature is 80C+ b) The miner tag "Temperature 80+" isn't set Actions: a) Notification b) Run executable c) Set miner tag "Temperature 80+" (this would prevent the rule from being executed again, until this tag is removed either manually or by another rule. That other rule could for example run if the temperature is below 80C) Already today you can look at the trigger "Detect miner tag" and the action "Modify miner tag" to get an understanding of the concept. |
|
|
|
Hello Patrike, I encounter those type of errors more and more often : Mining process not running, initiating restart (PhoenixMiner, Ethereum, ZergPool [Phi2])
Mining process not running, initiating restart (T-Rex nVidia GPU Miner, Phi2, europe.ethash-hub.miningpoolhub.com)
Mining process not running, initiating restart (PhoenixMiner, Ethereum, ZergPool [HSR])
Those are just examples, but as you can see, it's like AM was shuffling algorithms and compatible online services  PhoenixMiner trying to mine ethereum on Zergpool phi2 pool is kind of weird... Do you have an idea of what's happening ? Can you please send me the full log file for this issue by mail? I agree that the pool names look strange here, but it could be that the error message didn't pick up the correct pool name here. With the log files I can verify this as well. As you requested, i send you my log file. To add to this random problem, i get sometimes alert windows error like the one i get this morning :  As you can see, AM still try to mine an algorithm with an incompatible software... When this error occur, rig stop working until i click on the OK button. It's annoying because when it happens at night, i can lose severals hours of mining. Tell me if you need more info or more log than the one i sent you. Thanks for the logs, I will investigate. If you get an error message like this, it's most likely that the mining software either crash or simply give an error message when starting. When this happend, please click the Diagnostics button in the toolbar as instructed, as it will often tell you what the isssue is. An update on the issue related to notifications of mining software being restarted (or failed to start, as in the dialog): If a mining software crashes, Awesome Miner will display a notification about it where the mining software and pool is also indicated. The pool information is based on what the mining software reported. However, if the mining software crashes fast once started, and didn't send any pool information to Awesome Miner, Awesome Miner would incorrectly use the last provided pool information which in this case is from the previous mining software that was running, so it could be the name of a pool that was used before and not the current one. Please note that it's only the error message that is incorrect here, as it would indicate the last successfully reported pool. The actual pool for mining is correct. |
|
|
|
May i see the total hashrate of second GPU algo in dual mode? if it is not supported, it would be good to see such feature in future.
In the Miners tab in the Windows application you will see the secondary hashrate, if any. It's however not displayed in the web and dashboard. |
|
|
|
Hello Patrike, I encounter those type of errors more and more often : Mining process not running, initiating restart (PhoenixMiner, Ethereum, ZergPool [Phi2])
Mining process not running, initiating restart (T-Rex nVidia GPU Miner, Phi2, europe.ethash-hub.miningpoolhub.com)
Mining process not running, initiating restart (PhoenixMiner, Ethereum, ZergPool [HSR])
Those are just examples, but as you can see, it's like AM was shuffling algorithms and compatible online services PhoenixMiner trying to mine ethereum on Zergpool phi2 pool is kind of weird... Do you have an idea of what's happening ? Can you please send me the full log file for this issue by mail? I agree that the pool names look strange here, but it could be that the error message didn't pick up the correct pool name here. With the log files I can verify this as well. It's the same mistake I've been reporting for a couple of months, even with videos. In an aletoria way it fails, and when it does mix one thing with another, I do not know why. Sometime it has been because of having an order placed in a miner, instead of a simple error it gives you an error downloading protocols. But other times it's because he wants, fails and then tomorrow when mining the same thing in a car, it does not fail. I now choose lyra2z to pool in that rig and it works, as seen in capture now I fail lyra2z in zergpool in automatic, perp set as a mix Lyra2z and PHI, the same as when I showed the videos with the failures in the pop-ups I have reported it several times, I have rarely received an answer for this, and in any case there are a couple of lions who believe in the right of reason. Let's see if someone else reports it now, these random flaws are better tuned. I'm sorry Patrike, I can not give you any script to reproduce the fault, I do not know what conditions occur, I can only say that it happens to me now, and tomorrow surely I will not fail. The miner does not really start, or at least I do not see it in the console. Let's see if there is luck, because these failures when they occur stop the Rig and the income. Thanks for the information. I think there are two things to consider here 1) Mining software do crash every now and then on most mining rigs. Sometimes it can be due to high OC and instable drivers, while it in other cases is simply a bug in the mining software. When a mining process is no longer running, Awesome Miner will detect it within a few seconds and provide these kind of notifications, and then restart the mining. The crashes themselves are typically not related to Awesome Miner, and Awesome Miner can't really do much except restarting the process. You can configure how many restart attempts you want within the last 5 minutes via the Options dialog, Advanced section. 2) When Awesome Miner is displaying the pool information for a crashed process, I think it might do this incorrectly when the profit switcher is used. So the crash notification message may display the wrong pool under some scenarios and I will one more time investigate to see if I can find out why. Update: I've identified the issue for #2. Please see: https://bitcointalk.org/index.php?topic=676942.msg42773748#msg42773748 |
|
|
|
Hello Patrike, I encounter those type of errors more and more often : Mining process not running, initiating restart (PhoenixMiner, Ethereum, ZergPool [Phi2])
Mining process not running, initiating restart (T-Rex nVidia GPU Miner, Phi2, europe.ethash-hub.miningpoolhub.com)
Mining process not running, initiating restart (PhoenixMiner, Ethereum, ZergPool [HSR])
Those are just examples, but as you can see, it's like AM was shuffling algorithms and compatible online services PhoenixMiner trying to mine ethereum on Zergpool phi2 pool is kind of weird... Do you have an idea of what's happening ? Can you please send me the full log file for this issue by mail? I agree that the pool names look strange here, but it could be that the error message didn't pick up the correct pool name here. With the log files I can verify this as well. As you requested, i send you my log file. To add to this random problem, i get sometimes alert windows error like the one i get this morning : As you can see, AM still try to mine an algorithm with an incompatible software... When this error occur, rig stop working until i click on the OK button. It's annoying because when it happens at night, i can lose severals hours of mining. Tell me if you need more info or more log than the one i sent you. Thanks for the logs, I will investigate. If you get an error message like this, it's most likely that the mining software either crash or simply give an error message when starting. When this happend, please click the Diagnostics button in the toolbar as instructed, as it will often tell you what the isssue is. |
|
|
|
Hello Patrike, I encounter those type of errors more and more often : Mining process not running, initiating restart (PhoenixMiner, Ethereum, ZergPool [Phi2])
Mining process not running, initiating restart (T-Rex nVidia GPU Miner, Phi2, europe.ethash-hub.miningpoolhub.com)
Mining process not running, initiating restart (PhoenixMiner, Ethereum, ZergPool [HSR])
Those are just examples, but as you can see, it's like AM was shuffling algorithms and compatible online services PhoenixMiner trying to mine ethereum on Zergpool phi2 pool is kind of weird... Do you have an idea of what's happening ? Can you please send me the full log file for this issue by mail? I agree that the pool names look strange here, but it could be that the error message didn't pick up the correct pool name here. With the log files I can verify this as well. |
|
|
|
Found an annoying bug, I hope you can reproduce it to fix.
1) Enter 1 or more "User defined online services" and mark the "Include in managed profile switcher". I did this, for example, with the new Timetravel blockmasters.co:3555
2) Click on any profile and "Edit profit profile", edit something and click "OK".
3) Now your freshly made User defined online service is not visible in "View details -> Profit switching" and is also not visible in the online services tab. So the profit switcher will ignore it.
4a) To activate, you have to go back to "User defined online service", click the service, demark "Include in managed profile switcher" and hit "OK"+"OK".
4b) Back again to "User defined online service", click the service, now mark "Include in managed profile switcher" and hit "OK"+"OK".
Profit switching will work now until you edit something again in any profile. So you have to repeat 4a and 4b again to activate the profit switching again.
If you have more than one User defined online service, you have to demark all of them and also mark all of them whenever you edit some profiles.
EDIT: They are also not visible in benchmark until you done 4a and 4b.
When I tried this at first, at #3 I could see that there was quite some delay before it showed up on the Online Services tab. It turned out to be related to that another profit source MultiPool.us had an API request that took 30 seconds to timeout. For this reason, I had to sit and wait for more than 30 seconds on the Online Services tab - but then the Blockmasters Timetravel entry showed up. So it was slow, but eventually showed up. I went ahead and disabled the MultiPool.us integration in Awesome Miner as their API has been down for a while now, and now the Blockmasters Timetravel entry shows up in a few seconds after adding it. |
|
|
|
Awesome Miner Version 5.3.4 (Development preview of 5.4)
- Added YescryptR16 and Allium algorithms, including support in CpuMiner-Opt
Thank you for adding those algorithms. Allium is also supported by ccminer. Thanks - I will add it for ccminer as well. |
|
|
|
please help me to setup one rig, i have 2 GPUs , one 1060, one 1070,
1070 mining ethereum and 1060 crash , i created 2 profit profile one for 1070 one for 1060 and 2 profit miner and alocated to profit profile and selected only one gpu for each miner... when i pres start miner for 1060 (with selected gpu 1060) its run on 1070.. please help me.
Which mining software is it? Each mining software have their own ordering of the GPU's, but Awesome Miner is doing its best to figure out which order to use for each software. What could be of interest here is also the ID and PCI Bus ID of each device in the GPU selection dialog, as Awesome Miner uses this information to find out the GPU number. The number that Awesome Miner is passing to the mining software can then be found via the Diagnostics button in the toolbar. |
|
|
|
Awesome Miner Version 5.3.4 (Development preview of 5.4)- Coins tab improved by separating Revenue and Profit into two separate columns that can be sorted individually - Improved threading performance when using larger number of miners - Ensure miner hostnames cannot contain blank spaces - Added YescryptR16 and Allium algorithms, including support in CpuMiner-Opt - Added mining software: T-Rex nVidia GPU Miner - Correction to coins per day calculations for some algorithms like Blake 2b - Correction to SRBMiner configuration file entries related to GPU settings - Correction to hash rate for latest firmware versions of Innosilicon A9 Zmaster miner. If an older firmware is used for this miner, please upgrade to the latest firmware version. 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 http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msihttp://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi
|
|
|
|
Hey Patrike, since I mine more often the crazy coins like X16r, I think a more intelligent profit switching is what AwesomeMiner needs. Here is the problem, just as an example: I have setup in my profile a hashrate of 100 MH/s. AM is using this hashrate to calculate the profit and switch to another algo if that profit is higher. Lets say my calculated profit now is $10. But now, X16r mines with lets say 150 MH/s and $15 profit. But AM still use the 100 MH/s from profile to calculate. Another algo is now at $12, which is higher than the $10 and AM switch. But now I'am losing $3 profit, because the real hashrate of 150 MH/s would give me $15. I hope you get the idea. As a workaround I have made some rules (like a 100 MH/s rule, a 110 MH/s rule, 120, 130...) to check the hashrate and then loads just different profiles. But this must be easier So here is my suggestion how this could be done: 1) If no API/Stats exists, then take the hashrate from the actual loaded profile to calculate the profit switching. Just like now. 2) If API/Stats exists, use them instead to calculate the real profit and only switch to another algo if the real calculated profit right now is lower. Maybe some people outthere dont like such intelligent switching. So you could make a choice in the preferences like "Use fixes switching" and "Use intelligent switching". Thanks for your feedback. I do know that X16r is a bit special as it can have different hashrates over time. But could it be that the profit reporting from the pools is some kind of average for X16r - so do you really get paid more during the time the hashrate is 150MH/s on X16r compared to when it's lower on the same pool? I don't have the answer to this, but I just want to make sure I fully understand the issue here. X16r is for sure a bit complex. |
|
|
|
Thanks for your suggestion. Right now it says that it doesn't have any monitoring interface (API). It will not be supported until that's available, so the only option right now is to launch it as a Generic Miner: http://www.awesomeminer.com/help/genericminer.aspx |
|
|
|
Hi team, can you have a look/add T-Rex miner, please? https://bitcointalk.org/index.php?topic=4432704.0It is mining really faster on 1080Ti (latest drivers 398.x), on all Supported algorithms (on some a WAY FASTER : lyra2z phi2 hsr c11 x17 phi tribus (for now?) Yeah I am getting over 4.3 mh/s , with cryptodredge about 3.6 I've implemented support for T-Rex today, so it will be included in the next release. I might be able to provide a new development release tomorrow already. Once available, please give it a try. Thanks! |
|
|
|
|
Show Posts
