I have a PABLO_redo_goal_RMSD2_KIX_CMY task I think I have figured out it is swamping my normal Seti work requests on the host it is on.

It has run for 3 hours so far and is projected to run for another 4.45 hours. When I run sched_ops it is shown to be have more shortfall than Seti. That should never happen with my resource split for Seti at 900 and GPUGrid at 50.

Anybody else run this task type yet? Run into problems? I have figured out if I suspend GPUGrid then Seti is able to ask for its normal amount of work to keep the caches up.

This has had me stumped all afternoon after Seti came back from outage yet my task cache continued to fall and my Seti gpu work requests were for pitiful amount of seconds. I did not know whether the upgrade in the graphics drivers had anything to do with it or coincidence.

Comments?

I have run those work units but you know I run dedicated machines for each project so I will not be able to comment on the swapping. Hopefully someone else will be able to help you with this.
____________

Something is major going wrong on this host. I can't maintain my Seti gpu cache. It is not requesting any gpu work.

This has had me stumped all afternoon after Seti came back from outage yet my task cache continued to fall and my Seti gpu work requests were for pitiful amount of seconds. I did not know whether the upgrade in the graphics drivers had anything to do with it or coincidence.

Comments?

I normally only have a maximum of 6 long/short tasks on any host at any time. That is what my 1 day cache and 900/50 Seti/GPUGrid resource share split nets me. I either have 400 or 500 Seti tasks on board all the time on each of my hosts. None of my other hosts had any troubles with getting work. Only the 477434 host was having issues. I think the scheduler has messed up that host as I show 12 tasks in progress so 6 of them are 'ghosts' and I am pretty sure that is what messed things up. So BOINC thought I had much more GPUGrid work than I actually have. I only have 6 actual tasks on board that host like normal.

I aborted the suspect long running task that the thread title is about and that didn't have any effect. I aborted a couple others and received some short tasks in return and that didn't help. Only when I suspended the project did I finally regain the ability to request Seti gpu work.

The solution was to reset the project on that host and that cleared things up and back to normal except now I have the 6 ghost tasks. Hope they clear from the database once the deadline is reached early next month.

These are the 'ghost' tasks.
https://www.gpugrid.net/result.php?resultid=19811972
https://www.gpugrid.net/result.php?resultid=19812931
https://www.gpugrid.net/result.php?resultid=19815503
https://www.gpugrid.net/result.php?resultid=19818063
https://www.gpugrid.net/result.php?resultid=19820978
https://www.gpugrid.net/result.php?resultid=19830474

The "ghost" task issue is perplexing. The GPUGrid task scheduler seems to ignore cache settings and sends a max of two jobs per gpu installed on any given system if tasks are available. In your case with 4 tasks (2 ghosts) per gpu, I can see why you are not receiving WU's from Seti as you pointed out.

In the past I had what I believe you are describing as ghost tasks from WCG (cpu work) appear rarely on several machines. The issue showed up as a completed task ready to send but WCG was not aware that the task existed. I never got credit for it and it persisted for months until I finally gave up trying to locate the problem. As I recall, I suspended receiving new tasks with all projects and when my cache was empty, I re-installed boinc and re-registered the new client with the projects and that cleared things up. Actually, I think re-installing boinc is a bit of overkill as there must be a xml file containing information that the WU exists and ready to send but the other xml files that schedule the upload are not including that particular task so it never gets picked up. That was several years ago and hasn't happened since with any project.

I am sure that if you empty you queue, remove boinc and then do a fresh install the ghosts will be gone but again, you may want to see if you can locate and edit the file(s) showing the ghost jobs first. If you find them, would you please report back which ones are the culprits? Good luck.

By resetting the project I got rid of the "ghosts" in the client_state.xml file. That allowed BOINC to correctly assess each project credit debt so that I could once again start receiving Seti tasks again.

That does nothing for the scheduler database though. If a project allows "resend lost tasks" as Seti does for example there is a way to get the lost tasks resent to the host. You have to use a specific technique to get them resent. I don't know if GPUGrid has that turned on in the scheduler software or not. It is up to the administrators to enable that. You as user have no control.

Once I reset the project, all remnants of the "ghost" tasks were removed from the client_state.xml file so no chance of recovering them now. Now just have to wait for the task deadlines to clear them from my account database.