Can someone please let me know what causes this? I seem to get this at various times so I am not sure what is causing this

---

It means the seti client stopped for some reason, but before it finished analyzing the data. BOINC usually just restarts seti and it continues processing the same WU.

Usually it this: "No heartbeat from core client for 31.000000 sec - exiting" meaning the BOINC wasn't communicating with seti anymore , so it (seti) exited.

Seti writes an appropriate error message to its stderr.txt file so you can look there. Not BOINCs stderr.txt file, seti uses a folder in the slots folder, slots/0 or maybe some other number depending. And BOINC sends the error messages along when it "reports" the result, so you can check your results if you want to see what the message was.

That was the exact message I had in there. Is there any way around it or is it just part of the way the program works?

> It means the seti client stopped for some reason, but before it finished
> analyzing the data. BOINC usually just restarts seti and it continues
> processing the same WU.
>
> Usually it this: "No heartbeat from core client for 31.000000 sec - exiting"
> meaning the BOINC wasn't communicating with seti anymore , so it (seti)
> exited.
>
> Seti writes an appropriate error message to its stderr.txt file so you can
> look there. Not BOINCs stderr.txt file, seti uses a folder in the slots
> folder, slots/0 or maybe some other number depending. And BOINC sends the
> error messages along when it "reports" the result, so you can check your
> results if you want to see what the message was.
>
>

---

> That was the exact message I had in there. Is there any way around it or is it
> just part of the way the program works?

Its the way it works. So if BOINC goes away without notifying the seti program (like if BOINC crashed) the seti program won't stay running forever. Just that there are some things that can interfere with BOINC so while its still running it doesn't get any CPU cycles to actually do anything.

Since the WU gets restarted OK don't worry about it.

Ok, that is fine, I was just afraid that I had been getting alot of corrupt WU's or that they were getting corrupted while on my computer.

Thanks all for the reply

> > That was the exact message I had in there. Is there any way around it or
> is it
> > just part of the way the program works?
>
> Its the way it works. So if BOINC goes away without notifying the seti
> program (like if BOINC crashed) the seti program won't stay running forever.
> Just that there are some things that can interfere with BOINC so while its
> still running it doesn't get any CPU cycles to actually do anything.
>
> Since the WU gets restarted OK don't worry about it.
>
>

---