I check Boinc once a day just to make sure it's going, and now I notice it's frozen. The messages say that it's resuming a Seti unit, but the timer is frozen at 6 minutes and 25 seconds and it shows 0.00% done in the indicator.

I tried rebooting, but I get the exact same thing. It's not a preferences thing because I set Boinc manually to run always to check this. Still frozen. Any ideas? I'd hate to have to reset Seti.

http://img22.exs.cx/img22/1998/seti8ov.jpg

---

-----

It was just sitting there, so I reset Seti. Now it's going fine. Nothing else I could do.

---

-----

Had this problem. Sometimes solved itself with time.
Once solved by exiting BOINC and deleting offending WU from BOINC_projects_setiathome.berkeley.edu directory.
Restart BOINC and after errors It’s all Good but your work on this WU is lost.
Good news is future GUI will have ability to Abort WU.
MattDavis, your CPDN progress is outstanding.

---

Yeah, since LHC and Predictor are down, my two active computers run only Seti and Climate. I've got 2 Climate units completely done, and the one in that screenshot is almost done too. It has 65 hours left, not over 300. I took that screenshot after a reboot and before Boinc started working on that unit again, so it has the incorrect "to completion" time.

---

-----

I've seen this a couple of times in the past week. Exiting Boinc and restarting worked in both cases and it picked up (crunching) at the same time (and same WU) where it had frozen.

Having the computer turned on all night, doing nothing, is not good.

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

I've seen this a couple of times in the past week. Exiting Boinc and restarting worked in both cases and it picked up (crunching) at the same time (and same WU) where it had frozen.
=========

Yes, I've come home from work or got up in the morning & have found 1 Pc Frozen in place on the Wu, usually a exit from BOINC and restart cured the problem ...

I rebooted the computer when it happened, but didn't exit Boinc first. If it happens again I'll be sure to exit Boinc first and then reboot.

---

-----

> I rebooted the computer when it happened, but didn't exit Boinc first. If it
> happens again I'll be sure to exit Boinc first and then reboot.
>
Matt,
First just try exiting Boinc and then retarting it. You may find you don't have to reboot your computer.

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

This "freeze" sounds similar to the problem I posted in the Linux Problems forum.

Within the last couple weeks, I had a CP WU complete on two different linux boxes. After uploading the results, and dowloading a new WU, boinc seemed to be confused and run both a seti WU and the new CP wu at the same time. (mono cpu systems)

This happened in the middle of the night, and when I saw it in the morning, the CP WU was still 0% complete with little or no CPU time, while the SETI WU was at 0.6% complete and 6 hours of CPU time! (seti completes on these systems normally in about 4 hours). Boincview had flagged the Seti WU's to "miss their deadline which was still 12 days away.

Rebooting brought everything back to normal. The new CP Wu seems to be the trigger, so I'll just insure that none will complete during the days I gone for the holidays.

---