Actually at home right now (I usually don't come in on Fridays - for my own sanity). Still, just for the record even when I'm not in the lab I do check in from time to time and I noticed we were draining work. So before the queue ran to zero I started more splitters. This is good and bad: we're filling the ready-to-send queue, but at the expense of throttling the work we are able to send out. So be it. I'm keeping my eyes on it (when taking breaks from cleaning out my basement) so don't fret...

- Matt

As some of you who installed 5.00 have experienced, some code that checked the major version of the client was left in the scheduler. It was supposed to have been removed months ago.

I have fixed the bug. However, the delta from when a server-side bug is fixed to when the various projects update the server-side components is generally a few weeks.

So that we can continue to stabilize the client and give the projects time to update their server-side software we have pulled the 5.00 release and reset our version to 4.70.

I know our previously stated policy was that versions x.50- x.99 were supposed to be development versions, but waiting until all the projects have updated the server-side code at the rate at which we intend to stabilize and release the client would cause a few problems and sleepless nights for a few people. So in the interest of all parties we are breaking our own policy.

On a happier note: It looks like when we start the next release cycle we’ll be using the Linux versioning system. I think that’ll take care of a bunch of issues related to how clients are released and peoples expectations of what has changed between releases.

Its difficult to pinpoint a problem with just error messages.

Install and run a network tracer like Ethereal and take a look at whats actually being returned. Theres eight seconds between the a request and reply, so something did come back. Just not what BOINC was looking for. Knowing what that reply is, and where it came from would really help towards understanding the problem.

Regrettably I do not know how to use said tracer, but looking at the messages below I am concerned that having changed my preferences from 5 days to 10 days just to see if I can get another workunit it recognised the change but then requested 0 work units, I now believe that there is a bug in BOINC 4.45 or that the process of uninstalling the previous version of BOINC and reinstalling the new version left a conflicting file somewhere.

Towards the begining of the messages it says '27/06/2005 18:43:34|SETI@home|Resuming computation for result 29fe04aa.10628.30560.847158.62_2 using setiathome version 4.18' but I have BOINC v4.45 installed, does that give a clue? Moreover, having downloaded 4 workunits after my reinstatement of climate prediction why did it stop again?

Pierre, I was replying to a message from Joseph Keene, about his connection problems starting again.

Looking at your logs, I don't see anything network related. Which is what Ethereal is for.

On your "requesting 0 seconds of work", if you look at the log you'll see this:

27/06/2005 18:43:34||Suspending work fetch because computer is overcommitted.
27/06/2005 18:43:34||Using earliest-deadline-first scheduling because computer is overcommitted.

Says you too much work already, so it won't download more.

Mr Keene,
i was the one who suggested trying another project.
we now know that it is not a boinc.exe issue, nor firewall. sadly, i am not sure what else it might be.

just things to try:

First, make a complete copy of the boinc folder into a safe place. if still no luck, you can just revert back.

you could uninstall and reinstall the current version, possibly a corruption

i do not know if you have tried it, but have you reset the project?

i also see from the first post that this was an upgrade? was the problem present before? maybe you still have the install file from your previous version? if not, i could come up with the link or file. (you should be able to just change the version # listed on the current d/l link to the version you want)

if i think of anything else to try, i'll let you know.

Micah

Hey Pierre could you cut n paste your preference to this post it may help.

...I cannot see any of the past work, even though I have been a seti@home member since 1999.

Here, http://setiathome.berkeley.edu/show_user.php?userid=375814, you show SETI BOINC credit of 5,859.25. 5,200.85 credits on computer ID 453566 and 658.40 credits on computer ID 486058. You also show, as of March 15, 2005, 800 SETI@home classic workunits and 8,948 hours SETI@home classic CPU time.

What past work isn't showing?