Other projects straight up ban Hosts. If they never notice zero points or constant errors then they won't notice being banned.

That host is from Gridcoin and it was probably ninja installed on someone else's computer for profit w/o them knowing. Def should be banned. Seen way too many errors from Gridcoin users across all projects.

What about systems like this wingman that have a turnaround of over 1 day and "inprogress" tasks of over 3000? one of my results is in there. Those tasks were accumulated just in last week it seems. I have .06 day turnaround and average under 200 "inprogress"

Limit on task downloads?

There is a limit on the number of workunits you can download and he is way over it. That seems like a bug in BOINC. Not sure what happened there, but is seems pretty rare. If it seems to happen more consistently, I will look into it a bit more.

Jake

That host is from Gridcoin and it was probably ninja installed on someone else's computer for profit w/o them knowing. Def should be banned. Seen way too many errors from Gridcoin users across all projects.

If the BOINC version is 7.0.80 then the user knowningly allowed the software to download but does not realize that they are actually mining gridcoins with the coins going here

Host 643627 does not seem to be gridcoin related. I assume it is just stupidity. Never attribute to malice what can be explained by stupidity. FWIW, I agree the host should be banned.

That host is from Gridcoin and it was probably ninja installed on someone else's computer for profit w/o them knowing. Def should be banned. Seen way too many errors from Gridcoin users across all projects.

If the BOINC version is 7.0.80 then the user knowningly allowed the software to download but does not realize that they are actually mining gridcoins with the coins going here

Host 643627 does not seem to be gridcoin related. I assume it is just stupidity. Never attribute to malice what can be explained by stupidity. FWIW, I agree the host should be banned.

Yes, is member of team gridcoin but not using grcpool. Found that out too late to edit my post. If on grcpool (like I am) one is not the owner of the project and cannot access the project page to make changes. Items like selecting the proper sub-project are much more difficult as the account manager cannot be used.

Hey Everyone,

I just tried turning on some options to reduce workunits sent to hosts that return a significant number of errors. If you see any issues, please let me know.

Thank you all for your continued support.

Jake

Jake, I wonder that by turning on some options might also have effected New Clients and or clients that have not retuned a value for some time. Like in my case where I have not contibuted to Milkyway for about a year and most of my machines been upgraded since, than that could be the reason for not receing WU's. My GPU's working OK on other Projects. Note that other users have reported this issue in other threads but have not received a reply to date.

N.B. Please read to forum: Number Crunching: Not able to download work for AMD GPU and further down: Unable to download work for NVIDIA GPU. The troops are restless as they have not received one word from any Admin for days.

How about we get more than 80 WUs per machine for reliable machines please? When there's issues we run out of WUs fairly quick. At least double it to start as a test.

Starting yesterday, the server is supplying my mac minis with GPU tasks that they cannot process, in spite of my BAM parameters specifying do-not-use-Nvidea-GPU. The only remedy so far is to suspend GPU in the BOINC client, but the server still feeds me a supply of GPU tasks that then just sit there. How can I get the server to honor BAM?

Starting yesterday, the server is supplying my mac minis with GPU tasks that they cannot process, in spite of my BAM parameters specifying do-not-use-Nvidea-GPU. The only remedy so far is to suspend GPU in the BOINC client, but the server still feeds me a supply of GPU tasks that then just sit there. How can I get the server to honor BAM?

Try going into your MilkyWay website settings and turning them off, this may be a time when Bam and MW don't talk to each other.

I have done that. The problem there is that it is a global setting, so my client that CAN process GPU WUs is now cut off also. This needs to be fixed, not just for my benefit, but also because it is responsible for a large number of failed WUs and the "creation" of unreliable hosts. I have over 700 errors in just a few minutes from machines that were previously processing error free.

I have done that. The problem there is that it is a global setting, so my client that CAN process GPU WUs is now cut off also. This needs to be fixed, not just for my benefit, but also because it is responsible for a large number of failed WUs and the "creation" of unreliable hosts. I have over 700 errors in just a few minutes from machines that were previously processing error free.

Put the pc that can do gpu's in a different venue work, school or home, instead of the default then. I do that all the time when I have different pc's doing cpu or gpu projects. I don't like doing both cpu and gpu workunits from the same project on the same pc, they workunits are different lengths and cause cache problems for me. So I put pc a in the default of no gpu units by yes to cpu workunits, and pc b in home and allow gpu units but no cpu workunits.

Put the pc that can do gpu's in a different venue work, school or home, instead of the default then. I do that all the time when I have different pc's doing cpu or gpu projects. I don't like doing both cpu and gpu workunits from the same project on the same pc, they workunits are different lengths and cause cache problems for me. So I put pc a in the default of no gpu units by yes to cpu workunits, and pc b in home and allow gpu units but no cpu workunits.

Excellent idea! I have adopted this workaround, and it seems to be the solution to my problem. Thanks.

I still believe that the project's failure to honor BAM's parameters (without warning) may be the root of the "unreliable host" problem. The only reason my failed WU count is in the hundreds, instead of thousands, is because I happened to look at the affected machines on the day of the change. Many machines run unattended and churn out errors unnoticed, until they are identified as unreliable and banned.

Could we increase the tasks sent to reliable hosts? A GPU only gets an hour's work so BOINC keeps going off to my backup project.