I'll take the opportunity to delete all the lockfiles again, as previously advised, and reset the project. Seems to me like the perfect opportunity.

Make sure you upload your results before you reset, or you will lose everything.

Good point. I realised that just in time. I've set Boinc Manager not to get new WUs just yet and waiting for the upload to go through successfully before I reset.

Please send email to my account when an alternate to mini 1.40 test is available. Thanks in Advance.

I second that!

i'll stay as my error rate is low, but i have to agree, the team needs to take and revamp all these tasks with stupid errors, such as Nan's and recovering checkpoints and lock file errors along with all the other stupid problems that could be taken care of if they were tested on Ralph properly before being released to here.

the idea of Rosetta is research of proteins and not research of bad programing.

Very well put.

So why do the project developers say nothing about this here?

I suspect it's because they're too busy reading all the problem reports.

Do you think it would be enough to move just the workunits using the new features introduced in 1.39 and 1.40 back to Ralph, so they'd still have something for the rest of the participants to do until they fix the new problems?

Please send email to my account when an alternate to mini 1.40 test is available. Thanks in Advance.

I second that!

i'll stay as my error rate is low, but i have to agree, the team needs to take and revamp all these tasks with stupid errors, such as Nan's and recovering checkpoints and lock file errors along with all the other stupid problems that could be taken care of if they were tested on Ralph properly before being released to here.

the idea of Rosetta is research of proteins and not research of bad programing.

Please send email to my account when an alternate to mini 1.40 test is available. Thanks in Advance.

read this. It was posted in another new thread by peter leman.

within that wiki article is the link to "lockfile" and it mentions: Where this becomes problematical is when a process dies (crashes) and the Lock File is never closed. This us usually corrected with a reboot action, but not always.

If you are going to delete it then you can find the lockfile that is actually called boinc_lockfile and it is in boinc folder then subfolder projects and then subfolder slots.

see if the reboot of boinc helps and if not then follow the directions in the wiki article.

Thank you!

It worked out, booting the computer. The 'slots' disappeared and, with them, the lock file. Now to see if the error wont happen again after I resume Rosetta's tasks.

glad to help, but also thanks to peter leman for creating the original thread with the lockfile topic.

read this. It was posted in another new thread by peter leman.

within that wiki article is the link to "lockfile" and it mentions: Where this becomes problematical is when a process dies (crashes) and the Lock File is never closed. This us usually corrected with a reboot action, but not always.

If you are going to delete it then you can find the lockfile that is actually called boinc_lockfile and it is in boinc folder then subfolder projects and then subfolder slots.

see if the reboot of boinc helps and if not then follow the directions in the wiki article.

nice, wheres the link to that specific task?

I generally need to abort about 30 or more Rosetta Mini WUs to get one Rosetta Beta WU. . About once a week, I allow one Rosetta Mini WU to run, to see if the problem is fixed yet -- which hasn't happened yet.

Well, well, it seems I'm not alone here.

No, you're not. But no one has yet admitted this is a problem,
so I too will be forced to abort until it is settled.

On my AMD Athlon 64 X2 Dual Core with Windows XP Pro SP3, and with 2 GB RAM and 100 GB available HD, no Rosetta Mini WU of any version has ever completed successrfully since Rosetta Mini came into existence. . They fail with a compute error or sometimes lockup my computer after wasting time that could be applied to WUs that can complete OK.

So I abort all Rosetta Mini WUs until I finally get a Rosetta Beta WU. . This is a lot of work, since I generally need to abort about 30 or more Rosetta Mini WUs to get one Rosetta Beta WU. . About once a week, I allow one Rosetta Mini WU to run, to see if the problem is fixed yet -- which hasn't happened yet.

Other project sites such as World Community Grid and PrimeGrid allow me to choose which applications my computer will run. . Why can't Rosetta provide this feature, too? . I would like to run the Rosetta Beta WUs, but if I get tired of aborting hundreds of Rosetta Mini WUs, I may feel forced to abandon Rosetta altogether.

What about this "refusal to stop" issue ?

19/11/2008 02:40:10|rosetta@home|Starting foldcst_minimalist_core3_homo_bench_foldcst_cheat_chunk_t312__olange_IGNORE_THE_REST_1XV2A_5_4741_186_0
19/11/2008 02:40:14|rosetta@home|Starting task foldcst_minimalist_core3_homo_bench_foldcst_cheat_chunk_t312__olange_IGNORE_THE_REST_1XV2A_5_4741_186_0 using minirosetta version 140
19/11/2008 02:56:51|rosetta@home|Restarting task foldcst_minimalist_core3_homo_bench_foldcst_cheat_chunk_t312__olange_IGNORE_THE_REST_1XV2A_5_4741_186_0 using minirosetta version 140
19/11/2008 02:57:32|rosetta@home|Task foldcst_minimalist_core3_homo_bench_foldcst_cheat_chunk_t312__olange_IGNORE_THE_REST_1XV2A_5_4741_186_0 exited with zero status but no 'finished' file
19/11/2008 02:57:32|rosetta@home|If this happens repeatedly you may need to reset the project.
.
.
.