I've startet CP computing some time ago ... today i looked to results and I found that theer are only "Client errors" as Outcome ... so what can be wrong?

Also today in console i found:
2tl4_000152985 - PH 1 TS 012067 - 12/08/1811 09:30 - H:M:S=0027:37:04 AVG= 8.24 DLT= 3.89
2tl4_000152985 - PH 1 TS 012068 - 12/08/1811 10:00 - H:M:S=0027:37:33 AVG= 8.24 DLT=29.16

Model crashed...retrying...restart level 0
Preparing for restart...
Rewinding a model-day...
Starting model ID 2tl4_000152985 Phase 1
Stack size=48.00 MB
Waiting for model startup, this may take a minute...

few moments and:
2tl4_000152985 - PH 1 TS 011989 - 10/08/1811 18:30 - H:M:S=0027:42:12 AVG= 8.32 DLT= 3.97
2tl4_000152985 - PH 1 TS 011990 - 10/08/1811 19:00 - H:M:S=0027:42:41 AVG= 8.32 DLT=28.87

Model crashed...retrying...restart level 1
Preparing for restart...
Rewinding a model-month...
Copying restart files for model retry...
Starting model ID 2tl4_000152985 Phase 1
Stack size=48.00 MB
Waiting for model startup, this may take a minute...

what it is going wrong? crash after crash ... if it is not working or the client is buggy it has no sense to waste the power... :>

i'm using boinc 4.13 under GNU/Linux

---

When it encounters a processing anomaly, the Model rewinds a Model-day and retries. If it encounters a similar problem at the same place, it rewinds a Model Month and retries. If the same problem recurs, it rewinds a Model-year and retries. If it fails this time, it packs-up and sends the results home. This is by-design behavior.

The experts will check the results. Assuming the problem was not machine error, we're given to understand that these results can be as valuable to the project as completed routine runs. Scientists learn from what doesn't work as well as from what does work.

HTH.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Hi Panda Mala,

when looking at your stats, I would say it's a hardware failure (cpu or memory), though I'm not 100% sure.
You can test the cpu with mprime and some other progs. To test the memory you can use memtest86 (some linux cds have memtest as boot option, or download iso from www.memtest86.com --> burn on cd --> boot from it).
You can try to clock the FSB 1-2% down, if BIOS makes that possible. Perhaps that helps.

Josti

---