I've just started getting this message, which is followed by "If this happens repeatedly you may need to reset the project."

Does anyone have any ideas on what's going wrong/ workarounds etc? For future reference, what's the consequences of resetting the project? Do you lose your record of work done and credits etc. (not that I've had any credit downloaded yet, but I'm told that "All good things......")

I'd appreciate any help or advice that people could give

Hattra

For future reference, what's the consequences of resetting the project? Do you lose your record of work done and credits etc. (not that I've had any credit downloaded yet, but I'm told that "All good things......")

A reset deletes only the WU's in your project but does not delete credits.

A Boinc manual can be find here.

Greetings from Belgium.

Help Desk: use "Most recent answer first" sorting.

I saw this same error on my computer.

I reset the project.

The two work units in process were deleted and two new ones were download.

After that everything went back to normal.

The new work units completed with no errors.

No credits were lost.

SETI@home - 2004-09-23 20:48:37 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-09-23 20:49:52 - Result 06my04ab.10554.12128.909646.251_1 exited with zero status but no 'finished' file
SETI@home - 2004-09-23 20:49:52 - If this happens repeatedly you may need to reset the project.
SETI@home - 2004-09-23 20:49:54 - Restarting result 06my04ab.10554.12128.909646.251_1 using setiathome version 4.03

This box is running XP home with SP2 installed. P4 1.9Ghz, 256mb RAM.

Any news on this problem yet?


Visit Seti.org.uk


SETI News Mailing List


[/url]

I've been running into the same problem since I (recently) upgraded to v4. It started doing this repeatedly, so I reluctantly reset the project. After waiting for the scheduler to restart so it could give me new work, I find that the new work is also beginning to give me the same message.

I wasn't having any such trouble under 3.x, and this sounds to me like an actual problem (not just a warning to be ignored). I'm running S@H w/CC 4.09 on AMD 1.2Ghz under Win98. Does anyone have any comments?

Have same problem 1 machine.
have reset project,three times.
have uninstalled and installed anew boinc 4.09
and getting message again.
so I did the drastic, reinstall windows98 from scratch
different machine name, installed boinc
and its f**n doin it again.
machines are 3300 2800 2100 AMDs win98 Zonealarm, Router, Cable.
the problem mach. the 2800 M-3 formerly mom, has done 5 or six seti wu per day for a few weeks.
as mom it was never listed under my computers @lhc.

I have had this come up once or twice. I just restarted the client and/or computer and it got that workunit back into a usable state, and continued on from there.

John Keck -- BOINCing since 2002/12/08 --

In addition to this error situation, on my Windows 2000 installation, the screensaver no longer works. In fact, if the screensaver kicks in, my system becomes unusable. The screen goes white, and there are two BOINC windows listed, one marked as Default, the other I believe as screen saver. No matter what I do, the screen will not recover from the white out, except that the Windows application manager/bar (Explorer) is visible. Trying to force BOINC to close (via Task Manager) has no effect, and I can't even get Windows to restart without forcibly terminating the PC's power. (My reset button happens to be non-functional due to broken wire.) Hard disk usage is usually very high during these times.

Prior to the last occurance of this problem, BOINC was trying to remove at least two files in its directory, but I have no idea what they might have been except to say they seemed large. Windows was taking an extremely long time to fulfill the deletion request.

BOINC seems to operate normally under Fedora Core 2 Linux on the same machine.

PC:
Dual Pentium III 500 mhz
512 MB RAM
Windows 2000 Service Pack 4
Fedora Core 2 Linux
90 GB+ hard disk space, 10-15 GB free

