I usually run Seti/AP fairly blindly. Logging in I notice that a string of wu were issued on Nov 5 that ended with No Reply. One Ap is still in progress. Since I don't have this wu then it too will time out. I didn't have any issues on my end that I know of, or did I?

http://setiathome.berkeley.edu/workunit.php?wuid=359746449

---

This happens occasionally, usually during periods when the servers are playing up or in the recovery period after an outage.

It has been discussed frequently, the last thread is tasks assigned, not downloaded

Well that does explain how it could have happened. I do watch the messages in the manager and do see the "communication failed" often enough. Technical News lists the scheduler as having trouble on that night, so it may have been the issue. Can the AP wu that is still waiting to timeout be stopped instead of waiting five more days for it to timeout?

---

If it hasn't actually been downloaded to your system, then it simply has to time out.

---

Ok just trying to speed things up if possible. Thanks for the quick responces

---

Well that does explain how it could have happened. I do watch the messages in the manager and do see the "communication failed" often enough. Technical News lists the scheduler as having trouble on that night, so it may have been the issue. Can the AP wu that is still waiting to timeout be stopped instead of waiting five more days for it to timeout?

Ghosts can be released, but I don't think the method makes sense for your case. Here it is, though, for future reference:

1. Set No New Tasks for the project.
2. When all tasks you actually have are finished and uploaded, use the Update button to report them.
3. Detach from the project.
4. Reattach to the project.

When you reattach in the final step, the Scheduler will mark any ghosts with a "Client detached" outcome and send reissues to other hosts.

                                                               Joe

In my own case...my xp pro (32bit) box is doing fine...

but my vista 64bit one has not had new wu's for weeks.

If I cant figure it out by end of year, will go ahead and uninstall seti.

Its getting a pain in the but, where litterally every version upgrade seems to cause hiccups enough to make seti not worth the time.

But I am figuring that a version upgrade is what has caused it to fail.

---

try detaching it and the reattaching to the project... might work...

---

Post the first 20 lines of the message tab right after you start up BOINC, that way we can tell what might be going on with it.

---

In my own case...my xp pro (32bit) box is doing fine...

but my vista 64bit one has not had new wu's for weeks.

If I cant figure it out by end of year, will go ahead and uninstall seti.

Its getting a pain in the but, where litterally every version upgrade seems to cause hiccups enough to make seti not worth the time.

But I am figuring that a version upgrade is what has caused it to fail.

Restart Boinc and post the initial messages that the manager gives you.....might let us figure it out.....

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Post the first 20 lines of the message tab right after you start up BOINC, that way we can tell what might be going on with it.

LOL...beat me by a minute or so....

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

We know what to look for, at least those of us who post a lot on the board.

---

dont quite remember what happend...but all the sudden its back in full force.

to be honest the only thing i remember doing is reseting it...
but even then it was two-three days later that it seemed to be ok for now.
And even then it was the 3rd time I reset it.

After nearly a month or so of dead time...all the sudden.

---