I am getting "client error" dozens of times in the last two days. Only three tasks have been successful. I tried resetting the project but it is still not working.
Any advice to fix this would be appreciated. Thanks!

Bruce Downing
Sarasota

seems like you have the same problem as I do.

seems like you have the same problem as I do.

I am also running SETI and Einstein, no problems with those.

Me too. Just only Rosetta.

Me too. Just only Rosetta.

I have stopped new Rosetta tasks.

I have also started to receive Client Error/Compute Error since around Oct-30 or Oct-31.
Common to these errors are that the CPU time is always very low, something like 0.06 seconds.
The application is always "Rosetta Mini with new score terms" and the WU name is something like "1fna__BOINC_CASP8_ABRELAX_SPLIT_SPLIT_IGNORE_THE_REST-S25-9-S3-3--1fna_-_4662_210"

Since these erroneous WU's don't consume CPU at all, the break at the very beginning, they shouldn't harm at all I guess?

---

I have also started to receive Client Error/Compute Error since around Oct-30 or Oct-31.
Common to these errors are that the CPU time is always very low, something like 0.06 seconds.
The application is always "Rosetta Mini with new score terms" and the WU name is something like "1fna__BOINC_CASP8_ABRELAX_SPLIT_SPLIT_IGNORE_THE_REST-S25-9-S3-3--1fna_-_4662_210"

Since these erroneous WU's don't consume CPU at all, the break at the very beginning, they shouldn't harm at all I guess?

Same here exactly. I was worried that it is my computer, but now I don't think so. As to harm, I guess not, but I sure would like this resolved.

Bruce in Sarasota, Florida

I have also started to receive Client Error/Compute Error since around Oct-30 or Oct-31.
Common to these errors are that the CPU time is always very low, something like 0.06 seconds.
The application is always "Rosetta Mini with new score terms" and the WU name is something like "1fna__BOINC_CASP8_ABRELAX_SPLIT_SPLIT_IGNORE_THE_REST-S25-9-S3-3--1fna_-_4662_210"

Since these erroneous WU's don't consume CPU at all, the break at the very beginning, they shouldn't harm at all I guess?

I have run 7 new tasks, all were normal. Will come back here if any more problems.
Bruce.

2 Rosetta Mini 1.40 WUs failed as "Computation error."

h010__BOINC_ABRELAX_RANGE_yebf_IGNORE_THE_REST-S25-5-S3-7--h010_-_4675_452_0
h011__BOINC_ABRELAX_RANGE_yebf_IGNORE_THE_REST-S25-10-S3-5--h011_-_4675_475_0

The first WU ran for 00:53:51 and the second WU ran for 00:19:45 before aborting.

---

What is the resolution to this COMPUTE ERROR. Over half of my WU are ending with this message (and, consequently, no credits but gobs of my CPU being ripped.

It's obvious others are experiencing it too so why no fix/work-around.

If there's not something constructive available shortly, I will discontinue my contributions to rosetta in favour of another project that can better use my resources.

Thanks,

see also
Thread: download error MD5 check failed

I got these messages, some of my wingman end with compute errors.

I've set my computers to "no new work" till any update from Project administrator

---

Matthias

After getting the Compute Errors, I now get:
12/3/2008 9:45:26 AM|rosetta@home|Scheduler request succeeded: got 0 new tasks
12/3/2008 9:45:26 AM|rosetta@home|Message from server: Server error: can't attach shared memory
Sure looks like something broke.

---

Please review the Number Crunching board. Several threads there already discuss the shared memory issue.

---

Rosetta Moderator: Mod.Sense

WUs named like cs_vanilla_abrelax_... finish with error 'Output file ... absent'
and Windows shows message that Rosetta mini 1.4 causes an error and will be terminated (or something like this).

WUs named like cs_vanilla_abrelax_... finish with error 'Output file ... absent'
and Windows shows message that Rosetta mini 1.4 causes an error and will be terminated (or something like this).

Which complete version number of minirosetta? I've had workunits from both version 1.40 and version 1.45 lately. There's already separate threads for reporting problems in each of them - rather long for 1.40, and rather short for the newer 1.45. You might get a more useful response if you report the problem in the thread specific to that version, although similar problems have been reported in the thread for 1.40 before, mostly with more complete error reports.

WUs named like cs_vanilla_abrelax_... finish with error 'Output file ... absent'
and Windows shows message that Rosetta mini 1.4 causes an error and will be terminated (or something like this).

Which complete version number of minirosetta? I've had workunits from both version 1.40 and version 1.45 lately. There's already separate threads for reporting problems in each of them - rather long for 1.40, and rather short for the newer 1.45. You might get a more useful response if you report the problem in the thread specific to that version, although similar problems have been reported in the thread for 1.40 before, mostly with more complete error reports.

When i get this problem i was already runing version 1.45 but in the message generated by Windows was 1.4

Again same problem with WU named "cs_valilla_abrelax_...".
Application: Rosetta Mini 1.45
In Windows message appear minirosetta_1.4.exe instead of minirosetta_1.45_windows_intelx86.exe

With other WUs no Windows messages was displayed.

Again same problem with WU named "cs_valilla_abrelax_...".
Application: Rosetta Mini 1.45
In Windows message appear minirosetta_1.4.exe instead of minirosetta_1.45_windows_intelx86.exe

With other WUs no Windows messages was displayed.

There have been a number of problem reports for the workunits with names beginning with cs_vanilla over in the minirosetta 1.45 thread. For now, expect a much higher percentage of those workunits to fail than workunits with other names.