The system is just 2 weeks old in a well airconditioned room. It's very strange because seti@home runs at full throthle, but the content of state.sah is missing and stays missing.
I don't know if it were bad WU's.  There are 2 cli's running (dual proc) and both did the same.


Martin wrote:

When I got the FreeBSD cli of seti@home running for a little while it stops processing. (But still using CPU) . The system processes 6 to 8 WU's per day, so it pretty urgent. Only when I throw away all files and run seti@home clean, it runs again.
Does anyone have an idea how to solve this?

Bad WUs downloaded? (<350k in length?)
Hit some sort of resource limit??

Link to the s@h server unreachable? (Try a ping)

Anything unusual in you log files? (See /var/log/*)

High heat? (Dead fan, dust, baking in the sun?)

Ants trying to make a nest in all the dust under your CPU and occasionally shorting out a CPU pin??

Various other wild guesses unless you'd like to offer a few clues!


Also, try running the CLI in verbose mode ("-verbose") and see what happens.

Good luck,
Martin