Questions and Answers :
GPU applications :
Work units not starting
Message board moderation
Author | Message |
---|---|
Mr. Theta Send message Joined: 3 Apr 99 Posts: 3 Credit: 1,073,212 RAC: 0 |
BOINC has suddenly stopped running my SETI@home work units. It downloads them properly and says they are "Ready to start," but never actually starts them. This is true even if I pause my other projects. I have tried detaching from SETI@home and reattaching, with no success. I am running BOINC version 6.4.5, using the CUDA version of SETI@Home (obviously, from the thread section), and not using Astropulse. If anybody has any ideas about what might be going on, I would be very grateful to hear them. Please let me know if you need more information. |
Tribble Send message Joined: 21 Feb 02 Posts: 65 Credit: 7,978,002 RAC: 0 |
I am having the same issue now as well, they are all at 'Ready to start' |
Tribble Send message Joined: 21 Feb 02 Posts: 65 Credit: 7,978,002 RAC: 0 |
Oh I manually killed all 3 BOINCE processes and they resumed. |
Rick A. Sponholz Send message Joined: 13 Jun 99 Posts: 43 Credit: 23,179,807 RAC: 0 |
I am also experiencing occasional stopping, and not restartable CUDA work units, just a few instances on one (Computer #4 below) CUDA capable machine. Even if I suspend the hung work unit, no other CUDA work unit starts. Re-booting did not help, but completely shutting the computer down, then restarting the computer resulted in the work unit restarting. This happened to GGPUGrid, and SETI@Home work units. The issue above is different than the hanging SETI CUDA work unit problem well documented in other threads. I have 5 CUDA capable computers (Windows XP Service Pack 3) and I'm running SETI@ Home (CUDA 6.08 on BOINC 6.6.7) (also GPUGRID) on all 5, as well as World Community Grid, & Einstein@home. I've been running CUDA since BOINC 6.4.5 was released. I have also been using each test version of BOINC above 6.4.5 as soon as each version came out. Only since I upgraded to BOINC 6.6.7 have I had the above problem, but I'm not sure if the two events are linked. Below are the specs for my 5 CUDA capable computers: #1 Intel Core 2CPU 2.40Ghz 1.98GB RAM GeForce 9600GT 512RAM Driver 6.14.11.8122 #2 Intel 2 Quad 2.40GHz 1.98GB RAM GeForce 9800GTX+ 512MB RAM Driver 6.14.11.8122 #3 Intel 2 Quad 2.40GHz 1.98GB RAM GeForce 9600GT 512MB RAM Driver 6.14.11.8122 #4 Intel 2 Quad 2.83GHz 1.98GB RAM GeForce 9600GT 512MB RAM Driver 6.14.11.8122 #5 Intel 2 Quad 2.83GHz 3.25GB RAM GeForce 9800GT 1.024GB RAM Driver 6.14.11.8122 |
Rick A. Sponholz Send message Joined: 13 Jun 99 Posts: 43 Credit: 23,179,807 RAC: 0 |
Now computer # 5 abruptly stopped running CUDA work units too:-( |
Rick A. Sponholz Send message Joined: 13 Jun 99 Posts: 43 Credit: 23,179,807 RAC: 0 |
It appears as though BOINC 6.6.7 actually attempts to change CUDA applications every 60 minutes like the CPU aps. But what's happening is the first work unit getting switched from, never restarts. After the switched to work unit completes, BOINC goes to a new work unit, and not back to the first task, even when it results in a late completion of the original task. I've only had this problem with BOINC switching from GPUGRID to Seti (then BOINC never goes back to GPUGRID). At least for me, having each CUDA work unit complete once started worked much better anyway. Just my opinion. Rick |
Mr. Theta Send message Joined: 3 Apr 99 Posts: 3 Credit: 1,073,212 RAC: 0 |
Oh I manually killed all 3 BOINCE processes and they resumed. Thanks! The same thing worked for me. I'm not sure what the policy for closing threads is. Should I leave this one open since we don't know what the actual problem is, just a workaround? |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
The proper way to kick stuck workunits without corrupting the data is to exit (or stop the service of) BOINC. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
It appears as though BOINC 6.6.7 actually attempts to change CUDA applications every 60 minutes like the CPU aps. {snip} If forwarded this to the BOINC developers. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
The proper way to kick stuck workunits without corrupting the data is to exit (or stop the service of) BOINC. And restart it (Start->Programs->BOINC->BOINC Manager). ;-) |
Mr. Theta Send message Joined: 3 Apr 99 Posts: 3 Credit: 1,073,212 RAC: 0 |
Thanks everybody! Now that the problems have been resolved or forwarded to the proper channels I will close the thread. UPDATE: Never mind, evidently clicking 'My question was answered' doesn't close the thread. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.