Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 303. (Read 703512 times)
July 26, 2018, 06:31:28 AM
@ patrike, please add https://github.com/NebuTech/BTMiner_NebuTech/releases, now has api support
July 26, 2018, 04:41:57 AM
@ayiphelmy
your are running msi remote and msi afterburner on the rig? i think it is not running. check it. I think msi remote close after rig start. if it close then you must go to C:\Users\"your user"\AppData\Local and delete the folder "Micro-Star_Int'l_Co.,_Ltd"
it's running i start it manualy but still can't get gpu seting in awesome. This happen only in 1 rig, 5 rig i added not have this issues your are running msi remote and msi afterburner on the rig? i think it is not running. check it. I think msi remote close after rig start. if it close then you must go to C:\Users\"your user"\AppData\Local and delete the folder "Micro-Star_Int'l_Co.,_Ltd"
July 26, 2018, 03:14:58 AM
@ayiphelmy
your are running msi remote and msi afterburner on the rig? i think it is not running. check it. I think msi remote close after rig start. if it close then you must go to C:\Users\"your user"\AppData\Local and delete the folder "Micro-Star_Int'l_Co.,_Ltd"
your are running msi remote and msi afterburner on the rig? i think it is not running. check it. I think msi remote close after rig start. if it close then you must go to C:\Users\"your user"\AppData\Local and delete the folder "Micro-Star_Int'l_Co.,_Ltd"
July 26, 2018, 01:24:51 AM
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.
July 26, 2018, 01:14:47 AM
hai ...
i want to asking about gpu clock setting not showing in awesome miner... i already run msi remote server and awesome remote agent... please help
Thanks
i want to asking about gpu clock setting not showing in awesome miner... i already run msi remote server and awesome remote agent... please help
Thanks
Click on miner, at the bottom part of the screen, where the info about currently selected miner is shown, select the tab "GPU", then click on "map to system monitoring" and select all gpu to be shown.
July 26, 2018, 12:28:07 AM
Hi all,
I was going to mail Patrike today but i am having the same issue with my Nvidia miners where T-rex miner wont show temps on one of my miners. There also appear to be issue with stopping and restarting the miner when it freezes (which it does sometimes on one of my other rigs, it seems that the rule to restart after 2 minutes of no additional accepts doesnt kick off or cant restart the miner.
I was going to mail Patrike today but i am having the same issue with my Nvidia miners where T-rex miner wont show temps on one of my miners. There also appear to be issue with stopping and restarting the miner when it freezes (which it does sometimes on one of my other rigs, it seems that the rule to restart after 2 minutes of no additional accepts doesnt kick off or cant restart the miner.
https://www.dropbox.com/s/p9bgn57y059huto/Captura%20de%20pantalla%202018-07-26%20a%20las%204.43.50.png?dl=0
I'm surprised that nobody has reported this.
Some rigs using t-rex do not show the temperature information of the GPUs. In the capture all the rigs use t-rex at that moment, but I always have 2 that never show the temperature.
A plate is old but the rig 5 is a modern z270. But as far as I know, the temperature issue reacts on the remote aftherburner.
I read something in the T-rex forum about this same error.
I'm surprised that nobody has reported this.
Some rigs using t-rex do not show the temperature information of the GPUs. In the capture all the rigs use t-rex at that moment, but I always have 2 that never show the temperature.
A plate is old but the rig 5 is a modern z270. But as far as I know, the temperature issue reacts on the remote aftherburner.
I read something in the T-rex forum about this same error.
July 25, 2018, 11:43:39 PM
https://www.dropbox.com/s/p9bgn57y059huto/Captura%20de%20pantalla%202018-07-26%20a%20las%204.43.50.png?dl=0
I'm surprised that nobody has reported this.
Some rigs using t-rex do not show the temperature information of the GPUs. In the capture all the rigs use t-rex at that moment, but I always have 2 that never show the temperature.
A plate is old but the rig 5 is a modern z270. But as far as I know, the temperature issue reacts on the remote aftherburner.
I read something in the T-rex forum about this same error.
I'm surprised that nobody has reported this.
Some rigs using t-rex do not show the temperature information of the GPUs. In the capture all the rigs use t-rex at that moment, but I always have 2 that never show the temperature.
A plate is old but the rig 5 is a modern z270. But as far as I know, the temperature issue reacts on the remote aftherburner.
I read something in the T-rex forum about this same error.
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:
Code:
\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.
July 25, 2018, 11:41:34 PM
hai ...
i want to asking about gpu clock setting not showing in awesome miner... i already run msi remote server and awesome remote agent... please help
Thanks
i want to asking about gpu clock setting not showing in awesome miner... i already run msi remote server and awesome remote agent... please help
Thanks
you also need after burner running http://www.guru3d.com/files-details/msi-afterburner-beta-download.html on the main PC to use it remotely.
this link explains it better down the page some .
https://www.awesomeminer.com/help/gpuclocking.aspx
July 25, 2018, 11:31:42 PM
hai ...
i want to asking about gpu clock setting not showing in awesome miner... i already run msi remote server and awesome remote agent... please help
Thanks
i want to asking about gpu clock setting not showing in awesome miner... i already run msi remote server and awesome remote agent... please help
Thanks
Click on miner, at the bottom part of the screen, where the info about currently selected miner is shown, select the tab "GPU", then click on "map to system monitoring" and select all gpu to be shown.
July 25, 2018, 11:29:43 PM
I am running AM Professional. I am not profit switching. I run all my ASIC miners through NiceHash. I can't figure out how to get it to show the column under Main...Miners where it shows "Coin (Total per day:$0.00, per month: $0.00) with a value - It will show on occasion when they have failed over to their second pool, but then once they go back to NiceHash - the column is back to a blank. How do I get this to show these stats properly?
go to pools then define the coins you are mining and make sure the ASIC miners are set up right when you set them up with the right Algorithm.
July 25, 2018, 11:29:05 PM
I am running AM Professional. I am not profit switching. I run all my ASIC miners through NiceHash. I can't figure out how to get it to show the column under Main...Miners where it shows "Coin (Total per day:$0.00, per month: $0.00) with a value - It will show on occasion when they have failed over to their second pool, but then once they go back to NiceHash - the column is back to a blank. How do I get this to show these stats properly?
You should define algorithm to each miner. Right click on miner, select "define pool coin" and choice for example "unspecified sha-256" if you are running antminer for "sha-256" algo.
July 25, 2018, 11:25:27 PM
hai ...
i want to asking about gpu clock setting not showing in awesome miner... i already run msi remote server and awesome remote agent... please help
Thanks
i want to asking about gpu clock setting not showing in awesome miner... i already run msi remote server and awesome remote agent... please help
Thanks
July 25, 2018, 09:48:43 PM
https://www.dropbox.com/s/p9bgn57y059huto/Captura%20de%20pantalla%202018-07-26%20a%20las%204.43.50.png?dl=0
I'm surprised that nobody has reported this.
Some rigs using t-rex do not show the temperature information of the GPUs. In the capture all the rigs use t-rex at that moment, but I always have 2 that never show the temperature.
A plate is old but the rig 5 is a modern z270. But as far as I know, the temperature issue reacts on the remote aftherburner.
I read something in the T-rex forum about this same error.
I'm surprised that nobody has reported this.
Some rigs using t-rex do not show the temperature information of the GPUs. In the capture all the rigs use t-rex at that moment, but I always have 2 that never show the temperature.
A plate is old but the rig 5 is a modern z270. But as far as I know, the temperature issue reacts on the remote aftherburner.
I read something in the T-rex forum about this same error.
July 25, 2018, 06:53:21 PM
I am running AM Professional. I am not profit switching. I run all my ASIC miners through NiceHash. I can't figure out how to get it to show the column under Main...Miners where it shows "Coin (Total per day:$0.00, per month: $0.00) with a value - It will show on occasion when they have failed over to their second pool, but then once they go back to NiceHash - the column is back to a blank. How do I get this to show these stats properly?
July 25, 2018, 02:40:47 PM
https://www.dropbox.com/s/1f08ml9w109kygq/IMG_2298.MOV?dl=0
Hello 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.
Hello 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
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.
Thanks PAtrike, if through diagnosis I saw which group failed, it was not any of the indicated ones, it was a pool of GIN lyra2z defined by my aside and with a failure by me. I could only find it through diagnosis.
It is crucial that the notification tab of the best errors.
Thank you for your attention and your answers.
July 25, 2018, 02:36:36 PM
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.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 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.
Awesome!
July 25, 2018, 02:20:44 PM
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).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!
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.
July 25, 2018, 02:07:48 PM
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.
July 25, 2018, 02:05:46 PM
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 чacoв нaзaд
Eщe
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://.eu.mine.zpool.ca: 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? zpool
==========================
@_zpool_
5 ч.
5 чacoв нaзaд
Eщe
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://
=================================
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
July 25, 2018, 02:02:33 PM
https://www.dropbox.com/s/1f08ml9w109kygq/IMG_2298.MOV?dl=0
Hello 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.
Hello 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
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.
Jump to: