I think the scheduler is at it again and giving out phantom WUs.

---log---
5/26/2005 11:21:47 AM|SETI@home|Requesting 172800.00 seconds of work
5/26/2005 11:21:47 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
5/26/2005 11:21:48 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
5/26/2005 11:21:48 AM|SETI@home|No schedulers responded
5/26/2005 11:21:48 AM|SETI@home|Deferring communication with project for 2 minutes and 6 seconds
5/26/2005 11:23:55 AM|SETI@home|Requesting 172800.00 seconds of work
5/26/2005 11:23:55 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
5/26/2005 11:23:56 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
5/26/2005 11:23:56 AM|SETI@home|Message from server: Not sending work - last RPC too recent: 128 sec
5/26/2005 11:23:56 AM|SETI@home|No work from project

---end log---

I have 12 phantoms now, and haven't seen anything new for at least 24 hrs.

I'm also seeing quite a few master file fetch fails.

I would suggest everyone check their accounts.

I think the scheduler is at it again and giving out phantom WUs.

More likely the client bug.
Check your processes in task manager and you'll probably find the boinc.exe process running at a high CPU value.
Stop BOINC, wait for all science apps to gracefully quit (watch task manager) and restart BOINC. This should resolve your problem.

---

I think the scheduler is at it again and giving out phantom WUs.

More likely the client bug.
Check your processes in task manager and you'll probably find the boinc.exe process running at a high CPU value.
Stop BOINC, wait for all science apps to gracefully quit (watch task manager) and restart BOINC. This should resolve your problem.

I've seen this happen before, not only on this project but others as well (predictor and LHC come to mind as the most recent), usually the scheduler is overloaded or the pipes to the servers are dropping packets.

---