Subject: Re: No work?
From: "Zilva Zanga" <pretender@home.com.invalid>
Date: 01/07/2005, 15:30
Newsgroups: alt.sci.seti

"Cernnunos" <cernnunos2NO@SPAMMERSntlworld.com> wrote in message 
news:qhb2c11htnposvqkbqnqmg4r9s2mk5d9ts@4ax.com...
On Tue, 28 Jun 2005 10:39:44 GMT, Cernnunos
<cernnunos2NO@SPAMMERSntlworld.com> wrote:

Hi All

I haven't run BOINC (4.45) for a few days (maybe even a week), and
when I started it up yesterday, I noticed I had no work units to work
on.  I have checked through the hard drive and there is no work in the
directory at all.  I run climateprediction.net along side SETI, and
that's working fine, but even when I force an update on SETI, I get
the following message

28/06/2005 10:38:59||request_reschedule_cpus: project op
28/06/2005 10:38:59|SETI@home|Sending scheduler request to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
28/06/2005 10:38:59|SETI@home|Requesting 0 seconds of work, returning
0 results
28/06/2005 10:39:00|SETI@home|Scheduler request to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

Any body got any ideas?

Also, I'm about to re-format the hard drive (as well as make some
major changes to the system).  Can I just re-install BOINC then copy
the old (project specific) files across?  I used to be able to simply
swap folders between backup hard drive or computer.

Thanks for any help given.

Andy

Hi again

Well the first part of my problem has suddenly disappeared.

28/06/2005 11:39:00|SETI@home|Sending scheduler request to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
28/06/2005 11:39:00|SETI@home|Requesting 604800 seconds of work,
returning 0 results
28/06/2005 11:39:02|SETI@home|Scheduler request to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
28/06/2005 11:39:03||Using earliest-deadline-first scheduling because
computer is overcommitted.

Now I just need help with the re-format issue.

Andy

Although you've resolved your wu problem, think about running other projects 
besides SETI. Although each project is down from time to time, I've yet to 
encounter a problem with all the project servers down all at the same time.