2004-11-15 15:01:52 [SETI@home] Result 07mr04ab.6777.6690.192314.205_3 exited with zero status but no 'finished' file
2004-11-15 15:01:52 [SETI@home] If this happens repeatedly you may need to reset the project.
2004-11-15 15:01:52 [SETI@home] Restarting result 07mr04ab.6777.6690.192314.205_3 using setiathome version 4.02

This ALWAYS happens when processor 1 uploads a workunit. Whenever CPU 1 uploads, CPU 0 restarts. Percentage done stays as it was before, but CPU time starts from 0 therefore CPU 0 always claims too little credit (given that claimed credit is a function of time and benchmark results).

---

bump.

Usually restarting BOINC or the computer will get these things running again.

---

BOINC WIKI

BOINCing since 2002/12/8

I get these too, only on the SMP box. Sometimes it works the other way such
that one CPU inherits the current CPU time from the other, producing inflated
times and giving more credit than what is called for lol. Suppose it all evens
out in the end hey. Im not sure if this has been submitted as a bug or not.

Mark

> Usually restarting BOINC or the computer will get these things running again.

Wishful thinking, I'm afraid. This has been an on-going problem, and it has not been addressed.

I get this message every single time the client connects to the server. Something in the process of making the TCP/IP connection "stalls" and causes the client to time out.

Restart. Remove BOINC, remove all BOINC directories and registry keys, reinstall BOINC. Nothing helps. It's a software bug.

I'm running on WinME, Single-CPU Intel P3, 512MB RAM.

Luckily, the WU seems to recover and run to completion, so the net effect is a bloated log file.

But it's still a bug.

Jim

> Wishful thinking, I'm afraid. This has been an on-going problem, and it has
> not been addressed.

I'd rather not post the same thing all over the place, so I have made a note regarding this problem here.

---

> > Wishful thinking, I'm afraid. This has been an on-going problem, and it
> has
> > not been addressed.
>
> I'd rather not post the same thing all over the place, so I have made a note
> regarding this problem <a> href="http://setiweb.ssl.berkeley.edu/forum_thread.php?id=6620#48101">here[/url].
>


ralic,

unfortunately I cannot agree with what you write:

I get the same error on my Mac. This ALWAYS happens when processor 1 uploads a workunit. Whenever CPU 1 uploads, CPU 0 restarts. Percentage done stays as it was before, but CPU time starts from 0 therefore CPU 0 always claims too little credit (given that claimed credit is a function of time and benchmark results).

Your explaination is NOT valid here, since there is no grapic modul for the Mac version at all - just a command-line client, no graphic, no screensaver.

Although it might not influence the analysis or validity of any work it does influence stats since CPU 0 always starts from 0 seconds elapsed time and therefore claims too little credit. http://setiweb.ssl.berkeley.edu/forum_thread.php?id=5861#38764

---

@Martin P.

Since you're using a mac, do you object if we continue this discussion here, and not in the number crunching forum?

I don't own a mac, but would like to try and help resolve your problem. Continuing the discussion in the mac forum may hopefully spark some interest from the mac guru's...

---