Similar problem. running Boinc 4.09 and find the problem most, but not all times that my portable comes out of "stand by" state (suspend -but not hibernate).
Happens with both SAH and CPDN.
When I see it, the machine is still processing a unit. For SAH I don't know if that unit retarted or carried on from previous session. However, I can say that for CPDN it doesn't loose all of its previous work (I suppose that it might have lost the last partial or incremental addition to the work unit results, but I don't know.)

Moreover, for SAH its no big deal -you maybe loose an hour or 3... but this now makes me very reluctant to do a reset as I/CPDN would loose quite a bit of built up time on the current CPDN workunit. If it has to happen, c'est la vie, but ...
...I would appreciate guidance as I don't know if this represents a serious defect in the work my machine is running or the efficiency of the way that it is running, or if it is just a nuisance.

i to have just recievd this error witht he following info,

SETI@home - 2004-10-06 17:09:53 - No schedulers responded
SETI@home - 2004-10-06 17:09:53 - Deferring communication with project for 1 hours, 43 minutes, and 14 seconds
climateprediction.net - 2004-10-06 17:31:51 - Pausing result 1vh4_000108340_0 (left in memory)
SETI@home - 2004-10-06 17:31:51 - Resuming result 06my04ab.9911.27906.223570.83_3 using setiathome version 4.05
SETI@home - 2004-10-06 18:09:53 - Deferring communication with project for 43 minutes and 14 seconds
SETI@home - 2004-10-06 18:18:33 - Result 06my04ab.9911.27906.223570.83_3 exited with zero status but no 'finished' file
SETI@home - 2004-10-06 18:18:33 - If this happens repeatedly you may need to reset the project.
SETI@home - 2004-10-06 18:18:51 - Restarting result 06my04ab.9911.27906.223570.83_3 using setiathome version 4.05
climateprediction.net - 2004-10-06 18:18:56 - Result 1vh4_000108340_0 exited with zero status but no 'finished' file
climateprediction.net - 2004-10-06 18:18:56 - If this happens repeatedly you may need to reset the project.

as you can see this happend to both projects so im pritty sure its boinc core related and not project related, allso checkd event viewer and found no data on the problem and no abnormal operations at the time, system just became unresponsive for 20 minutes or so, allowd pc to recover on its own and thats where im at now, i have over 250 hours investid in cpdn and realy dont want to have to reset it, anyone have a clear cut answer to this?

runing
win xp sp2
512MB pc 2100 sd ddr ram
2.0ghz celeron
hp pavilion model 533w


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Pain dosen't hurt, when it's all you have ever felt"

Everytime my laptop comes out of hibernation I get the same error. Sometimes the progress on the workunit goes to 0% but sometimes SAH just continues from where (I assume) it stopped when I hibernated my computer. I have WinXP SP1. I think this started with client version 4.03. I have tried reseting the project, but it hasn't helpped...

I received a similiar error:


SETI@home - 2004-11-23 21:08:17 - Restarting result 08ap04aa.750.7986.573572.44_0 using setiathome version 4.08
climateprediction.net - 2004-11-23 21:08:17 - Pausing result 1z32_100113065_4 (left in memory)
SETI@home - 2004-11-23 21:28:00 - Result 08ap04aa.750.7986.573572.44_0 exited with zero status but no 'finished' file
SETI@home - 2004-11-23 21:28:00 - If this happens repeatedly you may need to reset the project.
SETI@home - 2004-11-23 21:28:03 - Restarting result 08ap04aa.750.7986.573572.44_0 using setiathome version 4.08
climateprediction.net - 2004-11-23 21:28:52 - Result 1z32_100113065_4 exited with zero status but no 'finished' file
climateprediction.net - 2004-11-23 21:28:52 - If this happens repeatedly you may need to reset the project.

On this occassion BOINC just continued on with the unit. This sort of thing happened before also.

System Specs:
Windows XP Home SP 2
Intel P4 @ 1.5 Ghz
256 MB SDRAM

---

<p>
<img src="http://www.infinisoft.34sp.com/boinc/signature.php?project=sah&amp;id=7813418" border="0" />
</p>

This happened regularly to me, but I have since found that changing the time between hard disk writes (from 5 minutes to 1 minute) in the Preferences section fixed the problem - it hasn't occured since on my computer...

I have just started using SETI@HOME on BOINC.
I have has this error on two WinXP SP2 AthlonXP machines.
It has happened to four out of five of the work units I have downloaded.
I suspect it is the setiathome executable crashing during processing, leaving no results file. Anyone suggest how we get this reported to the dev team and what information they might neeed to do a forensic diagnosis?
I have tried resetting the project - awaiting results.

BOINC Client 5.4.11
setathome enhanced 5.15
Microsoft Windows XP [Version 5.1.2600]

---

I have just started using SETI@HOME on BOINC.
I have has this error on two WinXP SP2 AthlonXP machines.
It has happened to four out of five of the work units I have downloaded.
I suspect it is the setiathome executable crashing during processing, leaving no results file. Anyone suggest how we get this reported to the dev team and what information they might neeed to do a forensic diagnosis?
I have tried resetting the project - awaiting results.

BOINC Client 5.4.11
setathome enhanced 5.15
Microsoft Windows XP [Version 5.1.2600]

None of the results showing has the message, however in the vast majority of cases where the "...may have to reset the project." message occurs on the message tab it is not necessary to do that.

When you see this happen, take a look at the stderr.txt file in the slot directory where the result is running. Most likely you will see a message from the science app that there was No Heartbeat from the client for 31 seconds, so it exited.

This is normal designed in behaviour to prevent the science app from running "wild" if the core client crashes for some reason. However, if the host gets busy doing other things it can cause the internal heartbeat to get blocked long enough to trigger the exit, even if the client is running fine. Once the blocking condition clears, the client sees what it thinks was an "abnormal" app exit (since the app isn't running anymore, the client didn't tell it to stop, and there's no output data file), posts the warning message, and restarts the app.

HTH,

Alinator